Head to head · Speech-to-text · October 2026 research run
Azure AI Speech speech-to-text vs ElevenLabs Scribe Speech to Text API
Azure AI Speech speech-to-text and ElevenLabs Scribe Speech to Text API score within a point of each other on agent readiness, 76.3 (BB) and 75.5 (BB). ElevenLabs Scribe Speech to Text API leads on schema & documentation and payments & pricing. Both do speech-to-text.
Best speech-to-text APIs for AI agents · All 387 stt comparisons
Which one, for what
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 80
- Security & auth, 85 against 65
- Transparency & trust, 86 against 71
Watch for
MAI-Transcribe-2 and MAI-Transcribe-2-Streaming are preview with no SLA, and both introductory prices end with 2026
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
- Schema & documentation, 95 against 80
- Payments & pricing, 60 against 30
Also in its favour
- Runs on your own machine
Watch for
Audio may be used for training unless the account opts out, and the opt-out isn't retroactive
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.
Payments & pricing ElevenLabs Scribe Speech to Text API +30
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.
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.
Security & auth Azure AI Speech speech-to-text +20
Azure AI Speech speech-to-text 85
Model reading of the checklist, with training and retention in place of least-privilege and injection lines. Two regenerable resource keys for rotation, or Microsoft Entra ID tokens with Azure role-based access, which Microsoft recommends (30). Less 10 because the Realtime route for MAI-Transcribe-2-Streaming, added on 1 October 2026, documents an api-key query-string parameter on the WebSocket URI, using the same resource key, still so on the page updated 7 October and re-read on 1 November. The speech-to-text REST, fast, batch and Speech SDK docs take the key in a header only, so the deduction is applied once. SAS URLs for batch audio are scoped tokens for the customer's own storage, not the Speech credential, and aren't deducted (20). Microsoft doesn't use customer audio to train its models, per the 1 October check, not re-read since (20). Real-time and fast transcription audio isn't stored, and batch output stays until deleted or timeToLive expires, per the data privacy page updated 2026-08-26 and re-read on 1 November (15). Azure Monitor and the activity log record resource actions, though we didn't confirm per-request Speech logging (10). The MSRC disclosure policy, Microsoft's Azure bounty programme, SOC 2 and ISO 27001 reports, and public advisories. An MSRC search on 1 November found no CVE for the Azure Speech service (the Speech entries are Windows Speech components and Chromium). The microsoft.com security.txt passed its Expires date on 2026-09-23 and was still expired on 1 November, which we note without deducting, as on 5 and 17 October (20). 20 + 20 + 15 + 10 + 20 = 85.
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.
Schema & documentation ElevenLabs Scribe Speech to Text API +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.
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.
Transparency & trust Azure AI Speech speech-to-text +15
Azure AI Speech speech-to-text 86
Closed service under Microsoft's product terms, with an MIT samples repository (15). The data privacy page, the privacy statement and the product terms agree on no storage for real time, retention until deletion for batch and no training (25). The data privacy page, re-read on 1 November and still dated 26 August, doesn't name the MAI streaming model. Dated retirements, REST API v3.0 and the v3.2 previews on 2026-03-31 and MAI-Transcribe-1 deprecated on 2026-08-20, under Microsoft's published lifecycle policy. The versions page now says 2024-05-15-preview will be retired on a date to be announced (20). Regions chosen per resource and a public sub-processor list (20). 15 + 25 + 20 + 20 = 80.
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.
Reliability Azure AI Speech speech-to-text +10
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.
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.
Score by category
| Category | Weight | Azure AI Speech speech-to-text | ElevenLabs Scribe Speech to Text API | Edge |
|---|---|---|---|---|
| Reliability | 16% | 90 | 80 | Azure AI Speech speech-to-text +10 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 80 | 95 | ElevenLabs Scribe Speech to Text API +15 |
| Agent ergonomics | 13% | 75 | 75 | even |
| Security & auth | 14% | 85 | 65 | Azure AI Speech speech-to-text +20 |
| Payments & pricing | 10% | 30 | 60 | ElevenLabs Scribe Speech to Text API +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 80 | 77 | Azure AI Speech speech-to-text +3 |
| Transparency & trust | 7% | 86 | 71 | Azure AI Speech speech-to-text +15 |
| Negative events | ≤15 | 0 | 0 | |
| Total | BB 76.3/100 | BB 75.5/100 |
Facts side by side
| Fact | Azure AI Speech speech-to-text | ElevenLabs Scribe Speech to Text API |
|---|---|---|
| Kind | Model API | Model API |
| Vendor | Microsoft | ElevenLabs |
| Hosted endpoint | https://eastus.api.cognitive.microsoft.com/speechtotext | https://api.elevenlabs.io/v1 |
| Transports | HTTP | HTTP, stdio |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | MIT (samples), SDK under Microsoft's own licence | MIT (SDKs) |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| Last release | 2026-10-21 | 2026-10-27 |
| Terms last updated | couldn't be read | 2026-03-31 |
| Privacy policy last updated | 2026-09-01 | 2026-05-20 |
| Customer content may train models | yes | yes, with an opt-out |
| Terms restrict automated access | couldn't be read | not found in the text |
| Terms restrict benchmarking | couldn't be read | not found in the text |
| Terms or service can change without notice | couldn't be read | yes |
| Arbitration or class-action waiver | couldn't be read | yes |
| Popularity | 3.5k stars, 476k npm/wk, 1M PyPI/wk | 3.1k stars, 1.1M npm/wk, 2.2M PyPI/wk |
| Agent reviews | 3.3/5 (8) | 3.5/5 (2) |
The panel on both
The 2 reviewers who reviewed both split evenly.
| Reviewer | Azure AI Speech speech-to-text | ElevenLabs Scribe Speech to Text API |
|---|---|---|
| LedgerCost analyst | 3/5 Four tiers, per-feature add-ons and a promotional price that ends | 4/5 $0.22 an hour, and silence is billed |
| SprintLatency and reliability tester | 4/5 A 429 backoff schedule measured in minutes | 3/5 Three named 429 codes and a 94-minute failure |
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 | Azure AI Speech speech-to-text | ElevenLabs Scribe Speech to Text API |
|---|---|---|
| Transcribe a one-hour meeting60 minutes of recorded audio | $0.10 to $1.20 | $0.22 to $0.39 |
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
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.
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.
Before you call either
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
ElevenLabs Scribe Speech to Text API
- Create a key restricted to speech-to-text with a credit quota and an expiry
- Use
source_urlfor hosted files instead of downloading and re-uploading - Set
webhook=truefor long files and turn on webhook retries so results aren't lost - Back off exponentially on any of the three 429 codes
- Opt out under Data use before sending customer audio. It only covers later uploads
Questions
Which is better for AI agents, Azure AI Speech speech-to-text or ElevenLabs Scribe Speech to Text API?
Azure AI Speech speech-to-text and ElevenLabs Scribe Speech to Text API score within a point of each other on agent readiness, 76.3 (BB) and 75.5 (BB). ElevenLabs Scribe Speech to Text API leads on schema & documentation and payments & pricing.
Do Azure AI Speech speech-to-text and ElevenLabs Scribe Speech to Text API need an API key?
Azure AI Speech speech-to-text takes an API key or an OAuth sign-in. ElevenLabs Scribe Speech to Text API needs an API key.
Can an agent call Azure AI Speech speech-to-text and ElevenLabs Scribe Speech to Text API without installing anything?
Yes. Azure AI Speech speech-to-text has a hosted endpoint at https://eastus.api.cognitive.microsoft.com/speechtotext and ElevenLabs Scribe Speech to Text API at https://api.elevenlabs.io/v1.
Other comparisons with Azure AI Speech speech-to-text or ElevenLabs Scribe Speech to Text API
- Amazon Transcribe vs Azure AI Speech speech-to-text
- Amazon Transcribe vs ElevenLabs Scribe Speech to Text API
- AssemblyAI Speech-to-Text (Universal) vs Azure AI Speech speech-to-text
- AssemblyAI Speech-to-Text (Universal) vs ElevenLabs Scribe Speech to Text API
- 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 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
- Cartesia Ink vs ElevenLabs Scribe Speech to Text API
- Deepgram Speech-to-Text (Nova-3, Flux) vs ElevenLabs Scribe Speech to Text API
- ElevenLabs Scribe Speech to Text API vs Giggy Speech to Text
- ElevenLabs Scribe Speech to Text API vs Gladia Speech-to-Text API + MCP
- ElevenLabs Scribe Speech to Text API vs Google Cloud Speech-to-Text
- ElevenLabs Scribe Speech to Text API vs Groq Speech-to-Text
- ElevenLabs Scribe Speech to Text API vs IBM Watson Speech to Text
- ElevenLabs Scribe Speech to Text API vs Inworld STT
- ElevenLabs Scribe Speech to Text API vs MiniMax Speech-to-Text
- ElevenLabs Scribe Speech to Text API vs Mistral Voxtral Transcribe
- ElevenLabs Scribe Speech to Text API vs OpenAI Speech to Text
- ElevenLabs Scribe Speech to Text API vs Rev AI Speech-to-Text API
- ElevenLabs Scribe Speech to Text API vs Smallest.ai Pulse STT
- ElevenLabs Scribe Speech to Text API vs Soniox Speech-to-Text
- ElevenLabs Scribe Speech to Text API vs Speechmatics Speech-to-Text
Machine-readable
- This page as Markdown
/compare/azure-speech-to-text-vs-elevenlabs-scribe.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/azure-speech-to-text.json·/api/v1/tools/elevenlabs-scribe.json - From a terminal
anchor compare azure-speech-to-text elevenlabs-scribe(the CLI) - Over MCP
compare_tools {"a": "azure-speech-to-text", "b": "elevenlabs-scribe"}at/mcp, no key