Provision record
Replicate · Replicate Acceptable Use Policy · View original document ↗

Flux API Requires Separate Black Forest Labs Agreement

High severity Explicit document language Common · 109 of 352 platforms
Stay ahead of the changes
Track Replicate and get the diff the day its terms change.
Share 𝕏 Share in Share 🔒 PDF

This analysis describes what Replicate's agreement states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability and practical outcomes may vary by jurisdiction, enforcement context, and individual circumstances. Read our methodology

How other platforms handle this

Runway Medium

Your Applications made available to end users must prominently display "Powered by Runway" and link to runwayml.com on applicable user interfaces and in accordance with our Branding Guidelines.

DeepL Medium

DeepL shall inform Customer of the proposed changes with two months' prior notice in writing (e-mail sufficient). Furthermore, DeepL shall grant Customer a reasonable period of at least two (2) months to confirm whether or not Customer accepts the proposed changes.

Ramp Medium

Company agrees that use of a developer account, including to access APIs to create automations or integrate the Services with Third-Party Services, is governed by the API Agreement.

See all platforms with this clause type →
▸ View Original Clause Language DOCUMENT RECORD
"
your usage is governed by the then-current version of the Flux Model API Agreement... By using and purchasing access to the Flux API, you hereby agree to the terms of such Flux Model API Agreement with respect to such use.

Excerpt from Replicate's Acceptable Use Policy

Applicable regulations

CFAA
United States Federal

Provision details

Document information
Document
Replicate Acceptable Use Policy
Entity
Replicate
Document last updated
May 12, 2026
Tracking information
First tracked
July 12, 2026
Last verified
July 12, 2026
Record ID
CA-P-070794
Document ID
CA-D-00841
Evidence Provenance
Source URL
Wayback Machine
Content hash (SHA-256)
6e158ac59e25bd27831c685c36128d67672522379cd78ffb80e77cda5b85e968
Analysis generated
July 12, 2026 16:39 UTC
Methodology
Evidence
✓ Snapshot stored   ✓ Hash verified
Citation Record
Entity: Replicate
Document: Replicate Acceptable Use Policy
Record ID: CA-P-070794
Captured: 2026-07-12 16:39:46 UTC
SHA-256: 6e158ac59e25bd27…
URL: https://conductatlas.com/platform/replicate/replicate-acceptable-use-policy/provision/CA-P-070794/flux-api-requires-separate-black-forest-labs-agreement/
Accessed: Aug. 2, 2026
Permanent archival reference. Stable identifier suitable for legal filings, compliance documentation, and research citation.
Classification
Severity
High
Categories

Other risks in this policy

Get the research letter

Companies change their terms quietly. We read every version and catch what actually changed. One email a week on the changes that matter and what they mean.

Frequently Asked Questions

What does Replicate's Flux API Requires Separate Black Forest Labs Agreement clause do?

The clause states: “your usage is governed by the then-current version of the Flux Model API Agreement... By using and purchasing access to the Flux API, you hereby agree to the terms of such Flux Model API Agreement with respect to such use.”

How many platforms have this type of clause?

ConductAtlas has identified this type of provision across 109 platforms. See the full comparison.

Is ConductAtlas affiliated with Replicate?

No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Replicate.