Pulse

WER on the English subset of FLEURS across providers in streaming mode. Lower is better.

A note on audio amplitude normalization

Audio amplitude normalization materially changes WER on FLEURS. Most competitors benchmark on raw FLEURS — which has variable, often low amplitude — without normalizing peak audio to −10 dBFS. This makes some models look much better than they actually are. Pulse is stable across all amplitude regimes.

WER on FLEURS in streaming mode, broken down by language family. Lower is better.

WER on FLEURS in pre-recorded mode (full-file upload). Lower is better.

WER across seven Hindi datasets covering read speech, conversational speech, telephony / contact-center audio, and noise-augmented variants. Compared against IndicWhisper, Sarvam Saaras v3, scribe v2, and Deepgram Nova-3. Lower is better.

For the full breakdown including training-data and evaluation-protocol notes, see the Performance page.

A Hugging Face benchmark suite aggregating 9 English speech datasets across diverse domains (audiobooks, parliament, meetings, finance, etc.) to test STT generalization. Lower WER is better.

Evaluated on the open-source Hugging Face ESB datasets. Numbers from internal evaluation.

An open-source robustness benchmark designed to stress-test STT under real-world degraded conditions: clipping, far-field capture, background noise, phone codec compression, reverberation, and accented speech. Lower WER is better. n/a = not supported by that provider.

Evaluated on the open-source WildASR dataset. Numbers from internal evaluation.

WER for the four East Asian languages newly enabled on the streaming endpoint (us-west-2). Three datasets per language covering read speech (FLEURS), conversational/crowdsourced speech (Common Voice 25), and language-specific corpora (JSUT, Zeroth-Korean, MDCC, AISHELL-1). Compared head-to-head against Deepgram Nova-3. Lower WER is better.

Pulse averages 10.91% WER vs Deepgram Nova-3’s 15.50% across the four East Asian languages — Pulse leads on 10 of 12 dataset rows, with the largest gains on Japanese CV-25 and Cantonese CV-25.

These four languages stream from wss://api.us.smallest.ai/waves/v1/stt/live?model=pulse only (US region). See the streaming Asian-language documentation for the region-routing details.

Not a public dataset. The English audio is sliced by perturbation type (Noise, Silence, Telephony 911, Boundary, Disfluency, Long Audios, Repetition, Entity, Accent, Emotion, Speaker Diversity, Speed, Pitch, Volume, Audio Quality) to isolate model weaknesses. Lower WER is better.

Not a public dataset. Hindi audio sliced by perturbation type to isolate model weaknesses. Lower WER is better except for Entity EDR where higher is better (↑).

[*] East Asian languages (zh, yue, ja, ko, multi-asian) are served from the US region only. Connect to wss://api.us.smallest.ai/waves/v1/stt/live instead of wss://api.smallest.ai/... for these.

[**] South Indian languages (ta, te, kn, ml, multi-south-indic) are served from the India region only (wss://api.smallest.ai/...). Requests to wss://api.us.smallest.ai/... are rejected with error code LANGUAGE_NOT_ENABLED_IN_REGION. Contact support to request access.

Pulse runs two independent inference paths. Streaming uses a WebSocket connection and emits partial transcripts in real time — suited for live call transcription, voice assistants, and conversational AI where first-token latency matters. Batch accepts a full audio file over HTTP and returns the complete transcript once processing is done — suited for call recordings, media archives, and any workload where you have the full audio upfront. Features also differ: keyword boosting and sentence-level timestamps are streaming-only, and batch supports a broader set of 26 languages vs 17 on streaming.

Use a specific language code (e.g. hi, es, en) whenever you know the language of the audio. Pulse optimises directly for that language and handles code-switching with English automatically — so hi covers Hindi–English mixed speech without needing an aggregator. Use north_indic or multi-asian only when the source language is genuinely unknown or mixed across several languages. Auto-detection adds a small accuracy overhead compared to an explicit code.

The complete request/response schema, all query parameters, error codes, and WebSocket protocol details are in the API Reference. For step-by-step setup, see the Realtime quickstart for streaming and the Pre-recorded quickstart for batch.

Pulse supports both streaming and batch transcription across 31 languages (17 streaming + 26 pre-recorded). Pulse Pro is English-only and batch-only, but achieves higher accuracy — tied for #2 on the Open ASR Leaderboard at 5.42% average WER vs Pulse’s 6.03% on English FLEURS. Use Pulse for live streaming, multilingual audio, or latency-sensitive workloads. Use Pulse Pro for high-volume English batch transcription where accuracy is the top requirement.

Pulse applies built-in redaction on both streaming and batch surfaces — no preprocessing required. PII redaction masks personal identifiers such as names, phone numbers, email addresses, and SSNs. PCI redaction masks payment card data including card numbers, CVVs, and expiry dates. Both are enabled via query parameters in the API request. Redacted content is replaced with a placeholder in the transcript; the original audio is not retained post-processing.