Hume AI Introduces the Audio Decision API, Which Answers Questions About Recordings Such as How Many Speakers or Whether a Caller Is Frustrated
Introducing the Hume Audio Decision API. Ask anything: How many speakers? Is anyone laughing? Is the caller frustrated? What used to take 10+ models is now one call. Trained on 10M+ human judgments, so it answers the way human listeners would. Realtime, or across hours of recordings. Request access below.
Context
Replacing a stack of separate audio models with one call could make it much easier for call centers and voice apps to understand what is happening in a conversation.
Hume AI builds voice AI focused on emotion and expression, including its empathic voice interface and text to speech models. Understanding audio usually takes several specialised models, such as speaker counting, emotion detection and event detection. The Audio Decision API is offered through a request access form rather than general release.
Deep dive
Hume AI (@hume_ai) introduced the Hume Audio Decision API on Nov 2 with a launch video showing its team at work.
The post says users can ask anything about audio, giving examples such as how many speakers there are, whether anyone is laughing and whether the caller is frustrated. Hume says what used to take more than 10 models is now one call. It says the system was trained on more than 10 million human judgments, so it answers the way human listeners would, and that it works in realtime or across hours of recordings. Access is by request.
These are Hume's own descriptions. The post does not give accuracy figures, supported languages, latency or pricing, and no independent tests were available at launch.
The pitch is a question answering layer for sound. Instead of wiring up a speaker diarization model, an emotion classifier and an event detector, a developer would describe what they want to know in plain language and get an answer. That fits a broader shift toward general multimodal models that handle many tasks from one prompt, applied here to an area where Hume has long focused on vocal expression.
Likely uses include customer support monitoring, meeting analysis, media review and safety tools that flag distress. Those same uses raise privacy questions, since judging a caller's emotional state from their voice is sensitive, and the post does not say how consent or data retention are handled.
What to expect next
Watch for pricing, documentation and accuracy numbers once access widens, and for early customers in call centers or meeting tools. Comparisons with general audio models from OpenAI and Google will show whether a specialised API keeps an edge. Privacy rules on emotion recognition, especially in Europe, could shape where it can be used. Hume's own voice products may also start using the API to react to how users sound.