This analysis describes what Cohere'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
The provision establishes a gating mechanism for API access that conditions deployment on prior authorization and documentation of application-level risks. This structures Cohere's ability to assess downstream use cases and maintain operational control over prohibited application categories.
The updated policy removes all substantive acceptable use requirements that were previously posted and enforceable. Users no longer have a referenced standard defining what conduct is prohibited on the platform. The removal of enforcement procedures means users cannot verify what conduct may trigger access restriction, suspension, or termination. The elimination of the child safety and sexually explicit content prohibitions from the posted policy creates uncertainty about whether these protections remain in effect through other terms or have been abandoned.
View change record →Developers must obtain approval before API access becomes available and are required to document potential application harms as a condition of use. The terms prohibit development of applications in specified categories regardless of approval status.
How other platforms handle this
To the maximum extent permitted by applicable law, Kit shall not be liable for any indirect, incidental, special, consequential or punitive damages, or any loss of profits or revenues, whether incurred directly or indirectly, or any loss of data, use, goodwill, or other intangible losses, resulting ...
Marketplace Models are not provided by Replicate and Replicate does not control and has no liability for any Marketplace Models, including their security, functionality, operation, availability, or interoperability with the Services or how the Marketplace Models use your Content. Use of any Marketpl...
To the maximum extent permitted by applicable law, Pinterest shall not be liable for any indirect, incidental, special, consequential, or punitive damages, or any loss of profits or revenues, whether incurred directly or indirectly, or any loss of data, use, goodwill, or other intangible losses, res...
Monitoring
Cohere has changed this document before.
Receive same-day alerts, structured change summaries, and monitoring for up to 25 platforms.
"Developers must outline and get approval for their use case to access the Cohere API. They should refer to model cards for detailed information and document potential harms of their application. Certain use cases, such as violence, hate speech, fraud, and privacy violations, are strictly prohibited.— Excerpt from Cohere's Cohere Usage Policy
Compliance Governance Intelligence
Need to monitor specific governance provisions?
Compliance includes provision-level monitoring, governance timelines, regulatory mapping, and audit-ready analysis.
Built from archived source documents, structured governance mappings, and historical version tracking.
The provision establishes a gating mechanism for API access that conditions deployment on prior authorization and documentation of application-level risks. This structures Cohere's ability to assess downstream use cases and maintain operational control over prohibited application categories.
Developers must obtain approval before API access becomes available and are required to document potential application harms as a condition of use. The terms prohibit development of applications in specified categories regardless of approval status.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Cohere.