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 API Growth and DeepL API Developer are designed to process at least 600 characters per minute and per Customer; exceeding use may be limited, and Customers may encounter a 429 "Too Many Requests" error message.
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.
Your Applications made available to end users must prominently display "Powered by Runway" and link to runwayml.com on applicable user interfaces and in accordance with our Branding Guidelines.
"the number of calls Customer or Customer Application makes to the Cohere API during any given period may be limited, at Cohere's sole discretion, based on various factors...Excerpt from Cohere's SaaS Agreement
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.
The clause states: “the number of calls Customer or Customer Application makes to the Cohere API during any given period may be limited, at Cohere's sole discretion, based on various factors...”
ConductAtlas has identified this type of provision across 109 platforms. See the full comparison.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Cohere.