Deepgram Flux numerals toggle vs Sume STT digits

Sume STT has no numerals setting and no stream to toggle it on. It is a batch job: you submit an audio_url, and the transcript comes back with whatever formatting the fixed provider settings produce. Deepgram's Flux STT, by contrast, lets you send a Configure message mid-stream to switch to digits for a PIN or phone number.

Deepgram facts are from its changelog; Sume facts are from the API reference. Both read 2026-10-01.

What did Deepgram add to Flux?

The Sep 25, 2026 changelog entry says you can switch Flux STT to digits for a PIN, phone number or order number, then back to words, without reconnecting. You send { "type": "Configure", "numerals": true }. The update applies to transcripts Flux sends after it processes the message, and the numerals query parameter still sets the initial value.

How does Sume STT handle this?

Sume has no equivalent control. The schema states that provider knobs such as diarize and tag_audio_events are fixed server-side, and the only language control is an optional BCP-47 hint. With mode: async the call returns immediately with status_url, so there is no open connection to reconfigure.

How do I find a spoken PIN or phone number in a Sume transcript?

Read words[]. Each entry has word, start and end, so you can locate the digits in the audio. Then normalize in your own code: map spelled-out digits to numerals, or the reverse, after the job completes. Do not assume the transcript will already be in digit form.

What should I do next?

If digits must be correct live, in a call flow, use a streaming service that offers the toggle. For recorded audio, normalize after transcription and verify against word timings. See also real-time speech-to-text on Sume.