This analysis describes what Meta'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
Meta added Exhibit C, “Hosted Platform Access”, to its Meta Model API Terms of Service, last updated October 2, 2026. It applies when the Meta Materials are used through a third-party cloud platform authorized by Meta. The platform provider may disclose “Platform Account Data” to Meta, which can include the customer's organization name and domain, account and billing identifiers, location, subscription details, usage volumes, and revenue, fee and billing metrics; Meta may use it to operate and secure the service and to administer its arrangements with platform providers. Meta states that it does not receive or process customer content, including inputs and outputs, accessed through a hosted platform, and does not use that content to train or improve its models. The terms' sections on accounts and API keys, discounted services, and fees and taxes do not apply to hosted-platform access, where the platform provider bills fees under its own agreement.
View change record →The updated terms establish that the Llama API Services are intended for commercial use, except where Meta expressly permits personal or consumer use through a subscription. Developers and integrators can no longer share API keys with third parties or resell access through model aggregators, API gateways, or proxies without Meta's prior written permission. The terms now explicitly govern a new Coding Harness Subscription offering, which is subject to separate Meta Subscription Terms but uses API keys restricted to use only within the coding harness and subject to usage limits and billing controls.
View change record →The updated terms expand what developers must warrant they have rights to use (now including code, libraries, and databases accessed through integrations) and introduce new compliance obligations around AI-generated content labeling and disclosure. Developers are now explicitly responsible for meeting applicable legal requirements for labeling, disclosure, provenance marking, or classification of AI-generated or AI-assisted content in their Integrated Products. The terms also clarify that outputs may include third-party licensed materials, which developers must account for in their own products.
View change record →How other platforms handle this
xAI shall have received from Customer: (a) prompt written notice of such claim; (b) the exclusive right to control and direct the investigation, defense, or settlement...
the indemnified party will promptly notify the indemnifying party in writing of any threatened or actual claim or suit; (b) the indemnifying party will have sole control of the defense or settlement...
(viii) Customer's use of the Product after PlanetScale notifies Customer to discontinue running it due to an Infringement Claim.
"you (a) give Meta prompt written notice when you become aware of the claim, including the nature of the claim, the relief sought and the amount of damages sought...Excerpt from Meta's Llama API Terms of Service
Get the weekly coverage letter
Companies change their terms without announcing it. We capture governance documents, compare each new version with the last, and publish what changed, with the source text behind it. One email a week on what we found and what we could not reach.
The clause states: “you (a) give Meta prompt written notice when you become aware of the claim, including the nature of the claim, the relief sought and the amount of damages sought...”
ConductAtlas has identified this type of provision across 225 platforms. See the full comparison.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Meta.