SignalStack
Back to feed

Soniox STT v6 Adds Agent Text Input and Echo Filtering for Voice Agents

Read original

AI summary

Soniox STT v6 improves voice agent performance by filtering out the agent's own voice and recognizing short caller replies, enhancing accuracy across 60+ languages.

AI-generated summary. Check the original reporting for context and accuracy.

Source excerpt

This is the available feed excerpt, which may be shortened or in the publisher’s original language.

Soniox has released Soniox STT v6, the latest generation of its speech-to-text API. Soniox STT v6 is a speech-to-text model that reads what a voice agent says while hearing the caller. It uses that text to recognize short replies and to drop the agent’s own voice. The release ships as stt-rt-v6 for streaming and stt-async-v6 for files, across 60+ languages. TL;DR Size: Soniox STT v6 is a proprietary hosted model, no parameter count published. Runs on: Soniox cloud API only (WebSocket streaming and async REST). No self-hosted or on-device option disclosed. Performance: Soniox calls it “significantly” more accurate than v5, but publishes no v6 numbers yet. Best: Price. $0.12/hour streaming and $0.10/hour async, with diarization and language ID bundled. Worst: Zero independent v6 results. Its v5 predecessor scored 1.34% semantic WER on Pipecat, behind v4’s 1.25%. What problem does Soniox STT v6 solve? In a cascaded voice agent, STT usually hears only the caller. It never sees the question being answered. Short answers suffer most. In Soniox’s docs, “River Roast” becomes “River Road” and “a tow” becomes “a tour.” The second problem is echo. Agent audio leaks back through speakerphones and laptops, gets transcribed as user speech, and the agent interrupts itself. How does agent text input work? You enable it with one flag in the start request: "enable_agent_text_input": true. It is only available on stt-rt-v6, not the async model. While the agent speaks, you stream its words on the same WebSocket as the caller’s audio. Each message is a small JSON frame: {"type": "agent_text", "text": "...", "end_of_segment": true}. Timing matters. Messages carry no timestamps, so the model places text where it arrives in the audio stream. Soniox recommends sending each piece 500 ms to 1 second before playback, paced by TTS timestamps. On barge-in, you flush what was already played, send end_of_segment: true, and drop the unplayed rest. The agent’s text never appears in th

About priority

An automated sorting aid based on source trust, keywords, and entities, on a scale of 1–12. High: 9–12; medium: 6–8; low: 1–5. It does not measure urgency, verify reporting, or indicate editorial endorsement.

More in this topic