# Hume — Introducing Hume's Audio Decision API: A decision layer for speech and sound

- Company: Hume (hume.ai)
- Announced: 2026-11-02
- Category: api-release
- Coverage: not counted
- Announcement: yes
- Group: announcements
- Source: https://www.hume.ai/blog/introducing-hume-audio-decision-api
- Record: https://forck.live/items/30566-introducing-hume-s-audio-decision-api-a-decision-layer-for-speech-and-sound
- Subject: EVI / Octave

Hume is introducing an Audio Decision API that it describes as a decision layer for speech and sound, aimed at contact centers that score every call against a rubric. Hume says changing what gets scored in a call is a project involving a new rubric, pipeline and evaluations, taking days if not weeks before the first answer. The transcript such scoring runs on captures only the words, according to Hume, missing the pause, the sigh and two people talking over each other. Hume says that information sits in the audio, in call recordings or ignored on real-time calls, and that until now there was no way to extract it in a form you can act on.

## Evidence

Verbatim from https://www.hume.ai/blog/introducing-hume-audio-decision-api:

> Featured Contact centers score every call against a rubric. Changing what gets scored in the call is a project: new rubric, new pipeline, new evaluations, days if not weeks before the first answer. And the transcript this all runs on is only the words. Not the pause, not the sigh, not the two people talking over each other. It misses the reasons a call went wrong. That information is in the audio, sitting in call recordings or actively getting ignored on real time calls. Until now, there has been no way to extract this information in a form you can act on.

---

Record: https://forck.live/items/30566-introducing-hume-s-audio-decision-api-a-decision-layer-for-speech-and-sound
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md