Echo Turn Detector
Zero Runtime’s turn detector is Echo, a server-hosted model you pass to yourPipeline as the turn_detector. It runs on the Zero Runtime Inference Gateway through the TurnDetector class, so nothing is downloaded to your machine. Authentication requires ZERORUNTIME_AUTH_TOKEN.
Pick echo-small for speed, echo-large for accuracy, or echo-omni for the widest language support.
VAD detects that speech is happening; the turn detector decides when the turn is over.
How It Works
As the user speaks, VAD detects the speech and STT produces a transcript. After each user utterance, the latest transcript is sent to the Inference Gateway, where the selected Echo model classifies the turn into one of four states:echo-omni works the same way, but it also listens to the audio. It reads the speech and the transcript of the same turn together, so it catches what was said and how it was said at once: the trailing pitch, the hesitation, the clipped “mm-hm” that was never a turn at all. It returns one prediction per turn, with a confidence score, in under 80 ms.
Per turn it takes:
Models
All three share the same four states. They differ in what they read and in the speed/accuracy trade-off:Supported Languages
echo-small and echo-large take no language parameter; they work across their 12 languages as they are. Only echo-omni needs one: pass a code from the table below to its language parameter.
Usage
Set your auth token, then constructTurnDetector with the model you want. Only echo-omni takes a language:
Performance
echo-small and echo-large are benchmarked on the TURNS2K dataset against a leading third-party model, called Baseline here. Each sample is labeled Complete (user finished) or Incomplete (user still speaking).
echo-omni is measured separately, on a multilingual set of 25,000+ utterances covering all four states. Accuracy holds across all 27 languages.
Results are measured on the benchmark datasets described above. Performance may vary depending on language, deployment configuration, user behavior, and application requirements.
End-of-Utterance Handling
End-of-Utterance (EOU) handling decides when the pipeline treats the user as finished speaking. InADAPTIVE mode, the wait timeout adjusts based on confidence scores, so the agent waits longer when the user is hesitant and responds faster when intent is clear.
Configure it with EOUConfig in your pipeline options:
How the modes behave
DEFAULT: Fixed wait within your min–max range. For clear utterances you respond near the minimum; for hesitations you wait near the maximum.ADAPTIVE: The wait scales with confidence. Low confidence (hesitation) increases wait; high confidence shortens it, always clamped to your min–max.
What’s Next
VAD and Interruptions
Pair turn detection with Silero VAD.
De-noise
Feed the detector cleaner input audio.
References
- Python
- Node JS
Examples
Cascade Basic
Voice agent with a turn detector configured.