AsyncAPI channel · perplexity · Perplexity Streaming API (HTTP + Server-Sent Events)

/chat/completions

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.

Open source AsyncAPI → All perplexity channels perplexity provider profile
Provider: perplexity AsyncAPI: v2.6.0 Spec: Perplexity Streaming API (HTTP + Server-Sent Events) Operations: 2 Messages: 3

Channel address

/chat/completions

Operations

publish
openChatCompletionsStream
Open an SSE stream for chat completions
receiveChatCompletionChunks
Receive SSE chat completion chunks

Messages

ChatCompletionStreamRequest
Chat Completions request with stream=true
Content-Type: application/json
ChatCompletionChunk
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.

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.