AsyncAPI channel · Mistral AI · Mistral AI Streaming Completions API

/chat/completions

Streaming chat completions. Client POSTs a ChatCompletionRequest with `stream: true`. The server responds with `Content-Type: text/event-stream` and emits a sequence of `chat.completion.chunk` events, terminated by a `data: [DONE]` line. When `stream_options.include_usage` is true, the final chunk before `[DONE]` carries a populated `usage` object and an empty `choices` array.

Open source AsyncAPI → All Mistral AI channels Mistral AI provider profile
Provider: Mistral AI AsyncAPI: v2.6.0 Spec: Mistral AI Streaming Completions API Operations: 1 Messages: 3

Channel address

/chat/completions

Operations

receiveChatCompletionStream
Receive streamed chat completion chunks

Messages

ChatCompletionChunk
One streamed delta from POST /chat/completions.
Content-Type: application/json
ChatCompletionUsageChunk
Final usage chunk emitted when stream_options.include_usage is true.
Content-Type: application/json
StreamDone
Sentinel marking end of SSE stream.
Content-Type: text/plain

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.