AsyncAPI channel · Agno · Agno AgentOS Run Streaming (HTTP + SSE)

/agents/{agent_id}/runs

Agent run SSE stream. The client opens this channel by issuing `POST /agents/{agent_id}/runs` with a form-encoded body containing `message` and `stream=true` (the default). The server responds with `Content-Type: text/event-stream` and emits a sequence of named SSE events, each carrying a JSON payload in the `data:` field.

Open source AsyncAPI → All Agno channels Agno provider profile
Provider: Agno AsyncAPI: v2.6.0 Spec: Agno AgentOS Run Streaming (HTTP + SSE) Operations: 1 Messages: 4

Channel address

/agents/{agent_id}/runs

Parameters

Operations

streamAgentRunEvents
Subscribe to streamed agent run events (SSE).

Messages

RunStarted
First SSE event emitted when a run begins.
Content-Type: application/json
RunContent
A single SSE event carrying an incremental slice of model output. Many of these are emitted per request, in order.
Content-Type: application/json
RunCompleted
Terminal event marking successful completion of the run.
Content-Type: application/json
RunError
Terminal event emitted if the run fails.
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 Agent Skill and MCP server surfaces of the same providers.