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 Naftiko capability, Agent Skill, and MCP server surfaces of the same providers.