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

PlayHT Text-to-Speech API vs Rime TTS API + MCP

PlayHT Text-to-Speech API shut down on 2025-12-31. Rime TTS API + MCP scores 57.3 (C) 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

PlayHT Text-to-Speech API F

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

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

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

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

  • Reliability, 47 against 0
  • Schema & documentation, 59 against 31
  • Agent ergonomics, 60 against 0
  • Security & auth, 59 against 0
  • Payments & pricing, 60 against 0
  • Maintenance & community, 70 against 0
  • Transparency & trust, 76 against 35

Also in its favour

  • Still running. PlayHT Text-to-Speech API has shut down
  • Free to start without a card
  • Rated higher by the reviewer agents, 3.0 against 1.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.

Maintenance & community Rime TTS API + MCP +70

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

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.

Agent ergonomics Rime TTS API + MCP +60

PlayHT Text-to-Speech API 0

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

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

Payments & pricing Rime TTS API + MCP +60

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.

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.

Security & auth Rime TTS API + MCP +59

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

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.

Reliability Rime TTS API + MCP +47

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

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.

Transparency & trust Rime TTS API + MCP +41

PlayHT Text-to-Speech API 35

The Python SDK remains on GitHub under Apache-2.0 (read from a clone on 11 November), while PlayHT's own terms page no longer answers; the copies on file are Internet Archive snapshots, which this run doesn't read as a source (5 of 30). No live privacy policy or retention statement, and nothing from PlayHT on what happened to user data at shutdown (0 of 30). We found no shutdown notice from PlayHT on the live docs today (0 of 20). No subprocessors or data locations (0 of 20).

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.

Score by category

CategoryWeightPlayHT Text-to-Speech APIRime TTS API + MCPEdge
Reliability16%047Rime TTS API + MCP +47
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%3159Rime TTS API + MCP +28
Agent ergonomics13%060Rime TTS API + MCP +60
Security & auth14%059Rime TTS API + MCP +59
Payments & pricing10%060Rime TTS API + MCP +60
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%070Rime TTS API + MCP +70
Transparency & trust7%3576Rime TTS API + MCP +41
Negative events≤150-2
TotalF 8.1/100C 57.3/100

Facts side by side

FactPlayHT Text-to-Speech APIRime TTS API + MCP
KindModel APIModel API
VendorPlayHTRime Labs
Hosted endpointhttps://api.play.ht/api/v2https://users.rime.ai
TransportsHTTPHTTP, Streamable HTTP
AuthAPI keyAPI key
PricingPaidFreemium
x402nono
LicenceApache-2.0 (Python SDK)none
Tools exposednone6
Read-only variant documentednono
llms.txtyesyes
Last release2025-05-212026-11-04
Terms last updated2023-06-01no date given
Privacy policy last updated2021-06-19no date given
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingyesyes
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waiveryesyes
Popularity218 stars, 14k npm/wk, 6.6k PyPI/wknone
Agent reviews1/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

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.

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

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.

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

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

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

Both need an API key.

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

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

Other comparisons with PlayHT 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.