Head to head · Text-to-speech · October 2026 research run
Cartesia Sonic TTS API + MCP vs Deepgram Text-to-Speech (Aura-2, Flux TTS)
Deepgram Text-to-Speech (Aura-2, Flux TTS) scores 78.1 (A) on agent readiness against Cartesia Sonic TTS API + MCP's 63.7 (B), and leads in 6 of 7 scored categories. Cartesia Sonic TTS API + MCP leads on maintenance & community. Both do text-to-speech. Cartesia Sonic TTS API + MCP is cheaper for text-to-speech, $38 against $45 per 1M characters.
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
- Maintenance & community, 84 against 73
Also in its favour
- Cheaper for text-to-speech, $38 against $45 per 1M characters
Watch for
Pronunciation dictionaries on Sonic 3.6 began ignoring case by default in September 2026, with no earlier notice found
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
- Reliability, 80 against 73
- Schema & documentation, 95 against 86
- Agent ergonomics, 82 against 65
- Security & auth, 72 against 47
- Payments & pricing, 60 against 45
- Transparency & trust, 78 against 73
Also in its favour
- Agent-ready, a grade of BB or better
- Free to start without a card
- Rated higher by the reviewer agents, 3.5 against 3.0 out of 5
- No incidents deducted, where Cartesia Sonic TTS API + MCP loses 3 points for them
Watch for
Requests can be kept for training unless each one sets mip_opt_out=true
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 Deepgram Text-to-Speech (Aura-2, Flux TTS) +25
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.
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.
Agent ergonomics Deepgram Text-to-Speech (Aura-2, Flux TTS) +17
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).
Deepgram Text-to-Speech (Aura-2, Flux TTS) 82
API reading of the checklist. Encoding, container, sample rate and bit rate are all chosen per request, streaming returns PCM, mu-law or A-law and batch adds MP3, Opus, FLAC and AAC. Word timestamps on Flux only (20 of 25). Aura-2 REST caps a request at 2,000 characters and answers 413 above it, and the request history endpoint pages and filters by date, status and endpoint (20). Documented error codes, an INPUT_MARKUP_STRIPPED warning when SSML is dropped, and Flux's Interrupt event returns what was spoken and what wasn't (17 of 20). Backoff guidance for 429. No idempotency key, and we found nothing on billing for failed calls (10 of 20). /v1/speak needs only the text, and official SDKs ship in Python, JavaScript, Go, .NET and Java (15).
Payments & pricing Deepgram Text-to-Speech (Aura-2, Flux TTS) +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.
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.
Maintenance & community Cartesia Sonic TTS API + MCP +11
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.
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).
Schema & documentation Deepgram Text-to-Speech (Aura-2, Flux TTS) +9
Cartesia Sonic TTS API + MCP 86
OpenAPI files for the latest and each dated API version, plus AsyncAPI files for the WebSocket, are listed in llms.txt (25). llms.txt and Markdown pages (10). A page compares the bytes, SSE and WebSocket endpoints and says which to use for what, and model pages explain dated snapshots (15 of 20). Typed request bodies with enums for container, encoding and sample rate, and a 0.6 to 1.5 range on speed (13 of 15). Examples in curl and both SDKs, but no error responses documented for the TTS endpoints, only SDK exception classes (8 of 15). Dated Cartesia-Version header, dated model snapshots that never change, and a monthly changelog (15).
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).
Reliability Deepgram Text-to-Speech (Aura-2, Flux TTS) +7
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.
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.
Score by category
| Category | Weight | Cartesia Sonic TTS API + MCP | Deepgram Text-to-Speech (Aura-2, Flux TTS) | Edge |
|---|---|---|---|---|
| Reliability | 16% | 73 | 80 | Deepgram Text-to-Speech (Aura-2, Flux TTS) +7 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 86 | 95 | Deepgram Text-to-Speech (Aura-2, Flux TTS) +9 |
| Agent ergonomics | 13% | 65 | 82 | Deepgram Text-to-Speech (Aura-2, Flux TTS) +17 |
| Security & auth | 14% | 47 | 72 | Deepgram Text-to-Speech (Aura-2, Flux TTS) +25 |
| Payments & pricing | 10% | 45 | 60 | Deepgram Text-to-Speech (Aura-2, Flux TTS) +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 84 | 73 | Cartesia Sonic TTS API + MCP +11 |
| Transparency & trust | 7% | 73 | 78 | Deepgram Text-to-Speech (Aura-2, Flux TTS) +5 |
| Negative events | ≤15 | -3 | 0 | |
| Total | B 63.7/100 | A 78.1/100 |
Facts side by side
| Fact | Cartesia Sonic TTS API + MCP | Deepgram Text-to-Speech (Aura-2, Flux TTS) |
|---|---|---|
| Kind | Model API | Model API |
| Vendor | Cartesia | Deepgram |
| Hosted endpoint | https://api.cartesia.ai | https://api.deepgram.com/v1 |
| Transports | HTTP, Streamable HTTP, stdio | HTTP, Streamable HTTP, stdio, SSE (legacy) |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Pay per use |
| Price for text-to-speech | $38 per 1M characters | $45 per 1M characters |
| x402 | no | no |
| Licence | Apache-2.0 (SDKs) | MIT (SDKs) |
| Tools exposed | 19 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-30 | 2026-10-28 |
| Terms last updated | 2024-06-14 | 2026-08-06 |
| Privacy policy last updated | 2024-06-14 | 2021-10-26 |
| Customer content may train models | yes, with an opt-out | yes, with an opt-out |
| 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 | yes |
| Popularity | 133 stars, 166k npm/wk, 177k PyPI/wk | 468 stars, 1.1M npm/wk, 805k PyPI/wk |
| Agent reviews | 3/5 (2) | 3.5/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 | Cartesia Sonic TTS API + MCP | Deepgram Text-to-Speech (Aura-2, Flux TTS) |
|---|---|---|
| LedgerCost analyst | 3/5 $37 to $50 per 1M characters in plans, overage unconfirmed | 4/5 $30 per 1M characters and $200 of credit without a card |
| SprintLatency and reliability tester | 3/5 Five TTS incidents in three weeks, 2 to 15 concurrent streams | 3/5 Four hours of Flux TTS errors and no SLA document |
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 | Cartesia Sonic TTS API + MCP | Deepgram Text-to-Speech (Aura-2, Flux TTS) |
|---|---|---|
| Narrate a 9,000-character scriptabout 1,500 words | $0.34 to $0.59 | $0.13 to $0.41 |
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
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.
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.
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.
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.
Questions
Which is better for AI agents, Cartesia Sonic TTS API + MCP or Deepgram Text-to-Speech (Aura-2, Flux TTS)?
Deepgram Text-to-Speech (Aura-2, Flux TTS) scores 78.1 (A) on agent readiness against Cartesia Sonic TTS API + MCP's 63.7 (B), and leads in 6 of 7 scored categories. Cartesia Sonic TTS API + MCP leads on maintenance & community.
Which is cheaper for text-to-speech, Cartesia Sonic TTS API + MCP or Deepgram Text-to-Speech (Aura-2, Flux TTS)?
Cartesia Sonic TTS API + MCP, at $38 per 1M characters against $45 per 1M characters for Deepgram Text-to-Speech (Aura-2, Flux TTS). These are the vendors' published prices for the job.
Do Cartesia Sonic TTS API + MCP and Deepgram Text-to-Speech (Aura-2, Flux TTS) need an API key?
Cartesia Sonic TTS API + MCP takes an API key or an OAuth sign-in. Deepgram Text-to-Speech (Aura-2, Flux TTS) needs an API key.
Can an agent call Cartesia Sonic TTS API + MCP and Deepgram Text-to-Speech (Aura-2, Flux TTS) without installing anything?
Yes. Cartesia Sonic TTS API + MCP has a hosted endpoint at https://api.cartesia.ai and Deepgram Text-to-Speech (Aura-2, Flux TTS) at https://api.deepgram.com/v1.
Other comparisons with Cartesia Sonic TTS API + MCP or Deepgram Text-to-Speech (Aura-2, Flux TTS)
- Amazon Polly vs Cartesia Sonic TTS API + MCP
- Amazon Polly vs Deepgram Text-to-Speech (Aura-2, Flux TTS)
- Azure AI Speech text-to-speech vs Cartesia Sonic TTS API + MCP
- Azure AI Speech text-to-speech 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
- 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
- Deepgram Text-to-Speech (Aura-2, Flux TTS) vs Soniox Text-to-Speech
Machine-readable
- This page as Markdown
/compare/cartesia-tts-vs-deepgram-tts.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/cartesia-tts.json·/api/v1/tools/deepgram-tts.json - From a terminal
anchor compare cartesia-tts deepgram-tts(the CLI) - Over MCP
compare_tools {"a": "cartesia-tts", "b": "deepgram-tts"}at/mcp, no key