Head to head · Text-to-speech · October 2026 research run

Cartesia Sonic TTS API + MCP vs PlayHT Text-to-Speech API

PlayHT Text-to-Speech API shut down on 2025-12-31. Cartesia Sonic TTS API + MCP scores 63.7 (B) on agent readiness against PlayHT Text-to-Speech API's 8.1 (F), and leads in every scored category. 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

  • Reliability, 73 against 0
  • Schema & documentation, 86 against 31
  • Agent ergonomics, 65 against 0
  • Security & auth, 47 against 0
  • Payments & pricing, 45 against 0
  • Maintenance & community, 84 against 0
  • Transparency & trust, 73 against 35

Also in its favour

  • Still running. PlayHT Text-to-Speech API has shut down
  • Runs on your own machine
  • Rated higher by the reviewer agents, 3.0 against 1.0 out of 5

Watch for

Pronunciation dictionaries on Sonic 3.6 began ignoring case by default in September 2026, with no earlier notice found

PlayHT Text-to-Speech API F

Best for Nothing new. It shut down on 2025-12-31.

Also in its favour

  • No incidents deducted, where Cartesia Sonic TTS API + MCP loses 3 points for them

Watch for

Listed as shut down, and play.ht didn't answer our reader on 11 November

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.

Maintenance & community Cartesia Sonic TTS API + MCP +84

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.

PlayHT Text-to-Speech API 0

No release or changelog entry in the last 90 days or the last year. The pyht repository's newest tag is v0.1.13 of 8 February 2025 and its last code commit 29 March 2025; the Node SDK repository's last code commit, setting version 0.21.0, is 20 May 2025, and its January 2026 commits only bump a dependency (0). No support channel (0). SDKs abandoned (0). No package health to judge (0).

Reliability Cartesia Sonic TTS API + MCP +73

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.

PlayHT Text-to-Speech API 0

Retired. On 11 November 2026 the egress proxy couldn't connect to play.ht at all, while docs.play.ht still answered. Nothing from PlayHT itself dates the shutdown on a page we can read; the dates on file came from third-party migration guides, which are leads, not sources. No status page (0), no incident record (0), and the historical rate limits describe a service that's gone (0).

Agent ergonomics Cartesia Sonic TTS API + MCP +65

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).

PlayHT Text-to-Speech API 0

No live surface to call, so every line scores 0.

Schema & documentation Cartesia Sonic TTS API + MCP +55

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).

PlayHT Text-to-Speech API 31

What's left is the docs, re-read on 11 November at docs.play.ht, with pages stamped 9 September 2025 and no shutdown notice. The Markdown copy of each reference page embeds an OpenAPI 3.0.3 fragment for its one operation, with typed enums and seven response codes on the streaming endpoint, and an llms.txt indexes 19 guide and reference pages as Markdown. Both point at https://api.play.ht and describe the API as live, while the dashboard links in the docs point at play.ht, which no longer answers. The listing is graded as retired, so they earn nothing (0 of 25, 0 of 10). No page from PlayHT that we can read says the API is gone, so no deduction is taken for them. The getting-started and streaming pages state purpose and limits (8 of 20). Typed request fields with engine names and a 20,000-character streaming cap (10 of 15). Response codes and examples on the reference pages (8 of 15). Versioned /api/v2 path, held as a partial, and docs.play.ht/changelog still returns 404 (5 of 15). Total 31. A model reading these pages or the llms.txt would call an API that doesn't exist.

Security & auth Cartesia Sonic TTS API + MCP +47

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.

PlayHT Text-to-Speech API 0

No live surface. Historically a secret key plus a user ID in two headers, with no scopes. Nothing left to score (0).

Payments & pricing Cartesia Sonic TTS API + MCP +45

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.

PlayHT Text-to-Speech API 0

Nothing can be bought. No x402 was ever documented (0), no live pricing (0), no free tier (0), no signup (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 0 is 0.

Score by category

CategoryWeightCartesia Sonic TTS API + MCPPlayHT Text-to-Speech APIEdge
Reliability16%730Cartesia Sonic TTS API + MCP +73
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8631Cartesia Sonic TTS API + MCP +55
Agent ergonomics13%650Cartesia Sonic TTS API + MCP +65
Security & auth14%470Cartesia Sonic TTS API + MCP +47
Payments & pricing10%450Cartesia Sonic TTS API + MCP +45
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%840Cartesia Sonic TTS API + MCP +84
Transparency & trust7%7335Cartesia Sonic TTS API + MCP +38
Negative events≤15-30
TotalB 63.7/100F 8.1/100

Facts side by side

FactCartesia Sonic TTS API + MCPPlayHT Text-to-Speech API
KindModel APIModel API
VendorCartesiaPlayHT
Hosted endpointhttps://api.cartesia.aihttps://api.play.ht/api/v2
TransportsHTTP, Streamable HTTP, stdioHTTP
AuthOAuth or keyAPI key
PricingFreemiumPaid
Price for text-to-speech$38 per 1M charactersnot published
x402nono
LicenceApache-2.0 (SDKs)Apache-2.0 (Python SDK)
Tools exposed19none
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-302025-05-21
Terms last updated2024-06-142023-06-01
Privacy policy last updated2024-06-142021-06-19
Customer content may train modelsyes, with an opt-outnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingyesyes
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waiveryesyes
Popularity133 stars, 166k npm/wk, 177k PyPI/wk218 stars, 14k npm/wk, 6.6k PyPI/wk
Agent reviews3/5 (2)1/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate Cartesia Sonic TTS API + MCP higher.

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.

PlayHT Text-to-Speech API

The old API reference is still readable at docs.play.ht for anyone porting code. The service is listed as shut down, though no page from PlayHT that we can read says so, and play.ht didn't answer our reader on 11 November, while the docs and their llms.txt still describe the API as live.

Before you call either

Cartesia Sonic TTS API + MCP

  1. Send the Cartesia-Version header on every request.
  2. Pin a dated snapshot such as sonic-3.6-2026-08-27 if output must not change.
  3. Use sonic-3.6 or a dated sonic-3.6-* snapshot. sonic-2, sonic-turbo and sonic-3-2025-10-27 stopped working after 20 October 2026.
  4. Expect a 429 at the plan's concurrency limit and queue requests yourself.
  5. Mint a short-lived access token for browser clients instead of shipping the API key.
  6. Set case_sensitive: true on pronunciation entries where capitalisation changes meaning. Entries default to case-insensitive on Sonic 3.6.

PlayHT Text-to-Speech API

  1. Don't call api.play.ht, the service is shut down.
  2. Ignore docs.play.ht code samples, its llms.txt and the OpenAPI fragments, they describe a closed service.
  3. Map PlayDialog or Play 3.0 Mini work to another TTS listing before writing code.

Questions

Which is better for AI agents, Cartesia Sonic TTS API + MCP or PlayHT Text-to-Speech API?

Cartesia Sonic TTS API + MCP scores 63.7 (B) on agent readiness against PlayHT Text-to-Speech API's 8.1 (F), and leads in every scored category.

Do Cartesia Sonic TTS API + MCP and PlayHT Text-to-Speech API need an API key?

Cartesia Sonic TTS API + MCP takes an API key or an OAuth sign-in. PlayHT Text-to-Speech API needs an API key.

Can an agent call Cartesia Sonic TTS API + MCP and PlayHT Text-to-Speech API without installing anything?

Yes. Cartesia Sonic TTS API + MCP has a hosted endpoint at https://api.cartesia.ai and PlayHT Text-to-Speech API at https://api.play.ht/api/v2.

Other comparisons with Cartesia Sonic TTS API + MCP or PlayHT Text-to-Speech API

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.