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 that requires pre-approval of use cases to enforce content policy compliance. This allows the provider to review applications against prohibited categories before API access is granted.
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 explicit approval for their use case before API access is provided. Use cases falling within the prohibited categories cannot proceed without documented approval from Cohere.
How other platforms handle this
You may not automatedly crawl or query the Services for any purpose or by any means (including, without limitation, screen and database scraping, spiders, robots, crawlers and any other automated activity with the purpose of obtaining information from the Services) unless you have received prior exp...
relate to transactions involving (f) the promotion of hate, violence, racial or other forms of intolerance that is discriminatory or the financial exploitation of a crime... (i) involve offering or receiving payments for the purpose of bribery or corruption.
You must not, and must not allow others to: Facilitate illegal or harmful activity through the End User Services; Cause harm to us or others through the End User Services;
Monitoring
Cohere has changed this document before.
Receive same-day alerts, structured change summaries, and monitoring for up to 25 platforms.
"Certain use cases, such as violence, hate speech, fraud, and privacy violations, are strictly prohibited. Developers must outline and get approval for their use case to access the Cohere API.— 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 that requires pre-approval of use cases to enforce content policy compliance. This allows the provider to review applications against prohibited categories before API access is granted.
Developers must obtain explicit approval for their use case before API access is provided. Use cases falling within the prohibited categories cannot proceed without documented approval from Cohere.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Cohere.