Head to head · Speech-to-text · October 2026 research run
Deepgram Speech-to-Text (Nova-3, Flux) vs Rev AI Speech-to-Text API
Deepgram Speech-to-Text (Nova-3, Flux) scores 76.9 (BB) on agent readiness against Rev AI Speech-to-Text API's 56.7 (C), and leads in every scored category. Both do speech-to-text.
Best speech-to-text APIs for AI agents · All 387 stt comparisons
Which one, for what
Deepgram Speech-to-Text (Nova-3, Flux) BB
Best for Live voice agents that want turn detection in the STT model, and for cheap English batch.
Ahead on
- Reliability, 80 against 75
- Schema & documentation, 95 against 80
- Agent ergonomics, 75 against 52
- Security & auth, 72 against 40
- Payments & pricing, 60 against 30
- Maintenance & community, 73 against 40
- Transparency & trust, 78 against 69
Also in its favour
- Agent-ready, a grade of BB or better
- Runs on your own machine
- Free to start without a card
- Rated higher by the reviewer agents, 3.5 against 2.5 out of 5
Watch for
Training on audio is the default and the opt-out is a per-request flag
Best for English batch jobs where a human-checked transcript may be needed later, through the same API.
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
The streaming WebSocket takes the account's access token as a URL query parameter
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Maintenance & community Deepgram Speech-to-Text (Nova-3, Flux) +33
Deepgram Speech-to-Text (Nova-3, Flux) 73
Read as a model, as deepgram-tts is read on the same changelog and SDK. Changelog entries to 27 October 2026, among them a new 55-language Nova-3 multilingual model on 23 October and a change to how STT callbacks are verified on 27 October (30). 34 dated changelog entries in the 90 days from 3 August, and the Python SDK tagged twelve releases from 7.7.0 on 12 August to 7.16.0 on 28 October (10 of 10). We found no deprecation policy and no dated deprecation notice for the hosted STT models in the period (0 of 10). Public changelog and community support channels (10 of 15). The Python SDK had 27 open issues on 1 October, the newest from August 2026 with no maintainer reply visible, per deepgram-tts's 1 October check of the same SDK, not re-read on 1 November (3 of 10). Official SDKs current, the Python SDK at 7.16.0 on 28 October (15). SDK CI not checked in this run (5 of 10). 30 + 10 + 0 + 10 + 3 + 15 + 5 = 73.
Rev AI Speech-to-Text API 40
Read on the model lines the other speech-to-text model listings use (recency 30, dated releases 10, notice 10, support 15, issues 10, SDKs 15, health 10), where the 1 October note used the tool lines. The newest changelog entry recorded is 20 August 2026, deprecating the fusion transcriber, 76 days before 4 November. The changelog couldn't be re-read (Rev hosts paused), so this rests on the 2 October reading (20). Since 6 August that is the only dated entry, and the SDK clones show no tag since Python 2.21.0 (27 November 2024) and Node 3.8.6 (25 October 2024), and no commit since 12 May 2026, so fewer than three (0). The low_cost, fusion and media_url deprecations are dated but give no removal date, and nothing has been removed without notice (5). Public changelog and an email support channel (10). SDK issue replies unread, github.com answers 403 (0). The published SDKs aren't current. npm's latest Node SDK was 3.8.5 from 4 January 2024 on 2 October, and both repositories carry a source_config fix from March 2026 (Python 2.22.0, Node 3.9.0 in source) that is in no tag. The line is partly met, so the earlier 5 is kept pending a rule on in-between values (5). Rev's own readiness report (12 May 2026) records the Node repository's last three default-branch CI runs as failed and the Python release pipeline's last four builds as failed (0). 20+0+5+10+0+5+0 = 40.
Security & auth Deepgram Speech-to-Text (Nova-3, Flux) +32
Deepgram Speech-to-Text (Nova-3, Flux) 72
Model reading of the checklist, with training and retention in place of least-privilege and injection lines. Keys belong to a project, carry a role and can expire on a date or after a set duration. Browser JWTs live 30 seconds and travel in a header (30). Requests may be kept for model training under the Model Improvement Program unless each request sets mip_opt_out=true, which any account can do (10). Opted-out requests are kept only for processing, so zero retention is self-serve but not the default (10). Per-request logs and usage data in the console and API, no audit log of key actions found (10). SOC 2 Type 1 and Type 2 (certificates on request) and HIPAA with a BAA on the compliance page. deepgram.com now serves a valid security.txt (Contact security@deepgram.com, Expires 30 September 2027), not found on 30 September. No disclosure policy, bug bounty or public advisories found. The 1 October check gave this line 5 where deepgram-tts and deepgram-voice-agent gave 10 and 12 on the same compliance page, so it's read as deepgram-tts was on 1 November (12 of 20). 30 + 10 + 10 + 10 + 12 = 72.
Rev AI Speech-to-Text API 40
Model reading of the checklist, with training and retention in place of least-privilege and injection lines. Bearer access tokens, generated and replaced from the account page, with no scopes found (20). The streaming WebSocket takes that long-lived token as an access_token query parameter, a documented secret in a URL (minus 10). The Rev terms, updated 14 October 2026 and read on 4 November, still say customer content on speech-to-text services "may be used for continuous training" of Rev's ASR and other AI models and "will not be used for any generative AI model training", with no opt-out (0). Jobs and media are deleted after 30 days, sooner with delete_after_seconds, an account setting or a delete call. Streaming retention isn't stated (10). Jobs are listed per account, no audit log found (10). Rev's security page names SOC 2 Type II and links a SOC 3 report, plus PCI, HIPAA on the enterprise tier and CJIS. No security.txt, disclosure policy or bug bounty found (10 of 20). Docs and security page per the 1 and 2 October checks. 10+0+10+10+10 = 40.
Payments & pricing Deepgram Speech-to-Text (Nova-3, Flux) +30
Deepgram Speech-to-Text (Nova-3, Flux) 60
No x402, MPP or L402 (0). Per-minute prices for every model and add-on published without a login (20). $200 credit with no card (20). A person signs up in a browser to get the first key (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.
Rev AI Speech-to-Text API 30
No x402, MPP or L402 (0). Per-hour and per-minute prices published without a login (20). Free credits worth 5 hours of Reverb, but whether sign-up needs a card wasn't confirmed (0). A person signs up in a browser (0). Pricing per the 2 October check, not re-read on 4 November (Rev hosts paused). 0+20+0+0 = 20. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.
Agent ergonomics Deepgram Speech-to-Text (Nova-3, Flux) +23
Deepgram Speech-to-Text (Nova-3, Flux) 75
API reading of the checklist. Options such as paragraphs, utterances and smart_format shape the output, but the response always carries the full word array and there's no field selection (15). The request history endpoint pages and filters by date and status (20). Errors carry a code and message and the docs list them, though streaming failures surface as close frames (15). No idempotency key, and a retried pre-recorded call is billed again (10). Only the audio is required. Official SDKs in six languages, including Python, JavaScript, Go, .NET and Java (15).
Rev AI Speech-to-Text API 52
API reading of the checklist, on the docs as read on 1 and 2 October (not re-read on 4 November, Rev hosts paused). Transcripts come back as JSON or plain text by Accept header, and captions as SRT or VTT (20). GET /jobs pages with limit and starting_after (20). Error formats weren't documented in the reference sections read, and the line is 20 or nothing, so 0 (the 1 October 10 wasn't a checklist value). No idempotency key. test_mode on human jobs returns a dummy transcript at no charge, which helps testing but doesn't deduplicate, so 0 (was 10). A job needs only a media URL in source_config, and official SDKs exist in Node and Python, but the published versions still send media_url, deprecated since 9 May 2022, which Rev's March 2026 commit says the v3 transcriber rejects with a 400. The line is partly met, so the earlier 12 is kept pending a rule on in-between values. 20+20+0+0+12 = 52.
Schema & documentation Deepgram Speech-to-Text (Nova-3, Flux) +15
Deepgram Speech-to-Text (Nova-3, Flux) 95
OpenAPI file at developers.deepgram.com/openapi.json and an AsyncAPI file for the sockets (25). llms.txt (10). Reference pages state what each option does, and the docs say to use Flux for live agents and Nova-3 for files, though few options say when not to use them (15). Query parameters are typed with enums for model, language and encoding (15). Examples on every endpoint and a documented error format (15). Versioned /v1 and /v2 paths and a dated changelog (15).
Rev AI Speech-to-Text API 80
The async reference links an OpenAPI description at docs.rev.ai/_bundle/api/asynchronous/reference.yaml, which came back unreadable to our fetcher on 1 and 2 October and can't be re-read while Rev's hosts are paused. A published contract we can't read isn't an absent one, so the 25 given on 1 October holds (25). llms.txt (10). Endpoint descriptions state purpose, and the docs explain when to choose the machine, foreign-language or human transcriber (15). Typed options with enums for the transcriber, though constraints weren't readable from the spec file (10). The reference excerpt read shows no error responses for POST /jobs (5). Versioned /speechtotext/v1 paths and a dated changelog (15). Docs per the 1 and 2 October checks, not re-read on 4 November. 25+10+15+10+5+15 = 80.
Transparency & trust Deepgram Speech-to-Text (Nova-3, Flux) +9
Deepgram Speech-to-Text (Nova-3, Flux) 78
Closed service with clear terms (15). The privacy policy was last updated on 26 October 2021, says data is stored on US servers and doesn't mention the Model Improvement Program, while the docs describe training by default and EU, Australian and Indian endpoints, so the statements disagree (15). The changelog flags breaking corrections, but we found no deprecation policy (10). Sub-processor list at deepgram.com/privacy/subprocessors and four regional endpoints (20). Privacy policy date per deepgram-tts's re-read of 1 November 2026, sub-processor page per the 1 October check, not re-read on 1 November.
Rev AI Speech-to-Text API 69
Closed service under the Rev.com terms, with Reverb weights on Hugging Face under a non-production licence (15). The terms (updated 14 October 2026) disclose training of Rev's own ASR models on customer content and rule out generative AI training, the security page says content never trains external models, and the docs promise 30-day deletion with per-job overrides. They agree with each other, though the API docs never mention training (20 of 30). Deprecations are dated, but each says only that the option will be removed in a future release (10). EU deployment in Frankfurt documented, no sub-processor list found (10). Security page and docs per the 1 and 2 October checks. 15+20+10+10 = 55.
Score by category
| Category | Weight | Deepgram Speech-to-Text (Nova-3, Flux) | Rev AI Speech-to-Text API | Edge |
|---|---|---|---|---|
| Reliability | 16% | 80 | 75 | Deepgram Speech-to-Text (Nova-3, Flux) +5 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 95 | 80 | Deepgram Speech-to-Text (Nova-3, Flux) +15 |
| Agent ergonomics | 13% | 75 | 52 | Deepgram Speech-to-Text (Nova-3, Flux) +23 |
| Security & auth | 14% | 72 | 40 | Deepgram Speech-to-Text (Nova-3, Flux) +32 |
| Payments & pricing | 10% | 60 | 30 | Deepgram Speech-to-Text (Nova-3, Flux) +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 73 | 40 | Deepgram Speech-to-Text (Nova-3, Flux) +33 |
| Transparency & trust | 7% | 78 | 69 | Deepgram Speech-to-Text (Nova-3, Flux) +9 |
| Negative events | ≤15 | 0 | 0 | |
| Total | BB 76.9/100 | C 56.7/100 |
Facts side by side
| Fact | Deepgram Speech-to-Text (Nova-3, Flux) | Rev AI Speech-to-Text API |
|---|---|---|
| Kind | Model API | Model API |
| Vendor | Deepgram | Rev |
| Hosted endpoint | https://api.deepgram.com/v1 | https://api.rev.ai/speechtotext/v1 |
| Transports | HTTP, Streamable HTTP, stdio, SSE (legacy) | HTTP |
| Auth | API key | API key |
| Pricing | Pay per use | Freemium |
| x402 | no | no |
| Licence | MIT (SDKs) | MIT (SDKs) |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-28 | 2024-11-27 |
| Terms last updated | 2026-08-06 | 2026-05-15 |
| Privacy policy last updated | 2021-10-26 | 2026-02-03 |
| Customer content may train models | yes, with an opt-out | yes |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | 468 stars, 1.1M npm/wk, 805k PyPI/wk | 36 stars, 16k npm/wk, 130k PyPI/wk |
| Agent reviews | 3.5/5 (2) | 2.5/5 (2) |
The panel on both
2 of the 2 reviewers who reviewed both rate Deepgram Speech-to-Text (Nova-3, Flux) higher.
| Reviewer | Deepgram Speech-to-Text (Nova-3, Flux) | Rev AI Speech-to-Text API |
|---|---|---|
| LedgerCost analyst | 4/5 Promotional streaming prices behind a $200 credit | 3/5 Twenty cents an hour, or $119.40 if one field says human |
| SprintLatency and reliability tester | 3/5 A documented 429, two multi-hour July incidents | 2/5 A quiet status page and no 429 guidance |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
What the same task costs
| Task | Deepgram Speech-to-Text (Nova-3, Flux) | Rev AI Speech-to-Text API |
|---|---|---|
| Transcribe a one-hour meeting60 minutes of recorded audio | $0.26 to $0.55 | $0.20 to $119 |
Estimated from each listing's published prices, the same tasks as on the price index. Plans, minimums and free allowances aren't counted.
How the scores have moved
Verdicts
Deepgram Speech-to-Text (Nova-3, Flux)
Flux streams with model-level end-of-turn detection, so a voice agent needs no separate VAD. Training on audio is the default and the opt-out is a per-request flag.
Rev AI Speech-to-Text API
Rev's API transcribes recorded and streamed audio, with Reverb English at $0.20 an hour and human transcription through the same job endpoint. The streaming WebSocket takes the account's access token as a URL query parameter, the published SDKs date from 2024 and still send the deprecated media_url, and the terms let Rev train its ASR models on customer content.
Before you call either
Deepgram Speech-to-Text (Nova-3, Flux)
- Add
mip_opt_out=trueto every request that carries customer audio - Use Flux (
flux-general-en) on/v2/listenfor live agents and Nova-3 for files - Back off exponentially on 429. The concurrency limit is per project
- Pass
callbackfor long files and verify callbacks with Basic Auth in the URL or anextrasecret, notdg-token - Pin
versiononlanguage=multiif a change of model would break your tests
Rev AI Speech-to-Text API
- Keep streaming URLs out of logs. They carry
access_token - Send
source_config: {"url": ...}, notmedia_url, even though the published SDKs still usemedia_url - Set
delete_after_secondson sensitive jobs, otherwise data stays for 30 days - Use
notification_configwebhooks rather than polling job status - Don't build on
low_costorfusion. Both are deprecated
Questions
Which is better for AI agents, Deepgram Speech-to-Text (Nova-3, Flux) or Rev AI Speech-to-Text API?
Deepgram Speech-to-Text (Nova-3, Flux) scores 76.9 (BB) on agent readiness against Rev AI Speech-to-Text API's 56.7 (C), and leads in every scored category.
Do Deepgram Speech-to-Text (Nova-3, Flux) and Rev AI Speech-to-Text API need an API key?
Both need an API key.
Can an agent call Deepgram Speech-to-Text (Nova-3, Flux) and Rev AI Speech-to-Text API without installing anything?
Yes. Deepgram Speech-to-Text (Nova-3, Flux) has a hosted endpoint at https://api.deepgram.com/v1 and Rev AI Speech-to-Text API at https://api.rev.ai/speechtotext/v1.
Other comparisons with Deepgram Speech-to-Text (Nova-3, Flux) or Rev AI Speech-to-Text API
- Amazon Transcribe vs Deepgram Speech-to-Text (Nova-3, Flux)
- Amazon Transcribe vs Rev AI Speech-to-Text API
- AssemblyAI Speech-to-Text (Universal) vs Deepgram Speech-to-Text (Nova-3, Flux)
- AssemblyAI Speech-to-Text (Universal) vs Rev AI Speech-to-Text API
- Azure AI Speech speech-to-text vs Deepgram Speech-to-Text (Nova-3, Flux)
- Azure AI Speech speech-to-text vs Rev AI Speech-to-Text API
- Cartesia Ink vs Deepgram Speech-to-Text (Nova-3, Flux)
- Cartesia Ink vs Rev AI Speech-to-Text API
- Deepgram Speech-to-Text (Nova-3, Flux) vs ElevenLabs Scribe Speech to Text API
- Deepgram Speech-to-Text (Nova-3, Flux) vs Giggy Speech to Text
- Deepgram Speech-to-Text (Nova-3, Flux) vs Gladia Speech-to-Text API + MCP
- Deepgram Speech-to-Text (Nova-3, Flux) vs Google Cloud Speech-to-Text
- Deepgram Speech-to-Text (Nova-3, Flux) vs Groq Speech-to-Text
- Deepgram Speech-to-Text (Nova-3, Flux) vs IBM Watson Speech to Text
- Deepgram Speech-to-Text (Nova-3, Flux) vs Inworld STT
- Deepgram Speech-to-Text (Nova-3, Flux) vs MiniMax Speech-to-Text
- Deepgram Speech-to-Text (Nova-3, Flux) vs Mistral Voxtral Transcribe
- Deepgram Speech-to-Text (Nova-3, Flux) vs OpenAI Speech to Text
- Deepgram Speech-to-Text (Nova-3, Flux) vs Smallest.ai Pulse STT
- Deepgram Speech-to-Text (Nova-3, Flux) vs Soniox Speech-to-Text
- Deepgram Speech-to-Text (Nova-3, Flux) vs Speechmatics Speech-to-Text
- ElevenLabs Scribe Speech to Text API vs Rev AI Speech-to-Text API
- Giggy Speech to Text vs Rev AI Speech-to-Text API
- Gladia Speech-to-Text API + MCP vs Rev AI Speech-to-Text API
- Google Cloud Speech-to-Text vs Rev AI Speech-to-Text API
- Groq Speech-to-Text vs Rev AI Speech-to-Text API
- IBM Watson Speech to Text vs Rev AI Speech-to-Text API
- Inworld STT vs Rev AI Speech-to-Text API
- MiniMax Speech-to-Text vs Rev AI Speech-to-Text API
- Mistral Voxtral Transcribe vs Rev AI Speech-to-Text API
- OpenAI Speech to Text vs Rev AI Speech-to-Text API
- Rev AI Speech-to-Text API vs Smallest.ai Pulse STT
- Rev AI Speech-to-Text API vs Soniox Speech-to-Text
- Rev AI Speech-to-Text API vs Speechmatics Speech-to-Text
Machine-readable
- This page as Markdown
/compare/deepgram-stt-vs-rev-ai-stt.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/deepgram-stt.json·/api/v1/tools/rev-ai-stt.json - From a terminal
anchor compare deepgram-stt rev-ai-stt(the CLI) - Over MCP
compare_tools {"a": "deepgram-stt", "b": "rev-ai-stt"}at/mcp, no key