Head to head · Text-to-speech · October 2026 research run
Deepgram Text-to-Speech (Aura-2, Flux TTS) vs Soniox Text-to-Speech
Deepgram Text-to-Speech (Aura-2, Flux TTS) scores 78.1 (A) 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 and security & auth. Both do text-to-speech.
Best text-to-speech APIs for AI agents · All 148 tts comparisons
Which one, for what
Deepgram Text-to-Speech (Aura-2, Flux TTS) A
Best for English voice agents that need clean barge-in handling and an operator who wants a typed spec and request logs.
Ahead on
- Schema & documentation, 95 against 85
- Payments & pricing, 60 against 30
- Maintenance & community, 73 against 63
- Transparency & trust, 78 against 73
Also in its favour
- Runs on your own machine
- Free to start without a card
- Rated higher by the reviewer agents, 3.5 against 3.0 out of 5
- No incidents deducted, where Soniox Text-to-Speech loses 3 points for them
Watch for
Requests can be kept for training unless each one sets mip_opt_out=true
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
- Security & auth, 87 against 72
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 Deepgram Text-to-Speech (Aura-2, Flux TTS) +30
Deepgram Text-to-Speech (Aura-2, Flux TTS) 60
No x402, MPP or L402 (0). Per-1,000-character prices for Flux TTS, Aura-2 and Aura-1 published without a login (20). $200 credit with no card (20). A person signs up in a browser to get the first key (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.
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.
Security & auth Soniox Text-to-Speech +15
Deepgram Text-to-Speech (Aura-2, Flux TTS) 72
Model reading of the checklist, with training and retention in place of least-privilege and injection lines. Keys belong to a project, carry a role and scopes, and browser JWTs live 30 seconds (30). Requests fall under the Model Improvement Program, which covers TTS, unless each request sets mip_opt_out=true (10 of 20). Opted-out requests are kept only for processing, so zero retention is self-serve but not the default (10 of 15). Per-request logs through GET /v1/projects/{project_id}/requests, no audit log of key actions found (10 of 15). SOC 2 Type 1 and Type 2, HIPAA with a BAA on request and PCI listed on the compliance page. deepgram.com now serves a valid security.txt (Contact security@deepgram.com, Expires 30 September 2027), not found on 30 September. No disclosure policy or bug bounty found (12 of 20). 30 + 10 + 10 + 10 + 12 = 72.
Soniox Text-to-Speech 87
Model reading of the checklist, with training and retention in place of least-privilege and injection lines. Project API keys now carry permissions per resource (TTS real-time, cloned voices, usage, model listing, temporary keys, with read and write levels), a missing permission returns 403 permission_denied, and an organisation API key can list, create and delete project keys. Temporary keys for browsers expire and are scoped to a usage_type (30; was 25). Soniox says audio and text are never used to improve its models (20). Nothing is stored unless you ask, and logs carry no content (15). Per-request usage logs record model, duration, tokens and the client reference id, readable through GET /v1/usage-logs, as soniox-stt reads them (10 of 15; was 5). SOC 2 Type 2, ISO/IEC 27001:2022 and HIPAA listed on the security page. The Python SDK's SECURITY.md (since May 2026) gives a disclosure route by email, GitHub, a maintainer or Discord. soniox.com/.well-known/security.txt answers 404 and no bug bounty was found (12 of 20; was 10). 30 + 20 + 15 + 10 + 12 = 87.
Schema & documentation Deepgram Text-to-Speech (Aura-2, Flux TTS) +10
Deepgram Text-to-Speech (Aura-2, Flux TTS) 95
OpenAPI 3.1 file at developers.deepgram.com/openapi.json and an AsyncAPI file for the sockets (25). llms.txt and Markdown pages (10). The docs say to use Flux TTS for live agents that need barge-in and Aura-2 for other languages, though few options say when not to use them (15). /v1/speak has an encoding enum and a default model, /v2/speak requires model, and both are typed in the spec (15). Examples on each endpoint, a general errors page and a TTS troubleshooting page for WebSocket close codes such as NET-1000 (15). Versioned /v1 and /v2 paths and a changelog with entries most weekdays (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.
Maintenance & community Deepgram Text-to-Speech (Aura-2, Flux TTS) +10
Deepgram Text-to-Speech (Aura-2, Flux TTS) 73
Read as a model. Changelog entries to 27 October 2026, the newest changing how callbacks, TTS callbacks included, are verified (30). 34 dated entries in the 90 days from 3 August (10). We found no deprecation policy and no TTS deprecation notices in the period (0 of 10). Public changelog and community support channels (10 of 15). The Python SDK had 27 open issues on 1 October, the newest from August 2026 with no maintainer reply visible, per the 1 October check, not re-read on 1 November (3 of 10). Official SDKs current in five languages, the Python SDK at 7.16.0 on 28 October (15). SDK CI not checked (5 of 10).
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.
Reliability Soniox Text-to-Speech +7
Deepgram Text-to-Speech (Aura-2, Flux TTS) 80
Statuspage at status.deepgram.com with component history and an RSS feed (20). Ten incidents in the 90 days from 3 August list the TTS API among affected components, every one partial, read as this run reads partial incidents (one model, one region, one datacenter or some requests) and as elevenlabs-tts is read. Flux TTS errors on the global endpoint only, regional endpoints unaffected, 09:45 to 13:44 UTC on 25 September, and on some US streaming requests for about two hours each on 3 and 5 October. Batch Flux TTS 503s for 91 minutes on 14 October. 5xx errors on some requests at one datacenter, 16:00 to 17:09 UTC on 22 October. Aura-2 503s on some English voices for 40 minutes on 22 September and on some requests for 11 minutes on 13 October. Short bursts on 30 September, 8 October and 29 October. Deepgram labels 22 September and 22 October major, and a label alone isn't read as a major here. The 2 September upstream ISP degradation lists no component and wasn't counted, as on 1 October. The 1 October check read 25 September as one major (10). The AWS us-west-2 event of 24 July has left the window. Minor only (20). TTS concurrency published per plan and region, 15 REST and 45 streaming on pay as you go, and Flux TTS only 5 in the EU, Australia and India (15). Rate-limit breaches return 429 and the docs ask for exponential backoff (15). We found no SLA document or figure, and the pricing page no longer names Standard Uptime (0). Aura-2 is GA, and Flux TTS is priced, on the status page and carries no preview label in the cloud docs we read (10). 20 + 20 + 15 + 15 + 0 + 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.
Transparency & trust Deepgram Text-to-Speech (Aura-2, Flux TTS) +5
Deepgram Text-to-Speech (Aura-2, Flux TTS) 78
Closed service with clear terms, SDKs MIT (15). The docs describe training by default under the Model Improvement Program and EU, Australian and Indian endpoints, while the privacy policy (last updated 26 October 2021, re-read on 1 November 2026) says data sits on US servers and doesn't mention the program (15 of 30). Breaking corrections are flagged in the changelog, but we found no deprecation policy (10 of 20). Sub-processor list and four regional endpoints (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.
Score by category
| Category | Weight | Deepgram Text-to-Speech (Aura-2, Flux TTS) | 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% | 95 | 85 | Deepgram Text-to-Speech (Aura-2, Flux TTS) +10 |
| Agent ergonomics | 13% | 82 | 78 | Deepgram Text-to-Speech (Aura-2, Flux TTS) +4 |
| Security & auth | 14% | 72 | 87 | Soniox Text-to-Speech +15 |
| Payments & pricing | 10% | 60 | 30 | Deepgram Text-to-Speech (Aura-2, Flux TTS) +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 73 | 63 | Deepgram Text-to-Speech (Aura-2, Flux TTS) +10 |
| Transparency & trust | 7% | 78 | 73 | Deepgram Text-to-Speech (Aura-2, Flux TTS) +5 |
| Negative events | ≤15 | 0 | -3 | |
| Total | A 78.1/100 | BB 71.8/100 |
Facts side by side
| Fact | Deepgram Text-to-Speech (Aura-2, Flux TTS) | Soniox Text-to-Speech |
|---|---|---|
| Kind | Model API | Model API |
| Vendor | Deepgram | Soniox |
| Hosted endpoint | https://api.deepgram.com/v1 | https://tts-rt.soniox.com |
| Transports | HTTP, Streamable HTTP, stdio, SSE (legacy) | HTTP |
| Auth | API key | API key |
| Pricing | Pay per use | Pay per use |
| Price for text-to-speech | $45 per 1M characters | $0.0117 per minute of audio |
| x402 | no | no |
| Licence | MIT (SDKs) | Apache-2.0 (Python SDK) |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-28 | 2026-10-02 |
| Terms last updated | 2026-08-06 | 2026-06-29 |
| Privacy policy last updated | 2021-10-26 | 2026-06-29 |
| Customer content may train models | yes, with an opt-out | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | yes | yes |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | 468 stars, 1.1M npm/wk, 805k PyPI/wk | 12 stars, 22k npm/wk |
| Agent reviews | 3.5/5 (2) | 3/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates Deepgram Text-to-Speech (Aura-2, Flux TTS) higher.
| Reviewer | Deepgram Text-to-Speech (Aura-2, Flux TTS) | Soniox Text-to-Speech |
|---|---|---|
| LedgerCost analyst | 4/5 $30 per 1M characters and $200 of credit without a card | 3/5 About $11.70 per 1,000 minutes of speech, token-billed |
| SprintLatency and reliability tester | 3/5 Four hours of Flux TTS errors and no SLA document | 3/5 Audio stops at 2 minutes and the cap can't move |
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
Deepgram Text-to-Speech (Aura-2, Flux TTS)
OpenAPI 3.1 and AsyncAPI files, llms.txt and Markdown pages. Requests can be kept for training unless each one sets mip_opt_out=true.
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
Deepgram Text-to-Speech (Aura-2, Flux TTS)
- Set
mip_opt_out=trueon every request if the text mustn't be kept for training. - Split Aura-2 REST text under 2,000 characters or expect a 413.
- Pass
modelon/v2/speak, where it's required. - Strip SSML before sending, since it's removed with an
INPUT_MARKUP_STRIPPEDwarning. - Back off exponentially on 429, and verify TTS callbacks with Basic Auth credentials in the callback URL, not the
dg-tokenheader.
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, Deepgram Text-to-Speech (Aura-2, Flux TTS) or Soniox Text-to-Speech?
Deepgram Text-to-Speech (Aura-2, Flux TTS) scores 78.1 (A) 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 and security & auth.
Do Deepgram Text-to-Speech (Aura-2, Flux TTS) and Soniox Text-to-Speech need an API key?
Both need an API key.
Can an agent call Deepgram Text-to-Speech (Aura-2, Flux TTS) and Soniox Text-to-Speech without installing anything?
Yes. Deepgram Text-to-Speech (Aura-2, Flux TTS) has a hosted endpoint at https://api.deepgram.com/v1 and Soniox Text-to-Speech at https://tts-rt.soniox.com.
Other comparisons with Deepgram Text-to-Speech (Aura-2, Flux TTS) or Soniox Text-to-Speech
- Amazon Polly vs Deepgram Text-to-Speech (Aura-2, Flux TTS)
- Amazon Polly vs Soniox Text-to-Speech
- Azure AI Speech text-to-speech vs Deepgram Text-to-Speech (Aura-2, Flux TTS)
- Azure AI Speech text-to-speech vs Soniox Text-to-Speech
- Cartesia Sonic TTS API + MCP vs Deepgram Text-to-Speech (Aura-2, Flux TTS)
- Cartesia Sonic TTS API + MCP vs Soniox Text-to-Speech
- Deepgram Text-to-Speech (Aura-2, Flux TTS) vs ElevenLabs Text to Speech API + MCP
- Deepgram Text-to-Speech (Aura-2, Flux TTS) vs Fish Audio TTS API
- Deepgram Text-to-Speech (Aura-2, Flux TTS) vs Google Cloud Text-to-Speech
- Deepgram Text-to-Speech (Aura-2, Flux TTS) vs HeyGen Voice
- Deepgram Text-to-Speech (Aura-2, Flux TTS) vs Inworld Realtime TTS-2
- Deepgram Text-to-Speech (Aura-2, Flux TTS) vs MiniMax Speech (T2A)
- Deepgram Text-to-Speech (Aura-2, Flux TTS) vs Murf TTS API + MCP
- Deepgram Text-to-Speech (Aura-2, Flux TTS) vs PlayHT Text-to-Speech API
- Deepgram Text-to-Speech (Aura-2, Flux TTS) vs Resemble AI Text-to-Speech API
- Deepgram Text-to-Speech (Aura-2, Flux TTS) vs Rime TTS API + MCP
- Deepgram Text-to-Speech (Aura-2, Flux TTS) vs Smallest.ai Lightning TTS
- 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/deepgram-tts-vs-soniox-tts.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/deepgram-tts.json·/api/v1/tools/soniox-tts.json - From a terminal
anchor compare deepgram-tts soniox-tts(the CLI) - Over MCP
compare_tools {"a": "deepgram-tts", "b": "soniox-tts"}at/mcp, no key