AsyncAPI channel · Kimi (Moonshot AI) · Kimi (Moonshot AI) Streaming Chat Completions API

/v1/chat/completions

Kimi / Moonshot chat completions streaming channel. The client issues a single HTTPS POST to `/v1/chat/completions` with `"stream": true` in the request body. The server replies with a `text/event-stream` body composed of `chat.completion.chunk` events (one JSON object per SSE `data:` line), optionally followed by a final `usage`-only chunk when `stream_options.include_usage` is set, and terminate

Open source AsyncAPI → All Kimi (Moonshot AI) channels Kimi (Moonshot AI) provider profile
Provider: Kimi (Moonshot AI) AsyncAPI: v2.6.0 Spec: Kimi (Moonshot AI) Streaming Chat Completions API Operations: 1 Messages: 3

Channel address

/v1/chat/completions

Operations

publish
receiveChatCompletionStream
Receive chat completion streaming events

Messages

chatCompletionChunk
Incremental chat completion chunk emitted during streaming.
Content-Type: application/json
chatCompletionUsageChunk
Final usage-only chunk emitted immediately before `data: [DONE]` when `stream_options.include_usage` is true. Carries an empty `choices` array and a populated `usage` object.
Content-Type: application/json
chatCompletionDone
Stream termination sentinel. The literal payload is the ASCII string `[DONE]` (not a JSON object) on a single SSE `data:` line. After this line the server closes the response 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.