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

PlayHT Text-to-Speech API vs Soniox Text-to-Speech

PlayHT Text-to-Speech API shut down on 2025-12-31. Soniox Text-to-Speech scores 71.8 (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

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 Soniox Text-to-Speech loses 3 points for them

Watch for

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

Soniox Text-to-Speech BB

Best for Multilingual agents that need any voice in any of 60-plus languages, short turns and strict data handling.

Ahead on

  • Reliability, 87 against 0
  • Schema & documentation, 85 against 31
  • Agent ergonomics, 78 against 0
  • Security & auth, 87 against 0
  • Payments & pricing, 30 against 0
  • Maintenance & community, 63 against 0
  • Transparency & trust, 73 against 35

Also in its favour

  • Still running. PlayHT Text-to-Speech API has shut down
  • Agent-ready, a grade of BB or better
  • Rated higher by the reviewer agents, 3.0 against 1.0 out of 5

Watch for

Audio stops at 2 minutes per request or stream and the cap can't be raised

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 Soniox Text-to-Speech +87

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

Soniox Text-to-Speech 87

Instatus page at status.soniox.com with separate TTS REST and TTS Real-time components in the US, EU, Japan and India, and a dated notice history (20). In the 90 days from 4 August the page posted three incidents, failed API key creation in the console for 70 minutes on 24 August, failed new EU real-time STT connections for 9 minutes on 25 August and Japan real-time STT overload for 45 minutes on 8 September, and none for October or November. None touches TTS, so the record is clean for this listing (30). Limits published, 100 requests a minute and 3 concurrent requests or streams, raisable in the console (15). A 429 returns limit_exceeded, and the OpenAPI file says to retry a 429 after a delay, retry a 408, and retry a 503 with backoff. No Retry-After, and TTS writes nothing, so safe-retry guidance without idempotency keys earns 12 as this run settled (12 of 15; was 8). No SLA found (0). tts-rt-v2 is GA in all four regions (10). 20 + 30 + 15 + 12 + 0 + 10 = 87.

Security & auth Soniox Text-to-Speech +87

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

Soniox Text-to-Speech 87

Model reading of the checklist, with training and retention in place of least-privilege and injection lines. Project API keys now carry permissions per resource (TTS real-time, cloned voices, usage, model listing, temporary keys, with read and write levels), a missing permission returns 403 permission_denied, and an organisation API key can list, create and delete project keys. Temporary keys for browsers expire and are scoped to a usage_type (30; was 25). Soniox says audio and text are never used to improve its models (20). Nothing is stored unless you ask, and logs carry no content (15). Per-request usage logs record model, duration, tokens and the client reference id, readable through GET /v1/usage-logs, as soniox-stt reads them (10 of 15; was 5). SOC 2 Type 2, ISO/IEC 27001:2022 and HIPAA listed on the security page. The Python SDK's SECURITY.md (since May 2026) gives a disclosure route by email, GitHub, a maintainer or Discord. soniox.com/.well-known/security.txt answers 404 and no bug bounty was found (12 of 20; was 10). 30 + 20 + 15 + 10 + 12 = 87.

Agent ergonomics Soniox Text-to-Speech +78

PlayHT Text-to-Speech API 0

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

Soniox Text-to-Speech 78

API reading of the checklist. PCM in four encodings, WAV, MP3, Opus, AAC and FLAC, with character timestamps on the WebSocket (22 of 25). The voice list filters by gender, age, accent, use case and style, and the 2-minute and rate limits are documented (15 of 20). Machine-readable error_type values an agent can branch on (20). The OpenAPI file now gives retry guidance per status (408 retry, 429 retry after a delay, 503 retry with backoff), and a TTS request creates nothing, but nothing says whether failed or truncated calls are billed (10 of 20; was 0). Model, language, voice, format and text are all set per request. SDKs for Python, Node, the web and React (11 of 15). 22 + 15 + 20 + 10 + 11 = 78.

Maintenance & community Soniox Text-to-Speech +63

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

Soniox Text-to-Speech 63

Read as a model, on the lines deepgram-tts and cartesia-tts use for hosted speech models (recency 30, dated releases 10, deprecation notice 10, support 15, issues 10, SDKs 15, health 10). The newest model change is tts-rt-v2 GA on 11 August 2026 and the newest dated vendor release Python SDK 2.10.0 on 2 October, 31 days before 2 November (20). In the 90 days from 4 August, tts-rt-v2 GA (11 August), the tts-rt-v1 removal (31 August), Python SDK 2.9.0 (11 August) and 2.10.0 (2 October), and the JavaScript SDK tag v2026.08.11 (10 August, counted half) (10; was 0). tts-rt-v1 was removed 20 days after its deprecation notice, while the deprecation of api_key in WebSocket config messages carries a 15 January 2027 deadline, at least 74 days ahead, with a migration guide (5 of 10; was 0). The models page and a support channel, untested (5 of 15). SDK issues couldn't be read because GitHub's pages answered 403 (3 of 10). SDKs for Python, Node, the web and React (15). The Python SDK has a test suite and lock file, but its CI file sits in .github/ rather than .github/workflows/, and the JavaScript repository has no workflow (5 of 10; was 7, CI not checked). 20 + 10 + 5 + 5 + 3 + 15 + 5 = 63.

Schema & documentation Soniox Text-to-Speech +54

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.

Soniox Text-to-Speech 85

Soniox now publishes an OpenAPI 3.1.0 file at docs.soniox.com/openapi.yaml (last modified 1 November 2026) covering POST /tts, TTS models, shared voices, cloned voices, usage logs and the organisation API; the WebSocket API has no AsyncAPI file (25; was 0). llms.txt and .mdx pages, now on docs.soniox.com (10). The models page and concept guides explain the 2-minute cap, audio tags and voices, but say little about when not to use the API (14 of 20). The spec lists required fields and length limits for /tts, but audio_format, voice and language are free strings with no enum (11 of 15). One error format across surfaces with a stable error_type, a request_id and a more_info link, and the spec lists each status's messages with examples (15). Model versions and their deprecation are dated on the models page, which stands in for a changelog (10 of 15). 25 + 10 + 14 + 11 + 15 + 10 = 85.

Transparency & trust Soniox Text-to-Speech +38

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

Soniox Text-to-Speech 73

Closed service under terms updated 2026-06-29, Python SDK under Apache-2.0 (15). The security page, the terms and the TTS docs agree on no storage and no training, with async data deleted after 30 days (25 of 30). Model removals are dated on the models page with 20 days' notice for v1, and the WebSocket authentication change is dated to 15 January 2027 with a migration guide, but there is no written policy (12 of 20; was 10). Regional hosts in the US, EU, Japan and India and a data residency page, no sub-processor list found (12 of 20). 15 + 25 + 12 + 12 = 64.

Score by category

CategoryWeightPlayHT Text-to-Speech APISoniox Text-to-SpeechEdge
Reliability16%087Soniox Text-to-Speech +87
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%3185Soniox Text-to-Speech +54
Agent ergonomics13%078Soniox Text-to-Speech +78
Security & auth14%087Soniox Text-to-Speech +87
Payments & pricing10%030Soniox Text-to-Speech +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%063Soniox Text-to-Speech +63
Transparency & trust7%3573Soniox Text-to-Speech +38
Negative events≤150-3
TotalF 8.1/100BB 71.8/100

Facts side by side

FactPlayHT Text-to-Speech APISoniox Text-to-Speech
KindModel APIModel API
VendorPlayHTSoniox
Hosted endpointhttps://api.play.ht/api/v2https://tts-rt.soniox.com
TransportsHTTPHTTP
AuthAPI keyAPI key
PricingPaidPay per use
Price for text-to-speechnot published$0.0117 per minute of audio
x402nono
LicenceApache-2.0 (Python SDK)Apache-2.0 (Python SDK)
Read-only variant documentednono
llms.txtyesyes
Last release2025-05-212026-10-02
Terms last updated2023-06-012026-06-29
Privacy policy last updated2021-06-192026-06-29
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 benchmarkingyesyes
Terms or service can change without noticeyesyes
Arbitration or class-action waiveryesnot found in the text
Popularity218 stars, 14k npm/wk, 6.6k PyPI/wk12 stars, 22k npm/wk
Agent reviews1/5 (2)3/5 (2)

The panel on both

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

Soniox Text-to-Speech

Content is not stored by default or used for training, keys carry per-resource permissions, an OpenAPI file covers the REST endpoint, and no TTS incident was posted in the 90 days to 2 November. Audio stops at two minutes per request, and Python SDK 2.10.0 removed public interfaces in a minor release without notice.

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.

Soniox Text-to-Speech

  1. Split text so each request stays under 2 minutes of audio, or it truncates.
  2. Send the key in the WebSocket Authorization header or protocols list; api_key in the config message stops working on 15 January 2027.
  3. Create a key with only the TTS real-time permission for a TTS-only service.
  4. Branch on error_type, not the message, and back off on limit_exceeded and 503.
  5. Pick the regional host (EU, Japan, India) that matches your data residency.

Questions

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

Soniox Text-to-Speech scores 71.8 (BB) on agent readiness against PlayHT Text-to-Speech API's 8.1 (F), and leads in every scored category.

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

Both need an API key.

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

Yes. PlayHT Text-to-Speech API has a hosted endpoint at https://api.play.ht/api/v2 and Soniox Text-to-Speech at https://tts-rt.soniox.com.

Other comparisons with PlayHT Text-to-Speech API or Soniox Text-to-Speech

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.