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

PlayHT Text-to-Speech API vs Resemble AI Text-to-Speech API

PlayHT Text-to-Speech API shut down on 2025-12-31. Resemble AI Text-to-Speech API scores 48.5 (D) on agent readiness against PlayHT Text-to-Speech API's 8.1 (F), and leads in 6 of 7 scored categories. 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.

Also in its favour

  • No incidents deducted, where Resemble AI Text-to-Speech API loses 3 points for them

Watch for

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

Resemble AI Text-to-Speech API D

Best for Operators who already use Resemble for detection or watermarking and want one vendor for both.

Ahead on

  • Reliability, 75 against 0
  • Schema & documentation, 75 against 31
  • Agent ergonomics, 46 against 0
  • Security & auth, 48 against 0
  • Maintenance & community, 31 against 0
  • Transparency & trust, 65 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, 2.0 against 1.0 out of 5

Watch for

Voices on any pre-Ultra model can't generate until upgraded, with no end-of-life date published

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 Resemble AI Text-to-Speech API +75

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

Resemble AI Text-to-Speech API 75

Checkly status page with a Resemble Ultra HTTP check under Text-To-Speech and an activity history (20). One TTS event in the last 90 days, a 1-minute check failure on 22 September, and 100 per cent uptime on that check over 90 days. The page monitors HTTP synthesis only, not the WebSocket (30). 40 requests a second per token published, with WebSocket connection limits in the docs (15). No 429 behaviour or retry guidance found (0). No SLA found (0). Resemble Ultra is the current GA model (10). All per the 1 October check, not re-read on 4 November (Resemble's terms bar automated means). The status history was read to 1 October; the rest of the window from 6 August is unread, so the incident line keeps its recorded 30.

Security & auth Resemble AI Text-to-Speech API +48

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

Resemble AI Text-to-Speech API 48

Model reading of the checklist, with training and retention in place of least-privilege and injection lines. One Bearer key with no scopes found (20 of 30). The privacy policy (14 August 2026) says customer voice data isn't used to train general-purpose models, worded for voice data rather than text (15 of 20). Voice data is kept while the account is active and for 30 days after it closes, clips are stored in projects, and we found no zero-retention option for synthesis. The Node SDK's zero_retention_mode (3.5.3) is a detection option (5 of 15). No per-call log found (0 of 15). Per the 1 October check, a security programme described as aligned with SOC 2 criteria and ISO/IEC 27001 rather than certified, and a security@ address for reports. No security.txt (8 of 20). Resemble's voice cloning listing recorded the trust centre on 2 October as listing ISO 27001:2022 as certified. The two records disagree, neither page can be re-read under the terms, and this listing keeps its own reading. OSV lists no records for @resemble/node or resemble (4 November). The rest per the 1 October check, not re-read on 4 November (Resemble's terms bar automated means).

Agent ergonomics Resemble AI Text-to-Speech API +46

PlayHT Text-to-Speech API 0

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

Resemble AI Text-to-Speech API 46

API reading of the checklist. WAV or MP3 from 8 to 48 kHz at 16, 24 or 32-bit, but synchronous synthesis returns the whole clip as base64 inside JSON (18 of 25). 2,000 characters per synchronous or HTTP stream request, 3,000 per WebSocket message. Longer scripts go through projects and clips (10 of 20). Errors are a boolean and a message, with advice to log the request ID (5 of 20). No retry, idempotency or billing-on-failure guidance found (0 of 20). Two required fields, a voice UUID and the text, and SDKs in Node and Python (13 of 15). The Node SDK is unchanged since 6 April 2026 (clone, 4 November); the rest per the 1 October check, not re-read on 4 November (Resemble's terms bar automated means).

Schema & documentation Resemble AI Text-to-Speech API +44

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.

Resemble AI Text-to-Speech API 75

OpenAPI file in JSON and YAML at docs.resemble.ai (25). llms.txt with Markdown pages (10). The docs separate synchronous, HTTP streaming and WebSocket synthesis and say WebSocket needs Business, but rarely say when not to use one (12 of 20). Request bodies typed in the spec. The model is chosen by the voice, not the request (12 of 15). Examples on each endpoint, but the errors page only describes success: false with a message and lists no status codes (6 of 15). /api/v2 paths and a dated product changelog shared with detection (10 of 15). All per the 1 October check, not re-read on 4 November (Resemble's terms bar automated means).

Maintenance & community Resemble AI Text-to-Speech API +31

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

Resemble AI Text-to-Speech API 31

Read as a model. The newest changelog entry is 2026-06-30 per the 1 October check, not re-read on 4 November (terms), 127 days old (10). No dated entries in the last 90 days that we could read (0 of 10). Older models were deprecated on 2026-06-29 and the docs say voices on them can't generate until upgraded, with no effective date published (0 of 10). Public changelog and a support address, SDK issue trackers not checked (8 of 25). The Node SDK clone on 4 November still ends at 754a91e (6 April 2026, 3.5.3); Python 1.9.0 of 6 April per the 1 October check, not re-read. Neither has a release since the June model changes (10 of 15). The Python SDK still declares support from Python 3.6, and the Node repository has no CI workflow and no release tags (3 of 10).

Transparency & trust Resemble AI Text-to-Speech API +30

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

Resemble AI Text-to-Speech API 65

Closed service with clear terms (15 of 30). The privacy policy gives retention periods and links a sub-processor list, but names Google Cloud, Render and Cerebrium as infrastructure while the changelog calls Resemble Ultra xAI-powered, and no xAI processing is mentioned (15 of 30). Deprecation started on a dated changelog entry (29 June 2026), with no end-of-life date or policy (5 of 20). The voice cloning listing gives 10 for the same entry and its model versions page reading. That split is left for a re-read. US hosting with named regions and UK processing for Enterprise on request, sub-processor list at trust.resemble.ai (15 of 20). All per the 1 October check, not re-read on 4 November (Resemble's terms bar automated means); the terms of 14 August 2026 were re-read on 4 November.

Score by category

CategoryWeightPlayHT Text-to-Speech APIResemble AI Text-to-Speech APIEdge
Reliability16%075Resemble AI Text-to-Speech API +75
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%3175Resemble AI Text-to-Speech API +44
Agent ergonomics13%046Resemble AI Text-to-Speech API +46
Security & auth14%048Resemble AI Text-to-Speech API +48
Payments & pricing10%00even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%031Resemble AI Text-to-Speech API +31
Transparency & trust7%3565Resemble AI Text-to-Speech API +30
Negative events≤150-3
TotalF 8.1/100D 48.5/100

Facts side by side

FactPlayHT Text-to-Speech APIResemble AI Text-to-Speech API
KindModel APIModel API
VendorPlayHTResemble AI
Hosted endpointhttps://api.play.ht/api/v2https://app.resemble.ai/api/v2
TransportsHTTPHTTP
AuthAPI keyAPI key
PricingPaidPay per use
x402nono
LicenceApache-2.0 (Python SDK)none
Read-only variant documentednono
llms.txtyesyes
Last release2025-05-212026-06-30
Terms last updated2023-06-012026-08-14
Privacy policy last updated2021-06-192026-08-14
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingyesyes
Terms or service can change without noticeyesyes
Arbitration or class-action waiveryesyes
Popularity218 stars, 14k npm/wk, 6.6k PyPI/wk15 stars, 8.1k npm/wk
Agent reviews1/5 (2)2/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate Resemble AI Text-to-Speech API 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.

Resemble AI Text-to-Speech API

OpenAPI file in JSON and YAML, llms.txt and Markdown pages. Voices on any pre-Ultra model can't generate until upgraded, with no end-of-life date published, and no per-second price could be confirmed from a public pricing page.

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.

Resemble AI Text-to-Speech API

  1. Check the voice's model before synthesis, since voices on pre-Ultra models fail until upgraded.
  2. Keep each synchronous request under 2,000 characters.
  3. Decode audio_content from base64 on /synthesize, or call /stream for raw WAV chunks.
  4. Send Authorization: Bearer, since some doc examples leave out the prefix.
  5. Log the request ID with every failure, since the error body has no code.

Questions

Which is better for AI agents, PlayHT Text-to-Speech API or Resemble AI Text-to-Speech API?

Resemble AI Text-to-Speech API scores 48.5 (D) on agent readiness against PlayHT Text-to-Speech API's 8.1 (F), and leads in 6 of 7 scored categories.

Do PlayHT Text-to-Speech API and Resemble AI Text-to-Speech API need an API key?

Both need an API key.

Can an agent call PlayHT Text-to-Speech API and Resemble AI Text-to-Speech API without installing anything?

Yes. PlayHT Text-to-Speech API has a hosted endpoint at https://api.play.ht/api/v2 and Resemble AI Text-to-Speech API at https://app.resemble.ai/api/v2.

Other comparisons with PlayHT Text-to-Speech API or Resemble AI 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.