Head to head · Speech-to-text · October 2026 research run
Amazon Transcribe vs Google Cloud Speech-to-Text
Amazon Transcribe scores 75.5 (BB) on agent readiness against Google Cloud Speech-to-Text's 67.8 (B), and leads in 4 of 7 scored categories. Both do speech-to-text.
Best speech-to-text APIs for AI agents · All 387 stt comparisons
Which one, for what
Best for Teams already on AWS with audio in S3 and IAM in place, especially batch jobs at volume.
Ahead on
- Schema & documentation, 90 against 80
- Agent ergonomics, 80 against 70
- Payments & pricing, 45 against 30
- Maintenance & community, 60 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, 4.0 against 3.0 out of 5
Watch for
AWS may store and use audio to improve the service unless an organisation-wide AI services opt-out policy is set
Best for Google Cloud teams with audio already in Cloud Storage who want no training and no retention by default.
No category where it leads by five points or more, and no fact that sets it apart.
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 Amazon Transcribe +35
Amazon Transcribe 60
Read by the listing's own service models (transcribe and transcribe-streaming), as this run's amazon-s3 re-check read models/s3. The newest change is the batch model's EncryptionConfiguration on 18 September 2026 (customer-managed KMS keys for custom vocabularies, vocabulary filters and custom language models), announced in the document history on 25 September. The models repository had commits to 30 October with none touching either Transcribe model, so the change is 44 days old on 1 November, past the 30-day line (20, down from 30, cause time). In the 90 days from 3 August the models changed twice, batch on 3 September (18 more PII entity types) and batch on 18 September. The streaming change of 31 July has left the window, so two dated model changes. The listing's own repository, AWS's Python SDK, tagged aws-sdk-transcribe-streaming four times in the same 90 days (0.9.0 on 13 August, 0.10.0 on 20 August, 0.11.0 on 24 August and 0.12.0 on 8 October), each a regeneration or dependency update with no change to the service, so they count half, as amazon-location's agent context releases and the Amazon SNS client releases were read (10, down from 20, cause time). Public document history, AWS re:Post and paid support plans (10). Official SDKs are current, @aws-sdk/client-transcribe and -streaming at 3.1161.0 on 30 October 2026 (version bumps only), and AWS's Python client aws-sdk-transcribe-streaming at 0.12.0 on 8 October (15). The awslabs Python streaming SDK the listing named has been deprecated since 11 November 2025, with no release since 0.6.4 in May 2025, and its replacement is marked pre-alpha and needs Python 3.12 or later (5 of 10). 20 + 10 + 10 + 15 + 5 = 60.
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 Amazon Transcribe +15
Amazon Transcribe 45
No x402, MPP or L402 (0). Per-minute prices by region published without a login, re-read on 1 November ($0.006 batch and $0.01 streaming in US East) (20). The pricing page still shows 60 free minutes a month for 12 months, which per the 1 October check applies only to accounts opened before 2025-07-15. Newer accounts get up to $200 in Free Tier credits, and Free Tier FAQ Q4, re-read on 1 November, says a payment method isn't required to sign up for most new customers, though AWS may request one to verify identity. Half, as on the Polly, S3 and Secrets Manager listings (10). A person signs up in a browser. IAM can mint keys by API, but only after a human has an account (0). 0 + 20 + 10 + 0 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.
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 Amazon Transcribe +10
Amazon Transcribe 90
The service model is public in aws/api-models-aws and the AWS SDKs, a machine-readable contract in the role OpenAPI plays (25). llms.txt for the developer guide, 260 lines on 1 November (10). Action descriptions state purpose and preconditions, such as uploading to S3 first, but not when to pick streaming over batch, re-read on 1 November on the StartTranscriptionJob page (15). Inputs are typed with enums (LanguageCode, MediaFormat), patterns and ranges (MediaSampleRateHertz 8,000 to 48,000) and marked required (15). Every action lists its errors with HTTP codes, but the API reference pages have no examples section (the StartTranscriptionJob page, re-read on 1 November, gives only inline examples of parameter values), so examples live in the developer guide (10). API version 2017-10-26 and a dated document history, whose newest entry is still 25 September 2026 (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.
Agent ergonomics Amazon Transcribe +10
Amazon Transcribe 80
API reading of the checklist. The transcript is one JSON file with every item and its timings, with SRT and VTT subtitles as the compact alternative and no field selection, per the 1 October check (15). ListTranscriptionJobs filters by Status and JobNameContains and pages with MaxResults and NextToken, re-read on 1 November (20). Typed exceptions per action, each with a recovery hint (20). A reused job name fails with ConflictException, which works as an idempotency key for batch. Streaming has no resume (15). Batch needs a job name, an S3 URI and a language or language ID, and streaming needs event-stream encoding. SDKs in every major language (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).
Score by category
| Category | Weight | Amazon Transcribe | Google Cloud Speech-to-Text | Edge |
|---|---|---|---|---|
| Reliability | 16% | 75 | 75 | even |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 90 | 80 | Amazon Transcribe +10 |
| Agent ergonomics | 13% | 80 | 70 | Amazon Transcribe +10 |
| Security & auth | 14% | 83 | 85 | Google Cloud Speech-to-Text +2 |
| Payments & pricing | 10% | 45 | 30 | Amazon Transcribe +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 60 | 25 | Amazon Transcribe +35 |
| Transparency & trust | 7% | 85 | 87 | Google Cloud Speech-to-Text +2 |
| Negative events | ≤15 | 0 | 0 | |
| Total | BB 75.5/100 | B 67.8/100 |
Facts side by side
| Fact | Amazon Transcribe | Google Cloud Speech-to-Text |
|---|---|---|
| Kind | Model API | Model API |
| Vendor | Amazon Web Services | Google Cloud |
| Hosted endpoint | https://transcribe.us-east-1.amazonaws.com | https://speech.googleapis.com/v2 |
| Transports | HTTP | HTTP |
| Auth | API key | OAuth |
| Pricing | Pay per use | Freemium |
| x402 | no | no |
| Licence | Apache-2.0 (SDKs) | Apache-2.0 (SDKs) |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| Last release | 2026-09-25 | 2026-10-01 |
| Terms last updated | 2026-10-01 | 2026-09-02 |
| Privacy policy last updated | 2026-05-18 | 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 | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 185 stars, 506k npm/wk, 201k PyPI/wk | 713k npm/wk, 3.7M PyPI/wk |
| Agent reviews | 4/5 (2) | 3/5 (2) |
The panel on both
2 of the 2 reviewers who reviewed both rate Amazon Transcribe higher.
| Reviewer | Amazon Transcribe | Google Cloud Speech-to-Text |
|---|---|---|
| LedgerCost analyst | 4/5 Six dollars per 1,000 minutes, plus a bucket | 3/5 Sixteen dollars per 1,000 minutes, and stereo bills twice |
| SprintLatency and reliability tester | 4/5 Safe batch retries, and a 400 where a 429 belongs | 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 | Amazon Transcribe | Google Cloud Speech-to-Text |
|---|---|---|
| Transcribe a one-hour meeting60 minutes of recorded audio | $0.36 to $0.60 | $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
Amazon Transcribe
Batch transcription costs $0.006 a minute and streaming $0.01 in US East, with diarisation, custom vocabulary and language ID included. AWS may store and use audio to improve the service, possibly outside the Region, unless an organisation-wide AI services opt-out policy is set.
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
Amazon Transcribe
- Give every job a unique
TranscriptionJobName. A retry with the same name fails withConflictExceptionrather than starting a second job - Poll
GetTranscriptionJobor listen on EventBridge, and setOutputBucketName, because job records are deleted after 90 days - Back off on
LimitExceededException. It arrives as a 400, not a 429 - Set the organisation's AI services opt-out policy before sending customer audio
- For Python streaming install
aws-sdk-transcribe-streamingon Python 3.12 or later, not the deprecatedamazon-transcribepackage
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, Amazon Transcribe or Google Cloud Speech-to-Text?
Amazon Transcribe scores 75.5 (BB) on agent readiness against Google Cloud Speech-to-Text's 67.8 (B), and leads in 4 of 7 scored categories.
Do Amazon Transcribe and Google Cloud Speech-to-Text need an API key?
Amazon Transcribe needs an API key. Google Cloud Speech-to-Text uses an OAuth sign-in.
Can an agent call Amazon Transcribe and Google Cloud Speech-to-Text without installing anything?
Yes. Amazon Transcribe has a hosted endpoint at https://transcribe.us-east-1.amazonaws.com and Google Cloud Speech-to-Text at https://speech.googleapis.com/v2.
Other comparisons with Amazon Transcribe or Google Cloud Speech-to-Text
- Amazon Transcribe vs AssemblyAI Speech-to-Text (Universal)
- Amazon Transcribe vs Azure AI Speech speech-to-text
- Amazon Transcribe vs Cartesia Ink
- Amazon Transcribe vs Deepgram Speech-to-Text (Nova-3, Flux)
- Amazon Transcribe vs ElevenLabs Scribe Speech to Text API
- Amazon Transcribe vs Giggy Speech to Text
- Amazon Transcribe vs Gladia Speech-to-Text API + MCP
- Amazon Transcribe vs Groq Speech-to-Text
- Amazon Transcribe vs IBM Watson Speech to Text
- Amazon Transcribe vs Inworld STT
- Amazon Transcribe vs MiniMax Speech-to-Text
- Amazon Transcribe vs Mistral Voxtral Transcribe
- Amazon Transcribe vs OpenAI Speech to Text
- Amazon Transcribe vs Rev AI Speech-to-Text API
- Amazon Transcribe vs Smallest.ai Pulse STT
- Amazon Transcribe vs Soniox Speech-to-Text
- Amazon Transcribe vs Speechmatics Speech-to-Text
- AssemblyAI Speech-to-Text (Universal) vs Google Cloud 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/amazon-transcribe-vs-google-speech-to-text.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/amazon-transcribe.json·/api/v1/tools/google-speech-to-text.json - From a terminal
anchor compare amazon-transcribe google-speech-to-text(the CLI) - Over MCP
compare_tools {"a": "amazon-transcribe", "b": "google-speech-to-text"}at/mcp, no key