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

Azure AI Speech speech-to-text vs Soniox Speech-to-Text

Azure AI Speech speech-to-text scores 76.3 (BB) on agent readiness against Soniox Speech-to-Text's 69.8 (B), and leads in 4 of 7 scored categories. Soniox Speech-to-Text leads on schema & documentation. 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 77
  • Agent ergonomics, 75 against 70
  • Maintenance & community, 80 against 75
  • Transparency & trust, 86 against 76

Also in its favour

  • Agent-ready, a grade of BB or better
  • No incidents deducted, where Soniox Speech-to-Text loses 3 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

Soniox Speech-to-Text B

Best for Price-led multilingual transcription and translation, live or async, and for operators who want no training and no retention.

Ahead on

  • Schema & documentation, 85 against 80

Watch for

No free credits for new accounts since October 2025

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.

Reliability Azure AI Speech speech-to-text +13

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.

Soniox Speech-to-Text 77

Instatus page at status.soniox.com with per-region components and a paged history (20). Minor incidents only since 6 August, with 70 minutes of failed API key creation in the console on 24 August, failed new WebSocket connections to stt-rt.eu.soniox.com between 12:50 and 13:03 UTC on 25 August (existing connections unaffected), and 45 minutes of real-time overload in the Japan region on 8 September ("some customers", partial). October and November have no notices (20). Limits published with numbers, 100 requests a minute, 10 concurrent streams, a connection limit derived from them and a fixed 300-minute stream cap (15). The errors reference documents limit_exceeded as HTTP 429 on REST and the STT WebSocket with what to do for each limit, "retry with exponential backoff" for 503 service_unavailable, and resubmitting failed async jobs, which aren't auto-retried. No idempotency key, so safe-retry guidance without one (12), as soniox-tts. No SLA found (0). stt-rt-v6 and stt-async-v6 are active and the v5 models deprecated, with no preview label (10). 20+20+15+12+0+10 = 77.

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

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.

Soniox Speech-to-Text 76

Closed service with clear terms, last updated 2026-06-29, and an Apache-2.0 Python SDK (15). The security page, limits page and pricing page agree on no training, no default retention and 30-day async deletion (25). Model retirements are dated and old names route to the new model (v5 to v6 on 15 December 2026), though the October 2025 retirement of the preview models was described as accelerated (15). A data residency page names region-specific domains for the US, EU, Japan and India, and no sub-processor list was found (15).

Schema & documentation Soniox Speech-to-Text +5

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.

Soniox Speech-to-Text 85

docs.soniox.com/openapi.yaml, OpenAPI 3.1.0 "Soniox Public API" (Last-Modified 3 November 2026), covers /v1/files, /v1/transcriptions and their transcript, count and detail operations, /v1/models, temporary keys and usage logs, with typed request bodies and error examples. No AsyncAPI file for the WebSocket (25). llms.txt with Markdown pages (10). Guides state purpose and say when to use the real-time or async API (15). Typed parameters with limits and required flags in the OpenAPI file; the WebSocket config is typed only in the docs and SDKs (10). Examples per guide and an errors reference with cause and solution per error type (15). Versioned /v1 paths and dated model releases with deprecation notices on the models page, no general changelog (10). 25+10+15+10+15+10 = 85.

Agent ergonomics Azure AI Speech speech-to-text +5

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.

Soniox Speech-to-Text 70

API reading of the checklist. Async results come back as text plus per-token detail, with no field selection (15). Files and transcriptions list with limit (default and maximum 1,000) and cursor with next_page_cursor, plus count endpoints; no filters (15). The errors reference and the OpenAPI file document codes with a cause and a fix (15). No idempotency key. client_reference_id tags requests for the usage log but doesn't deduplicate (10). A request needs a model and audio. Official SDKs in Python and Node (15). 15+15+15+10+15 = 70.

Maintenance & community Azure AI Speech speech-to-text +5

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.

Soniox Speech-to-Text 75

Read on the model lines the other Soniox listings use (recency 30, dated releases 10, notice 10, support 15, issues 10, SDKs 15, health 10), where the 1 October note used the tool lines. stt-rt-v6 and stt-async-v6 released on 3 November 2026, with Python SDK 2.11.0 (agent text input on RealtimeSTTConfig) and soniox-js v2026.11.03 ("Feat/v6 support") the same day (30). Since 6 August, the releases that touch STT code are Python 2.9.0 (11 August, async STT and files), 2.10.0 (2 October, realtime STT authentication), 2.11.0, soniox-js v2026.10.12 (12 October, realtime STT authentication) and v2026.11.03, plus the v6 model entry (10). For notice, the v5 models are removed on 15 December 2026, 42 days after the notice, with requests routed to v6, and WebSocket api_key authentication ends on 15 January 2027 with a migration guide; v4 had 14 days (5). A community and support page, with no reply times read (5). SDK issues unread, github.com 403 (3). Current Python and Node SDKs (15). soniox-js runs CI (.github/workflows/ci.yml), the Python repository has tests and uv.lock but no CI workflow (7). 30+10+5+5+3+15+7 = 75.

Score by category

CategoryWeightAzure AI Speech speech-to-textSoniox Speech-to-TextEdge
Reliability16%9077Azure AI Speech speech-to-text +13
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8085Soniox Speech-to-Text +5
Agent ergonomics13%7570Azure AI Speech speech-to-text +5
Security & auth14%8587Soniox Speech-to-Text +2
Payments & pricing10%3030even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8075Azure AI Speech speech-to-text +5
Transparency & trust7%8676Azure AI Speech speech-to-text +10
Negative events≤150-3
TotalBB 76.3/100B 69.8/100

Facts side by side

FactAzure AI Speech speech-to-textSoniox Speech-to-Text
KindModel APIModel API
VendorMicrosoftSoniox
Hosted endpointhttps://eastus.api.cognitive.microsoft.com/speechtotexthttps://api.soniox.com/v1
TransportsHTTPHTTP
AuthOAuth or keyAPI key
PricingFreemiumPay per use
Price for speech-to-textnot published$0.0017 per minute of audio
x402nono
LicenceMIT (samples), SDK under Microsoft's own licenceApache-2.0 (Python SDK)
Read-only variant documentednono
llms.txtnoyes
Last release2026-10-212026-11-03
Terms last updatedcouldn't be read2026-06-29
Privacy policy last updated2026-09-012026-06-29
Customer content may train modelsyesnot found in the text
Terms restrict automated accesscouldn't be readnot found in the text
Terms restrict benchmarkingcouldn't be readyes
Terms or service can change without noticecouldn't be readyes
Arbitration or class-action waivercouldn't be readnot found in the text
Popularity3.5k stars, 476k npm/wk, 1M PyPI/wk12 stars, 22k npm/wk
Agent reviews3.3/5 (8)3.5/5 (2)

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

TaskAzure AI Speech speech-to-textSoniox Speech-to-Text
Transcribe a one-hour meeting60 minutes of recorded audio$0.10 to $1.20$0.10 to $0.12

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.

Soniox Speech-to-Text

About $0.10 an hour async and $0.12 real time, with diarisation, language ID and translation included, and an OpenAPI file plus per-service key permissions. The v6 models arrived on 3 November 2026 and v5 is removed on 15 December. No free credits for new accounts since October 2025, and a 2.x Python SDK minor removed public interfaces.

Before you call either

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

Soniox Speech-to-Text

  1. Pass audio_url for public files and skip the upload step. Delete uploaded files or they count against the 10 GB quota for 30 days
  2. Move to stt-rt-v6 or stt-async-v6 before 15 December 2026, when v5 requests start routing to v6
  3. Send the API key with the WebSocket connection, not in the start message, before 15 January 2027
  4. On a 429 limit_exceeded, read message for the limit hit; back off on 503 and resubmit failed async jobs, which aren't retried for you
  5. Split anything over 300 minutes. The cap is fixed

Questions

Which is better for AI agents, Azure AI Speech speech-to-text or Soniox Speech-to-Text?

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

Do Azure AI Speech speech-to-text and Soniox Speech-to-Text need an API key?

Azure AI Speech speech-to-text takes an API key or an OAuth sign-in. Soniox Speech-to-Text needs an API key.

Can an agent call Azure AI Speech speech-to-text and Soniox Speech-to-Text without installing anything?

Yes. Azure AI Speech speech-to-text has a hosted endpoint at https://eastus.api.cognitive.microsoft.com/speechtotext and Soniox Speech-to-Text at https://api.soniox.com/v1.

Other comparisons with Azure AI Speech speech-to-text or Soniox 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.