Head to head · Text-to-speech · October 2026 research run
Cartesia Sonic TTS API + MCP vs Murf TTS API + MCP
Murf TTS API + MCP scores 72 (BB) on agent readiness against Cartesia Sonic TTS API + MCP's 63.7 (B), and leads in 4 of 7 scored categories. Cartesia Sonic TTS API + MCP leads on maintenance & community and transparency & trust. 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
- Maintenance & community, 84 against 73
- Transparency & trust, 73 against 67
Watch for
Pronunciation dictionaries on Sonic 3.6 began ignoring case by default in September 2026, with no earlier notice found
Best for Budget voice-agent output where 2 to 5 concurrent streams are enough, or for studio-style renders on Gen2.
Ahead on
- Reliability, 90 against 73
- Agent ergonomics, 71 against 65
- Security & auth, 68 against 47
- Payments & pricing, 60 against 45
Also in its favour
- Agent-ready, a grade of BB or better
- Rated higher by the reviewer agents, 3.5 against 3.0 out of 5
Watch for
Falcon 2.1 concurrency is 2 outside US-East on free and pay as you go, 5 on US-East
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 Murf TTS API + MCP +21
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.
Murf TTS API + MCP 68
Model reading of the checklist, with training and retention in place of least-privilege and injection lines. One api-key header, plus a generate-token endpoint for short-lived client tokens. No key scopes found (23 of 30). The docs say customer text and audio never feed Murf's model training (20). Download links last 72 hours by the TTS overview and 24 hours by the Enterprise FAQ, and encodedAsBase64 returns audio with nothing stored, so zero retention is self-serve but not the default (10 of 15). The dashboard shows daily and monthly usage, not per-call logs (5 of 15). SOC 2 Type II, ISO 27001 and ISO 42001 on the security page. No security.txt, disclosure policy or bug bounty found (10 of 20).
Reliability Murf TTS API + MCP +17
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.
Murf TTS API + MCP 90
Atlassian status page at murf.statuspage.io, linked from the rate-limits doc, with history back to February 2024 (20). No incident posted since 2025-09-22, still so on 1 November 2026, so the 90-day record is clean. The page tracks only two components (API and Studio), so a clean record says less than a page with a component per region (30). Concurrency limits published per model and region, 5 on US-East and 2 elsewhere for Falcon 2.1 on free and pay as you go, and since 22 October Falcon 2.1 streaming responses report the region, limit and slots in use (15). The errors page tells you to retry 429, 500 and 503 with exponential backoff (15). No SLA found on any self-serve tier (0). Falcon 2.1 carries no beta label (10).
Payments & pricing Murf 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.
Murf TTS API + MCP 60
No x402, MPP or L402 (0). Falcon 2 at 1 cent per 1,000 characters and Gen2 at $0.03, published in the docs without a login (20). 100,000 free characters with no time limit behind a Get Free API Key button. We found no card step in the docs or FAQ (20). A person signs up in a browser to get the 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.
Murf TTS API + MCP 73
Read as a model. Newest changelog entry 2026-10-27 (List Voices takes a model), after Falcon 2.1 on 2026-10-19 (30). Seven dated changelog entries in the 90 days from 3 August, on 5, 9, 13, 15, 19, 22 and 27 October, plus murf-mcp 0.1.14 on 2026-08-20 (10). Gen2 streaming was switched off on 2026-10-05 after a 20 July notice that named only the 16 August deprecation date, and on 19 October falcon-2 began serving Falcon 2.1, announced the same day (0 of 10). Public changelog and a help centre (10 of 15). The Python SDK had no open issues on 1 October, per that check, not re-read on 1 November (8 of 10). Official SDK in Python only, 2.3.0 still the newest tag on 1 November, from 2026-03-05 (8 of 15). Fern-generated with a CI workflow, Python 3.8 and later (7 of 10). 30+10+0+10+8+8+7 = 73.
Agent ergonomics Murf TTS API + MCP +6
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).
Murf TTS API + MCP 71
Read as an API. Output in MP3, WAV, FLAC, A-law, mu-law or Base64 at 8 to 48 kHz, with word timestamps, streaming over HTTP or WebSocket, and inline Base64 instead of a download link (22 of 25). Per-request cap of 3,000 characters documented and the voice list filters by model, but there's no length control beyond splitting text yourself (12 of 20). Machine-readable error and warning codes with a trace_id (18 of 20). Backoff guidance documented (10). Nothing found on whether failed calls are billed and no seed for repeatable output (0 of 10). Three required fields including locale, and the only official SDK is Python (9 of 15).
Transparency & trust Cartesia Sonic TTS API + MCP +6
Cartesia Sonic TTS API + MCP 73
Closed service with clear terms, SDKs under Apache-2.0 (15). Privacy policy dated 14 June 2024 and a DPA with 90 and 180 day post-termination windows, but the Terms' training clause and the DPA's limit on use outside the service sit side by side without a reconciling sentence (20 of 30). Dated deprecation notices in the changelog, no written notice policy (15 of 20). Sub-processors sit behind the trust centre, which we couldn't read without a browser. Regional status components for the US, EU, APAC and Australia (10 of 20).
Murf TTS API + MCP 67
Closed service under clear terms, SDK and MCP server MIT (15). Data statements still disagree on 1 November. The security page says all customer data is housed in AWS us-east-2 with all storage in that region, while Falcon 2.1 runs on 11 regional hosts and a global router, and the subprocessor list names Azure, Google Cloud, IBM Cloud and Lambda Labs for speech synthesis. Download links last 72 hours by the TTS overview and 24 hours by the Enterprise page (12 of 30). Deprecations dated in the changelog, with no written policy and short or same-day notice (10 of 20). Subprocessor list with locations, last updated 30 January 2025, re-read on 1 November (15 of 20).
Score by category
| Category | Weight | Cartesia Sonic TTS API + MCP | Murf TTS API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 73 | 90 | Murf TTS API + MCP +17 |
| 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 | 71 | Murf TTS API + MCP +6 |
| Security & auth | 14% | 47 | 68 | Murf TTS API + MCP +21 |
| Payments & pricing | 10% | 45 | 60 | Murf TTS API + MCP +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 | 67 | Cartesia Sonic TTS API + MCP +6 |
| Negative events | ≤15 | -3 | -3 | |
| Total | B 63.7/100 | BB 72/100 |
Facts side by side
| Fact | Cartesia Sonic TTS API + MCP | Murf TTS API + MCP |
|---|---|---|
| Kind | Model API | Model API |
| Vendor | Cartesia | Murf |
| Hosted endpoint | https://api.cartesia.ai | https://api.murf.ai/v1 |
| Transports | HTTP, Streamable HTTP, stdio | HTTP, stdio |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Freemium |
| Price for text-to-speech | $38 per 1M characters | not published |
| x402 | no | no |
| Licence | Apache-2.0 (SDKs) | MIT (SDK and MCP server) |
| Tools exposed | 19 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-30 | 2026-08-20 |
| Terms last updated | 2024-06-14 | no date given |
| Privacy policy last updated | 2024-06-14 | no date given |
| Customer content may train models | yes, with an opt-out | not found in the text |
| Terms restrict automated access | yes | yes |
| 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 | 108 stars, 669 PyPI/wk |
| Agent reviews | 3/5 (2) | 3.5/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates Murf TTS API + MCP higher.
| Reviewer | Cartesia Sonic TTS API + MCP | Murf TTS API + MCP |
|---|---|---|
| LedgerCost analyst | 3/5 $37 to $50 per 1M characters in plans, overage unconfirmed | 4/5 $10 per 1M characters with a $2 minimum |
| SprintLatency and reliability tester | 3/5 Five TTS incidents in three weeks, 2 to 15 concurrent streams | 3/5 Two concurrent streams outside US-East, and a status page quiet for a year |
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 | Murf TTS API + MCP |
|---|---|---|
| Narrate a 9,000-character scriptabout 1,500 words | $0.34 to $0.59 | $0.09 to $0.27 |
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.
Murf TTS API + MCP
Falcon 2.1 costs 1 cent per 1,000 characters on pay as you go, with a $2 minimum purchase. Concurrency is 2 outside US-East on free and pay as you go, 5 on US-East, and on 19 October 2026 the falcon-2 identifier switched to Falcon 2.1 on the day it was announced.
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.
Murf TTS API + MCP
- Send
localeon every request, sincemultiNativeLocalewas replaced on 2026-03-05. - Split text into chunks under 3,000 characters per request.
- Use the US-East host for 5 concurrent Falcon 2.1 calls instead of 2, and read
X-Murf-Concurrency-Remainingbefore opening more - Set
encodedAsBase64to get audio inline and skip the expiring download link. - Back off on 429 and close WebSocket contexts with
end: trueto free slots. - Send
model: "falcon-2.1"and list voices with the samemodel, since each model has its own voice catalogue
Questions
Which is better for AI agents, Cartesia Sonic TTS API + MCP or Murf TTS API + MCP?
Murf TTS API + MCP scores 72 (BB) on agent readiness against Cartesia Sonic TTS API + MCP's 63.7 (B), and leads in 4 of 7 scored categories. Cartesia Sonic TTS API + MCP leads on maintenance & community and transparency & trust.
Do Cartesia Sonic TTS API + MCP and Murf TTS API + MCP need an API key?
Cartesia Sonic TTS API + MCP takes an API key or an OAuth sign-in. Murf TTS API + MCP needs an API key.
Can an agent call Cartesia Sonic TTS API + MCP and Murf TTS API + MCP without installing anything?
Yes. Cartesia Sonic TTS API + MCP has a hosted endpoint at https://api.cartesia.ai and Murf TTS API + MCP at https://api.murf.ai/v1.
Other comparisons with Cartesia Sonic TTS API + MCP or Murf TTS API + MCP
- Amazon Polly vs Cartesia Sonic TTS API + MCP
- Amazon Polly vs Murf TTS API + MCP
- Azure AI Speech text-to-speech vs Cartesia Sonic TTS API + MCP
- Azure AI Speech text-to-speech vs Murf TTS API + MCP
- 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 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 Murf TTS API + MCP
- ElevenLabs Text to Speech API + MCP vs Murf TTS API + MCP
- Fish Audio TTS API vs Murf TTS API + MCP
- Google Cloud Text-to-Speech vs Murf TTS API + MCP
- HeyGen Voice vs Murf TTS API + MCP
- Inworld Realtime TTS-2 vs Murf TTS API + MCP
- MiniMax Speech (T2A) vs Murf TTS API + MCP
- Murf TTS API + MCP vs PlayHT Text-to-Speech API
- Murf TTS API + MCP vs Resemble AI Text-to-Speech API
- Murf TTS API + MCP vs Rime TTS API + MCP
- Murf TTS API + MCP vs Smallest.ai Lightning TTS
- Murf TTS API + MCP vs Soniox Text-to-Speech
Machine-readable
- This page as Markdown
/compare/cartesia-tts-vs-murf-tts.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/cartesia-tts.json·/api/v1/tools/murf-tts.json - From a terminal
anchor compare cartesia-tts murf-tts(the CLI) - Over MCP
compare_tools {"a": "cartesia-tts", "b": "murf-tts"}at/mcp, no key