Skip to main content
The exact strings the config takes, tested by us end to end. Newer model ids that are not listed may exist and work — the assistant config doesn’t necessarily block them, as we pass it to the provider APIs directly — but we update this page only after testing a model ourselves on real calls. An unlisted string that doesn’t work fails at dial time, with a caller on the line. Per-provider knobs, defaults, and BYOK keys are on the config tabs of Create an assistant. What we’d pick: Recommended stack.

​
LLM

gemini-2.5-flash is the fastest. gemini-3.5-flash is the good balance of intelligence and speed.

​
STT

​
Soniox turn end

Soniox sends the final transcript when it decides the caller has stopped. The agent can’t reply before that, so this wait is in every turn. Three keys on stt.default tune it:
Omit a key for the Soniox default. A value out of range is ignored, and the call runs on the default. On the default settings, the final transcript comes 0.6 to 2 s after the caller stops. maxEndpointDelayMs caps that wait on its own. On our Urdu test calls, stt-rt-v5 with endpointLatencyAdjustmentLevel set was a lot faster to end turns. The risk of a higher level is a turn that ends at a pause, mid-sentence. We saw no cut-offs, but our test answers were short. Test with your own callers before you go above 1.

​
TTS