AsyncAPI channel · Cohere · Cohere Streaming API

/v2/chat

Cohere v2 Chat streaming endpoint. The client sends a single HTTPS POST with `"stream": true`; Cohere returns a `text/event-stream` response. Each event on the wire is a typed object discriminated by its `type` field. Documented events: `message-start`, `content-start`, `content-delta`, `content-end`, `tool-plan-delta`, `tool-call-start`, `tool-call-delta`, `tool-call-end`, `citation-start`, `cit

Open source AsyncAPI → All Cohere channels Cohere provider profile
Provider: Cohere AsyncAPI: v2.6.0 Spec: Cohere Streaming API Operations: 1 Messages: 12

Channel address

/v2/chat

Operations

publish
receiveV2ChatStream
Receive v2 Chat streaming events

Messages

messageStart
First event in the stream; carries the generated message id.
Content-Type: application/json
contentStart
Beginning of a content block.
Content-Type: application/json
contentDelta
Incremental text chunk for the current content block.
Content-Type: application/json
contentEnd
End of a content block.
Content-Type: application/json
toolPlanDelta
Incremental token of the model's tool plan text.
Content-Type: application/json
toolCallStart
Start of a tool call (id, type, function name).
Content-Type: application/json
toolCallDelta
Incremental tool-call arguments.
Content-Type: application/json
toolCallEnd
End of a tool call.
Content-Type: application/json
citationStart
Start of a citation; carries spans and sources.
Content-Type: application/json
citationEnd
End of a citation.
Content-Type: application/json
messageEnd
Final event; carries finish_reason and usage.
Content-Type: application/json
debug
Debug event; contains the raw prompt sent to the model.
Content-Type: application/json

About AsyncAPI

The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.

Browse every event-driven channel on the APIs.io network or compare with the broader Agent Skill and MCP server surfaces of the same providers.

Work with this as data

Every channel here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for event channels

4 MCP tools reach this
  • find_channelsBrowse and filter every channel in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This channel 
curl "https://apis.io/api/v1/channels/v2-chat"
All event channels 
curl "https://apis.io/api/v1/channels?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.