cohere
Generates a text response to a user message and streams it down, token by token.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles cohere the way a machine reads it — 80 machine-readable artifacts across 9 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — cohere scores 48.5/100 (developing), with a separate agent-readiness read of 54/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile cohere
Each block below is one kind of artifact we hold for cohere. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 9
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Cohere Chat API
The Cohere Chat API enables developers to integrate large language model text generation capabilities into their applications through a conversational interface. It supports mul...
Cohere Embed API
The Cohere Embed API generates vector embeddings from text and images, enabling semantic search, clustering, and classification use cases. It supports multilingual content and c...
Cohere Rerank API
The Cohere Rerank API takes a query and a list of text documents and returns them ordered by relevance with assigned relevance scores. It is commonly used as a second-stage rank...
Cohere Classify API
The Cohere Classify API performs text classification by assigning labels to input text based on provided examples. It can be used for sentiment analysis, content moderation, top...
Cohere Embed Jobs API
The Cohere Embed Jobs API allows developers to create and manage batch embedding jobs for processing large volumes of text data asynchronously. Rather than embedding texts one a...
Cohere Datasets API
The Cohere Datasets API provides endpoints for uploading, managing, and retrieving datasets used with other Cohere services such as fine-tuning and embed jobs. Developers can cr...
Cohere Models API
The Cohere Models API allows developers to list and retrieve information about available Cohere models, including the Command, Embed, and Rerank model families. It provides deta...
Cohere Tokenize API
The Cohere Tokenize API splits input text into tokens using the tokenizer associated with a specified model. It returns both the token strings and their corresponding token IDs....
Cohere Detokenize API
The Cohere Detokenize API converts a sequence of token IDs back into their corresponding text string using the tokenizer for a specified model. It is the inverse operation of th...
Scroll within the panel for all 9 ·
Open Collections 9
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Cohere Chat API
OPEN COLLECTIONCohere Classify API
OPEN COLLECTIONCohere Datasets API
OPEN COLLECTIONCohere Detokenize API
OPEN COLLECTIONCohere Embed API
OPEN COLLECTIONCohere Embed Jobs API
OPEN COLLECTIONCohere Models API
OPEN COLLECTIONCohere Rerank API
OPEN COLLECTIONCohere Tokenize API
OPEN COLLECTIONScroll within the panel for all 9 ·
GraphQL 1
Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.
GraphQL schemas published by this provider.
Cohere GraphQL Schema
This document describes a conceptual GraphQL schema for the Cohere AI API, covering the full surface of Cohere's language model, embedding, reranking, classification, tokenizati...
GRAPHQLPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Cohere Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Cohere Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Cohere Finops
FINOPSFeatures 16
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Scroll within the panel for all 16 ·
Event Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Cohere Streaming API
AsyncAPI definition for Cohere's HTTP+SSE streaming endpoints. Cohere's streaming responses are NOT delivered via WebSockets. They are delivered as Server-Sent Events (SSE) over...
ASYNCAPISemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Cohere Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
cohere API Rules
SPECTRALcohere API Rules
SPECTRALJSON Schema 34
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Cohere Chat Message
JSON SCHEMAChatRequest
JSON SCHEMAChatResponse
JSON SCHEMAClassification
JSON SCHEMAClassifyExample
JSON SCHEMAClassifyRequest
JSON SCHEMAClassifyResponse
JSON SCHEMACreateDatasetRequest
JSON SCHEMACreateDatasetResponse
JSON SCHEMACreateEmbedJobRequest
JSON SCHEMACreateEmbedJobResponse
JSON SCHEMACohere Dataset
JSON SCHEMADatasetUsage
JSON SCHEMADetokenizeRequest
JSON SCHEMADetokenizeResponse
JSON SCHEMACohere Embedding
JSON SCHEMAEmbedJob
JSON SCHEMAEmbedRequest
JSON SCHEMAEmbedResponse
JSON SCHEMAError
JSON SCHEMAListDatasetsResponse
JSON SCHEMAListEmbedJobsResponse
JSON SCHEMAListModelsResponse
JSON SCHEMAMessage
JSON SCHEMACohere Model
JSON SCHEMARerankRequest
JSON SCHEMARerankResponse
JSON SCHEMARerankResult
JSON SCHEMAStreamEvent
JSON SCHEMATokenizeRequest
JSON SCHEMATokenizeResponse
JSON SCHEMATool
JSON SCHEMAToolCall
JSON SCHEMAUsage
JSON SCHEMAScroll within the panel for all 34 ·
JSON Structure 1
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Cohere Structure
JSON STRUCTURESecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for cohere — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 4
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/cohere · machine-readable index on apis.io