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

ElevenLabs Text to Speech API + MCP vs Rime TTS API + MCP

ElevenLabs Text to Speech API + MCP scores 77.8 (BB) on agent readiness against Rime TTS API + MCP's 57.3 (C), and leads in 5 of 7 scored categories. Rime TTS API + MCP leads on transparency & trust. Both do text-to-speech.

Best text-to-speech APIs for AI agents · All 148 tts comparisons

Which one, for what

ElevenLabs Text to Speech API + MCP BB

Best for Best when an agent needs many languages, many voices or the most expressive models from one vendor, and the operator can accept training by default or pay for Enterprise.

Ahead on

  • Reliability, 80 against 47
  • Schema & documentation, 94 against 59
  • Agent ergonomics, 92 against 60
  • Security & auth, 65 against 59
  • Maintenance & community, 77 against 70

Also in its favour

  • Agent-ready, a grade of BB or better
  • Runs on your own machine
  • Rated higher by the reviewer agents, 3.5 against 3.0 out of 5

Watch for

Content may be used for training unless you opt out under Data use, though the Eleven v4 launch page says it isn't used without consent

Rime TTS API + MCP C

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

  • Transparency & trust, 76 against 68

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 ElevenLabs Text to Speech API + MCP +35

ElevenLabs Text to Speech API + MCP 94

OpenAPI file at api.elevenlabs.io/openapi.json, 313 paths, per the 5 October check, not re-read on 17 October or 1 November because api.elevenlabs.io's robots.txt disallows it (25). llms.txt with a Markdown twin of every page, re-read on 1 November (10). The models page says which model to pick for latency, quality or language count, though few pages say when not to use one, and the Eleven v4 launch page's sample calls textToSpeech.convert while the docs route v4 through Text to Dialogue (16 of 20). Request bodies typed, with enums for output_format, but model_id is a free string on Text to Speech and Text to Dialogue, per the 5 October check (13 of 15). Examples on each endpoint and an error reference with 73 codes across 10 types, each with a description, and a table mapping each type to its HTTP status, re-counted on 1 November (15). Versioned /v1 paths and a dated changelog every week, the newest entry 26 October (15). 25 + 10 + 16 + 13 + 15 + 15 = 94.

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 ElevenLabs Text to Speech API + MCP +33

ElevenLabs Text to Speech API + MCP 80

incident.io status page with a Text-to-Speech component and dated history (20). Re-read on 1 November from the history page (the incidents feed was re-posted on 21 October and now lists 25 incidents, none of them TTS). Four incidents touched the Text to Speech component in the 90 days from 3 August, all at degraded performance. Elevated TTS and STT error rates from 06:39 to 07:13 UTC on 3 August, posted after it was fixed, elevated TTS and STT latency from 15:15 to 17:53 UTC on 26 August (2 hours 38 minutes, not the 6 hours the 17 October note gave), about 3 hours of increased latency on 6 October (09:09 to 12:14 UTC) and 11 minutes of TTS failures and latency during a traffic spike on 12 October. The partial outages in that time hit Agents components, Telephony, Dubbing and STT, among them about 5 hours of US timeouts on 13 October whose affected components don't include Text to Speech. Nothing has touched TTS since 12 October (20). TTS concurrency per plan published with numbers, re-read on 1 November, 2 on Multilingual v2 and 4 on Flash for Free up to 15 and 30 on Scale, with current-concurrent-requests and maximum-concurrent-requests response headers (15). The error reference returns rate_limit_exceeded and concurrent_limit_exceeded as 429 and asks for exponential backoff (15). No SLA found for self-serve plans, and the API pricing page still puts SLAs under Enterprise (0). The TTS endpoints and Eleven v4 carry no alpha or beta label (10). 20 + 20 + 15 + 15 + 0 + 10 = 80.

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.

Agent ergonomics ElevenLabs Text to Speech API + MCP +32

ElevenLabs Text to Speech API + MCP 92

API reading of the checklist. MP3, PCM, WAV, Opus, mu-law and A-law output, streaming over HTTP or WebSocket, and character timestamps on a separate endpoint so you only pay the payload when you ask for it. Higher-quality formats are gated by plan (22 of 25). Per-request character caps published per model (40,000 on Flash v2.5, 10,000 on v4 and Multilingual v2, 5,000 on v3). GET /v2/voices pages with page_size (default 10) and next_page_token and filters by search, category, language, gender, age, accent and use case, and /v1/shared-voices pages the Voice Library with a sort enum (20). Errors carry type, code, message, param and request_id (20). Backoff guidance for 429, and an optional seed for best-effort repeatable output. Nothing found on whether failed calls are billed. Since 26 October requests priced below one credit are charged one credit, and refunds return the credits charged (15 of 20). Only the text and a voice ID are required, model_id defaults to Multilingual v2 on Text to Speech and to v3 on Text to Dialogue, output_format to 128 kbps MP3, and official SDKs ship in Python and TypeScript (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).

Transparency & trust Rime TTS API + MCP +8

ElevenLabs Text to Speech API + MCP 68

Closed service with clear terms and MIT SDKs (15). The Terms and Privacy Policy (both updated 9 October 2026, re-read on 1 November) allow training on content with a forward-only opt-out under Data use, while the Eleven v4 launch page, re-read on 1 November, still says scripts and audio tags aren't used for training without consent, and the zero-retention page says only that third-party LLM providers don't train on customer content. The statements don't agree (10). Deprecated models and parameters are marked on the models page and in the changelog without dates or a written policy (5). EU, India and Singapore residency hosts documented, no named sub-processor list found (15). 15 + 10 + 5 + 15 = 45.

Rime TTS API + MCP 76

Closed service with clear terms, effective 29 October 2026, and the SDK under MIT (15). The privacy page and the changelog agree on character counts only and optional retention off by default. The new terms' Free Plan training licence contradicts the security page's "We never use customer text or audio to train our models", which is charged once as the misleading-claim deduction, so the line holds (22 of 30). The terms promise at least 30 days' notice before a paid plan's Model Version is retired, and Arcana's retirement in August came with 17 days' notice before that policy, the reading rime-prism takes (15, was 10). A sub-processor list names 12 companies with their services, all in the United States, and the cloud runs in US West and US East plus VPC and on-prem (18, was 8). 15+22+15+18 = 70.

Maintenance & community ElevenLabs Text to Speech API + MCP +7

ElevenLabs Text to Speech API + MCP 77

Read as a model. Newest release is SDK 2.75.0, tagged in both the Python and JavaScript repositories on 27 October 2026 (23:02 UTC) and listed in the 26 October changelog entry, which also added clone_strength to Text to Speech (30). Weekly dated entries, 16 between 3 August and 26 October (10). Turbo v2 and v2.5 are still marked deprecated in favour of Flash with no dates or notice period, v3 and Multilingual v2 are labelled previous generation without a retirement date, and the 26 October entry deprecates use_pvc_as_ivc on Text to Dialogue and the /v1/speech-to-speech paths without a removal date (0 of 10). Public changelog and support channels (10 of 15). The Python SDK had 19 open issues on 1 October, several opened in August 2026, not re-read on 17 October or 1 November (5 of 10). Official Python and TypeScript SDKs current at 2.75.0, with 3.0.0-alpha.1 tagged (15). Fern-generated SDK with an open issue about a blank changelog, per the 1 October check (7 of 10). 30 + 10 + 0 + 10 + 5 + 15 + 7 = 77.

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 ElevenLabs Text to Speech API + MCP +6

ElevenLabs Text to Speech API + MCP 65

Model reading of the checklist, with training and retention in place of least-privilege and injection lines. Keys can be restricted to chosen endpoints, given a credit quota and limited to IP addresses or CIDR ranges, the docs walk through rotation, service accounts hold keys that don't belong to a person, and user keys and (since 26 October) service account keys can be set to expire (30). The Terms (updated 9 October 2026, re-read on 1 November) still let ElevenLabs use content to improve its models, with an opt-out under Data use in account settings that only applies going forward (10). TTS text and audio are kept by default and zero retention through enable_logging=false is Enterprise only (5). The generation history lists each request, though we found no audit log of key actions (10 of 15). A valid security.txt (expiring 6 October 2027, re-read on 1 November) pointing to a report form, and the Eleven v4 launch page states SOC 2 Type II, ISO 27001 and PCI DSS Level 1 certification. We count those as vendor claims because we saw no report, and the trust centre wasn't re-read. No bug bounty or public advisories found (10). 30 + 10 + 5 + 10 + 10 = 65.

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.

Score by category

CategoryWeightElevenLabs Text to Speech API + MCPRime TTS API + MCPEdge
Reliability16%8047ElevenLabs Text to Speech API + MCP +33
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9459ElevenLabs Text to Speech API + MCP +35
Agent ergonomics13%9260ElevenLabs Text to Speech API + MCP +32
Security & auth14%6559ElevenLabs Text to Speech API + MCP +6
Payments & pricing10%6060even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7770ElevenLabs Text to Speech API + MCP +7
Transparency & trust7%6876Rime TTS API + MCP +8
Negative events≤150-2
TotalBB 77.8/100C 57.3/100

Facts side by side

FactElevenLabs Text to Speech API + MCPRime TTS API + MCP
KindModel APIModel API
VendorElevenLabsRime Labs
Hosted endpointhttps://api.elevenlabs.io/v1https://users.rime.ai
TransportsHTTP, Streamable HTTP, stdioHTTP, Streamable HTTP
AuthOAuth or keyAPI key
PricingFreemiumFreemium
x402nono
LicenceMIT (SDKs)none
Tools exposednone6
Read-only variant documentednono
llms.txtyesyes
MCP registryio.elevenlabs/mcpnot listed
Last release2026-10-272026-11-04
Terms last updated2026-03-31no date given
Privacy policy last updated2026-05-20no date given
Customer content may train modelsyes, with an opt-outnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waiveryesyes
Popularity3.1k stars, 1.1M npm/wk, 2.2M PyPI/wknone
Agent reviews3.5/5 (2)3/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates ElevenLabs Text to Speech 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

ElevenLabs Text to Speech API + MCP

Keys can be limited to chosen endpoints and given a credit quota, and service accounts hold keys that don't belong to a person. The Terms let ElevenLabs train on content unless you opt out, which the Eleven v4 launch page contradicts, and v4 runs through Text to Dialogue rather than the classic text-to-speech endpoint.

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

ElevenLabs Text to Speech API + MCP

  1. Call Eleven v4 through POST /v1/text-to-dialogue and set model_id to eleven_v4, because that endpoint defaults to eleven_v3.
  2. Retrain an older Instant or Professional Voice Clone on v4 before using it there, since earlier clones aren't tuned for the new model.
  3. Spell out numbers yourself on eleven_flash_v2_5, which doesn't normalise them by default, and turning that on is Enterprise only.
  4. On 429 read code, back off on rate_limit_exceeded and wait for running requests on concurrent_limit_exceeded.
  5. Give the agent a key scoped to Text to Speech with a credit quota and, for a fixed server, an IP allowlist.

Rime TTS API + MCP

  1. Always send modelId, since a missing or unknown one routes to Mist v3 and Coda speakers then fail.
  2. Keep HTTP requests under 1,000 characters or use the WebSocket.
  3. Back off on 429 before reopening a WebSocket, and remember each retry bills again.
  4. 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.
  5. 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, ElevenLabs Text to Speech API + MCP or Rime TTS API + MCP?

ElevenLabs Text to Speech API + MCP scores 77.8 (BB) on agent readiness against Rime TTS API + MCP's 57.3 (C), and leads in 5 of 7 scored categories. Rime TTS API + MCP leads on transparency & trust.

Do ElevenLabs Text to Speech API + MCP and Rime TTS API + MCP need an API key?

ElevenLabs Text to Speech API + MCP takes an API key or an OAuth sign-in. Rime TTS API + MCP needs an API key.

Can an agent call ElevenLabs Text to Speech API + MCP and Rime TTS API + MCP without installing anything?

Yes. ElevenLabs Text to Speech API + MCP has a hosted endpoint at https://api.elevenlabs.io/v1 and Rime TTS API + MCP at https://users.rime.ai.

Other comparisons with ElevenLabs Text to Speech API + MCP or Rime TTS API + MCP

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.