OpenAI-compatible Chat Completions endpoint. When the request body
includes `stream: true`, the server upgrades the response to SSE and
emits a sequence of `chat.completion.chunk` events terminated by a
`data: [DONE]` sentinel (OpenAI-compatible behavior). Search results,
citations, and the final `usage` object are documented to arrive in
the final chunk(s) of the stream, not progressively.
One `data:` SSE event whose payload is a JSON object with
`object: chat.completion.chunk`. The stream ends with a terminal
`data: [DONE]` line.
Content-Type: application/json
StreamDoneSentinel
OpenAI-compatible terminal SSE line `data: [DONE]` marking end of 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.
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.