/agents/{agent_id}/messages
Agent message SSE stream. The client opens this channel by issuing `POST /agents/{agent_id}/messages` with `Content-Type: application/json` and a JSON body containing `stream_steps: true` (add `stream_tokens: true` to additionally stream partial assistant-message tokens). The server responds with `Content-Type: text/event-stream` and emits an ordered sequence of `data:` lines, each carrying one JS
Channel address
Parameters
agent_id— The ID of the agent, in the format `agent-`.
Operations
Messages
application/jsonapplication/jsonapplication/jsonapplication/jsonapplication/jsonapplication/jsontext/plainAbout 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.