AsyncAPI channel · Corti
· Real-Time Ambient Documentation
/audio-bridge/v2/interactions/{id}/streams?tenant-name={tenant-name}&token={token}
Channel address
/audio-bridge/v2/interactions/{id}/streams?tenant-name={tenant-name}&token={token}
Parameters
id—tenant-name—token—
Operations
send
sendConfiguration
send
sendAudio
send
sendEnd
receive
receiveConfigStatus
receive
receiveTranscript
receive
receiveFacts
receive
receiveEnded
receive
receiveUsage
receive
receiveError
Messages
Stream Configuration Message
Stream Configuration Message
Content-Type:
application/jsonConfiguration Status Message
Configuration Status Message
Content-Type:
application/jsonTranscript
Transcript
Content-Type:
application/jsonFacts
Facts
Content-Type:
application/jsonEnd Stream Message
End Stream Message
Content-Type:
application/jsonStream Ended Message
Stream Ended Message
Content-Type:
application/jsonUsage Information Message
Usage Information Message
Content-Type:
application/jsonError
Error
Content-Type:
application/jsonAudio Data
Audio Data
Content-Type:
application/octet-streamAbout 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.
Work with this as data
Every channel here is available over the APIs.io API and to AI agents over MCP.