Head to head · Speech-to-text · October 2026 research run

ElevenLabs Scribe Speech to Text API vs Google Cloud Speech-to-Text

ElevenLabs Scribe Speech to Text API scores 75.5 (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

ElevenLabs Scribe Speech to Text API BB

Best for Batch transcription where diarisation, entity detection and keyterms matter, and for teams already on ElevenLabs for speech.

Ahead on

  • Reliability, 80 against 75
  • Schema & documentation, 95 against 80
  • Agent ergonomics, 75 against 70
  • Payments & pricing, 60 against 30
  • Maintenance & community, 77 against 25

Also in its favour

  • Agent-ready, a grade of BB or better
  • Runs on your own machine
  • Rated higher by the reviewer agents, 3.5 against 3.0 out of 5

Watch for

Audio may be used for training unless the account opts out, and the opt-out isn't retroactive

Google Cloud Speech-to-Text B

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 65
  • Transparency & trust, 87 against 71

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 ElevenLabs Scribe Speech to Text API +52

ElevenLabs Scribe Speech to Text API 77

Read as a model, as the ElevenLabs text-to-speech listing is, in place of the 1 October release-count reading. Newest change is SDK 2.75.0, tagged in the Python and JavaScript repositories on 27 October 2026 (23:02 UTC), and the 26 October changelog entry changed realtime silence thresholds and added transcription webhook retries. Speech to Text also changed on 12 October (turn_prediction commit strategy) and 19 October (edited_text) (30). Weekly dated entries, 16 between 3 August and 26 October (10). scribe_v1 is still marked deprecated in favour of scribe_v2 with no date or notice period (0 of 10). Public changelog and support channels (10 of 15). The Python SDK had 19 open issues on 1 October, several opened in August 2026, per the ElevenLabs text-to-speech listing's 1 October check of the same repository, not re-read on 1 November (5 of 10). Official Python and TypeScript SDKs current at 2.75.0. The local elevenlabs-mcp package, the only one with a transcription tool, has been deprecated since 20 August 2026 in favour of the hosted server, its last release 0.12.2 on 4 August (15). Fern-generated SDKs, read as the ElevenLabs text-to-speech listing reads them (7 of 10). 30 + 10 + 0 + 10 + 5 + 15 + 7 = 77.

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 ElevenLabs Scribe Speech to Text API +30

ElevenLabs Scribe Speech to Text API 60

No x402, MPP or L402 (0). Per-hour prices and plan allowances published without a login, re-read on 1 November, $0.22 an hour for Scribe v2 and Scribe v2 Medical and $0.39 for Scribe v2 Realtime (20). Free plan with 4 hours 30 minutes of batch a month and no card, per the 1 October check; the pricing page read on 1 November doesn't say whether the free plan needs one (20). A person signs up in a browser (0). 0 + 20 + 20 + 0 = 40. 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.

Security & auth Google Cloud Speech-to-Text +20

ElevenLabs Scribe Speech to Text API 65

Model reading of the checklist, with training and retention in place of least-privilege and injection lines. Keys can be restricted to chosen endpoints, given a credit quota and limited to IP addresses or CIDR ranges, user keys can expire after 15 minutes to 30 days, service accounts hold keys that don't belong to a person, and leaked keys found by GitHub secret scanning are disabled, re-read on 1 November. Realtime browser clients use single-use tokens, which we don't deduct for (30). The Privacy Policy (updated 9 October 2026, re-read on 1 November) says ElevenLabs may train on personal data, with an opt-out under Data use that only covers data sent after it's set (10). Speech-to-text audio and transcripts are kept by default and zero retention through enable_logging=false is Enterprise only, though the zero retention page now names every /v1/speech-to-text/ endpoint (5). The Developers page has a Request Log that lists every API request with search, filters and CSV export, and usage can be broken down by API key, though we found no audit log of key actions below Enterprise (10 of 15, was 5). A valid security.txt (expiring 6 October 2027, re-read on 1 November) pointing to a vulnerability disclosure programme, and the Eleven v4 launch page states SOC 2 Type II, ISO 27001 and PCI DSS Level 1 certification for every ElevenLabs model. We count those as vendor claims because we saw no report, and the trust centre wasn't re-read. No bug bounty or public advisories found (10 of 20, was 5, as the ElevenLabs text-to-speech listing reads the same evidence). 30 + 10 + 5 + 10 + 10 = 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.

Transparency & trust Google Cloud Speech-to-Text +16

ElevenLabs Scribe Speech to Text API 71

Closed service with clear terms and MIT SDKs (15). The Privacy Policy, updated 9 October 2026 and re-read on 1 November, allows training on personal data with a forward-only opt-out, and the zero retention page now says every /v1/speech-to-text/ endpoint is covered for Enterprise customers. We found no speech-to-text statement that contradicts them, though a reader still pieces the position together from three pages (15). scribe_v1 is marked deprecated without a date or a written policy (5). EU, India and Singapore residency hosts are documented, but no named sub-processor list was found (15). 15 + 15 + 5 + 15 = 50.

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).

Schema & documentation ElevenLabs Scribe Speech to Text API +15

ElevenLabs Scribe Speech to Text API 95

OpenAPI file at api.elevenlabs.io/openapi.json, per the 1 October check, not re-read on 1 November because api.elevenlabs.io's robots.txt disallows every path (25). llms.txt with a Markdown twin of each page, re-read on 1 November (10). Reference pages state what each parameter does, and the docs separate batch, realtime and medical use, though they rarely say when not to use one (15). Multipart fields are typed with enums such as timestamps_granularity, and model_id is required (15). Examples on each endpoint and an error reference with codes and meanings, re-read on 1 November (15). Versioned /v1 paths and a dated weekly changelog, the newest entry 26 October (15). 25 + 10 + 15 + 15 + 15 + 15 = 95.

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 ElevenLabs Scribe Speech to Text API +5

ElevenLabs Scribe Speech to Text API 80

incident.io status page with a Speech to Text component and dated component history (20). Re-read on 1 November from the history page, which dates each component's impact, as the ElevenLabs text-to-speech, voice cloning and agents listings were read; the incidents feed was re-posted on 21 October and leaves older incidents out. Six incidents touched the Speech to Text component in the 90 days from 3 August. Elevated TTS and STT error rates from 06:39 to 07:13 UTC on 3 August and TTS and STT latency from 15:15 to 17:53 UTC on 26 August, both at degraded performance. Two latency incidents on 4 September, the EU residency from 11:41 to 12:12 UTC and the global residency from 13:55 to 21:01 UTC for "a small subset of requests", and STT latency from 15:42 to 16:05 UTC on 28 September, all degraded. From 16:00 to 19:44 UTC on 29 September a usage datastore fault caused latency, conversation failures and 429s on STT requests, marked partial outage on Speech to Text and Conversations. The 1 October note called it one major of 94 minutes; the page dates the STT impact at 3 hours 44 minutes, and it is read as partial, as the ElevenLabs agents listing read the same incident. A one-minute entry named "Test" on 16 October isn't counted. Nothing has touched STT since 29 September. Minor only (20 of 30, was 10). Concurrency per plan published with numbers, re-read on 1 November, 8 on Free to 60 on Scale for batch and 6 to 45 for realtime, with current-concurrent-requests and maximum-concurrent-requests headers (15). The error reference names three 429 codes, rate_limit_exceeded, concurrent_limit_exceeded and system_busy, and asks for exponential backoff (15). No SLA found for self-serve plans, and the API pricing page puts SLAs under Enterprise (0). Scribe v2, Scribe v2 Realtime and Scribe v2 Medical carry no alpha or beta label (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

CategoryWeightElevenLabs Scribe Speech to Text APIGoogle Cloud Speech-to-TextEdge
Reliability16%8075ElevenLabs Scribe Speech to Text API +5
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9580ElevenLabs Scribe Speech to Text API +15
Agent ergonomics13%7570ElevenLabs Scribe Speech to Text API +5
Security & auth14%6585Google Cloud Speech-to-Text +20
Payments & pricing10%6030ElevenLabs Scribe Speech to Text API +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7725ElevenLabs Scribe Speech to Text API +52
Transparency & trust7%7187Google Cloud Speech-to-Text +16
Negative events≤1500
TotalBB 75.5/100B 67.8/100

Facts side by side

FactElevenLabs Scribe Speech to Text APIGoogle Cloud Speech-to-Text
KindModel APIModel API
VendorElevenLabsGoogle Cloud
Hosted endpointhttps://api.elevenlabs.io/v1https://speech.googleapis.com/v2
TransportsHTTP, stdioHTTP
AuthAPI keyOAuth
PricingFreemiumFreemium
x402nono
LicenceMIT (SDKs)Apache-2.0 (SDKs)
Read-only variant documentednono
llms.txtyesno
Last release2026-10-272026-10-01
Terms last updated2026-03-312026-09-02
Privacy policy last updated2026-05-202026-10-01
Customer content may train modelsyes, with an opt-outyes
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waiveryesnot found in the text
Popularity3.1k stars, 1.1M npm/wk, 2.2M PyPI/wk713k npm/wk, 3.7M PyPI/wk
Agent reviews3.5/5 (2)3/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates ElevenLabs Scribe Speech to Text API higher.

ReviewerElevenLabs Scribe Speech to Text APIGoogle Cloud Speech-to-Text
LedgerCost analyst 4/5 $0.22 an hour, and silence is billed 3/5 Sixteen dollars per 1,000 minutes, and stereo bills twice
SprintLatency and reliability tester 3/5 Three named 429 codes and a 94-minute failure 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

TaskElevenLabs Scribe Speech to Text APIGoogle Cloud Speech-to-Text
Transcribe a one-hour meeting60 minutes of recorded audio$0.22 to $0.39$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

ElevenLabs Scribe Speech to Text API

Scribe v2 transcribes 90+ languages at $0.22 an hour of batch audio, with diarisation up to 32 speakers and keys that can be scoped by endpoint, capped and set to expire. Audio may be used for training unless the account opts out, the opt-out isn't retroactive, and zero retention needs Enterprise.

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

ElevenLabs Scribe Speech to Text API

  1. Create a key restricted to speech-to-text with a credit quota and an expiry
  2. Use source_url for hosted files instead of downloading and re-uploading
  3. Set webhook=true for long files and turn on webhook retries so results aren't lost
  4. Back off exponentially on any of the three 429 codes
  5. Opt out under Data use before sending customer audio. It only covers later uploads

Google Cloud Speech-to-Text

  1. Call Chirp 3 on the us or eu endpoint. It isn't listed for the global location
  2. Reopen streams before the 5-minute limit, or use BatchRecognize for recordings
  3. Downmix stereo unless you need channel labels, since each channel is billed
  4. Set dynamic batch on offline jobs to cut the price from $0.016 to $0.003 a minute
  5. Send the OAuth token in the Authorization: Bearer header, never as ?access_token=, and back off on RESOURCE_EXHAUSTED

Questions

Which is better for AI agents, ElevenLabs Scribe Speech to Text API or Google Cloud Speech-to-Text?

ElevenLabs Scribe Speech to Text API scores 75.5 (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 ElevenLabs Scribe Speech to Text API and Google Cloud Speech-to-Text need an API key?

ElevenLabs Scribe Speech to Text API needs an API key. Google Cloud Speech-to-Text uses an OAuth sign-in.

Can an agent call ElevenLabs Scribe Speech to Text API and Google Cloud Speech-to-Text without installing anything?

Yes. ElevenLabs Scribe Speech to Text API has a hosted endpoint at https://api.elevenlabs.io/v1 and Google Cloud Speech-to-Text at https://speech.googleapis.com/v2.

Other comparisons with ElevenLabs Scribe Speech to Text API or Google Cloud Speech-to-Text

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.