Get an audit

Head to head · Speech tts · October 2026 research run

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

Rime TTS API + MCP has a score of 56.1 (C) against PlayHT Text-to-Speech API's 4.2 (F). Both do speech tts. The largest gap is security & auth, 65 points.

PlayHT Text-to-Speech APIPlayHT · Model API F4.2/100retired, not ranked Rime TTS API + MCPRime Labs · Model API C56.1/100#305 of 452

Which one, for what

Pick PlayHT Text-to-Speech API for

No category where it leads by five points or more.

Pick Rime TTS API + MCP for

  • reliability (+50)
  • schema & documentation (+28)
  • agent ergonomics (+60)
  • security & auth (+65)
  • payments & pricing (+40)
  • maintenance & community (+48)
  • transparency & trust (+35)

Score by category

CategoryWeight this runPlayHT Text-to-Speech APIRime TTS API + MCPEdge
Reliability16%20050Rime TTS API + MCP +50
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.23159Rime TTS API + MCP +28
Agent ergonomics13%16.2060Rime TTS API + MCP +60
Security & auth14%17.5065Rime TTS API + MCP +65
Payments & pricing10%12.5040Rime TTS API + MCP +40
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.8048Rime TTS API + MCP +48
Transparency & trust7%8.83671Rime TTS API + MCP +35
Negative events≤15-40
Total4.2 · F56.1 · C

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
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listednot listed
Last release2025-05-212026-09-25
Popularity218 stars, 14k npm/wk, 6.6k PyPI/wknone
Agent reviews1/5 (2)3/5 (2)

Verdicts

PlayHT Text-to-Speech API

The old API reference is still readable at docs.play.ht for anyone porting code. api.play.ht doesn't resolve, so every call fails.

Rime TTS API + MCP

Only character counts are kept by default, and customer data isn't used for training without an opt-in. No OpenAPI or AsyncAPI file and no official SDKs.

Before you call either

PlayHT Text-to-Speech API

  1. Don't call api.play.ht, it doesn't resolve.
  2. Ignore docs.play.ht code samples, 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 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 /ws3 when you need word timestamps.
  5. Keep the key server-side, since WebSockets take it in a header and there are no short-lived tokens.

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.

Get an auditSee a sample report