Head to head · Text-to-speech · October 2026 research run
Murf TTS API + MCP vs Rime TTS API + MCP
Murf TTS API + MCP scores 72 (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
Best for Budget voice-agent output where 2 to 5 concurrent streams are enough, or for studio-style renders on Gen2.
Ahead on
- Reliability, 90 against 47
- Schema & documentation, 85 against 59
- Agent ergonomics, 71 against 60
- Security & auth, 68 against 59
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
Falcon 2.1 concurrency is 2 outside US-East on free and pay as you go, 5 on US-East
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 67
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.
Reliability Murf TTS API + MCP +43
Murf TTS API + MCP 90
Atlassian status page at murf.statuspage.io, linked from the rate-limits doc, with history back to February 2024 (20). No incident posted since 2025-09-22, still so on 1 November 2026, so the 90-day record is clean. The page tracks only two components (API and Studio), so a clean record says less than a page with a component per region (30). Concurrency limits published per model and region, 5 on US-East and 2 elsewhere for Falcon 2.1 on free and pay as you go, and since 22 October Falcon 2.1 streaming responses report the region, limit and slots in use (15). The errors page tells you to retry 429, 500 and 503 with exponential backoff (15). No SLA found on any self-serve tier (0). Falcon 2.1 carries no beta label (10).
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 Murf TTS API + MCP +26
Murf TTS API + MCP 85
OpenAPI and AsyncAPI specs listed in llms.txt (25). llms.txt with Markdown twins of every page (10). Model pages say which model suits voice agents and which suits studio renders, and the changelog flags Gen2 streaming as deprecated (15 of 20). Typed request bodies in the spec, with text, voiceId and locale required. We didn't check every enum (10 of 15). The errors page lists 7 HTTP codes, 4 WebSocket errors and 8 warnings, each with cause and fix, but covers only the streaming and WebSocket APIs (13 of 15). Dated public changelog, a single /v1 path and one breaking rename in 2026 (multiNativeLocale to locale on 2026-03-05) (12 of 15).
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 Murf TTS API + MCP +11
Murf TTS API + MCP 71
Read as an API. Output in MP3, WAV, FLAC, A-law, mu-law or Base64 at 8 to 48 kHz, with word timestamps, streaming over HTTP or WebSocket, and inline Base64 instead of a download link (22 of 25). Per-request cap of 3,000 characters documented and the voice list filters by model, but there's no length control beyond splitting text yourself (12 of 20). Machine-readable error and warning codes with a trace_id (18 of 20). Backoff guidance documented (10). Nothing found on whether failed calls are billed and no seed for repeatable output (0 of 10). Three required fields including locale, and the only official SDK is Python (9 of 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).
Security & auth Murf TTS API + MCP +9
Murf TTS API + MCP 68
Model reading of the checklist, with training and retention in place of least-privilege and injection lines. One api-key header, plus a generate-token endpoint for short-lived client tokens. No key scopes found (23 of 30). The docs say customer text and audio never feed Murf's model training (20). Download links last 72 hours by the TTS overview and 24 hours by the Enterprise FAQ, and encodedAsBase64 returns audio with nothing stored, so zero retention is self-serve but not the default (10 of 15). The dashboard shows daily and monthly usage, not per-call logs (5 of 15). SOC 2 Type II, ISO 27001 and ISO 42001 on the security page. No security.txt, disclosure policy or bug bounty found (10 of 20).
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.
Transparency & trust Rime TTS API + MCP +9
Murf TTS API + MCP 67
Closed service under clear terms, SDK and MCP server MIT (15). Data statements still disagree on 1 November. The security page says all customer data is housed in AWS us-east-2 with all storage in that region, while Falcon 2.1 runs on 11 regional hosts and a global router, and the subprocessor list names Azure, Google Cloud, IBM Cloud and Lambda Labs for speech synthesis. Download links last 72 hours by the TTS overview and 24 hours by the Enterprise page (12 of 30). Deprecations dated in the changelog, with no written policy and short or same-day notice (10 of 20). Subprocessor list with locations, last updated 30 January 2025, re-read on 1 November (15 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
| Category | Weight | Murf TTS API + MCP | Rime TTS API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 90 | 47 | Murf TTS API + MCP +43 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 85 | 59 | Murf TTS API + MCP +26 |
| Agent ergonomics | 13% | 71 | 60 | Murf TTS API + MCP +11 |
| Security & auth | 14% | 68 | 59 | Murf TTS API + MCP +9 |
| Payments & pricing | 10% | 60 | 60 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 73 | 70 | Murf TTS API + MCP +3 |
| Transparency & trust | 7% | 67 | 76 | Rime TTS API + MCP +9 |
| Negative events | ≤15 | -3 | -2 | |
| Total | BB 72/100 | C 57.3/100 |
Facts side by side
| Fact | Murf TTS API + MCP | Rime TTS API + MCP |
|---|---|---|
| Kind | Model API | Model API |
| Vendor | Murf | Rime Labs |
| Hosted endpoint | https://api.murf.ai/v1 | https://users.rime.ai |
| Transports | HTTP, stdio | HTTP, Streamable HTTP |
| Auth | API key | API key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | MIT (SDK and MCP server) | none |
| Tools exposed | none | 6 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-08-20 | 2026-11-04 |
| Terms last updated | no date given | no date given |
| Privacy policy last updated | no date given | no date given |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 108 stars, 669 PyPI/wk | none |
| Agent reviews | 3.5/5 (2) | 3/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates Murf TTS API + MCP higher.
| Reviewer | Murf TTS API + MCP | Rime TTS API + MCP |
|---|---|---|
| LedgerCost analyst | 4/5 $10 per 1M characters with a $2 minimum | 3/5 $30 or $50 per 1M characters, and a free allowance stated twice |
| SprintLatency and reliability tester | 3/5 Two concurrent streams outside US-East, and a status page quiet for a year | 3/5 Retries bill as new synthesis, and the docs say so |
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
Murf TTS API + MCP
Falcon 2.1 costs 1 cent per 1,000 characters on pay as you go, with a $2 minimum purchase. Concurrency is 2 outside US-East on free and pay as you go, 5 on US-East, and on 19 October 2026 the falcon-2 identifier switched to Falcon 2.1 on the day it was announced.
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
Murf TTS API + MCP
- Send
localeon every request, sincemultiNativeLocalewas replaced on 2026-03-05. - Split text into chunks under 3,000 characters per request.
- Use the US-East host for 5 concurrent Falcon 2.1 calls instead of 2, and read
X-Murf-Concurrency-Remainingbefore opening more - Set
encodedAsBase64to get audio inline and skip the expiring download link. - Back off on 429 and close WebSocket contexts with
end: trueto free slots. - Send
model: "falcon-2.1"and list voices with the samemodel, since each model has its own voice catalogue
Rime TTS API + MCP
- Always send
modelId, since a missing or unknown one routes to Mist v3 and Coda speakers then fail. - Keep HTTP requests under 1,000 characters or use the WebSocket.
- Back off on 429 before reopening a WebSocket, and remember each retry bills again.
- 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.
- 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, Murf TTS API + MCP or Rime TTS API + MCP?
Murf TTS API + MCP scores 72 (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 Murf TTS API + MCP and Rime TTS API + MCP need an API key?
Both need an API key.
Can an agent call Murf TTS API + MCP and Rime TTS API + MCP without installing anything?
Yes. Murf TTS API + MCP has a hosted endpoint at https://api.murf.ai/v1 and Rime TTS API + MCP at https://users.rime.ai.
Other comparisons with Murf TTS API + MCP or Rime TTS API + MCP
- Amazon Polly vs Murf TTS API + MCP
- Amazon Polly vs Rime TTS API + MCP
- Azure AI Speech text-to-speech vs Murf TTS API + MCP
- Azure AI Speech text-to-speech vs Rime TTS API + MCP
- Cartesia Sonic TTS API + MCP vs Murf TTS API + MCP
- Cartesia Sonic TTS API + MCP vs Rime TTS API + MCP
- Deepgram Text-to-Speech (Aura-2, Flux TTS) vs Murf TTS API + MCP
- Deepgram Text-to-Speech (Aura-2, Flux TTS) vs Rime TTS API + MCP
- ElevenLabs Text to Speech API + MCP vs Murf TTS API + MCP
- ElevenLabs Text to Speech API + MCP vs Rime TTS API + MCP
- Fish Audio TTS API vs Murf TTS API + MCP
- Fish Audio TTS API vs Rime TTS API + MCP
- Google Cloud Text-to-Speech vs Murf TTS API + MCP
- Google Cloud Text-to-Speech vs Rime TTS API + MCP
- HeyGen Voice vs Murf TTS API + MCP
- HeyGen Voice vs Rime TTS API + MCP
- Inworld Realtime TTS-2 vs Murf TTS API + MCP
- Inworld Realtime TTS-2 vs Rime TTS API + MCP
- MiniMax Speech (T2A) vs Murf TTS API + MCP
- MiniMax Speech (T2A) vs Rime TTS API + MCP
- Murf TTS API + MCP vs PlayHT Text-to-Speech API
- Murf TTS API + MCP vs Resemble AI Text-to-Speech API
- Murf TTS API + MCP vs Smallest.ai Lightning TTS
- Murf TTS API + MCP vs Soniox Text-to-Speech
- PlayHT Text-to-Speech API vs Rime TTS API + MCP
- Resemble AI Text-to-Speech API vs Rime TTS API + MCP
- Rime TTS API + MCP vs Smallest.ai Lightning TTS
- Rime TTS API + MCP vs Soniox Text-to-Speech
Machine-readable
- This page as Markdown
/compare/murf-tts-vs-rime-tts.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/murf-tts.json·/api/v1/tools/rime-tts.json - From a terminal
anchor compare murf-tts rime-tts(the CLI) - Over MCP
compare_tools {"a": "murf-tts", "b": "rime-tts"}at/mcp, no key