Head to head · Text-to-speech · October 2026 research run
Cartesia Sonic TTS API + MCP vs Rime TTS API + MCP
Cartesia Sonic TTS API + MCP scores 63.7 (B) on agent readiness against Rime TTS API + MCP's 57.3 (C), and leads in 4 of 7 scored categories. Rime TTS API + MCP leads on security & auth and payments & pricing. 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 47
- Schema & documentation, 86 against 59
- Agent ergonomics, 65 against 60
- Maintenance & community, 84 against 70
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 English and a handful of other languages in live voice agents where the operator cares most about data terms and price.
Ahead on
- Security & auth, 59 against 47
- Payments & pricing, 60 against 45
Also in its favour
- Free to start without a card
Watch for
No OpenAPI file read, and the official SDKs are all 0.1.0 alpha
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.
Schema & documentation Cartesia Sonic TTS API + MCP +27
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).
Rime TTS API + MCP 59
No OpenAPI file (0). The Coda Protobuf quickstart says the rime-api package on PyPI carries text_to_speech.proto and text_to_speech.asyncapi.yaml, but pypi.org didn't resolve on 4 November, so the files weren't read and the line stays at 0 as never read. llms.txt with Markdown pages (10). The models page says which model suits what, and that a request without modelId goes to Mist v3 (15 of 20). Parameters are typed in reference tables (10 of 15). Examples on each endpoint and an errors page listing the messages for each status, as plain text (12 of 15). Dated changelog and versioned WebSocket paths (/ws3, /ws2), no API version header (12 of 15). 0+10+15+10+12+12 = 59.
Reliability Cartesia Sonic TTS API + MCP +26
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.
Rime TTS API + MCP 47
status.rime.ai now redirects to www.rimestat.us, an incident.io page with a Text-to-speech API component and history since 30 August 2026 (20, was 10). Its feed lists two incidents in the 90 days from 6 August, "Text-to-speech APIs are partially degraded" on 3 and 5 September, both partial. The window before 30 August can't be read, and this run gives no credit for an unread part of the window, so the line keeps its recorded award (5). The errors page says synthesis concurrency depends on the plan and points to the pricing page, which on 4 November lists the Free, Flex, Scale and Enterprise plans with no concurrency or rate figure, and the WebSocket connection limit isn't published. The Starter figure of 20 concurrent generations is gone (0, was 10). The errors page says to back off on 429 and retry the upgrade after a delay, marks 500 and 502 as retryable and warns that retries bill as new synthesis. Synthesis writes nothing, so safe-retry guidance without idempotency keys earns 12 in this run, as soniox-tts, fish-audio-tts and rime-prism (12, was 15). SLAs are an Enterprise item, none published (0). Coda and Mist v3 are GA (10). 20+5+0+12+0+10 = 47.
Payments & pricing Rime 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.
Rime TTS API + MCP 60
No x402, MPP or L402 (0). Per-minute prices published without a login, Mist v3 $0.030 and Coda v2 $0.050 a minute on Flex, $0.024 and $0.040 on Scale, metered by characters at about 1,000 a minute (20). Every account gets $50 of usage a month on the Free plan with no card (20). A person signs up in a browser (0). 0+20+20+0 = 40. 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 +14
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.
Rime TTS API + MCP 70
Read as a model, on the lines cartesia-tts and fish-audio-tts use for hosted speech models (recency 30, dated releases 10, deprecation notice 10, support 15, issues 10, SDKs 15, health 10). The changelog's newest entry is on-prem release 20261104 for Coda v2 and Mist v3 on 4 November 2026 (30). In the 90 days from 6 August, text-to-speech entries on 15 August, 25 August, 12 September, 25 September, 13 October, 28 October and 4 November, and SDK releases touching the TTS client (10). The terms of 29 October promise at least 30 days' notice before retiring a Model Version used on a paid plan, while Arcana's cloud retirement came 17 days after its 29 July notice (5 of 10, was 0). Public changelog with RSS and a support address (8 of 15). The SDK repository's issues couldn't be read (github.com answers 403), so the line stays absent (0). Official Rime SDKs in Python, Node.js, Go and Rust with TTS clients, newest python-v0.1.0-alpha.29 on 3 November, all alpha, read as rime-prism reads the same SDK (12 of 15, was 0). The SDK repository's checks workflow runs the tests with locked dependencies, results unread (5 of 10, was 0). 30+10+5+8+0+12+5 = 70.
Security & auth Rime TTS API + MCP +12
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.
Rime TTS API + MCP 59
Model reading of the checklist, with training and retention in place of least-privilege and injection lines. One Bearer key per request, sent as a header on WebSockets too, with no scopes or short-lived tokens, so browser apps need a server bridge (20 of 30). The terms effective 29 October 2026 (section 6.3(b)) grant Rime a perpetual licence to train its models on Free Plan customer data, excluding voice recordings and audio with a natural person's voice, with no opt-out found. Paid plans aren't covered by that licence, and the privacy policy says customer data isn't used for training unless agreed (10, was 20). Only character counts are kept by default, and request retention for support is an off-by-default dashboard switch since 2026-08-25 (15). No per-call log found (0 of 15). SOC 2 Type II since May 2025, HIPAA since February 2024 with an audit in March 2026, and a formal vulnerability disclosure programme linked from the security page. No security.txt or bug bounty, the same reading as rime-prism (14 of 20, was 10). 20+10+15+0+14 = 59.
Agent ergonomics Cartesia Sonic TTS API + MCP +5
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).
Rime TTS API + MCP 60
API reading of the checklist. MP3, WAV, Opus, PCM and mu-law from 8 to 96 kHz, chosen by Accept, with word timestamps on /ws3 (22 of 25). HTTP requests stop at 1,000 characters and the WebSocket buffers by sentence, but no voice-list paging or filters found in the API (12 of 20). Errors are plain-text messages, 11 for validation and 5 for auth, with no machine-readable codes, and WebSocket failures arrive as close code 1011 with the reason in a string (12 of 20). Clear retry guidance, and the docs say retries are billed (10 of 20). Two required fields, but the default model breaks Coda speakers. The Rime SDK now has TTS clients in Python, Node.js, Go and Rust that require the model, all 0.1.0 alpha releases. Partly met, so the earlier 4 is kept and flagged (4 of 15).
Score by category
| Category | Weight | Cartesia Sonic TTS API + MCP | Rime TTS API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 73 | 47 | Cartesia Sonic TTS API + MCP +26 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 86 | 59 | Cartesia Sonic TTS API + MCP +27 |
| Agent ergonomics | 13% | 65 | 60 | Cartesia Sonic TTS API + MCP +5 |
| Security & auth | 14% | 47 | 59 | Rime TTS API + MCP +12 |
| Payments & pricing | 10% | 45 | 60 | Rime TTS API + MCP +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 84 | 70 | Cartesia Sonic TTS API + MCP +14 |
| Transparency & trust | 7% | 73 | 76 | Rime TTS API + MCP +3 |
| Negative events | ≤15 | -3 | -2 | |
| Total | B 63.7/100 | C 57.3/100 |
Facts side by side
| Fact | Cartesia Sonic TTS API + MCP | Rime TTS API + MCP |
|---|---|---|
| Kind | Model API | Model API |
| Vendor | Cartesia | Rime Labs |
| Hosted endpoint | https://api.cartesia.ai | https://users.rime.ai |
| Transports | HTTP, Streamable HTTP, stdio | HTTP, Streamable HTTP |
| 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) | none |
| Tools exposed | 19 | 6 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-30 | 2026-11-04 |
| 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 | not found in the text |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | yes | yes |
| Popularity | 133 stars, 166k npm/wk, 177k PyPI/wk | none |
| 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 | Rime TTS API + MCP |
|---|---|---|
| LedgerCost analyst | 3/5 $37 to $50 per 1M characters in plans, overage unconfirmed | 3/5 $30 or $50 per 1M characters, and a free allowance stated twice |
| SprintLatency and reliability tester | 3/5 Five TTS incidents in three weeks, 2 to 15 concurrent streams | 3/5 Retries bill as new synthesis, and the docs say so |
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.
Rime TTS API + MCP
Per-minute prices are public, $50 of free usage a month needs no card, and official SDKs now cover four languages, all alpha. Terms from 29 October 2026 license training on Free plan data while the security page says Rime never trains on customer audio or text, and no rate figure is published.
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.
Rime TTS API + MCP
- Always send
modelId, since a missing or unknown one routes to Mist v3 and Coda speakers then fail. - Keep HTTP requests under 1,000 characters or use the WebSocket.
- Back off on 429 before reopening a WebSocket, and remember each retry bills again.
- Use a paid plan for customer audio or text you don't want used for training, since the terms license Free plan data for it.
- Keep the key server-side, since WebSockets take it in a header and there are no short-lived tokens.
Questions
Which is better for AI agents, Cartesia Sonic TTS API + MCP or Rime TTS API + MCP?
Cartesia Sonic TTS API + MCP scores 63.7 (B) on agent readiness against Rime TTS API + MCP's 57.3 (C), and leads in 4 of 7 scored categories. Rime TTS API + MCP leads on security & auth and payments & pricing.
Do Cartesia Sonic TTS API + MCP and Rime TTS API + MCP need an API key?
Cartesia Sonic TTS API + MCP takes an API key or an OAuth sign-in. Rime TTS API + MCP needs an API key.
Can an agent call Cartesia Sonic TTS API + MCP and Rime TTS API + MCP without installing anything?
Yes. Cartesia Sonic TTS API + MCP has a hosted endpoint at https://api.cartesia.ai and Rime TTS API + MCP at https://users.rime.ai.
Other comparisons with Cartesia Sonic TTS API + MCP or Rime TTS API + MCP
- Amazon Polly vs Cartesia Sonic TTS API + MCP
- Amazon Polly vs Rime TTS API + MCP
- Azure AI Speech text-to-speech vs Cartesia Sonic TTS API + MCP
- Azure AI Speech text-to-speech vs Rime 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 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 Smallest.ai Lightning TTS
- Cartesia Sonic TTS API + MCP vs Soniox Text-to-Speech
- Deepgram Text-to-Speech (Aura-2, Flux TTS) vs Rime TTS API + MCP
- ElevenLabs Text to Speech API + MCP vs Rime TTS API + MCP
- Fish Audio TTS API vs Rime TTS API + MCP
- Google Cloud Text-to-Speech vs Rime TTS API + MCP
- HeyGen Voice vs Rime TTS API + MCP
- Inworld Realtime TTS-2 vs Rime TTS API + MCP
- MiniMax Speech (T2A) vs Rime TTS API + MCP
- Murf TTS API + MCP vs Rime TTS API + MCP
- PlayHT Text-to-Speech API vs Rime TTS API + MCP
- Resemble AI Text-to-Speech API vs Rime TTS API + MCP
- Rime TTS API + MCP vs Smallest.ai Lightning TTS
- Rime TTS API + MCP vs Soniox Text-to-Speech
Machine-readable
- This page as Markdown
/compare/cartesia-tts-vs-rime-tts.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/cartesia-tts.json·/api/v1/tools/rime-tts.json - From a terminal
anchor compare cartesia-tts rime-tts(the CLI) - Over MCP
compare_tools {"a": "cartesia-tts", "b": "rime-tts"}at/mcp, no key