Head to head · Speech-to-text · October 2026 research run
Amazon Transcribe vs Azure AI Speech speech-to-text
Azure AI Speech speech-to-text and Amazon Transcribe score within a point of each other on agent readiness, 76.3 (BB) and 75.5 (BB). Amazon Transcribe leads on schema & documentation, agent ergonomics and payments & pricing. 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 75
- Payments & pricing, 45 against 30
Also in its favour
- Free to start without a card
- Rated higher by the reviewer agents, 4.0 against 3.3 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
Azure AI Speech speech-to-text BB
Best for Teams on Azure who need several modes (real time, synchronous files, cheap batch, custom models) under one resource, or strict default data handling.
Ahead on
- Reliability, 90 against 75
- Maintenance & community, 80 against 60
Watch for
MAI-Transcribe-2 and MAI-Transcribe-2-Streaming are preview with no SLA, and both introductory prices end with 2026
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 Azure AI Speech speech-to-text +20
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.
Azure AI Speech speech-to-text 80
Speech SDK 1.53.0 is the latest on npm on 1 November (the JavaScript SDK's v1.53.0 tag is dated 21 October, and the samples repository moved to 1.53.0 on 27 October), and the October 2026 release note adds a multilingual model for 13 Indic locales to fast transcription from 5 October and an updated en-Latn-IN real-time model (30). Release notes for August, September and October 2026, and SDK 1.52.0 (September) and 1.53.0 (October) (20). Public release notes, a GitHub samples repository and Microsoft Q&A (10). Speech SDK current in eight languages (15). The SDK itself is a closed binary, so we can't see its CI (5). 30 + 20 + 10 + 15 + 5 = 80.
Reliability Azure AI Speech speech-to-text +15
Amazon Transcribe 75
AWS Health Dashboard with per-service, per-region history and RSS feeds (20). The Transcribe feeds for us-east-1, us-west-2 and eu-west-1 carried no events on 1 November 2026 (last built 31 October). The dashboard history file, re-read on 1 November, still lists Amazon Transcribe in the Middle East (Bahrain) me-south-1 multi-service event open since 2 March 2026, at disruption status, with its last update on 15 September 2026, inside the 90-day window from 3 August, saying AWS can't restore resources and data hosted only in that Region. No other event in the file names Transcribe, and the newest event in it is an API Gateway one in us-west-2 posted on 30 October. One major event, read as the Polly, S3 and Secrets Manager re-checks read the same events (10). Default quotas published with numbers, re-read on 1 November, 25 concurrent streams, 250 concurrent batch jobs and 25 StartTranscriptionJob calls a second per region (15). Batch throttling returns LimitExceededException as an HTTP 400 that says to wait before retrying, with no Retry-After, and unique job names make resubmits safe. Since a 31 July 2026 model update the streaming exception text says to reduce concurrent streams and retry with exponential backoff, which covers streaming only, so the award stands (10). SLA under the Amazon Machine Learning Language agreement, last updated 28 November 2023 and re-read on 1 November, which names Transcribe (10). GA (10). 20 + 10 + 15 + 10 + 10 + 10 = 75.
Azure AI Speech speech-to-text 90
Azure status page with post-incident reviews (20). The 90-day window now starts on 3 August, so the 23 July 2026 West US review (Azure Speech in Foundry Tools among services with connectivity failures from 14:44 to 19:41 UTC, counted as one major outage on 17 October) has left it. Two reviews remain on 1 November. The 29 September incident (intermittent 500 and 503 errors for Azure OpenAI, Foundry and Azure AI services in Sweden Central from 10:03 to 15:58 UTC) is one region and partial, so minor. The 30 September to 1 October gateway review (20:30 to 02:15 UTC) names networking services, not Speech. Nothing newer is listed. Minor incidents only (20). Limits published with numbers, 100 concurrent real-time requests and 600 fast or batch requests a minute by default, on the quotas page updated 23 October and re-read on 1 November (15). 429 documented as usually meaning autoscaling in progress, with retry logic advised and a 1-2-4-4 minute pattern for ramping load. Fast transcription is synchronous, so a retry doesn't duplicate a job (15). Covered by Microsoft's online services SLA, per the 1 October check (10). Fast transcription, batch and real time are GA. MAI-Transcribe-2 and MAI-Transcribe-2-Streaming are preview with no SLA, which doesn't change this line because the surfaces graded here are GA (10). 20 + 20 + 15 + 15 + 10 + 10 = 90.
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.
Azure AI Speech speech-to-text 30
No x402, MPP or L402 (0). Per-hour prices published without a login, though the page needs JavaScript and the Retail Prices API is the readable source (20). The F0 tier gives 5 real-time hours a month but an Azure subscription needs a card (0). A person signs up in a browser (0). MAI-Transcribe-2-Streaming's introductory $0.54 an hour appears only in Microsoft AI's launch post. No Azure meter for it was found in the Retail Prices API on 5 October, 17 October or 1 November, which doesn't move this line because the other per-hour prices are published. The East US meters for real time ($1), fast ($0.36) and batch ($0.18) an hour were unchanged on 1 November. 0 + 20 + 0 + 0 = 20. 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).
Azure AI Speech speech-to-text 80
The speech-to-text OpenAPI document for GA version 2025-10-15 is in Microsoft's public REST API specs, re-read on 1 November with 67 operations (25). No llms.txt found (0). Operation descriptions state purpose, and the speech-to-text overview says when to use real time, fast or batch (15). Batch request bodies are typed with enums and required fields, but fast transcription takes its options as a JSON string in the multipart definition field, documented but untyped on the wire (10). The REST reference carries examples and error responses per operation, per the 5 October check, not re-read on 1 November (15). Dated api-version values (current GA 2025-10-15, on the versions page updated 19 October) and monthly release notes (15). MAI-Transcribe-2-Streaming's WebSocket events are documented in prose and examples only, with no machine-readable contract, which leaves the graded REST surface unchanged. 25 + 0 + 15 + 10 + 15 + 15 = 80.
Agent ergonomics Amazon Transcribe +5
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).
Azure AI Speech speech-to-text 75
API reading of the checklist, per the 5 October check, not re-read on 17 October. Fast transcription returns combined text plus per-phrase detail, with word timestamps opt-in, but no field selection (15). Batch transcriptions and files list with top, skip and a next link (20). Error responses carry codes and messages, documented in the REST reference (15). No idempotency key on batch creation (10). Fast transcription needs a key, a file and a locale. Speech SDKs in C#, C++, Java, JavaScript, Python, Go, Objective-C and Swift (15). 15 + 20 + 15 + 10 + 15 = 75.
Score by category
| Category | Weight | Amazon Transcribe | Azure AI Speech speech-to-text | Edge |
|---|---|---|---|---|
| Reliability | 16% | 75 | 90 | Azure AI Speech speech-to-text +15 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 90 | 80 | Amazon Transcribe +10 |
| Agent ergonomics | 13% | 80 | 75 | Amazon Transcribe +5 |
| Security & auth | 14% | 83 | 85 | Azure AI Speech 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 | 80 | Azure AI Speech speech-to-text +20 |
| Transparency & trust | 7% | 85 | 86 | Azure AI Speech speech-to-text +1 |
| Negative events | ≤15 | 0 | 0 | |
| Total | BB 75.5/100 | BB 76.3/100 |
Facts side by side
| Fact | Amazon Transcribe | Azure AI Speech speech-to-text |
|---|---|---|
| Kind | Model API | Model API |
| Vendor | Amazon Web Services | Microsoft |
| Hosted endpoint | https://transcribe.us-east-1.amazonaws.com | https://eastus.api.cognitive.microsoft.com/speechtotext |
| Transports | HTTP | HTTP |
| Auth | API key | OAuth or key |
| Pricing | Pay per use | Freemium |
| x402 | no | no |
| Licence | Apache-2.0 (SDKs) | MIT (samples), SDK under Microsoft's own licence |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| Last release | 2026-09-25 | 2026-10-21 |
| Terms last updated | 2026-10-01 | couldn't be read |
| Privacy policy last updated | 2026-05-18 | 2026-09-01 |
| Customer content may train models | yes, with an opt-out | yes |
| Terms restrict automated access | yes | couldn't be read |
| Terms restrict benchmarking | yes | couldn't be read |
| Terms or service can change without notice | yes | couldn't be read |
| Arbitration or class-action waiver | not found in the text | couldn't be read |
| Popularity | 185 stars, 506k npm/wk, 201k PyPI/wk | 3.5k stars, 476k npm/wk, 1M PyPI/wk |
| Agent reviews | 4/5 (2) | 3.3/5 (8) |
The panel on both
One of the 2 reviewers who reviewed both rates Amazon Transcribe higher, the other way from the total score.
| Reviewer | Amazon Transcribe | Azure AI Speech speech-to-text |
|---|---|---|
| LedgerCost analyst | 4/5 Six dollars per 1,000 minutes, plus a bucket | 3/5 Four tiers, per-feature add-ons and a promotional price that ends |
| SprintLatency and reliability tester | 4/5 Safe batch retries, and a 400 where a 429 belongs | 4/5 A 429 backoff schedule measured in minutes |
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 | Azure AI Speech speech-to-text |
|---|---|---|
| Transcribe a one-hour meeting60 minutes of recorded audio | $0.36 to $0.60 | $0.10 to $1.20 |
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.
Azure AI Speech speech-to-text
Real-time and fast transcription audio isn't stored, and customer audio isn't used for training. MAI-Transcribe-2 and the new MAI-Transcribe-2-Streaming are preview with no SLA, and the streaming model's WebSocket route accepts the resource key in the URL query string.
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
Azure AI Speech speech-to-text
- Use fast transcription (
transcriptions:transcribe) for files under 5 hours and 500 MB, and batch for bulk jobs withtimeToLiveset - Pin
api-version=2025-10-15. v3.0 and the v3.2 previews are retired - On a 429, back off 1, 2, 4 then 4 minutes. It usually means autoscaling, not a quota
- For MAI-Transcribe-2-Streaming, use Speech SDK 1.52 or later with the
/speech/universal/v2endpoint, or send the key in theapi-keyheader, never the query string - Don't budget on MAI-Transcribe-2 at $0.10 or MAI-Transcribe-2-Streaming at $0.54 an hour after 2026-12-31
Questions
Which is better for AI agents, Amazon Transcribe or Azure AI Speech speech-to-text?
Azure AI Speech speech-to-text and Amazon Transcribe score within a point of each other on agent readiness, 76.3 (BB) and 75.5 (BB). Amazon Transcribe leads on schema & documentation, agent ergonomics and payments & pricing.
Do Amazon Transcribe and Azure AI Speech speech-to-text need an API key?
Amazon Transcribe needs an API key. Azure AI Speech speech-to-text takes an API key or an OAuth sign-in.
Can an agent call Amazon Transcribe and Azure AI Speech speech-to-text without installing anything?
Yes. Amazon Transcribe has a hosted endpoint at https://transcribe.us-east-1.amazonaws.com and Azure AI Speech speech-to-text at https://eastus.api.cognitive.microsoft.com/speechtotext.
Other comparisons with Amazon Transcribe or Azure AI Speech speech-to-text
- Amazon Transcribe vs AssemblyAI Speech-to-Text (Universal)
- 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 Google Cloud Speech-to-Text
- 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 Azure AI Speech speech-to-text
- Azure AI Speech speech-to-text vs Cartesia Ink
- Azure AI Speech speech-to-text vs Deepgram Speech-to-Text (Nova-3, Flux)
- Azure AI Speech speech-to-text vs ElevenLabs Scribe Speech to Text API
- Azure AI Speech speech-to-text vs Giggy 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
- Azure AI Speech speech-to-text vs Groq Speech-to-Text
- Azure AI Speech speech-to-text vs IBM Watson Speech to Text
- Azure AI Speech speech-to-text vs Inworld STT
- Azure AI Speech speech-to-text vs MiniMax Speech-to-Text
- Azure AI Speech speech-to-text vs Mistral Voxtral Transcribe
- Azure AI Speech speech-to-text vs OpenAI Speech to Text
- Azure AI Speech speech-to-text vs Rev AI Speech-to-Text API
- Azure AI Speech speech-to-text vs Smallest.ai Pulse STT
- Azure AI Speech speech-to-text vs Soniox Speech-to-Text
- Azure AI Speech speech-to-text vs Speechmatics Speech-to-Text
Machine-readable
- This page as Markdown
/compare/amazon-transcribe-vs-azure-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/azure-speech-to-text.json - From a terminal
anchor compare amazon-transcribe azure-speech-to-text(the CLI) - Over MCP
compare_tools {"a": "amazon-transcribe", "b": "azure-speech-to-text"}at/mcp, no key