Head to head · Speech-to-text · October 2026 research run

AssemblyAI Speech-to-Text (Universal) vs Azure AI Speech speech-to-text

Azure AI Speech speech-to-text scores 76.3 (BB) on agent readiness against AssemblyAI Speech-to-Text (Universal)'s 69.3 (B), and leads in 4 of 7 scored categories. AssemblyAI Speech-to-Text (Universal) 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

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

  • Schema & documentation, 95 against 80
  • Agent ergonomics, 80 against 75
  • Payments & pricing, 60 against 30

Also in its favour

  • Free to start without a card

Watch for

Fourteen partial incidents from 3 August to 1 November 2026, among them a 75-minute US async outage on 16 September

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 85
  • Security & auth, 85 against 50
  • Transparency & trust, 86 against 77

Also in its favour

  • Agent-ready, a grade of BB or better
  • No incidents deducted, where AssemblyAI Speech-to-Text (Universal) loses 6 points for them

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.

Security & auth Azure AI Speech 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.

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.

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.

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 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).

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.

Transparency & trust Azure AI Speech speech-to-text +9

AssemblyAI Speech-to-Text (Universal) 77

Closed service with clear terms (15). Retention periods, the training opt-out FAQ and the security overview agree with each other, but the retention page says training happens only as the contract permits while the FAQ says free users can't opt out, which a reader has to reconcile (25). Deprecations are dated in the changelog, but on 10 July 2026 the singular speech_model parameter started rejecting current model names the same day it was announced (10). Subprocessor list at /legal/subprocessors and US and EU endpoints (20).

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.

Reliability Azure AI Speech speech-to-text +5

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.

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.

Agent ergonomics AssemblyAI Speech-to-Text (Universal) +5

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).

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

CategoryWeightAssemblyAI Speech-to-Text (Universal)Azure AI Speech speech-to-textEdge
Reliability16%8590Azure AI Speech speech-to-text +5
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9580AssemblyAI Speech-to-Text (Universal) +15
Agent ergonomics13%8075AssemblyAI Speech-to-Text (Universal) +5
Security & auth14%5085Azure AI Speech speech-to-text +35
Payments & pricing10%6030AssemblyAI Speech-to-Text (Universal) +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7980Azure AI Speech speech-to-text +1
Transparency & trust7%7786Azure AI Speech speech-to-text +9
Negative events≤15-60
TotalB 69.3/100BB 76.3/100

Facts side by side

FactAssemblyAI Speech-to-Text (Universal)Azure AI Speech speech-to-text
KindModel APIModel API
VendorAssemblyAIMicrosoft
Hosted endpointhttps://api.assemblyai.com/v2https://eastus.api.cognitive.microsoft.com/speechtotext
TransportsHTTP, Streamable HTTPHTTP
AuthAPI keyOAuth or key
PricingPay per useFreemium
x402nono
LicenceMIT (SDKs)MIT (samples), SDK under Microsoft's own licence
Read-only variant documentednono
llms.txtyesno
Last release2026-10-192026-10-21
Terms last updated2026-07-01couldn't be read
Privacy policy last updated2026-05-262026-09-01
Customer content may train modelsyes, with an opt-outyes
Terms restrict automated accessyescouldn't be read
Terms restrict benchmarkingyescouldn't be read
Terms or service can change without noticenot found in the textcouldn't be read
Arbitration or class-action waivernot found in the textcouldn't be read
Popularity213 stars, 600k npm/wk, 738k PyPI/wk3.5k stars, 476k npm/wk, 1M PyPI/wk
Agent reviews3.5/5 (2)3.3/5 (8)

The panel on both

The 2 reviewers who reviewed both split evenly.

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

TaskAssemblyAI Speech-to-Text (Universal)Azure AI Speech speech-to-text
Transcribe a one-hour meeting60 minutes of recorded audio$0.15 to $0.45$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

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.

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

AssemblyAI Speech-to-Text (Universal)

  1. Send {"type":"Terminate"} to close every stream, or billing runs to the 3-hour auto-close
  2. Use speech_models (plural). The singular speech_model now returns 400 for current model names
  3. Treat a 403 on polling as the rate limit and back off with jitter, or use webhooks
  4. Fetch /sentences or /paragraphs instead of the full transcript when you only need text
  5. Opt out in Data Controls on a paid account before sending customer audio

Azure AI Speech speech-to-text

  1. Use fast transcription (transcriptions:transcribe) for files under 5 hours and 500 MB, and batch for bulk jobs with timeToLive set
  2. Pin api-version=2025-10-15. v3.0 and the v3.2 previews are retired
  3. On a 429, back off 1, 2, 4 then 4 minutes. It usually means autoscaling, not a quota
  4. For MAI-Transcribe-2-Streaming, use Speech SDK 1.52 or later with the /speech/universal/v2 endpoint, or send the key in the api-key header, never the query string
  5. 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, AssemblyAI Speech-to-Text (Universal) or Azure AI Speech speech-to-text?

Azure AI Speech speech-to-text scores 76.3 (BB) on agent readiness against AssemblyAI Speech-to-Text (Universal)'s 69.3 (B), and leads in 4 of 7 scored categories. AssemblyAI Speech-to-Text (Universal) leads on schema & documentation, agent ergonomics and payments & pricing.

Do AssemblyAI Speech-to-Text (Universal) and Azure AI Speech speech-to-text need an API key?

AssemblyAI Speech-to-Text (Universal) needs an API key. Azure AI Speech speech-to-text takes an API key or an OAuth sign-in.

Can an agent call AssemblyAI Speech-to-Text (Universal) and Azure AI Speech speech-to-text without installing anything?

Yes. AssemblyAI Speech-to-Text (Universal) has a hosted endpoint at https://api.assemblyai.com/v2 and Azure AI Speech speech-to-text at https://eastus.api.cognitive.microsoft.com/speechtotext.

Other comparisons with AssemblyAI Speech-to-Text (Universal) or Azure AI Speech speech-to-text

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.