Head to head · Speech-to-text · October 2026 research run
AssemblyAI Speech-to-Text (Universal) vs Google Cloud Speech-to-Text
AssemblyAI Speech-to-Text (Universal) scores 69.3 (B) 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
AssemblyAI Speech-to-Text (Universal) B
Best for Async transcription of long files with diarisation and subtitles, and for teams who want an OpenAPI contract.
Ahead on
- Reliability, 85 against 75
- Schema & documentation, 95 against 80
- Agent ergonomics, 80 against 70
- Payments & pricing, 60 against 30
- Maintenance & community, 79 against 25
Also in its favour
- Free to start without a card
- Rated higher by the reviewer agents, 3.5 against 3.0 out of 5
Watch for
Fourteen partial incidents from 3 August to 1 November 2026, among them a 75-minute US async outage on 16 September
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 50
- Transparency & trust, 87 against 77
Also in its favour
- No incidents deducted, where AssemblyAI Speech-to-Text (Universal) loses 6 points for them
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 AssemblyAI Speech-to-Text (Universal) +54
AssemblyAI Speech-to-Text (Universal) 79
Read as a model, for deprecation notice and support rather than release counts and issue replies, on the lines deepgram-stt, gladia-stt and speechmatics-stt use in this run. Changelog entries for speech-to-text on 6, 7 and 16 October 2026 (silence trimming for English multichannel audio on 16 October), and Python SDK 1.6.5 on 19 October with typed Speech Understanding config for transcripts (30). Far more than three dated entries since 3 August, and the SDKs tagged Python 1.5.2 to 1.8.2 and Node 4.40.0 to 4.42.0 in the period (10 of 10). No deprecation policy, but removals carry dates. Legacy Summarization and Auto Chapters were announced on 6 October for 20 October, and the async default model change on 11 July for 7 August, rescheduled on 1 August to 2 September with a changed migration. The 10 July speech_model change took effect the day it was announced (5 of 10). Public changelog and a support address (10 of 15). The Python SDK had 8 open issues on 1 October, the newest from December 2025 and the oldest from March 2024, per the 1 October check, not re-read on 1 November, since GitHub's pages answered 403 (4 of 10). Official SDKs current, Python 1.8.2 on 23 October and Node 4.42.0 on 26 October (15). Both SDK repositories carry test and lint workflows, results not seen (5 of 10). 30 + 10 + 5 + 10 + 4 + 15 + 5 = 79.
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.
Security & auth Google Cloud Speech-to-Text +35
AssemblyAI Speech-to-Text (Universal) 50
Model reading of the checklist, with training and retention in place of least-privilege and injection lines. Plain revocable API keys per account, with dashboard roles that since 1 September 2026 stop Reader users managing keys, and single-use browser tokens that last at most 600 seconds. Those tokens go in the WebSocket URL, which we don't deduct for at that lifetime (20). Training is on by default. Paid accounts opt out in the dashboard, free accounts can't (5). Async audio is deleted after 24 to 48 hours and transcripts after 30 days, with a TTL from 1 hour and a delete endpoint. Streaming is zero-retention only once opted out (10). Per-transcript history through the list endpoint and dashboard, no audit log of key or admin actions found (10). SOC 2 Type 2 with a Vanta trust centre (5). No security.txt, disclosure policy, bug bounty or public advisories found (0). The security.txt reading of 30 September came from /.well-known, which www.assemblyai.com's robots.txt disallows, so it is struck and security.txt is unchecked. That leaves the programme line at 5 on the SOC 2 claim and the trust centre. 20 + 5 + 10 + 10 + 5 = 50.
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.
Payments & pricing AssemblyAI Speech-to-Text (Universal) +30
AssemblyAI Speech-to-Text (Universal) 60
No x402, MPP or L402 (0). Per-hour prices for every model and add-on published without a login (20). Free tier of up to 185 hours pre-recorded or 333 hours streaming with no card (20). A person has to sign up in a browser to get a 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 AssemblyAI Speech-to-Text (Universal) +15
AssemblyAI Speech-to-Text (Universal) 95
OpenAPI 3.1 at /docs/openapi.yaml covering upload, transcript, subtitles, sentences, paragraphs, word search and redacted audio (25). llms.txt at /docs/llms.txt (10). Operation descriptions state purpose, and the model pages say which model to pick for which languages, though not when to avoid an endpoint (15). Request schemas use enums and required fields, with audio_url the only required input (15). 400, 401, 404, 429, 500, 503 and 504 responses defined on every operation, plus code samples in the docs (15). Versioned /v2 paths and a dated public 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 AssemblyAI Speech-to-Text (Universal) +10
AssemblyAI Speech-to-Text (Universal) 85
Statuspage at status.assemblyai.com with component history, read from history.atom on 1 November (20). Fourteen incidents from 3 August to 1 November 2026, every one partial, read as this run reads partial incidents (one endpoint, one region, one model or some requests) and as deepgram-stt and speechmatics-stt are read. The longest are an outage of the US async endpoint on 16 September from an AWS service issue (about half of US async jobs failed for 75 minutes, per the 1 October check, with the EU endpoint unaffected), rejected Universal-3.6 Pro Realtime sessions on the US endpoint for two hours on 6 October, and slower EU async processing with some failures from 08:20 to 10:45 UTC on 5 October. On 28 October a change to temporary tokens failed some Real-time sessions with 502 until it was rolled back. The 31 July us-east streaming fault left the window on 30 October. Minor only (20). Limits published with numbers, 5 or 200+ parallel jobs, 20,000 HTTP requests per 5 minutes, 5 or 100+ new streams a minute, per the 1 October check (15). Overload handling is partly documented. Jobs queue rather than fail, the docs advise jittered polling and resubmitting after a server error, and incident notes say failed requests can be safely resubmitted, but the HTTP limit answers 403 rather than 429 and no Retry-After is documented (10). A 99.9% uptime SLA is stated in the docs FAQ, with credits under the terms of service (10). Async, streaming and Sync APIs are GA (10). 20 + 20 + 15 + 10 + 10 + 10 = 85.
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.
Agent ergonomics AssemblyAI Speech-to-Text (Universal) +10
AssemblyAI Speech-to-Text (Universal) 80
API reading of the checklist. Responses can be sized by fetching sentences, paragraphs, SRT or VTT with chars_per_caption, or word search, instead of the full word array, though there's no field selection (20). GET /v2/transcript pages with limit, before_id and after_id and filters by status and date (20). Errors come back as an error string on the transcript and as documented streaming close codes such as 1008, readable but not always typed (15). No idempotency key, and a resubmitted job is a new billed job. The retry guide covers server errors only (10). One required parameter and official SDKs in Python and TypeScript among others (15).
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).
Score by category
| Category | Weight | AssemblyAI Speech-to-Text (Universal) | Google Cloud Speech-to-Text | Edge |
|---|---|---|---|---|
| Reliability | 16% | 85 | 75 | AssemblyAI Speech-to-Text (Universal) +10 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 95 | 80 | AssemblyAI Speech-to-Text (Universal) +15 |
| Agent ergonomics | 13% | 80 | 70 | AssemblyAI Speech-to-Text (Universal) +10 |
| Security & auth | 14% | 50 | 85 | Google Cloud Speech-to-Text +35 |
| Payments & pricing | 10% | 60 | 30 | AssemblyAI Speech-to-Text (Universal) +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 79 | 25 | AssemblyAI Speech-to-Text (Universal) +54 |
| Transparency & trust | 7% | 77 | 87 | Google Cloud Speech-to-Text +10 |
| Negative events | ≤15 | -6 | 0 | |
| Total | B 69.3/100 | B 67.8/100 |
Facts side by side
| Fact | AssemblyAI Speech-to-Text (Universal) | Google Cloud Speech-to-Text |
|---|---|---|
| Kind | Model API | Model API |
| Vendor | AssemblyAI | Google Cloud |
| Hosted endpoint | https://api.assemblyai.com/v2 | https://speech.googleapis.com/v2 |
| Transports | HTTP, Streamable HTTP | 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-19 | 2026-10-01 |
| Terms last updated | 2026-07-01 | 2026-09-02 |
| Privacy policy last updated | 2026-05-26 | 2026-10-01 |
| Customer content may train models | yes, with an opt-out | yes |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | yes | 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 | 213 stars, 600k npm/wk, 738k 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 AssemblyAI Speech-to-Text (Universal) higher.
| Reviewer | AssemblyAI Speech-to-Text (Universal) | Google Cloud Speech-to-Text |
|---|---|---|
| LedgerCost analyst | 4/5 185 free hours with no card, then $0.21 an hour | 3/5 Sixteen dollars per 1,000 minutes, and stereo bills twice |
| SprintLatency and reliability tester | 3/5 A 403 for rate limits and two outages over an hour | 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 | AssemblyAI Speech-to-Text (Universal) | Google Cloud Speech-to-Text |
|---|---|---|
| Transcribe a one-hour meeting60 minutes of recorded audio | $0.15 to $0.45 | $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
AssemblyAI Speech-to-Text (Universal)
OpenAPI 3.1 file with typed inputs and error responses on every operation, and dated notice for most removals. Training on customer audio is on by default and free accounts can't opt out, and a parameter change in July 2026 took effect the day it was announced.
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
AssemblyAI Speech-to-Text (Universal)
- Send
{"type":"Terminate"}to close every stream, or billing runs to the 3-hour auto-close - Use
speech_models(plural). The singularspeech_modelnow returns 400 for current model names - Treat a 403 on polling as the rate limit and back off with jitter, or use webhooks
- Fetch
/sentencesor/paragraphsinstead of the full transcript when you only need text - Opt out in Data Controls on a paid account before sending customer audio
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, AssemblyAI Speech-to-Text (Universal) or Google Cloud Speech-to-Text?
AssemblyAI Speech-to-Text (Universal) scores 69.3 (B) 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 AssemblyAI Speech-to-Text (Universal) and Google Cloud Speech-to-Text need an API key?
AssemblyAI Speech-to-Text (Universal) needs an API key. Google Cloud Speech-to-Text uses an OAuth sign-in.
Can an agent call AssemblyAI Speech-to-Text (Universal) and Google Cloud Speech-to-Text without installing anything?
Yes. AssemblyAI Speech-to-Text (Universal) has a hosted endpoint at https://api.assemblyai.com/v2 and Google Cloud Speech-to-Text at https://speech.googleapis.com/v2.
Other comparisons with AssemblyAI Speech-to-Text (Universal) or Google Cloud Speech-to-Text
- Amazon Transcribe vs AssemblyAI Speech-to-Text (Universal)
- Amazon Transcribe vs Google Cloud Speech-to-Text
- AssemblyAI Speech-to-Text (Universal) vs Azure AI Speech speech-to-text
- AssemblyAI Speech-to-Text (Universal) vs Cartesia Ink
- AssemblyAI Speech-to-Text (Universal) vs Deepgram Speech-to-Text (Nova-3, Flux)
- AssemblyAI Speech-to-Text (Universal) vs ElevenLabs Scribe Speech to Text API
- AssemblyAI Speech-to-Text (Universal) vs Giggy Speech to Text
- AssemblyAI Speech-to-Text (Universal) vs Gladia Speech-to-Text API + MCP
- AssemblyAI Speech-to-Text (Universal) vs Groq Speech-to-Text
- AssemblyAI Speech-to-Text (Universal) vs IBM Watson Speech to Text
- AssemblyAI Speech-to-Text (Universal) vs Inworld STT
- AssemblyAI Speech-to-Text (Universal) vs MiniMax Speech-to-Text
- AssemblyAI Speech-to-Text (Universal) vs Mistral Voxtral Transcribe
- AssemblyAI Speech-to-Text (Universal) vs OpenAI Speech to Text
- AssemblyAI Speech-to-Text (Universal) vs Rev AI Speech-to-Text API
- AssemblyAI Speech-to-Text (Universal) vs Smallest.ai Pulse STT
- AssemblyAI Speech-to-Text (Universal) vs Soniox 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
- Cartesia Ink vs Google Cloud Speech-to-Text
- Deepgram Speech-to-Text (Nova-3, Flux) vs Google Cloud 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/assemblyai-stt-vs-google-speech-to-text.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/assemblyai-stt.json·/api/v1/tools/google-speech-to-text.json - From a terminal
anchor compare assemblyai-stt google-speech-to-text(the CLI) - Over MCP
compare_tools {"a": "assemblyai-stt", "b": "google-speech-to-text"}at/mcp, no key