Engines

Three ways to run a voice agent

Cascading, speech-to-speech and full duplex. Pick one per agent; telephony, tools and call logs stay the same.

Which engine fits?

Same tools, knowledge and phone numbers on all three. The engine is chosen per agent.

CascadingSTT → LLM → TTS
How it works
Speech-to-text, then a language model, then text-to-speech
Response feel
Fast, with every stage streaming
Control
Highest. Swap STT, model and voice independently
What you can inspect
Transcript, model and voice latency, end to end
Reach for it when
You need a specific voice, a specific model, or strict tool use
Speech-to-speechAudio in, audio out
How it works
One realtime model takes audio in and returns audio
Response feel
Fastest to first word; no transcription hop
Control
Choose the model and its voice; one provider per call
What you can inspect
Transcript and end-to-end latency
Reach for it when
Speed and natural tone matter more than per-stage control
Full duplexListens while it talks
How it works
Keeps listening while it speaks, so callers can overlap and interrupt
Response feel
Most like a person; overlaps, backchannels, barge-in
Control
Tune interruption sensitivity and listening cues
What you can inspect
Full transcript and call detail
Reach for it when
Callers talk over each other and the agent must keep up

Tell us what you are building

Tell us what you are making. We will walk you through the engines, the API, and what it takes to run it in production.