Latenode

Hume launches Audio Decision API behind waitlist access

Teams can use audio characteristics as structured inputs for routing and analysis instead of relying only on transcripts. Because access is still gated and the outputs reflect estimated human judgment, production use needs validation and conservative thresholds.

Hume launches Audio Decision API behind waitlist access

On November 2, Hume introduced an Audio Decision API that lets developers ask structured questions about speech and other sounds in raw audio, with access currently limited to a waitlist. A playground is also available for testing, according to the Hume announcement.

Rather than stopping at transcription, the API can return decision-style outputs including yes/no answers, multiple-choice selections, rating scales, and timestamped spans. Hume’s use-case documentation shows examples such as counting distinct speakers in a clip and marking where laughter occurs.

For builders, that creates a way to route automations from audio itself instead of text alone. A workflow could branch on speaker count, overlap, laughter, or perceived frustration before any transcript is parsed. Hume also describes these outputs as estimates of human judgment, so teams would still need to validate thresholds on their own recordings before using them for high-stakes actions.

When models and APIs shift keep the workflow running

Connect the models and apps from stories like this in one scenario. If a vendor changes routing, pricing, or availability, you update the workflow — you don't start over.

Start Free

Free forever plan. No credit card required.

What should Latenode build?

Continue without a prompt →