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

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

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

Murf TTS API + MCP BB

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 0
  • Schema & documentation, 85 against 31
  • Agent ergonomics, 71 against 0
  • Security & auth, 68 against 0
  • Payments & pricing, 60 against 0
  • Maintenance & community, 73 against 0
  • Transparency & trust, 67 against 35

Also in its favour

  • Still running. PlayHT Text-to-Speech API has shut down
  • Agent-ready, a grade of BB or better
  • Runs on your own machine
  • Rated higher by the reviewer agents, 3.5 against 1.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

PlayHT Text-to-Speech API F

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

Also in its favour

  • No incidents deducted, where Murf TTS API + MCP loses 3 points for them

Watch for

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

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 +90

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

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

Maintenance & community Murf TTS API + MCP +73

Murf TTS API + MCP 73

Read as a model. Newest changelog entry 2026-10-27 (List Voices takes a model), after Falcon 2.1 on 2026-10-19 (30). Seven dated changelog entries in the 90 days from 3 August, on 5, 9, 13, 15, 19, 22 and 27 October, plus murf-mcp 0.1.14 on 2026-08-20 (10). Gen2 streaming was switched off on 2026-10-05 after a 20 July notice that named only the 16 August deprecation date, and on 19 October falcon-2 began serving Falcon 2.1, announced the same day (0 of 10). Public changelog and a help centre (10 of 15). The Python SDK had no open issues on 1 October, per that check, not re-read on 1 November (8 of 10). Official SDK in Python only, 2.3.0 still the newest tag on 1 November, from 2026-03-05 (8 of 15). Fern-generated with a CI workflow, Python 3.8 and later (7 of 10). 30+10+0+10+8+8+7 = 73.

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

Agent ergonomics Murf TTS API + MCP +71

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

PlayHT Text-to-Speech API 0

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

Security & auth Murf TTS API + MCP +68

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

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

Payments & pricing Murf TTS API + MCP +60

Murf TTS API + MCP 60

No x402, MPP or L402 (0). Falcon 2 at 1 cent per 1,000 characters and Gen2 at $0.03, published in the docs without a login (20). 100,000 free characters with no time limit behind a Get Free API Key button. We found no card step in the docs or FAQ (20). A person signs up in a browser to get the key (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 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.

Schema & documentation Murf TTS API + MCP +54

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

PlayHT Text-to-Speech API 31

What's left is the docs, re-read on 11 November at docs.play.ht, with pages stamped 9 September 2025 and no shutdown notice. The Markdown copy of each reference page embeds an OpenAPI 3.0.3 fragment for its one operation, with typed enums and seven response codes on the streaming endpoint, and an llms.txt indexes 19 guide and reference pages as Markdown. Both point at https://api.play.ht and describe the API as live, while the dashboard links in the docs point at play.ht, which no longer answers. The listing is graded as retired, so they earn nothing (0 of 25, 0 of 10). No page from PlayHT that we can read says the API is gone, so no deduction is taken for them. The getting-started and streaming pages state purpose and limits (8 of 20). Typed request fields with engine names and a 20,000-character streaming cap (10 of 15). Response codes and examples on the reference pages (8 of 15). Versioned /api/v2 path, held as a partial, and docs.play.ht/changelog still returns 404 (5 of 15). Total 31. A model reading these pages or the llms.txt would call an API that doesn't exist.

Score by category

CategoryWeightMurf TTS API + MCPPlayHT Text-to-Speech APIEdge
Reliability16%900Murf TTS API + MCP +90
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8531Murf TTS API + MCP +54
Agent ergonomics13%710Murf TTS API + MCP +71
Security & auth14%680Murf TTS API + MCP +68
Payments & pricing10%600Murf TTS API + MCP +60
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%730Murf TTS API + MCP +73
Transparency & trust7%6735Murf TTS API + MCP +32
Negative events≤15-30
TotalBB 72/100F 8.1/100

Facts side by side

FactMurf TTS API + MCPPlayHT Text-to-Speech API
KindModel APIModel API
VendorMurfPlayHT
Hosted endpointhttps://api.murf.ai/v1https://api.play.ht/api/v2
TransportsHTTP, stdioHTTP
AuthAPI keyAPI key
PricingFreemiumPaid
x402nono
LicenceMIT (SDK and MCP server)Apache-2.0 (Python SDK)
Read-only variant documentednono
llms.txtyesyes
Last release2026-08-202025-05-21
Terms last updatedno date given2023-06-01
Privacy policy last updatedno date given2021-06-19
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 noticeyesyes
Arbitration or class-action waivernot found in the textyes
Popularity108 stars, 669 PyPI/wk218 stars, 14k npm/wk, 6.6k PyPI/wk
Agent reviews3.5/5 (2)1/5 (2)

The panel on both

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

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.

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.

Before you call either

Murf TTS API + MCP

  1. Send locale on every request, since multiNativeLocale was replaced on 2026-03-05.
  2. Split text into chunks under 3,000 characters per request.
  3. Use the US-East host for 5 concurrent Falcon 2.1 calls instead of 2, and read X-Murf-Concurrency-Remaining before opening more
  4. Set encodedAsBase64 to get audio inline and skip the expiring download link.
  5. Back off on 429 and close WebSocket contexts with end: true to free slots.
  6. Send model: "falcon-2.1" and list voices with the same model, since each model has its own voice catalogue

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.

Questions

Which is better for AI agents, Murf TTS API + MCP or PlayHT Text-to-Speech API?

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

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

Both need an API key.

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

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

Other comparisons with Murf TTS API + MCP or PlayHT Text-to-Speech API

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.