One endpoint instead of a voice cascade
A traditional voice agent makes you assemble and operate this:configure frame, then stream audio:
Connect
There is no agent resource you must create before opening a session. Authorize the WebSocket with an API key, then send the agent configuration:0x01 || audio_bytes. Server audio uses
0x01; plain UTF-8 caller-transcript deltas use 0x02; control JSON uses
0x03. Every server JSON body is keyed on event; the transcript body is not
JSON. See the browser tutorial for capture, playback, and frame handling.
Choose how to build
Choose your path
API primitives, console Agent, or a framework adapter.
Launch an Agent
Create, test, and put a Call Now button on your site without a token broker.
Create agents via API
Store a profile, bind knowledge and tools, open Omni with session_label.
Read the wire protocol
Binary audio framing, lifecycle events, tools, and session controls.