Head to head · Text-to-speech · October 2026 research run
Cartesia Sonic TTS API + MCP vs Soniox Text-to-Speech
Soniox Text-to-Speech scores 71.8 (BB) on agent readiness against Cartesia Sonic TTS API + MCP's 63.7 (B), and leads in 3 of 7 scored categories. Cartesia Sonic TTS API + MCP leads on payments & pricing and maintenance & community. Both do text-to-speech.
Best text-to-speech APIs for AI agents · All 148 tts comparisons
Which one, for what
Cartesia Sonic TTS API + MCP B
Best for Real-time voice agents that stream LLM output straight into speech and need stable, pinnable models.
Ahead on
- Payments & pricing, 45 against 30
- Maintenance & community, 84 against 63
Also in its favour
- Runs on your own machine
Watch for
Pronunciation dictionaries on Sonic 3.6 began ignoring case by default in September 2026, with no earlier notice found
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 73
- Agent ergonomics, 78 against 65
- Security & auth, 87 against 47
Also in its favour
- Agent-ready, a grade of BB or better
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.
Security & auth Soniox Text-to-Speech +40
Cartesia Sonic TTS API + MCP 47
Model reading of the checklist (credential, training, retention, operator visibility, programme), on the same evidence and values as cartesia-ink-stt. Standard and admin API keys are separate types, revocable, and a server can mint short-lived access tokens with TTS, STT and agent grants, but no key is scoped to TTS (26). Browsers pass the access token in the WebSocket query string, which the authentication guide documents ("In browsers, use an access token and query parameters instead"), and this run takes the full 10 off for a reusable token in a URL, as for cartesia-ink-stt and every Google API listing (16 of 30; the 1 October check didn't deduct). The Terms (last revised 14 June 2024, re-read on 2 November) say inputs, outputs and interactions may be used to train models unless otherwise agreed, with an opt-out form (5 of 20, aligned with cartesia-ink-stt; was 10). Zero data retention is Enterprise only and no retention period is published for other plans (5 of 15). Credit usage and key metadata are readable through admin endpoints and the usage dashboard, no per-call audit log found (7 of 15, aligned; was 8). security.txt at www.cartesia.ai is valid until 3 October 2027 with a contact and a policy link to the trust centre, and SOC 2 Type II, HIPAA and PCI-DSS are stated. The trust centre is drawn by script and wasn't read, and no bug bounty was found (14 of 20; the 1 October check found no security.txt, 10). 16+5+5+7+14 = 47.
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.
Maintenance & community Cartesia Sonic TTS API + MCP +21
Cartesia Sonic TTS API + MCP 84
Read as a model, on the lines deepgram-tts, gladia-stt and cartesia-ink-stt use for hosted speech models (recency 30, dated releases 10, deprecation notice 10, support 15, issues 10, SDKs 15, health 10). cartesia-mcp, whose text_to_speech tool calls Sonic, released 0.28.1 on 30 October 2026 after 0.27.0 (20 October), 0.27.1 (23 October) and 0.28.0 (27 October), and sonic-3.6-2026-08-27 is the newest snapshot (30). From 4 August the Python and TypeScript SDKs released 4.0.0, 4.0.1, 4.1.0 and 4.2.0 (14 August to 2 September) and the MCP server more than ten releases (10). Sonic-2, Sonic Turbo and sonic-3-2025-10-27 were sunset after 20 October 2026, announced in the July changelog, about 83 days ahead. The deprecations page dates each sunset but states no minimum notice period (5 of 10). The changelog has Text-to-Speech entries every month from May to September 2026, dated by month only, and no October entry, the same reading as cartesia-ink-stt (11 of 15; was 5). The Python SDK repository had 4 open issues on 9 October per the cartesia-ink-stt check, not re-read on 2 November since GitHub's pages answered 403 (5 of 10; was 7 on a 1 October count of one). Official cartesia and @cartesia/cartesia-js SDKs at 4.2.0 (2 September 2026), generated for API version 2026-08-14 (15). CI, release-please and lock files in both SDK repositories, with dependency updates merged on 23 October (8 of 10). 30+10+5+11+5+15+8 = 84.
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.
Payments & pricing Cartesia Sonic TTS API + MCP +15
Cartesia Sonic TTS API + MCP 45
No x402, MPP or L402 (0). Plan prices and credit allowances are public, about 1 credit a character, but there's no plain dollar price per character outside the plans (10). Free plan with 20,000 credits a month (about 27 minutes), no card step mentioned, non-commercial use only (20). 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): 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 +14
Cartesia Sonic TTS API + MCP 73
incident.io status page at status.cartesia.ai with TTS components for the US, EU, APAC and Australia and a dated history (20). feed.rss, read on 2 November, lists these items touching TTS from 4 August to 2 November 2026. Intermittent TTS timeouts on 5 August (21:25 to 23:21 per the 1 October reading), Agents telephony failing in the US on 7 August, region validation failing some TTS requests on 14 August, elevated time to first audio for sonic-3.5 and sonic-3 in the EU and US on 21 August, connection errors in the US on 2 September ("subsequent retries were successful"), WebSocket throttling in APAC on 3 September and degraded API performance in the US on 7 October. Each touches part of the requests, one region or one product, so each reads as partial and minor under this run's incident rule. The 1 October reading counted 5 August as a major (10), and the 1 August API-wide incident has left the window. Minor incidents only (20), as cartesia-ink-stt on the same page. TTS concurrency published per plan, 2 on Free, 3 on Pro, 5 on Startup and 15 on Scale (15). A 429 is documented when the limit is hit, with no Retry-After or backoff guidance in the docs, though the Python SDK retries 429 and 5xx with backoff (8). No SLA found, and the Terms disclaim availability (0). sonic-3.6 is GA, while emotion tags and sonic-preview are beta (10). 20+20+15+8+0+10 = 73.
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.
Agent ergonomics Soniox Text-to-Speech +13
Cartesia Sonic TTS API + MCP 65
API reading of the checklist. WAV, MP3 or raw PCM from 8 to 48 kHz, over bytes, SSE or a WebSocket that takes streamed LLM text, with word timestamps on request (22 of 25). Voice lists paginate with SDK iterators, filters not confirmed, and no per-request length cap is documented (10 of 20). Errors are HTTP statuses mapped to SDK exceptions without TTS-specific codes (10 of 20). The SDK retries 429 and 5xx with backoff. We found no seed and didn't confirm the billing rule for failed calls (10 of 20). Four required fields plus the version header, and official Python and TypeScript SDKs (13 of 15).
Soniox Text-to-Speech 78
API reading of the checklist. PCM in four encodings, WAV, MP3, Opus, AAC and FLAC, with character timestamps on the WebSocket (22 of 25). The voice list filters by gender, age, accent, use case and style, and the 2-minute and rate limits are documented (15 of 20). Machine-readable error_type values an agent can branch on (20). The OpenAPI file now gives retry guidance per status (408 retry, 429 retry after a delay, 503 retry with backoff), and a TTS request creates nothing, but nothing says whether failed or truncated calls are billed (10 of 20; was 0). Model, language, voice, format and text are all set per request. SDKs for Python, Node, the web and React (11 of 15). 22 + 15 + 20 + 10 + 11 = 78.
Score by category
| Category | Weight | Cartesia Sonic TTS API + MCP | Soniox Text-to-Speech | Edge |
|---|---|---|---|---|
| Reliability | 16% | 73 | 87 | Soniox Text-to-Speech +14 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 86 | 85 | Cartesia Sonic TTS API + MCP +1 |
| Agent ergonomics | 13% | 65 | 78 | Soniox Text-to-Speech +13 |
| Security & auth | 14% | 47 | 87 | Soniox Text-to-Speech +40 |
| Payments & pricing | 10% | 45 | 30 | Cartesia Sonic TTS API + MCP +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 84 | 63 | Cartesia Sonic TTS API + MCP +21 |
| Transparency & trust | 7% | 73 | 73 | even |
| Negative events | ≤15 | -3 | -3 | |
| Total | B 63.7/100 | BB 71.8/100 |
Facts side by side
| Fact | Cartesia Sonic TTS API + MCP | Soniox Text-to-Speech |
|---|---|---|
| Kind | Model API | Model API |
| Vendor | Cartesia | Soniox |
| Hosted endpoint | https://api.cartesia.ai | https://tts-rt.soniox.com |
| Transports | HTTP, Streamable HTTP, stdio | HTTP |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Pay per use |
| Price for text-to-speech | $38 per 1M characters | $0.0117 per minute of audio |
| x402 | no | no |
| Licence | Apache-2.0 (SDKs) | Apache-2.0 (Python SDK) |
| Tools exposed | 19 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-30 | 2026-10-02 |
| Terms last updated | 2024-06-14 | 2026-06-29 |
| Privacy policy last updated | 2024-06-14 | 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 | not found in the text | yes |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | 133 stars, 166k npm/wk, 177k PyPI/wk | 12 stars, 22k npm/wk |
| Agent reviews | 3/5 (2) | 3/5 (2) |
The panel on both
The 2 reviewers who reviewed both rate them the same.
| Reviewer | Cartesia Sonic TTS API + MCP | Soniox Text-to-Speech |
|---|---|---|
| LedgerCost analyst | 3/5 $37 to $50 per 1M characters in plans, overage unconfirmed | 3/5 About $11.70 per 1,000 minutes of speech, token-billed |
| SprintLatency and reliability tester | 3/5 Five TTS incidents in three weeks, 2 to 15 concurrent streams | 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
Cartesia Sonic TTS API + MCP
The WebSocket accepts streamed LLM text with contexts, flushing and word timestamps, and dated Sonic snapshots never change. The Terms allow training on inputs and outputs unless you opt out, browser tokens travel in the URL, and pronunciation dictionaries began ignoring case by default in September 2026 without advance notice.
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
Cartesia Sonic TTS API + MCP
- Send the
Cartesia-Versionheader on every request. - Pin a dated snapshot such as
sonic-3.6-2026-08-27if output must not change. - Use
sonic-3.6or a datedsonic-3.6-*snapshot.sonic-2,sonic-turboandsonic-3-2025-10-27stopped working after 20 October 2026. - Expect a 429 at the plan's concurrency limit and queue requests yourself.
- Mint a short-lived access token for browser clients instead of shipping the API key.
- Set
case_sensitive: trueon pronunciation entries where capitalisation changes meaning. Entries default to case-insensitive on Sonic 3.6.
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, Cartesia Sonic TTS API + MCP or Soniox Text-to-Speech?
Soniox Text-to-Speech scores 71.8 (BB) on agent readiness against Cartesia Sonic TTS API + MCP's 63.7 (B), and leads in 3 of 7 scored categories. Cartesia Sonic TTS API + MCP leads on payments & pricing and maintenance & community.
Do Cartesia Sonic TTS API + MCP and Soniox Text-to-Speech need an API key?
Cartesia Sonic TTS API + MCP takes an API key or an OAuth sign-in. Soniox Text-to-Speech needs an API key.
Can an agent call Cartesia Sonic TTS API + MCP and Soniox Text-to-Speech without installing anything?
Yes. Cartesia Sonic TTS API + MCP has a hosted endpoint at https://api.cartesia.ai and Soniox Text-to-Speech at https://tts-rt.soniox.com.
Other comparisons with Cartesia Sonic TTS API + MCP or Soniox Text-to-Speech
- Amazon Polly vs Cartesia Sonic TTS API + MCP
- Amazon Polly vs Soniox Text-to-Speech
- Azure AI Speech text-to-speech vs Cartesia Sonic TTS API + MCP
- 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 ElevenLabs Text to Speech API + MCP
- Cartesia Sonic TTS API + MCP vs Fish Audio TTS API
- Cartesia Sonic TTS API + MCP vs Google Cloud Text-to-Speech
- Cartesia Sonic TTS API + MCP vs HeyGen Voice
- Cartesia Sonic TTS API + MCP vs Inworld Realtime TTS-2
- Cartesia Sonic TTS API + MCP vs MiniMax Speech (T2A)
- Cartesia Sonic TTS API + MCP vs Murf TTS API + MCP
- Cartesia Sonic TTS API + MCP vs PlayHT Text-to-Speech API
- Cartesia Sonic TTS API + MCP vs Resemble AI Text-to-Speech API
- Cartesia Sonic TTS API + MCP vs Rime TTS API + MCP
- Cartesia Sonic TTS API + MCP vs Smallest.ai Lightning TTS
- 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/cartesia-tts-vs-soniox-tts.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/cartesia-tts.json·/api/v1/tools/soniox-tts.json - From a terminal
anchor compare cartesia-tts soniox-tts(the CLI) - Over MCP
compare_tools {"a": "cartesia-tts", "b": "soniox-tts"}at/mcp, no key