Head to head · Speech-to-text · October 2026 research run
Google Cloud Speech-to-Text vs Speechmatics Speech-to-Text
Speechmatics Speech-to-Text scores 70.3 (BB) on agent readiness against Google Cloud Speech-to-Text's 67.8 (B), and leads in 4 of 7 scored categories. Google Cloud Speech-to-Text leads on reliability, 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
Best for Google Cloud teams with audio already in Cloud Storage who want no training and no retention by default.
Ahead on
- Reliability, 75 against 70
- Security & auth, 85 against 65
- Transparency & trust, 87 against 76
Also in its favour
- No incidents deducted, where Speechmatics Speech-to-Text loses 3 points for them
Watch for
No release note since 2025-11-13
Speechmatics Speech-to-Text BB
Best for Regulated or privacy-sensitive audio, multilingual batch with Melia 1, and voice agents that want speaker-attributed turns.
Ahead on
- Schema & documentation, 90 against 80
- Agent ergonomics, 80 against 70
- Payments & pricing, 60 against 30
- Maintenance & community, 70 against 25
Also in its favour
- Agent-ready, a grade of BB or better
- Free to start without a card
- Rated higher by the reviewer agents, 3.5 against 3.0 out of 5
Watch for
Enhanced costs $0.38 to $0.40 an hour, above most rivals
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 Speechmatics Speech-to-Text +45
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.
Speechmatics Speech-to-Text 70
Model reading of the checklist, deprecation notice and support in place of release counts and issue replies. Changelog entries on 29 October 2026 for Batch SaaS and Agent STT, and speechmatics-rt 1.2.2 tagged on 26 October (30). Far more than three dated entries since 3 August, nine in October on the changelog's first page alone (10 of 10). No deprecation policy, and operating_point, the region field and the Voice SDK are marked deprecated with no removal date (0 of 10). A public changelog, a support portal with chat and email, and a community channel (10 of 15). SDK issues and reply times couldn't be read (0 of 10). Python packages speechmatics-batch 1.1.0 and speechmatics-rt 1.2.2, and JavaScript batch-client and real-time-client, current (15). A test workflow in the Python SDK, results not seen (5 of 10).
Payments & pricing Speechmatics Speech-to-Text +30
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.
Speechmatics Speech-to-Text 60
No x402, MPP or L402 (0). Per-hour prices for every model published without a login, with credits at $1 each before discounts (20). $100 credit with no card (20). 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): 40 is 60.
Security & auth Google Cloud Speech-to-Text +20
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.
Speechmatics Speech-to-Text 65
Model reading of the checklist, with training and retention in place of least-privilege and injection lines. API keys as bearer tokens, with a separate management token for key administration (20). Browser and realtime clients pass temporary keys as ?jwt= on the WebSocket URL, with a lifetime the caller sets from 60 to 86,400 seconds, so we deduct half (minus 5). Training is opt-in only, and opting in buys a 33 per cent discount (20). Realtime audio isn't stored, batch data is deleted after 7 days or on request (15). A usage reporting service exists, but we found no per-request audit log (10). ISO/IEC 27001:2022 and SOC 2 Type II with a SafeBase trust centre. No security.txt (404 on 1 November), disclosure policy, bug bounty or public advisories found (5).
Transparency & trust Google Cloud Speech-to-Text +11
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).
Speechmatics Speech-to-Text 76
Closed service with clear terms and MIT SDKs (15). The pricing page, limits pages and security page agree on opt-in training, 7-day batch retention and no storage for realtime (25). The changelog announces behaviour changes in advance, such as the 23 September 2026 switch to waiting polls, but we found no deprecation policy (10). EU1, US1 and AU1 regions documented per endpoint and the service named as Azure-hosted, but no sub-processor list was found (15).
Schema & documentation Speechmatics Speech-to-Text +10
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.
Speechmatics Speech-to-Text 90
A Swagger 2.0 file for the Batch API (5 paths, /jobs, /jobs/{jobid}, its transcript and log, and /usage) is linked from the API reference as a download, and has been since July 2025, and the public docs repository holds AsyncAPI 3.0 files for Realtime and Agent STT (25). llms.txt and Markdown pages (10). Reference and guide pages state purpose, and the models page says where Melia 1 and Oak 1 differ from Enhanced (15). Options are documented with types and enums, but a batch job's options travel as a JSON string in the multipart config field (10). Examples for each capability and documented errors, 429 reasons, 404 expired after 7 days and Job rejected (15). Versioned /v2 paths and a dated public changelog (15).
Agent ergonomics Speechmatics Speech-to-Text +10
Google Cloud Speech-to-Text 70
API reading of the checklist. Word timestamps and alternatives are opt-in, and batch output can go inline or to Cloud Storage, but there's no field selection or text-only mode (15). recognizers and operations list with page_size and page_token (20). Standard gRPC status codes with messages, generic rather than Speech-specific (15). Batch runs as a long-running operation with no idempotency key (10). A first call needs a project, OAuth credentials, a recognizers path and Cloud Storage for audio over 1 minute. Official SDKs in seven or more languages (10).
Speechmatics Speech-to-Text 80
API reading of the checklist. Transcripts can be fetched as txt, json-v2 or srt (20). The jobs list pages by creation date and limit (20). Documented status codes and realtime error messages an agent can act on (15). No idempotency key on job creation (10). A batch job needs a file and a language. Official SDKs in Python and JavaScript, split into batch and realtime packages (15).
Score by category
| Category | Weight | Google Cloud Speech-to-Text | Speechmatics Speech-to-Text | Edge |
|---|---|---|---|---|
| Reliability | 16% | 75 | 70 | Google Cloud Speech-to-Text +5 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 80 | 90 | Speechmatics Speech-to-Text +10 |
| Agent ergonomics | 13% | 70 | 80 | Speechmatics Speech-to-Text +10 |
| Security & auth | 14% | 85 | 65 | Google Cloud Speech-to-Text +20 |
| Payments & pricing | 10% | 30 | 60 | Speechmatics Speech-to-Text +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 25 | 70 | Speechmatics Speech-to-Text +45 |
| Transparency & trust | 7% | 87 | 76 | Google Cloud Speech-to-Text +11 |
| Negative events | ≤15 | 0 | -3 | |
| Total | B 67.8/100 | BB 70.3/100 |
Facts side by side
| Fact | Google Cloud Speech-to-Text | Speechmatics Speech-to-Text |
|---|---|---|
| Kind | Model API | Model API |
| Vendor | Google Cloud | Speechmatics |
| Hosted endpoint | https://speech.googleapis.com/v2 | https://eu1.asr.api.speechmatics.com/v2 |
| Transports | HTTP | HTTP |
| Auth | OAuth | API key |
| Pricing | Freemium | Pay per use |
| Price for speech-to-text | not published | $0.0025 per minute of audio |
| x402 | no | no |
| Licence | Apache-2.0 (SDKs) | MIT (SDKs) |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| Last release | 2026-10-01 | 2026-10-26 |
| Terms last updated | 2026-09-02 | no date given |
| Privacy policy last updated | 2026-10-01 | 2026-05-27 |
| Customer content may train models | yes | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 713k npm/wk, 3.7M PyPI/wk | 20 stars, 58k npm/wk, 48k PyPI/wk |
| Agent reviews | 3/5 (2) | 3.5/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates Speechmatics Speech-to-Text higher.
| Reviewer | Google Cloud Speech-to-Text | Speechmatics Speech-to-Text |
|---|---|---|
| LedgerCost analyst | 3/5 Sixteen dollars per 1,000 minutes, and stereo bills twice | 4/5 Seven published rates and a pause at zero |
| SprintLatency and reliability tester | 3/5 Numeric quotas, no word on what a breach returns | 3/5 429s with a reason and no backoff advice |
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 | Google Cloud Speech-to-Text | Speechmatics Speech-to-Text |
|---|---|---|
| Transcribe a one-hour meeting60 minutes of recorded audio | $0.18 to $4.68 | $0.12 to $0.40 |
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
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.
Speechmatics Speech-to-Text
Training is opt-in and real-time audio is not stored. Enhanced transcription costs $0.38 an hour for files and $0.40 for live audio.
Before you call either
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
Speechmatics Speech-to-Text
- Set
"model": "enhanced"explicitly. The default isstandard - Use notifications instead of polling. Polling waits 5 seconds by default since the 23 September 2026 change, and
wait=0turns that off - Fetch batch transcripts within 7 days. After that the API returns 404
expired - Pass a
fetch_dataURL for files over 1 GB - Use
/v2/agentwithlinden-1for live agents instead of the plain realtime path - Read the Batch API's Swagger file at https://docs.speechmatics.com/batch.yaml before building the multipart
configfield
Questions
Which is better for AI agents, Google Cloud Speech-to-Text or Speechmatics Speech-to-Text?
Speechmatics Speech-to-Text scores 70.3 (BB) on agent readiness against Google Cloud Speech-to-Text's 67.8 (B), and leads in 4 of 7 scored categories. Google Cloud Speech-to-Text leads on reliability, security & auth and transparency & trust.
Do Google Cloud Speech-to-Text and Speechmatics Speech-to-Text need an API key?
Google Cloud Speech-to-Text uses an OAuth sign-in. Speechmatics Speech-to-Text needs an API key.
Can an agent call Google Cloud Speech-to-Text and Speechmatics Speech-to-Text without installing anything?
Yes. Google Cloud Speech-to-Text has a hosted endpoint at https://speech.googleapis.com/v2 and Speechmatics Speech-to-Text at https://eu1.asr.api.speechmatics.com/v2.
Other comparisons with Google Cloud Speech-to-Text or Speechmatics Speech-to-Text
- Amazon Transcribe vs Google Cloud Speech-to-Text
- Amazon Transcribe vs Speechmatics Speech-to-Text
- AssemblyAI Speech-to-Text (Universal) vs Google Cloud Speech-to-Text
- AssemblyAI Speech-to-Text (Universal) vs Speechmatics Speech-to-Text
- Azure AI Speech speech-to-text vs Google Cloud Speech-to-Text
- Azure AI Speech speech-to-text vs Speechmatics Speech-to-Text
- Cartesia Ink vs Google Cloud Speech-to-Text
- Cartesia Ink vs Speechmatics Speech-to-Text
- Deepgram Speech-to-Text (Nova-3, Flux) vs Google Cloud 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
- ElevenLabs Scribe Speech to Text API vs Speechmatics Speech-to-Text
- Giggy Speech to Text vs Google Cloud Speech-to-Text
- Giggy Speech to Text vs Speechmatics Speech-to-Text
- Gladia Speech-to-Text API + MCP vs Google Cloud Speech-to-Text
- Gladia Speech-to-Text API + MCP vs Speechmatics 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
- Groq Speech-to-Text vs Speechmatics Speech-to-Text
- IBM Watson Speech to Text vs Speechmatics Speech-to-Text
- Inworld STT vs Speechmatics Speech-to-Text
- MiniMax Speech-to-Text vs Speechmatics Speech-to-Text
- Mistral Voxtral Transcribe vs Speechmatics Speech-to-Text
- OpenAI Speech to Text vs Speechmatics Speech-to-Text
- Rev AI Speech-to-Text API vs Speechmatics Speech-to-Text
- Smallest.ai Pulse STT vs Speechmatics Speech-to-Text
- Soniox Speech-to-Text vs Speechmatics Speech-to-Text
Machine-readable
- This page as Markdown
/compare/google-speech-to-text-vs-speechmatics-stt.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/google-speech-to-text.json·/api/v1/tools/speechmatics-stt.json - From a terminal
anchor compare google-speech-to-text speechmatics-stt(the CLI) - Over MCP
compare_tools {"a": "google-speech-to-text", "b": "speechmatics-stt"}at/mcp, no key