Provision record
Cohere · Cohere SaaS Agreement · View original document ↗

Customer must not block Cohere API usage monitoring

Medium severity Explicit document language Common · 109 of 352 platforms
Stay ahead of the changes
Track Cohere and get the diff the day its terms change.
Share 𝕏 Share in Share 🔒 PDF

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

How other platforms handle this

DeepL Medium

If DeepL provides a new version of the API, Customer shall implement the new version of the API into Customer's Application within such reasonable period of time specified by DeepL from the announcement of the new API version.

Amazon Associates Medium

You will not exceed...any limit on calls per second set forth in any Specifications...and you will not send files to or from Creators API or PA API that are greater than 40KB without our prior written approval.

OpenAI Medium

This includes the right to use OpenAI's API to integrate the Services into Customer Applications and to make Customer Applications available to End Users.

See all platforms with this clause type →
▸ View Original Clause Language DOCUMENT RECORD
"
Customer acknowledges and agrees that Cohere may monitor Customer's use of the Cohere API and that Customer will not block or otherwise interfere with Cohere's monitoring.

Excerpt from Cohere's SaaS Agreement

Applicable regulations

CFAA
United States Federal

Provision details

Document information
Document
Cohere SaaS Agreement
Entity
Cohere
Document last updated
May 11, 2026
Tracking information
First tracked
May 11, 2026
Last verified
May 12, 2026
Record ID
CA-P-070022
Document ID
CA-D-00768
Evidence Provenance
Source URL
Wayback Machine
Content hash (SHA-256)
cf319db4fb54c8ae019dfe7b3515b554f5c486a7dd84bfbb5ce64abed79b18c3
Analysis generated
May 11, 2026 11:52 UTC
Methodology
Evidence
✓ Snapshot stored   ✓ Hash verified
Citation Record
Entity: Cohere
Document: Cohere SaaS Agreement
Record ID: CA-P-070022
Captured: 2026-05-11 11:52:52 UTC
SHA-256: cf319db4fb54c8ae…
URL: https://conductatlas.com/platform/cohere/cohere-saas-agreement/provision/CA-P-070022/customer-must-not-block-cohere-api-usage-monitoring/
Accessed: Aug. 2, 2026
Permanent archival reference. Stable identifier suitable for legal filings, compliance documentation, and research citation.
Classification
Severity
Medium
Categories

Other risks in this policy

Get the research letter

Companies change their terms quietly. We read every version and catch what actually changed. One email a week on the changes that matter and what they mean.

Frequently Asked Questions

What does Cohere's Customer must not block Cohere API usage monitoring clause do?

The clause states: “Customer acknowledges and agrees that Cohere may monitor Customer's use of the Cohere API and that Customer will not block or otherwise interfere with Cohere's monitoring.”

How many platforms have this type of clause?

ConductAtlas has identified this type of provision across 109 platforms. See the full comparison.

Is ConductAtlas affiliated with Cohere?

No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Cohere.