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 whereby Cohere retains authority to review and approve intended use cases prior to granting access, and places documentation obligations on developers to identify and record potential harms from their applications.
Interpretive note: The policy does not specify the required depth, format, or update cadence for harm documentation, creating uncertainty about what level of documentation constitutes compliance.
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 cannot access the Cohere API without first submitting use case information for approval, and the terms require developers to consult model cards and prepare harm documentation as a condition of use authorization.
Cross-platform context
See how other platforms handle Model Card and Harm Documentation Obligation and similar clauses.
Compare across platforms →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, understanding the models and limitations. They should refer to model cards for detailed information and document potential harms of their application.— 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 whereby Cohere retains authority to review and approve intended use cases prior to granting access, and places documentation obligations on developers to identify and record potential harms from their applications.
Developers cannot access the Cohere API without first submitting use case information for approval, and the terms require developers to consult model cards and prepare harm documentation as a condition of use authorization.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Cohere.