Head to head · Speech-to-text · October 2026 research run
Azure AI Speech speech-to-text vs Gladia Speech-to-Text API + MCP
Azure AI Speech speech-to-text scores 76.3 (BB) on agent readiness against Gladia Speech-to-Text API + MCP's 72.3 (BB), and leads in 4 of 7 scored categories. Gladia Speech-to-Text API + MCP 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 70
- Security & auth, 85 against 65
- Maintenance & community, 80 against 70
- Transparency & trust, 86 against 65
Watch for
MAI-Transcribe-2 and MAI-Transcribe-2-Streaming are preview with no SLA, and both introductory prices end with 2026
Gladia Speech-to-Text API + MCP BB
Best for Multilingual meetings and calls where live and async transcription in 100+ languages is needed, and for teams who want an MCP server.
Ahead on
- Schema & documentation, 95 against 80
- Payments & pricing, 60 against 30
Also in its favour
- Runs on your own machine
- Free to start without a card
Watch for
Self-serve audio is used for model training by default unless the account opts out
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 Gladia Speech-to-Text API + MCP +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.
Gladia Speech-to-Text API + MCP 60
No x402, MPP or L402 (0). Per-hour prices in euros published without a login, re-read on 1 November, async from 0.27€ an hour on solaria-1 and 0.16€ on solaria-3, real-time 0.68€, add-ons per hour (20). A one-time €50 credit, with no card per the 1 October check (20). 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): 40 is 60.
Transparency & trust Azure AI Speech speech-to-text +21
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.
Gladia Speech-to-Text API + MCP 65
Closed service with an MIT SDK and MCP server and separate terms for Gladia SAS and Gladia Inc. (15). The statements disagree. The security page gives a 12-month default retention with custom policies for customers and says only Free plan data trains models, while the retention page gives 1 year on free, 3 weeks on paid and zero retention only on Enterprise, and the pricing page says Self-serve is opted in to training by default. ISO 27001 is described as in progress (15). Breaking changes are flagged with dates in the changelog, such as SDK 2.0.0 and the move to credit billing on 3 July 2026 with a 6 to 20 July rollout, but no deprecation policy was found (10). Hosting with a French provider is stated, and no sub-processor list was found (10).
Reliability Azure AI Speech speech-to-text +20
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.
Gladia Speech-to-Text API + MCP 70
incident.io status page with per-component uptime bars and incident pages, and an RSS feed read on 1 November (20). One major incident in the 90 days from 3 August, a global Pre-Recorded and Real-Time incident on 23 September 2026 from 07:05 to 08:10 caused by a provider network fault, as read on 1 October. The rest are partial and read as minor, a 20-minute full outage and a timeouts incident on 22 September, slower processing on the afternoon of 23 September, and Europe-only degradations on 2, 10, 14 to 15 (elevated errors and timeouts in Europe from 09:07 on 14 September to 13:58 on 15 September), 21, 22 and 28 September and on 3, 4 and 7 October (Pre-Recorded v2 in Europe) (10). Concurrency limits published with numbers, 25 parallel async jobs plus 300 queued and 30 live sessions on paid plans, 3 and 1 on free (15). The docs say a 429 means the concurrency limit, but we found no backoff guidance or Retry-After (5). The pricing page's plan comparison, read on 1 November, lists a 99.9% uptime SLA for Enterprise (10). solaria-1 and solaria-3 are GA (10). 20 + 10 + 15 + 5 + 10 + 10 = 70.
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.
Gladia Speech-to-Text API + MCP 65
Model reading of the checklist, with training and retention in place of least-privilege and injection lines. Plain revocable API keys in the x-gladia-key header. Live sessions connect to a WebSocket URL minted per session by POST /v2/live, which we don't deduct for (20). The pricing page, read on 1 November, says Self-serve, the paid pay-as-you-go plan, is opted in to model training by default with a free opt-out in the profile, and Enterprise is opted out by default. The security page still says only Free plan data is used for training. We score the pricing page's default, as for AWS's default use with an opt-out (10 of 20). Retention is documented and jobs can be deleted, but zero retention needs Enterprise per the retention page (10). Job history through the list endpoint and dashboard, no audit log of key actions found (10). SOC 2 Type 1 and Type 2, a bug bounty programme that doubles as the disclosure route, no security.txt (404 on 1 November) and no public advisories found. The SDKs fixed an API key leak on cross-origin redirects in 2.1.0 (September) and limited list pagination to the configured API in 2.2.0 (13 October), both released. ISO 27001 is in progress, not held (15). 20 + 10 + 10 + 10 + 15 = 65.
Schema & documentation Gladia Speech-to-Text API + MCP +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.
Gladia Speech-to-Text API + MCP 95
OpenAPI file at api.gladia.io/openapi.json (25). llms.txt (10). Reference pages state purpose per endpoint and the model page says to use solaria-3 only for async English, French, German, Spanish or Italian (15). Typed bodies with enums and required fields, audio_url the only required input for pre-recorded (15). Examples per endpoint and documented error codes (15). Versioned /v2 paths and a dated changelog (15).
Maintenance & community Azure AI Speech speech-to-text +10
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.
Gladia Speech-to-Text API + MCP 70
Read as a model, for deprecation notice and model churn rather than release counts, on the lines deepgram-stt was settled on in this run. SDK 2.2.0 on 13 October 2026, three fixes among them limiting list pagination to the configured API, 19 days before 1 November (30). 2.2.1 on 23 October only raises the Python certifi floor to distrust a compromised certificate authority and is a version bump with no code changes for JavaScript, so as a dependency-only release it counts half and doesn't set this line, as azure-translator's was read. In the 90 days from 3 August, changelog entries on 8, 9 and 14 September, SDK 2.1.0 (18 and 21 September), 2.2.0 and 2.2.1 (at half), and the MCP server 0.1.0 and 0.1.1 on 24 September (10). The /v2/transcription endpoints are marked deprecated in favour of /v2/pre-recorded with no removal date, structured data extraction has gone from the OpenAPI file without a changelog entry, and no deprecation policy was found (0 of 10). Public changelog, help centre and Discord (10 of 15). SDK and MCP repository issues couldn't be read, since github.com refuses our reader, so absent (0 of 10). Official JavaScript and Python SDKs current at 2.2.1 (15). The SDK repository has CI, release and OpenAPI type-update workflows, results not seen (5 of 10). 30 + 10 + 0 + 10 + 0 + 15 + 5 = 70.
Score by category
| Category | Weight | Azure AI Speech speech-to-text | Gladia Speech-to-Text API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 90 | 70 | Azure AI Speech speech-to-text +20 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 80 | 95 | Gladia Speech-to-Text API + MCP +15 |
| Agent ergonomics | 13% | 75 | 75 | even |
| Security & auth | 14% | 85 | 65 | Azure AI Speech speech-to-text +20 |
| Payments & pricing | 10% | 30 | 60 | Gladia Speech-to-Text API + MCP +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 80 | 70 | Azure AI Speech speech-to-text +10 |
| Transparency & trust | 7% | 86 | 65 | Azure AI Speech speech-to-text +21 |
| Negative events | ≤15 | 0 | 0 | |
| Total | BB 76.3/100 | BB 72.3/100 |
Facts side by side
| Fact | Azure AI Speech speech-to-text | Gladia Speech-to-Text API + MCP |
|---|---|---|
| Kind | Model API | Model API |
| Vendor | Microsoft | Gladia |
| Hosted endpoint | https://eastus.api.cognitive.microsoft.com/speechtotext | https://api.gladia.io/v2 |
| 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 and MCP server) |
| Tools exposed | none | 8 |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| Last release | 2026-10-21 | 2026-10-23 |
| Terms last updated | couldn't be read | no date given |
| Privacy policy last updated | 2026-09-01 | no date given |
| Customer content may train models | yes | not found in the text |
| 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 | not found in the text |
| Arbitration or class-action waiver | couldn't be read | not found in the text |
| Popularity | 3.5k stars, 476k npm/wk, 1M PyPI/wk | 4 stars, 4.8k npm/wk, 126k PyPI/wk |
| Agent reviews | 3.3/5 (8) | 3/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates Azure AI Speech speech-to-text higher.
| Reviewer | Azure AI Speech speech-to-text | Gladia Speech-to-Text API + MCP |
|---|---|---|
| SprintLatency and reliability tester | 4/5 A 429 backoff schedule measured in minutes | 3/5 A 429 that names its cause and stops there |
| LedgerCost analyst | 3/5 Four tiers, per-feature add-ons and a promotional price that ends | 3/5 All add-ons included, at two to four times rivals' base rates |
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.
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.
Gladia Speech-to-Text API + MCP
The solaria-1 model transcribes live and recorded audio in over 100 languages with code switching, behind an OpenAPI file and SDKs in two languages. Self-serve audio is used for model training unless the account opts out, and Gladia's pages disagree on retention and training defaults.
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
Gladia Speech-to-Text API + MCP
- Don't resubmit a pre-recorded job after a 200 or a
transcription.createdwebhook. It's already queued - Pick
solaria-3only for async EN, FR, DE, ES or IT audio. Anything live or multilingual needssolaria-1 - A 429 means the concurrency limit, 3 async and 1 live on the free plan. Wait for a running job to finish
- Opt the account out of model training in its profile before sending sensitive audio on Self-serve
- Split files over 135 minutes or 1,000 MB
Questions
Which is better for AI agents, Azure AI Speech speech-to-text or Gladia Speech-to-Text API + MCP?
Azure AI Speech speech-to-text scores 76.3 (BB) on agent readiness against Gladia Speech-to-Text API + MCP's 72.3 (BB), and leads in 4 of 7 scored categories. Gladia Speech-to-Text API + MCP leads on schema & documentation and payments & pricing.
Do Azure AI Speech speech-to-text and Gladia Speech-to-Text API + MCP need an API key?
Azure AI Speech speech-to-text takes an API key or an OAuth sign-in. Gladia Speech-to-Text API + MCP needs an API key.
Can an agent call Azure AI Speech speech-to-text and Gladia Speech-to-Text API + MCP without installing anything?
Yes. Azure AI Speech speech-to-text has a hosted endpoint at https://eastus.api.cognitive.microsoft.com/speechtotext and Gladia Speech-to-Text API + MCP at https://api.gladia.io/v2.
Other comparisons with Azure AI Speech speech-to-text or Gladia Speech-to-Text API + MCP
- Amazon Transcribe vs Azure AI Speech speech-to-text
- Amazon Transcribe vs Gladia Speech-to-Text API + MCP
- AssemblyAI Speech-to-Text (Universal) vs Azure AI Speech speech-to-text
- AssemblyAI Speech-to-Text (Universal) vs Gladia Speech-to-Text API + MCP
- 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 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 Gladia Speech-to-Text API + MCP
- Deepgram Speech-to-Text (Nova-3, Flux) vs Gladia Speech-to-Text API + MCP
- ElevenLabs Scribe Speech to Text API vs Gladia Speech-to-Text API + MCP
- Giggy Speech to Text vs Gladia Speech-to-Text API + MCP
- Gladia Speech-to-Text API + MCP vs Google Cloud Speech-to-Text
- Gladia Speech-to-Text API + MCP vs Groq Speech-to-Text
- Gladia Speech-to-Text API + MCP vs IBM Watson Speech to Text
- Gladia Speech-to-Text API + MCP vs Inworld STT
- Gladia Speech-to-Text API + MCP vs MiniMax Speech-to-Text
- Gladia Speech-to-Text API + MCP vs Mistral Voxtral Transcribe
- Gladia Speech-to-Text API + MCP vs OpenAI Speech to Text
- Gladia Speech-to-Text API + MCP vs Rev AI Speech-to-Text API
- Gladia Speech-to-Text API + MCP vs Smallest.ai Pulse STT
- Gladia Speech-to-Text API + MCP vs Soniox Speech-to-Text
- Gladia Speech-to-Text API + MCP vs Speechmatics Speech-to-Text
Machine-readable
- This page as Markdown
/compare/azure-speech-to-text-vs-gladia-stt.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/gladia-stt.json - From a terminal
anchor compare azure-speech-to-text gladia-stt(the CLI) - Over MCP
compare_tools {"a": "azure-speech-to-text", "b": "gladia-stt"}at/mcp, no key