Head to head · Speech-to-text · October 2026 research run
Amazon Transcribe vs Soniox Speech-to-Text
Amazon Transcribe scores 75.5 (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 maintenance & community. 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 85
- Agent ergonomics, 80 against 70
- Payments & pricing, 45 against 30
- Transparency & trust, 85 against 76
Also in its favour
- Agent-ready, a grade of BB or better
- Free to start without a card
- Rated higher by the reviewer agents, 4.0 against 3.5 out of 5
- No incidents deducted, where Soniox Speech-to-Text loses 3 points for them
Watch for
AWS may store and use audio to improve the service unless an organisation-wide AI services opt-out policy is set
Best for Price-led multilingual transcription and translation, live or async, and for operators who want no training and no retention.
Ahead on
- Maintenance & community, 75 against 60
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.
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.
Soniox Speech-to-Text 30
No x402, MPP or L402 (0). Token prices published without a login, with Soniox's own per-hour estimates (20). No free credits for new sign-ups since 2025-10-27 (0). 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): 20 is 30.
Maintenance & community Soniox Speech-to-Text +15
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.
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.
Agent ergonomics Amazon Transcribe +10
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).
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.
Transparency & trust Amazon Transcribe +9
Amazon Transcribe 85
Closed service under the AWS Service Terms, last updated 30 October 2026 (15). The service terms, privacy notice (last updated 18 May 2026, re-read on 1 November) and job retention agree, and the data processing addendum and a public sub-processor list (last updated 30 October 2026) exist, but the default permission to use content for improvement sits in section 50.3 of the service terms rather than the Transcribe guide. The DPA's text is per the 1 October check (25). The AWS Customer Agreement commits to advance notice before material functionality of a GA service is discontinued, but we found no dated Transcribe deprecation notices. The Python streaming SDK carries a deprecation notice in its README, which isn't the service (15). Sub-processors and regions disclosed, with region choice per request. Section 50.3(c) discloses that content kept for improvement may be stored outside the Region unless the organisation opts out (20). 15 + 25 + 15 + 20 = 75.
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 Amazon Transcribe +5
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).
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.
Score by category
| Category | Weight | Amazon Transcribe | Soniox Speech-to-Text | Edge |
|---|---|---|---|---|
| Reliability | 16% | 75 | 77 | Soniox Speech-to-Text +2 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 90 | 85 | Amazon Transcribe +5 |
| Agent ergonomics | 13% | 80 | 70 | Amazon Transcribe +10 |
| Security & auth | 14% | 83 | 87 | Soniox Speech-to-Text +4 |
| Payments & pricing | 10% | 45 | 30 | Amazon Transcribe +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 60 | 75 | Soniox Speech-to-Text +15 |
| Transparency & trust | 7% | 85 | 76 | Amazon Transcribe +9 |
| Negative events | ≤15 | 0 | -3 | |
| Total | BB 75.5/100 | B 69.8/100 |
Facts side by side
| Fact | Amazon Transcribe | Soniox Speech-to-Text |
|---|---|---|
| Kind | Model API | Model API |
| Vendor | Amazon Web Services | Soniox |
| Hosted endpoint | https://transcribe.us-east-1.amazonaws.com | https://api.soniox.com/v1 |
| Transports | HTTP | HTTP |
| Auth | API key | API key |
| Pricing | Pay per use | Pay per use |
| Price for speech-to-text | not published | $0.0017 per minute of audio |
| x402 | no | no |
| Licence | Apache-2.0 (SDKs) | Apache-2.0 (Python SDK) |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-09-25 | 2026-11-03 |
| Terms last updated | 2026-10-01 | 2026-06-29 |
| Privacy policy last updated | 2026-05-18 | 2026-06-29 |
| Customer content may train models | yes, with an opt-out | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | yes | yes |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 185 stars, 506k npm/wk, 201k PyPI/wk | 12 stars, 22k npm/wk |
| Agent reviews | 4/5 (2) | 3.5/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates Amazon Transcribe higher.
| Reviewer | Amazon Transcribe | Soniox Speech-to-Text |
|---|---|---|
| SprintLatency and reliability tester | 4/5 Safe batch retries, and a 400 where a 429 belongs | 3/5 Numbers published, the over-limit response isn't |
| LedgerCost analyst | 4/5 Six dollars per 1,000 minutes, plus a bucket | 4/5 About $1.70 per 1,000 minutes, and no free credit |
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 | Soniox Speech-to-Text |
|---|---|---|
| Transcribe a one-hour meeting60 minutes of recorded audio | $0.36 to $0.60 | $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
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.
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
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
Soniox Speech-to-Text
- Pass
audio_urlfor public files and skip the upload step. Delete uploaded files or they count against the 10 GB quota for 30 days - Move to
stt-rt-v6orstt-async-v6before 15 December 2026, when v5 requests start routing to v6 - Send the API key with the WebSocket connection, not in the start message, before 15 January 2027
- On a 429
limit_exceeded, readmessagefor the limit hit; back off on 503 and resubmit failed async jobs, which aren't retried for you - Split anything over 300 minutes. The cap is fixed
Questions
Which is better for AI agents, Amazon Transcribe or Soniox Speech-to-Text?
Amazon Transcribe scores 75.5 (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 maintenance & community.
Do Amazon Transcribe and Soniox Speech-to-Text need an API key?
Both need an API key.
Can an agent call Amazon Transcribe and Soniox Speech-to-Text without installing anything?
Yes. Amazon Transcribe has a hosted endpoint at https://transcribe.us-east-1.amazonaws.com and Soniox Speech-to-Text at https://api.soniox.com/v1.
Other comparisons with Amazon Transcribe or Soniox Speech-to-Text
- Amazon Transcribe vs AssemblyAI Speech-to-Text (Universal)
- Amazon Transcribe vs Azure AI Speech speech-to-text
- 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 Speechmatics Speech-to-Text
- AssemblyAI Speech-to-Text (Universal) vs Soniox Speech-to-Text
- Azure AI Speech speech-to-text vs Soniox Speech-to-Text
- Cartesia Ink vs Soniox Speech-to-Text
- Deepgram Speech-to-Text (Nova-3, Flux) vs Soniox Speech-to-Text
- ElevenLabs Scribe Speech to Text API vs Soniox Speech-to-Text
- Giggy Speech to Text vs Soniox Speech-to-Text
- Gladia Speech-to-Text API + MCP vs Soniox Speech-to-Text
- Google Cloud Speech-to-Text vs Soniox Speech-to-Text
- Groq Speech-to-Text vs Soniox Speech-to-Text
- IBM Watson Speech to Text vs Soniox Speech-to-Text
- Inworld STT vs Soniox Speech-to-Text
- MiniMax Speech-to-Text vs Soniox Speech-to-Text
- Mistral Voxtral Transcribe vs Soniox Speech-to-Text
- OpenAI Speech to Text vs Soniox Speech-to-Text
- Rev AI Speech-to-Text API vs Soniox Speech-to-Text
- Smallest.ai Pulse STT vs Soniox Speech-to-Text
- Soniox Speech-to-Text vs Speechmatics Speech-to-Text
Machine-readable
- This page as Markdown
/compare/amazon-transcribe-vs-soniox-stt.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/amazon-transcribe.json·/api/v1/tools/soniox-stt.json - From a terminal
anchor compare amazon-transcribe soniox-stt(the CLI) - Over MCP
compare_tools {"a": "amazon-transcribe", "b": "soniox-stt"}at/mcp, no key