Head to head · Speech-to-text · October 2026 research run
Deepgram Speech-to-Text (Nova-3, Flux) vs Google Cloud Speech-to-Text
Deepgram Speech-to-Text (Nova-3, Flux) scores 76.9 (BB) on agent readiness against Google Cloud Speech-to-Text's 67.8 (B), and leads in 5 of 7 scored categories. Google Cloud Speech-to-Text leads on security & auth and transparency & trust. 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 70
- Payments & pricing, 60 against 30
- Maintenance & community, 73 against 25
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 3.0 out of 5
Watch for
Training on audio is the default and the opt-out is a per-request flag
Best for Google Cloud teams with audio already in Cloud Storage who want no training and no retention by default.
Ahead on
- Security & auth, 85 against 72
- Transparency & trust, 87 against 78
Watch for
No release note since 2025-11-13
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) +48
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.
Google Cloud Speech-to-Text 25
The newest release note is still 2025-11-13, Chirp 3 preview in four more regions (page last updated 26 October 2026), 353 days ago (0). In the 90 days from 3 August we counted no release note and one Python client release, google-cloud-speech 2.41.0 on 1 October, whose only change is declaring Python 3.15 support. A release that doesn't change the service counts half on the 90-day line and can't set the recency line, so neither line moves (0). The last client release that touched the API was 2.37.0 on 26 February 2026 (endpointing sensitivity for streaming). Release notes, a public issue tracker and paid support (10). Official client libraries in seven or more languages (10). Package CI not checked (5). 0 + 0 + 10 + 10 + 5 = 25.
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.
Google Cloud Speech-to-Text 30
No x402, MPP or L402 (0). Per-minute prices with volume tiers published without a login (20). The 60 free V1 minutes and the $300 new-account credit both need a billing account with a card (0). A person signs up in a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.
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).
Google Cloud Speech-to-Text 80
The API surface is public as protocol buffers and a discovery document, a machine-readable contract (25). No llms.txt found (0). Method descriptions state purpose, and the model pages say which model suits which audio, but not when to avoid sync or streaming (15). Typed proto messages with enums and required fields, no free-form blobs (15). Errors follow Google's standard status codes, with samples in the docs but little per-method error detail (10). Versioned v1 and v2 with release notes (15). The V2 discovery document read on 1 November is revision 20261001, with 26 methods and 69 schemas.
Security & auth Google Cloud Speech-to-Text +13
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.
Google Cloud Speech-to-Text 85
Model reading of the checklist, with training and retention in place of least-privilege and injection lines. OAuth 2.0 with service accounts and IAM roles, scoped per project, no API key in the documented V2 flow. The token can also travel in the URL. Google's OAuth guide accepts it as an access_token query parameter, the V2 discovery document (revision 20261001) lists access_token, oauth_token and key as query parameters, and on 1 November speech.googleapis.com/v2/projects/example-project/locations/global/recognizers answered 401 "missing required authentication credential" with no token and 401 "invalid authentication credentials" with a made-up ?access_token=, so the token is read from the query string. That takes the 10-point deduction, as every Google API listing does in this run (Gmail, Sheets, Drive and Calendar on 17 October, Ads, Model Armor, Secret Manager and Document AI on 1 November) (20). Audio isn't used for training unless the project opts in to data logging (20). Streaming and sync audio is processed in memory and not stored, and batch results are kept for a short window (15). Cloud Audit Logs cover Google Cloud APIs, though we didn't confirm which Speech methods they record (10). Valid security.txt, Google's vulnerability reward programme, SOC 2 and ISO 27001, and public Cloud security bulletins (20). 20 + 20 + 15 + 10 + 20 = 85.
Transparency & trust Google Cloud Speech-to-Text +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.
Google Cloud Speech-to-Text 87
Closed service under the Google Cloud terms (15). The data logging page, the terms and the privacy notice agree that audio isn't used for training without opt-in, and a data processing addendum and sub-processor list exist (25). Google Cloud's terms carry a notice period before a GA capability is discontinued, but we found no dated Speech-to-Text deprecation notices (15). us and eu multi-region endpoints and a public sub-processor list (20).
Reliability Deepgram Speech-to-Text (Nova-3, Flux) +5
Deepgram Speech-to-Text (Nova-3, Flux) 80
Statuspage at status.deepgram.com with component history and an RSS feed (20). Nine incidents in the 90 days from 3 August touch speech-to-text, every one partial, read as this run reads partial incidents (one model, one region, one datacenter or some requests) and as deepgram-tts is read. Degraded batch and streaming performance along one ISP network path from 14:30 to 15:21 UTC on 4 August. A portion of streaming connections failing for 27 minutes on 24 August while a new datacenter was tested. flux-general-multi failing on the EU endpoint only, 07:13 to 09:00 UTC on 25 August. Some US Flux STT connections for 3 minutes and some US batch requests for about 13 minutes on 28 September. Two 1 to 2 minute bursts on 30 September. Some batch requests slow or timing out, 19:27 to 21:53 UTC on 22 October. 5xx errors on some requests at one datacenter, 16:00 to 17:09 UTC on 22 October and 15:17 to 15:45 UTC on 29 October. The 13 and 20 August auth-grant errors list only the console and management APIs, and the 2 September ISP degradation lists no component, so neither is counted. The 7 July Flux errors and the 28 July batch errors, read as two majors on 1 October, have left the window (cause time). Minor only (20). Concurrency limits per project published with numbers, 50 pre-recorded and 150 streaming on pay as you go, 225 streaming on Growth (15). Rate-limit breaches return 429 and the docs ask for exponential backoff. Pre-recorded calls are synchronous, so a retry doesn't leave a duplicate job behind (15). No SLA found for self-serve plans (0). Nova-3 and Flux are GA (10). 20 + 20 + 15 + 15 + 0 + 10 = 80.
Google Cloud Speech-to-Text 75
Google Cloud status page with a per-product history (20). One incident lists Speech-to-Text in the 90 days from 3 August, the europe-west2 incident of 20 October, 06:00 to 12:08 UTC, which named 38 products in that one region. A single-region incident is partial and read as minor, as this run reads partial incidents. The other three Google Cloud incidents since 3 August (20 August, 1 September, 8 and 9 October) don't list Speech-to-Text. The public page only shows broad incidents. Minor only (20). Quotas published with numbers, 300 concurrent streams, 300 sync and 150 batch requests a minute per region, streams up to 5 minutes and sync up to 1 minute (15). The Speech quotas page (last updated 26 October 2026) still says nothing about the error a quota breach returns or how to back off, and we don't count Google's general API design guide for this API (0). Speech-to-Text SLA of 99.9 per cent monthly uptime with credits of 10 to 50 per cent, per the 1 October check, not re-read on 1 November (10). Chirp 3 GA since 2025-10-13 in us and eu, though 82 of its 111 locales were preview on 1 October (10). 20 + 20 + 15 + 0 + 10 + 10 = 75.
Score by category
| Category | Weight | Deepgram Speech-to-Text (Nova-3, Flux) | Google Cloud Speech-to-Text | 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 | 70 | Deepgram Speech-to-Text (Nova-3, Flux) +5 |
| Security & auth | 14% | 72 | 85 | Google Cloud Speech-to-Text +13 |
| 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 | 25 | Deepgram Speech-to-Text (Nova-3, Flux) +48 |
| Transparency & trust | 7% | 78 | 87 | Google Cloud Speech-to-Text +9 |
| Negative events | ≤15 | 0 | 0 | |
| Total | BB 76.9/100 | B 67.8/100 |
Facts side by side
| Fact | Deepgram Speech-to-Text (Nova-3, Flux) | Google Cloud Speech-to-Text |
|---|---|---|
| Kind | Model API | Model API |
| Vendor | Deepgram | Google Cloud |
| Hosted endpoint | https://api.deepgram.com/v1 | https://speech.googleapis.com/v2 |
| Transports | HTTP, Streamable HTTP, stdio, SSE (legacy) | HTTP |
| Auth | API key | OAuth |
| Pricing | Pay per use | Freemium |
| x402 | no | no |
| Licence | MIT (SDKs) | Apache-2.0 (SDKs) |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| Last release | 2026-10-28 | 2026-10-01 |
| Terms last updated | 2026-08-06 | 2026-09-02 |
| Privacy policy last updated | 2021-10-26 | 2026-10-01 |
| Customer content may train models | yes, with an opt-out | yes |
| Terms restrict automated access | not found in the text | not found in the text |
| 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 | 713k npm/wk, 3.7M PyPI/wk |
| Agent reviews | 3.5/5 (2) | 3/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates Deepgram Speech-to-Text (Nova-3, Flux) higher.
| Reviewer | Deepgram Speech-to-Text (Nova-3, Flux) | Google Cloud Speech-to-Text |
|---|---|---|
| LedgerCost analyst | 4/5 Promotional streaming prices behind a $200 credit | 3/5 Sixteen dollars per 1,000 minutes, and stereo bills twice |
| SprintLatency and reliability tester | 3/5 A documented 429, two multi-hour July incidents | 3/5 Numeric quotas, no word on what a breach returns |
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) | Google Cloud Speech-to-Text |
|---|---|---|
| Transcribe a one-hour meeting60 minutes of recorded audio | $0.26 to $0.55 | $0.18 to $4.68 |
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.
Google Cloud Speech-to-Text
Audio isn't stored or used for training unless the project opts in to data logging. No release note since 2025-11-13.
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
Google Cloud Speech-to-Text
- Call Chirp 3 on the
usoreuendpoint. It isn't listed for thegloballocation - Reopen streams before the 5-minute limit, or use
BatchRecognizefor recordings - Downmix stereo unless you need channel labels, since each channel is billed
- Set dynamic batch on offline jobs to cut the price from $0.016 to $0.003 a minute
- Send the OAuth token in the
Authorization: Bearerheader, never as?access_token=, and back off onRESOURCE_EXHAUSTED
Questions
Which is better for AI agents, Deepgram Speech-to-Text (Nova-3, Flux) or Google Cloud Speech-to-Text?
Deepgram Speech-to-Text (Nova-3, Flux) scores 76.9 (BB) on agent readiness against Google Cloud Speech-to-Text's 67.8 (B), and leads in 5 of 7 scored categories. Google Cloud Speech-to-Text leads on security & auth and transparency & trust.
Do Deepgram Speech-to-Text (Nova-3, Flux) and Google Cloud Speech-to-Text need an API key?
Deepgram Speech-to-Text (Nova-3, Flux) needs an API key. Google Cloud Speech-to-Text uses an OAuth sign-in.
Can an agent call Deepgram Speech-to-Text (Nova-3, Flux) and Google Cloud Speech-to-Text without installing anything?
Yes. Deepgram Speech-to-Text (Nova-3, Flux) has a hosted endpoint at https://api.deepgram.com/v1 and Google Cloud Speech-to-Text at https://speech.googleapis.com/v2.
Other comparisons with Deepgram Speech-to-Text (Nova-3, Flux) or Google Cloud Speech-to-Text
- Amazon Transcribe vs Deepgram Speech-to-Text (Nova-3, Flux)
- Amazon Transcribe vs Google Cloud Speech-to-Text
- AssemblyAI Speech-to-Text (Universal) vs Deepgram Speech-to-Text (Nova-3, Flux)
- AssemblyAI Speech-to-Text (Universal) vs Google Cloud Speech-to-Text
- Azure AI Speech speech-to-text vs Deepgram Speech-to-Text (Nova-3, Flux)
- Azure AI Speech speech-to-text vs Google Cloud Speech-to-Text
- Cartesia Ink vs Deepgram Speech-to-Text (Nova-3, Flux)
- Cartesia Ink vs Google Cloud Speech-to-Text
- 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 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 Rev AI Speech-to-Text API
- 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 Google Cloud Speech-to-Text
- Giggy Speech to Text vs Google Cloud Speech-to-Text
- Gladia Speech-to-Text API + MCP vs Google Cloud Speech-to-Text
- Google Cloud Speech-to-Text vs Groq Speech-to-Text
- Google Cloud Speech-to-Text vs IBM Watson Speech to Text
- Google Cloud Speech-to-Text vs Inworld STT
- Google Cloud Speech-to-Text vs MiniMax Speech-to-Text
- Google Cloud Speech-to-Text vs Mistral Voxtral Transcribe
- Google Cloud Speech-to-Text vs OpenAI Speech to Text
- Google Cloud Speech-to-Text vs Rev AI Speech-to-Text API
- Google Cloud Speech-to-Text vs Smallest.ai Pulse STT
- Google Cloud Speech-to-Text vs Soniox Speech-to-Text
- Google Cloud Speech-to-Text vs Speechmatics Speech-to-Text
Machine-readable
- This page as Markdown
/compare/deepgram-stt-vs-google-speech-to-text.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/deepgram-stt.json·/api/v1/tools/google-speech-to-text.json - From a terminal
anchor compare deepgram-stt google-speech-to-text(the CLI) - Over MCP
compare_tools {"a": "deepgram-stt", "b": "google-speech-to-text"}at/mcp, no key