Best STT API for voice agents? I’d test latency before accuracy
Summary
The author argues that for live voice agents, STT latency and real-time behavior are more critical than raw transcription accuracy, and proposes a different evaluation scorecard.
Similar Articles
My voice agent sounded smart until one phone number was transcribed wrong.
The article argues that voice agent STT should be evaluated on entity accuracy (e.g., phone numbers, dates) rather than general word error rate, because missing critical fields can break workflows. It mentions testing with HubSpot fields and notes Smallest AI Pulse as an interesting tool for capturing workflow-critical entities in real time.
What STT API are you using for production voice agents, and what broke first?
A developer asks what STT APIs people use in production voice agents, comparing Deepgram, AssemblyAI, and Smallest AI Pulse, and highlighting common failure points like endpointing, latency, and barge-in.
Before choosing an STT API, rank which transcript mistakes would actually hurt users.
A guide on evaluating speech-to-text APIs by ranking transcript mistakes based on their actual impact on users, rather than raw accuracy metrics.
Where does voice-agent latency still hide after you fix streaming?
The article discusses hidden sources of latency in voice-agent systems after streaming is enabled and seeks advice on which performance metrics are crucial for real-time agents.
6 months running a production voice agent for service businesses. The latency math is way harder than the demos suggest.
After 6 months running a voice AI agent for service businesses, the author reveals that real-world latency is bimodal (median ~800ms, p95 ~2.4s) and this p95 determines user perception. Issues like VAD misfires, function call degradation with long prompts, and TTS quality matter more than LLM choice, with multilingual support adding significant costs.