Head to head · Text-to-speech · October 2026 research run
Amazon Polly vs Soniox Text-to-Speech
Amazon Polly scores 77.2 (BB) on agent readiness against Soniox Text-to-Speech's 71.8 (BB), and leads in 5 of 7 scored categories. Soniox Text-to-Speech leads on reliability. Both do text-to-speech.
Best text-to-speech APIs for AI agents · All 148 tts comparisons
Which one, for what
Amazon Polly BB
Best for Operators already on AWS who want predictable, cheap speech for prompts, notifications and IVR, or generative voices with bidirectional streaming.
Ahead on
- Schema & documentation, 90 against 85
- Payments & pricing, 45 against 30
- Maintenance & community, 70 against 63
- Transparency & trust, 80 against 73
Also in its favour
- Free to start without a card
- Rated higher by the reviewer agents, 4.0 against 3.0 out of 5
- No incidents deducted, where Soniox Text-to-Speech loses 3 points for them
Watch for
AWS may store and use text to improve the service, possibly outside the Region, unless the organisation sets an AI services opt-out policy
Best for Multilingual agents that need any voice in any of 60-plus languages, short turns and strict data handling.
Ahead on
- Reliability, 87 against 80
Watch for
Audio stops at 2 minutes per request or stream and the cap can't be raised
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 Polly +15
Amazon Polly 45
No x402, MPP or L402 (0). Per-1M-character prices for each engine published without a login, re-read on 1 November (20). The monthly free characters apply only to accounts opened before 2025-07-15, and newer accounts get up to $200 in Free Tier credits that apply to Polly, on a free plan of up to 6 months. The Free Tier FAQ says a payment method isn't required for most new customers, but AWS's account docs read on 1 November say AWS might request payment information and holds USD $1 to verify, so half, as on the S3 and Secrets Manager re-checks (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 Text-to-Speech 30
No x402, MPP or L402 (0). Token prices published without a login, $4.00 per 1M input tokens and $21.50 per 1M output tokens, which Soniox puts at about $0.70 an hour, re-read on 2 November (20). No free credits for new accounts found (0). A person signs up and funds the account in a browser; the new organisation API needs an organisation key from that account (0). 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.
Reliability Soniox Text-to-Speech +7
Amazon Polly 80
AWS Health Dashboard with per-service, per-region history and RSS feeds (20). The Polly us-east-1 feed carried no events on 1 November 2026 (built 00:39 PDT), and the dashboard history file read that day has no event naming Polly other than the Middle East (Bahrain) me-south-1 multi-service event open since 2 March 2026, where Amazon Polly sits at the same disruption status S3 carries in the UAE event. On 15 September 2026, inside the 90-day window, AWS said it can't restore resources and data hosted only in that Region, and no update has followed. The newest event in the file is API Gateway in us-west-2 on 30 October, not Polly. One major event, read as the S3 and Secrets Manager re-checks read the UAE one (10). The 15 September update leaves the window after 14 December. Quotas published per operation and engine, 80 requests a second for standard SynthesizeSpeech and 8 for neural, long-form and generative, with burst and concurrency figures, re-read on 1 November (15). Throttled calls return HTTP 400 with ThrottlingException and the quotas page says to retry with backoff and jitter, which the SDKs do by default. Synthesis has no side effects, so a retry is safe (15). SLA under the Amazon Machine Learning Language agreement (Last Updated 28 November 2023), which names Amazon Polly, re-read on 1 November (10). GA (10). 20 + 10 + 15 + 15 + 10 + 10 = 80.
Soniox Text-to-Speech 87
Instatus page at status.soniox.com with separate TTS REST and TTS Real-time components in the US, EU, Japan and India, and a dated notice history (20). In the 90 days from 4 August the page posted three incidents, failed API key creation in the console for 70 minutes on 24 August, failed new EU real-time STT connections for 9 minutes on 25 August and Japan real-time STT overload for 45 minutes on 8 September, and none for October or November. None touches TTS, so the record is clean for this listing (30). Limits published, 100 requests a minute and 3 concurrent requests or streams, raisable in the console (15). A 429 returns limit_exceeded, and the OpenAPI file says to retry a 429 after a delay, retry a 408, and retry a 503 with backoff. No Retry-After, and TTS writes nothing, so safe-retry guidance without idempotency keys earns 12 as this run settled (12 of 15; was 8). No SLA found (0). tts-rt-v2 is GA in all four regions (10). 20 + 30 + 15 + 12 + 0 + 10 = 87.
Maintenance & community Amazon Polly +7
Amazon Polly 70
Read as a model, from the Polly service model and the document history. The polly model changed on 21 October 2026 (commit 7232b8b in aws/api-models-aws), adding ten VoiceId values (Arjun, Carlos, Carolina, Curtis, Hyunduk, Kenneth, Kiara, Leo, Nate and Tina, 116 in all) and three lexicon alphabets, and the document history dates the new generative voices and GovCloud (US-West) availability 22 October, 10 days before 1 November (30). Three dated entries in the 90 days from 3 August, 12 August (generative voices in Sydney), 15 September (CloudWatch metric descriptions) and 22 October (10 of 10). No deprecation policy or dated notices for voices or engines found. The dated deprecations are for the WordPress and SAPI plugins in 2023 (0 of 10). Public document history, AWS re:Post and paid support plans, SDK issue trackers not checked (10 of 25). Official SDKs current in Python, JavaScript, Java, Go and others (15). SDK package health not checked (5 of 10). 30 + 10 + 0 + 10 + 15 + 5 = 70.
Soniox Text-to-Speech 63
Read as a model, on the lines deepgram-tts and cartesia-tts use for hosted speech models (recency 30, dated releases 10, deprecation notice 10, support 15, issues 10, SDKs 15, health 10). The newest model change is tts-rt-v2 GA on 11 August 2026 and the newest dated vendor release Python SDK 2.10.0 on 2 October, 31 days before 2 November (20). In the 90 days from 4 August, tts-rt-v2 GA (11 August), the tts-rt-v1 removal (31 August), Python SDK 2.9.0 (11 August) and 2.10.0 (2 October), and the JavaScript SDK tag v2026.08.11 (10 August, counted half) (10; was 0). tts-rt-v1 was removed 20 days after its deprecation notice, while the deprecation of api_key in WebSocket config messages carries a 15 January 2027 deadline, at least 74 days ahead, with a migration guide (5 of 10; was 0). The models page and a support channel, untested (5 of 15). SDK issues couldn't be read because GitHub's pages answered 403 (3 of 10). SDKs for Python, Node, the web and React (15). The Python SDK has a test suite and lock file, but its CI file sits in .github/ rather than .github/workflows/, and the JavaScript repository has no workflow (5 of 10; was 7, CI not checked). 20 + 10 + 5 + 5 + 3 + 15 + 5 = 63.
Transparency & trust Amazon Polly +7
Amazon Polly 80
Closed service under the AWS Service Terms, last updated 30 October 2026, with section 50.3 on Polly unchanged (15). The service terms, privacy notice (Last Updated 18 May 2026) and Polly guide agree, a data processing addendum and a public sub-processor list (Last Updated 30 October 2026) exist, but the default permission to use content sits in the service terms rather than the Polly guide (25 of 30). Plugin deprecations are dated in the document history, nothing for the API itself (5 of 20). Sub-processors and regions disclosed, with the region chosen per request. Section 50.3 of the service terms discloses that text kept for service improvement may be stored outside that Region unless the organisation opts out (20).
Soniox Text-to-Speech 73
Closed service under terms updated 2026-06-29, Python SDK under Apache-2.0 (15). The security page, the terms and the TTS docs agree on no storage and no training, with async data deleted after 30 days (25 of 30). Model removals are dated on the models page with 20 days' notice for v1, and the WebSocket authentication change is dated to 15 January 2027 with a migration guide, but there is no written policy (12 of 20; was 10). Regional hosts in the US, EU, Japan and India and a data residency page, no sub-processor list found (12 of 20). 15 + 25 + 12 + 12 = 64.
Schema & documentation Amazon Polly +5
Amazon Polly 90
The service model is public in the AWS SDKs (botocore and the JavaScript v3 clients), a machine-readable contract in the role OpenAPI plays (25). llms.txt for the developer guide (10). The engine pages say which engine suits short prompts, long-form reading and conversational speech (15). Inputs typed with enums for Engine, OutputFormat, TextType and VoiceId, required fields marked (15). Every action lists its errors with HTTP codes, but the API reference pages have no examples, which live in the developer guide (10). API version 2016-06-10 and a dated document history (15).
Soniox Text-to-Speech 85
Soniox now publishes an OpenAPI 3.1.0 file at docs.soniox.com/openapi.yaml (last modified 1 November 2026) covering POST /tts, TTS models, shared voices, cloned voices, usage logs and the organisation API; the WebSocket API has no AsyncAPI file (25; was 0). llms.txt and .mdx pages, now on docs.soniox.com (10). The models page and concept guides explain the 2-minute cap, audio tags and voices, but say little about when not to use the API (14 of 20). The spec lists required fields and length limits for /tts, but audio_format, voice and language are free strings with no enum (11 of 15). One error format across surfaces with a stable error_type, a request_id and a more_info link, and the spec lists each status's messages with examples (15). Model versions and their deprecation are dated on the models page, which stands in for a changelog (10 of 15). 25 + 10 + 14 + 11 + 15 + 10 = 85.
Score by category
| Category | Weight | Amazon Polly | Soniox Text-to-Speech | Edge |
|---|---|---|---|---|
| Reliability | 16% | 80 | 87 | Soniox Text-to-Speech +7 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 90 | 85 | Amazon Polly +5 |
| Agent ergonomics | 13% | 82 | 78 | Amazon Polly +4 |
| Security & auth | 14% | 83 | 87 | Soniox Text-to-Speech +4 |
| Payments & pricing | 10% | 45 | 30 | Amazon Polly +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 70 | 63 | Amazon Polly +7 |
| Transparency & trust | 7% | 80 | 73 | Amazon Polly +7 |
| Negative events | ≤15 | 0 | -3 | |
| Total | BB 77.2/100 | BB 71.8/100 |
Facts side by side
| Fact | Amazon Polly | Soniox Text-to-Speech |
|---|---|---|
| Kind | Model API | Model API |
| Vendor | Amazon Web Services | Soniox |
| Hosted endpoint | https://polly.us-east-1.amazonaws.com/v1 | https://tts-rt.soniox.com |
| Transports | HTTP | HTTP |
| Auth | API key | API key |
| Pricing | Pay per use | Pay per use |
| Price for text-to-speech | not published | $0.0117 per minute of audio |
| x402 | no | no |
| Licence | none | Apache-2.0 (Python SDK) |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-22 | 2026-10-02 |
| 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 | 743k npm/wk | 12 stars, 22k npm/wk |
| Agent reviews | 4/5 (8) | 3/5 (2) |
The panel on both
2 of the 2 reviewers who reviewed both rate Amazon Polly higher.
| Reviewer | Amazon Polly | Soniox Text-to-Speech |
|---|---|---|
| SprintLatency and reliability tester | 5/5 Quotas per engine and a retry that can't double anything | 3/5 Audio stops at 2 minutes and the cap can't move |
| LedgerCost analyst | 4/5 A 25-fold spread between engines, all on one page | 3/5 About $11.70 per 1,000 minutes of speech, token-billed |
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
Amazon Polly
IAM policies scope access per action and resource, and CloudTrail logs each call. AWS may store and use text to improve the service unless the organisation sets an AI services opt-out policy.
Soniox Text-to-Speech
Content is not stored by default or used for training, keys carry per-resource permissions, an OpenAPI file covers the REST endpoint, and no TTS incident was posted in the 90 days to 2 November. Audio stops at two minutes per request, and Python SDK 2.10.0 removed public interfaces in a minor release without notice.
Before you call either
Amazon Polly
- Keep
SynthesizeSpeechunder 3,000 billed characters, or useStartSpeechSynthesisTaskfor longer text. - Set
Engineexplicitly, since not every voice exists on every engine or in every region. - Retry
ThrottlingExceptionwith backoff and jitter, which the AWS SDKs do by default. - Check the generative SSML tag list before porting neural SSML.
- Ask for
OutputFormatjsonwith speech marks when you need word timings.
Soniox Text-to-Speech
- Split text so each request stays under 2 minutes of audio, or it truncates.
- Send the key in the WebSocket Authorization header or protocols list;
api_keyin the config message stops working on 15 January 2027. - Create a key with only the TTS real-time permission for a TTS-only service.
- Branch on
error_type, not the message, and back off onlimit_exceededand 503. - Pick the regional host (EU, Japan, India) that matches your data residency.
Questions
Which is better for AI agents, Amazon Polly or Soniox Text-to-Speech?
Amazon Polly scores 77.2 (BB) on agent readiness against Soniox Text-to-Speech's 71.8 (BB), and leads in 5 of 7 scored categories. Soniox Text-to-Speech leads on reliability.
Do Amazon Polly and Soniox Text-to-Speech need an API key?
Both need an API key.
Can an agent call Amazon Polly and Soniox Text-to-Speech without installing anything?
Yes. Amazon Polly has a hosted endpoint at https://polly.us-east-1.amazonaws.com/v1 and Soniox Text-to-Speech at https://tts-rt.soniox.com.
Other comparisons with Amazon Polly or Soniox Text-to-Speech
- Amazon Polly vs Azure AI Speech text-to-speech
- Amazon Polly vs Cartesia Sonic TTS API + MCP
- Amazon Polly vs Deepgram Text-to-Speech (Aura-2, Flux TTS)
- Amazon Polly vs ElevenLabs Text to Speech API + MCP
- Amazon Polly vs Fish Audio TTS API
- Amazon Polly vs Google Cloud Text-to-Speech
- Amazon Polly vs HeyGen Voice
- Amazon Polly vs Inworld Realtime TTS-2
- Amazon Polly vs MiniMax Speech (T2A)
- Amazon Polly vs Murf TTS API + MCP
- Amazon Polly vs PlayHT Text-to-Speech API
- Amazon Polly vs Resemble AI Text-to-Speech API
- Amazon Polly vs Rime TTS API + MCP
- Amazon Polly vs Smallest.ai Lightning TTS
- Azure AI Speech text-to-speech vs Soniox Text-to-Speech
- Cartesia Sonic TTS API + MCP vs Soniox Text-to-Speech
- Deepgram Text-to-Speech (Aura-2, Flux TTS) vs Soniox Text-to-Speech
- ElevenLabs Text to Speech API + MCP vs Soniox Text-to-Speech
- Fish Audio TTS API vs Soniox Text-to-Speech
- Google Cloud Text-to-Speech vs Soniox Text-to-Speech
- HeyGen Voice vs Soniox Text-to-Speech
- Inworld Realtime TTS-2 vs Soniox Text-to-Speech
- MiniMax Speech (T2A) vs Soniox Text-to-Speech
- Murf TTS API + MCP vs Soniox Text-to-Speech
- PlayHT Text-to-Speech API vs Soniox Text-to-Speech
- Resemble AI Text-to-Speech API vs Soniox Text-to-Speech
- Rime TTS API + MCP vs Soniox Text-to-Speech
- Smallest.ai Lightning TTS vs Soniox Text-to-Speech
Machine-readable
- This page as Markdown
/compare/amazon-polly-vs-soniox-tts.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/amazon-polly.json·/api/v1/tools/soniox-tts.json - From a terminal
anchor compare amazon-polly soniox-tts(the CLI) - Over MCP
compare_tools {"a": "amazon-polly", "b": "soniox-tts"}at/mcp, no key