AsyncAPI channel · Deepgram · Deepgram Voice Agent Events

`/v1/agent/converse`

WebSocket channel for the Voice Agent API. After connecting, the client sends a Settings message to configure the agent's listen (STT), think (LLM), and speak (TTS) providers, followed by binary audio frames. The server responds with agent audio, transcription events, and lifecycle messages.

Open source AsyncAPI → All Deepgram channels Deepgram provider profile

Provider: Deepgram AsyncAPI: v2.6.0 Spec: Deepgram Voice Agent Events Operations: 2 Messages: 16

Channel address

/v1/agent/converse

Operations

publish

sendAgentInput

Send input to the voice agent

receiveAgentOutput

Receive output from the voice agent

Messages

Settings

Agent session configuration

Content-Type: application/json

AudioInput

User audio data

Content-Type: application/octet-stream

UpdateInstructions

Update agent instructions mid-session

Content-Type: application/json

UpdateSpeak

Update TTS settings mid-session

Content-Type: application/json

InjectAgentMessage

Inject a message into the agent conversation

Content-Type: application/json

FunctionCallResponse

Response to a function call request

Content-Type: application/json

AgentKeepAlive

Keep the agent connection alive

Content-Type: application/json

AgentAudioData

Agent speech audio

Content-Type: application/octet-stream

UserStartedSpeaking

User speech activity detected

Content-Type: application/json

AgentStartedSpeaking

Agent has begun speaking

Content-Type: application/json

AgentThinking

Agent is processing a response

Content-Type: application/json

ConversationText

Transcript of conversation

Content-Type: application/json

FunctionCallRequest

Agent requests a function call

Content-Type: application/json

FunctionCalling

Agent is invoking a function

Content-Type: application/json

Welcome

Connection established

Content-Type: application/json

AgentError

Agent error event

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 Naftiko capability, Agent Skill, and MCP server surfaces of the same providers.