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 by conditioning authorization on prior disclosure and approval of the use case. This allows the provider to evaluate proposed applications against the stated prohibited categories before granting service access.
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 submit use case descriptions for review and receive explicit approval before they can utilize the Cohere API. Failure to obtain this approval prior to access means the terms do not authorize API use for that application.
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...
You must not use Mailchimp to send to role-based email addresses (such as info@, sales@, or support@), to send to addresses harvested from websites or other online sources without permission, or to email addresses obtained through dictionary attacks or automated address generation.
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.
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 for API access by conditioning authorization on prior disclosure and approval of the use case. This allows the provider to evaluate proposed applications against the stated prohibited categories before granting service access.
Developers must submit use case descriptions for review and receive explicit approval before they can utilize the Cohere API. Failure to obtain this approval prior to access means the terms do not authorize API use for that application.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Cohere.