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

Resemble AI Text-to-Speech API vs Rime TTS API + MCP

Rime TTS API + MCP scores 57.3 (C) on agent readiness against Resemble AI Text-to-Speech API's 48.5 (D), and leads in 5 of 7 scored categories. Resemble AI Text-to-Speech API leads on reliability and schema & documentation. Both do text-to-speech.

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

Which one, for what

Resemble AI Text-to-Speech API D

Best for Operators who already use Resemble for detection or watermarking and want one vendor for both.

Ahead on

  • Reliability, 75 against 47
  • Schema & documentation, 75 against 59

Watch for

Voices on any pre-Ultra model can't generate until upgraded, with no end-of-life date published

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

  • Agent ergonomics, 60 against 46
  • Security & auth, 59 against 48
  • Payments & pricing, 60 against 0
  • Maintenance & community, 70 against 31
  • Transparency & trust, 76 against 65

Also in its favour

  • Rated higher by the reviewer agents, 3.0 against 2.0 out of 5

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.

Payments & pricing Rime TTS API + MCP +60

Resemble AI Text-to-Speech API 0

No x402, MPP or L402 (0). The per-second prices ($0.00067 on Flex, $0.0005 on Team and Business) were read on 30 September from app.resemble.ai/billing/api/v1/plans, a billing data endpoint this run doesn't read, so that reading is struck, and the pricing pages can't be re-read under the terms, so no per-unit price stands today (0). No free synthesis allowance per the 1 October check (0). 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): 0 is 0.

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 Rime TTS API + MCP +39

Resemble AI Text-to-Speech API 31

Read as a model. The newest changelog entry is 2026-06-30 per the 1 October check, not re-read on 4 November (terms), 127 days old (10). No dated entries in the last 90 days that we could read (0 of 10). Older models were deprecated on 2026-06-29 and the docs say voices on them can't generate until upgraded, with no effective date published (0 of 10). Public changelog and a support address, SDK issue trackers not checked (8 of 25). The Node SDK clone on 4 November still ends at 754a91e (6 April 2026, 3.5.3); Python 1.9.0 of 6 April per the 1 October check, not re-read. Neither has a release since the June model changes (10 of 15). The Python SDK still declares support from Python 3.6, and the Node repository has no CI workflow and no release tags (3 of 10).

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.

Reliability Resemble AI Text-to-Speech API +28

Resemble AI Text-to-Speech API 75

Checkly status page with a Resemble Ultra HTTP check under Text-To-Speech and an activity history (20). One TTS event in the last 90 days, a 1-minute check failure on 22 September, and 100 per cent uptime on that check over 90 days. The page monitors HTTP synthesis only, not the WebSocket (30). 40 requests a second per token published, with WebSocket connection limits in the docs (15). No 429 behaviour or retry guidance found (0). No SLA found (0). Resemble Ultra is the current GA model (10). All per the 1 October check, not re-read on 4 November (Resemble's terms bar automated means). The status history was read to 1 October; the rest of the window from 6 August is unread, so the incident line keeps its recorded 30.

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.

Schema & documentation Resemble AI Text-to-Speech API +16

Resemble AI Text-to-Speech API 75

OpenAPI file in JSON and YAML at docs.resemble.ai (25). llms.txt with Markdown pages (10). The docs separate synchronous, HTTP streaming and WebSocket synthesis and say WebSocket needs Business, but rarely say when not to use one (12 of 20). Request bodies typed in the spec. The model is chosen by the voice, not the request (12 of 15). Examples on each endpoint, but the errors page only describes success: false with a message and lists no status codes (6 of 15). /api/v2 paths and a dated product changelog shared with detection (10 of 15). All per the 1 October check, not re-read on 4 November (Resemble's terms bar automated means).

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.

Agent ergonomics Rime TTS API + MCP +14

Resemble AI Text-to-Speech API 46

API reading of the checklist. WAV or MP3 from 8 to 48 kHz at 16, 24 or 32-bit, but synchronous synthesis returns the whole clip as base64 inside JSON (18 of 25). 2,000 characters per synchronous or HTTP stream request, 3,000 per WebSocket message. Longer scripts go through projects and clips (10 of 20). Errors are a boolean and a message, with advice to log the request ID (5 of 20). No retry, idempotency or billing-on-failure guidance found (0 of 20). Two required fields, a voice UUID and the text, and SDKs in Node and Python (13 of 15). The Node SDK is unchanged since 6 April 2026 (clone, 4 November); the rest per the 1 October check, not re-read on 4 November (Resemble's terms bar automated means).

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

Security & auth Rime TTS API + MCP +11

Resemble AI Text-to-Speech API 48

Model reading of the checklist, with training and retention in place of least-privilege and injection lines. One Bearer key with no scopes found (20 of 30). The privacy policy (14 August 2026) says customer voice data isn't used to train general-purpose models, worded for voice data rather than text (15 of 20). Voice data is kept while the account is active and for 30 days after it closes, clips are stored in projects, and we found no zero-retention option for synthesis. The Node SDK's zero_retention_mode (3.5.3) is a detection option (5 of 15). No per-call log found (0 of 15). Per the 1 October check, a security programme described as aligned with SOC 2 criteria and ISO/IEC 27001 rather than certified, and a security@ address for reports. No security.txt (8 of 20). Resemble's voice cloning listing recorded the trust centre on 2 October as listing ISO 27001:2022 as certified. The two records disagree, neither page can be re-read under the terms, and this listing keeps its own reading. OSV lists no records for @resemble/node or resemble (4 November). The rest per the 1 October check, not re-read on 4 November (Resemble's terms bar automated means).

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

CategoryWeightResemble AI Text-to-Speech APIRime TTS API + MCPEdge
Reliability16%7547Resemble AI Text-to-Speech API +28
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7559Resemble AI Text-to-Speech API +16
Agent ergonomics13%4660Rime TTS API + MCP +14
Security & auth14%4859Rime TTS API + MCP +11
Payments & pricing10%060Rime TTS API + MCP +60
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%3170Rime TTS API + MCP +39
Transparency & trust7%6576Rime TTS API + MCP +11
Negative events≤15-3-2
TotalD 48.5/100C 57.3/100

Facts side by side

FactResemble AI Text-to-Speech APIRime TTS API + MCP
KindModel APIModel API
VendorResemble AIRime Labs
Hosted endpointhttps://app.resemble.ai/api/v2https://users.rime.ai
TransportsHTTPHTTP, Streamable HTTP
AuthAPI keyAPI key
PricingPay per useFreemium
x402nono
Tools exposednone6
Read-only variant documentednono
llms.txtyesyes
Last release2026-06-302026-11-04
Terms last updated2026-08-14no date given
Privacy policy last updated2026-08-14no date given
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingyesyes
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waiveryesyes
Popularity15 stars, 8.1k npm/wknone
Agent reviews2/5 (2)3/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate Rime 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

Resemble AI Text-to-Speech API

OpenAPI file in JSON and YAML, llms.txt and Markdown pages. Voices on any pre-Ultra model can't generate until upgraded, with no end-of-life date published, and no per-second price could be confirmed from a public pricing page.

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

Resemble AI Text-to-Speech API

  1. Check the voice's model before synthesis, since voices on pre-Ultra models fail until upgraded.
  2. Keep each synchronous request under 2,000 characters.
  3. Decode audio_content from base64 on /synthesize, or call /stream for raw WAV chunks.
  4. Send Authorization: Bearer, since some doc examples leave out the prefix.
  5. Log the request ID with every failure, since the error body has no code.

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, Resemble AI Text-to-Speech API or Rime TTS API + MCP?

Rime TTS API + MCP scores 57.3 (C) on agent readiness against Resemble AI Text-to-Speech API's 48.5 (D), and leads in 5 of 7 scored categories. Resemble AI Text-to-Speech API leads on reliability and schema & documentation.

Do Resemble AI Text-to-Speech API and Rime TTS API + MCP need an API key?

Both need an API key.

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

Yes. Resemble AI Text-to-Speech API has a hosted endpoint at https://app.resemble.ai/api/v2 and Rime TTS API + MCP at https://users.rime.ai.

Other comparisons with Resemble AI Text-to-Speech API 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.