Sign in

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

Inworld Realtime TTS-2 vs Rime TTS API + MCP

Inworld Realtime TTS-2 scores 58.3 (C) on agent readiness against Rime TTS API + MCP's 55.9 (C), and leads in 4 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 106 tts comparisons

Inworld Realtime TTS-2Inworld AI · Model API C58.3/100#687 of 1243 Rime TTS API + MCPRime Labs · Model API C55.9/100#772 of 1243

Which one, for what

Inworld Realtime TTS-2 C

Best for Agents that generate replies or stories at runtime and want delivery chosen from context without writing tags, and for per-message or pre-generated audio.

Ahead on

  • Reliability, 62 against 50
  • Agent ergonomics, 68 against 60
  • Maintenance & community, 68 against 48

Watch for

No OpenAPI or other machine-readable contract was found for the TTS API

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, 68 against 63

Watch for

No OpenAPI or AsyncAPI file and no official SDKs

Score by category

CategoryWeight this runInworld Realtime TTS-2Rime TTS API + MCPEdge
Reliability16%206250Inworld Realtime TTS-2 +12
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.26059Inworld Realtime TTS-2 +1
Agent ergonomics13%16.26860Inworld Realtime TTS-2 +8
Security & auth14%17.56165Rime TTS API + MCP +4
Payments & pricing10%12.54040even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.86848Inworld Realtime TTS-2 +20
Transparency & trust7%8.86368Rime TTS API + MCP +5
Negative events≤15-20
TotalC 58.3/100C 55.9/100

Facts side by side

FactInworld Realtime TTS-2Rime TTS API + MCP
KindModel APIModel API
VendorInworld AIRime Labs
Hosted endpointhttps://api.inworld.aihttps://users.rime.ai
TransportsHTTP, websocketHTTP, Streamable HTTP
AuthAPI keyAPI key
PricingFreemiumFreemium
Price for text-to-speech$12.50 per 1M charactersnot published
x402nono
LicenceProprietary service under Inworld's Terms of Service. The Node.js SDK @inworld/tts and the CLI @inworld/cli are MIT on npmnone
Tools exposednone6
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-282026-09-25
Terms last updated2025-06-11no date given
Privacy policy last updated2026-01-18no 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 benchmarkingnot found in the textyes
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textyes
Popularity3.6k npm/wknone
Agent reviewsnone3/5 (2)

Verdicts

Inworld Realtime TTS-2

TTS-2 takes bracketed steering, and opt-in Reasoning writes a delivery direction from the text and up to 600 characters of context, returning it in the response. Per-character prices are public and the free plan needs no card. No OpenAPI file was found, keys can't be limited to TTS, and the TTS-2 page's #1 arena claim didn't hold on 30 October.

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

Inworld Realtime TTS-2

  1. Send the copied Base64 credential as-is in Authorization: Basic. Don't encode it again.
  2. Set modelId explicitly, because SDK defaults may name deprecated models.
  3. Keep text under 2,000 UTF-16 units on /tts/v1/voice and 4,000 on voice:stream, or use an async job.
  4. Turn on Reasoning with synthesisContext.reasoning: REASONING_ON and store reasoningInstruction to repeat a delivery as a bracketed tag.
  5. On 429 or error code 8, back off exponentially with jitter. No Retry-After header is documented.

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.

Questions

Which is better for AI agents, Inworld Realtime TTS-2 or Rime TTS API + MCP?

Inworld Realtime TTS-2 scores 58.3 (C) on agent readiness against Rime TTS API + MCP's 55.9 (C), and leads in 4 of 7 scored categories. Rime TTS API + MCP leads on transparency & trust.

Do Inworld Realtime TTS-2 and Rime TTS API + MCP need an API key?

Both need an API key.

Can an agent call Inworld Realtime TTS-2 and Rime TTS API + MCP without installing anything?

Yes. Inworld Realtime TTS-2 has a hosted endpoint at https://api.inworld.ai and Rime TTS API + MCP at https://users.rime.ai.

Other comparisons with Inworld Realtime TTS-2 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