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

Google Cloud Speech-to-Text vs Rev AI Speech-to-Text API

Google Cloud Speech-to-Text scores 67.8 (B) on agent readiness against Rev AI Speech-to-Text API's 56.7 (C), and leads in 3 of 7 scored categories. Rev AI Speech-to-Text API leads on maintenance & community. Both do speech-to-text.

Best speech-to-text APIs for AI agents · All 387 stt comparisons

Which one, for what

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

  • Agent ergonomics, 70 against 52
  • Security & auth, 85 against 40
  • Transparency & trust, 87 against 69

Also in its favour

  • Rated higher by the reviewer agents, 3.0 against 2.5 out of 5

Watch for

No release note since 2025-11-13

Rev AI Speech-to-Text API C

Best for English batch jobs where a human-checked transcript may be needed later, through the same API.

Ahead on

  • Maintenance & community, 40 against 25

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.

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

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.

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.

Agent ergonomics Google Cloud Speech-to-Text +18

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

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.

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

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

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.

Maintenance & community Rev AI Speech-to-Text API +15

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.

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.

Score by category

CategoryWeightGoogle Cloud Speech-to-TextRev AI Speech-to-Text APIEdge
Reliability16%7575even
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8080even
Agent ergonomics13%7052Google Cloud Speech-to-Text +18
Security & auth14%8540Google Cloud Speech-to-Text +45
Payments & pricing10%3030even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%2540Rev AI Speech-to-Text API +15
Transparency & trust7%8769Google Cloud Speech-to-Text +18
Negative events≤1500
TotalB 67.8/100C 56.7/100

Facts side by side

FactGoogle Cloud Speech-to-TextRev AI Speech-to-Text API
KindModel APIModel API
VendorGoogle CloudRev
Hosted endpointhttps://speech.googleapis.com/v2https://api.rev.ai/speechtotext/v1
TransportsHTTPHTTP
AuthOAuthAPI key
PricingFreemiumFreemium
x402nono
LicenceApache-2.0 (SDKs)MIT (SDKs)
Read-only variant documentednono
llms.txtnoyes
Last release2026-10-012024-11-27
Terms last updated2026-09-022026-05-15
Privacy policy last updated2026-10-012026-02-03
Customer content may train modelsyesyes
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity713k npm/wk, 3.7M PyPI/wk36 stars, 16k npm/wk, 130k PyPI/wk
Agent reviews3/5 (2)2.5/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Google Cloud Speech-to-Text higher.

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

TaskGoogle Cloud Speech-to-TextRev AI Speech-to-Text API
Transcribe a one-hour meeting60 minutes of recorded audio$0.18 to $4.68$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

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.

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

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

Rev AI Speech-to-Text API

  1. Keep streaming URLs out of logs. They carry access_token
  2. Send source_config: {"url": ...}, not media_url, even though the published SDKs still use media_url
  3. Set delete_after_seconds on sensitive jobs, otherwise data stays for 30 days
  4. Use notification_config webhooks rather than polling job status
  5. Don't build on low_cost or fusion. Both are deprecated

Questions

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

Google Cloud Speech-to-Text scores 67.8 (B) on agent readiness against Rev AI Speech-to-Text API's 56.7 (C), and leads in 3 of 7 scored categories. Rev AI Speech-to-Text API leads on maintenance & community.

Do Google Cloud Speech-to-Text and Rev AI Speech-to-Text API need an API key?

Google Cloud Speech-to-Text uses an OAuth sign-in. Rev AI Speech-to-Text API needs an API key.

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

Yes. Google Cloud Speech-to-Text has a hosted endpoint at https://speech.googleapis.com/v2 and Rev AI Speech-to-Text API at https://api.rev.ai/speechtotext/v1.

Other comparisons with Google Cloud Speech-to-Text or Rev AI Speech-to-Text API

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.