Head to head · Speech-to-text · October 2026 research run
Gladia Speech-to-Text API + MCP vs Google Cloud Speech-to-Text
Gladia Speech-to-Text API + MCP scores 72.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
Gladia Speech-to-Text API + MCP BB
Best for Multilingual meetings and calls where live and async transcription in 100+ languages is needed, and for teams who want an MCP server.
Ahead on
- Schema & documentation, 95 against 80
- Agent ergonomics, 75 against 70
- Payments & pricing, 60 against 30
- Maintenance & community, 70 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
Watch for
Self-serve audio is used for model training by default unless the account opts out
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 65
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 Gladia Speech-to-Text API + MCP +45
Gladia Speech-to-Text API + MCP 70
Read as a model, for deprecation notice and model churn rather than release counts, on the lines deepgram-stt was settled on in this run. SDK 2.2.0 on 13 October 2026, three fixes among them limiting list pagination to the configured API, 19 days before 1 November (30). 2.2.1 on 23 October only raises the Python certifi floor to distrust a compromised certificate authority and is a version bump with no code changes for JavaScript, so as a dependency-only release it counts half and doesn't set this line, as azure-translator's was read. In the 90 days from 3 August, changelog entries on 8, 9 and 14 September, SDK 2.1.0 (18 and 21 September), 2.2.0 and 2.2.1 (at half), and the MCP server 0.1.0 and 0.1.1 on 24 September (10). The /v2/transcription endpoints are marked deprecated in favour of /v2/pre-recorded with no removal date, structured data extraction has gone from the OpenAPI file without a changelog entry, and no deprecation policy was found (0 of 10). Public changelog, help centre and Discord (10 of 15). SDK and MCP repository issues couldn't be read, since github.com refuses our reader, so absent (0 of 10). Official JavaScript and Python SDKs current at 2.2.1 (15). The SDK repository has CI, release and OpenAPI type-update workflows, results not seen (5 of 10). 30 + 10 + 0 + 10 + 0 + 15 + 5 = 70.
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 Gladia Speech-to-Text API + MCP +30
Gladia Speech-to-Text API + MCP 60
No x402, MPP or L402 (0). Per-hour prices in euros published without a login, re-read on 1 November, async from 0.27€ an hour on solaria-1 and 0.16€ on solaria-3, real-time 0.68€, add-ons per hour (20). A one-time €50 credit, with no card per the 1 October check (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.
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.
Transparency & trust Google Cloud Speech-to-Text +22
Gladia Speech-to-Text API + MCP 65
Closed service with an MIT SDK and MCP server and separate terms for Gladia SAS and Gladia Inc. (15). The statements disagree. The security page gives a 12-month default retention with custom policies for customers and says only Free plan data trains models, while the retention page gives 1 year on free, 3 weeks on paid and zero retention only on Enterprise, and the pricing page says Self-serve is opted in to training by default. ISO 27001 is described as in progress (15). Breaking changes are flagged with dates in the changelog, such as SDK 2.0.0 and the move to credit billing on 3 July 2026 with a 6 to 20 July rollout, but no deprecation policy was found (10). Hosting with a French provider is stated, and no sub-processor list was found (10).
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).
Security & auth Google Cloud Speech-to-Text +20
Gladia Speech-to-Text API + MCP 65
Model reading of the checklist, with training and retention in place of least-privilege and injection lines. Plain revocable API keys in the x-gladia-key header. Live sessions connect to a WebSocket URL minted per session by POST /v2/live, which we don't deduct for (20). The pricing page, read on 1 November, says Self-serve, the paid pay-as-you-go plan, is opted in to model training by default with a free opt-out in the profile, and Enterprise is opted out by default. The security page still says only Free plan data is used for training. We score the pricing page's default, as for AWS's default use with an opt-out (10 of 20). Retention is documented and jobs can be deleted, but zero retention needs Enterprise per the retention page (10). Job history through the list endpoint and dashboard, no audit log of key actions found (10). SOC 2 Type 1 and Type 2, a bug bounty programme that doubles as the disclosure route, no security.txt (404 on 1 November) and no public advisories found. The SDKs fixed an API key leak on cross-origin redirects in 2.1.0 (September) and limited list pagination to the configured API in 2.2.0 (13 October), both released. ISO 27001 is in progress, not held (15). 20 + 10 + 10 + 10 + 15 = 65.
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.
Schema & documentation Gladia Speech-to-Text API + MCP +15
Gladia Speech-to-Text API + MCP 95
OpenAPI file at api.gladia.io/openapi.json (25). llms.txt (10). Reference pages state purpose per endpoint and the model page says to use solaria-3 only for async English, French, German, Spanish or Italian (15). Typed bodies with enums and required fields, audio_url the only required input for pre-recorded (15). Examples per endpoint and documented error codes (15). Versioned /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.
Reliability Google Cloud Speech-to-Text +5
Gladia Speech-to-Text API + MCP 70
incident.io status page with per-component uptime bars and incident pages, and an RSS feed read on 1 November (20). One major incident in the 90 days from 3 August, a global Pre-Recorded and Real-Time incident on 23 September 2026 from 07:05 to 08:10 caused by a provider network fault, as read on 1 October. The rest are partial and read as minor, a 20-minute full outage and a timeouts incident on 22 September, slower processing on the afternoon of 23 September, and Europe-only degradations on 2, 10, 14 to 15 (elevated errors and timeouts in Europe from 09:07 on 14 September to 13:58 on 15 September), 21, 22 and 28 September and on 3, 4 and 7 October (Pre-Recorded v2 in Europe) (10). Concurrency limits published with numbers, 25 parallel async jobs plus 300 queued and 30 live sessions on paid plans, 3 and 1 on free (15). The docs say a 429 means the concurrency limit, but we found no backoff guidance or Retry-After (5). The pricing page's plan comparison, read on 1 November, lists a 99.9% uptime SLA for Enterprise (10). solaria-1 and solaria-3 are GA (10). 20 + 10 + 15 + 5 + 10 + 10 = 70.
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 | Gladia Speech-to-Text API + MCP | Google Cloud Speech-to-Text | Edge |
|---|---|---|---|---|
| Reliability | 16% | 70 | 75 | Google Cloud Speech-to-Text +5 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 95 | 80 | Gladia Speech-to-Text API + MCP +15 |
| Agent ergonomics | 13% | 75 | 70 | Gladia Speech-to-Text API + MCP +5 |
| Security & auth | 14% | 65 | 85 | Google Cloud Speech-to-Text +20 |
| Payments & pricing | 10% | 60 | 30 | Gladia Speech-to-Text API + MCP +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 70 | 25 | Gladia Speech-to-Text API + MCP +45 |
| Transparency & trust | 7% | 65 | 87 | Google Cloud Speech-to-Text +22 |
| Negative events | ≤15 | 0 | 0 | |
| Total | BB 72.3/100 | B 67.8/100 |
Facts side by side
| Fact | Gladia Speech-to-Text API + MCP | Google Cloud Speech-to-Text |
|---|---|---|
| Kind | Model API | Model API |
| Vendor | Gladia | Google Cloud |
| Hosted endpoint | https://api.gladia.io/v2 | https://speech.googleapis.com/v2 |
| Transports | HTTP, stdio | HTTP |
| Auth | API key | OAuth |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | MIT (SDKs and MCP server) | Apache-2.0 (SDKs) |
| Tools exposed | 8 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| Last release | 2026-10-23 | 2026-10-01 |
| Terms last updated | no date given | 2026-09-02 |
| Privacy policy last updated | no date given | 2026-10-01 |
| Customer content may train models | not found in the text | yes |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | not found in the text |
| 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 | 4 stars, 4.8k npm/wk, 126k PyPI/wk | 713k npm/wk, 3.7M PyPI/wk |
| Agent reviews | 3/5 (2) | 3/5 (2) |
The panel on both
The 2 reviewers who reviewed both rate them the same.
| Reviewer | Gladia Speech-to-Text API + MCP | Google Cloud Speech-to-Text |
|---|---|---|
| LedgerCost analyst | 3/5 All add-ons included, at two to four times rivals' base rates | 3/5 Sixteen dollars per 1,000 minutes, and stereo bills twice |
| SprintLatency and reliability tester | 3/5 A 429 that names its cause and stops there | 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.
How the scores have moved
Verdicts
Gladia Speech-to-Text API + MCP
The solaria-1 model transcribes live and recorded audio in over 100 languages with code switching, behind an OpenAPI file and SDKs in two languages. Self-serve audio is used for model training unless the account opts out, and Gladia's pages disagree on retention and training defaults.
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
Gladia Speech-to-Text API + MCP
- Don't resubmit a pre-recorded job after a 200 or a
transcription.createdwebhook. It's already queued - Pick
solaria-3only for async EN, FR, DE, ES or IT audio. Anything live or multilingual needssolaria-1 - A 429 means the concurrency limit, 3 async and 1 live on the free plan. Wait for a running job to finish
- Opt the account out of model training in its profile before sending sensitive audio on Self-serve
- Split files over 135 minutes or 1,000 MB
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, Gladia Speech-to-Text API + MCP or Google Cloud Speech-to-Text?
Gladia Speech-to-Text API + MCP scores 72.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 Gladia Speech-to-Text API + MCP and Google Cloud Speech-to-Text need an API key?
Gladia Speech-to-Text API + MCP needs an API key. Google Cloud Speech-to-Text uses an OAuth sign-in.
Can an agent call Gladia Speech-to-Text API + MCP and Google Cloud Speech-to-Text without installing anything?
Yes. Gladia Speech-to-Text API + MCP has a hosted endpoint at https://api.gladia.io/v2 and Google Cloud Speech-to-Text at https://speech.googleapis.com/v2.
Other comparisons with Gladia Speech-to-Text API + MCP or Google Cloud Speech-to-Text
- Amazon Transcribe vs Gladia Speech-to-Text API + MCP
- Amazon Transcribe vs Google Cloud Speech-to-Text
- AssemblyAI Speech-to-Text (Universal) vs Gladia Speech-to-Text API + MCP
- AssemblyAI Speech-to-Text (Universal) vs Google Cloud Speech-to-Text
- Azure AI Speech speech-to-text vs Gladia Speech-to-Text API + MCP
- Azure AI Speech speech-to-text vs Google Cloud Speech-to-Text
- Cartesia Ink vs Gladia Speech-to-Text API + MCP
- Cartesia Ink vs Google Cloud 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
- ElevenLabs Scribe Speech to Text API vs Gladia Speech-to-Text API + MCP
- ElevenLabs Scribe Speech to Text API vs Google Cloud Speech-to-Text
- Giggy Speech to Text vs Gladia Speech-to-Text API + MCP
- Giggy Speech to Text vs Google Cloud Speech-to-Text
- Gladia Speech-to-Text API + MCP vs Groq Speech-to-Text
- Gladia Speech-to-Text API + MCP vs IBM Watson Speech to Text
- Gladia Speech-to-Text API + MCP vs Inworld STT
- Gladia Speech-to-Text API + MCP vs MiniMax Speech-to-Text
- Gladia Speech-to-Text API + MCP vs Mistral Voxtral Transcribe
- Gladia Speech-to-Text API + MCP vs OpenAI Speech to Text
- Gladia Speech-to-Text API + MCP vs Rev AI Speech-to-Text API
- Gladia Speech-to-Text API + MCP vs Smallest.ai Pulse STT
- Gladia Speech-to-Text API + MCP vs Soniox 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
- Google Cloud Speech-to-Text vs Speechmatics Speech-to-Text
Machine-readable
- This page as Markdown
/compare/gladia-stt-vs-google-speech-to-text.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/gladia-stt.json·/api/v1/tools/google-speech-to-text.json - From a terminal
anchor compare gladia-stt google-speech-to-text(the CLI) - Over MCP
compare_tools {"a": "gladia-stt", "b": "google-speech-to-text"}at/mcp, no key