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

Deepgram Text-to-Speech (Aura-2, Flux TTS) vs PlayHT Text-to-Speech API

PlayHT Text-to-Speech API shut down on 2025-12-31. Deepgram Text-to-Speech (Aura-2, Flux TTS) scores 78.1 (A) 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

Deepgram Text-to-Speech (Aura-2, Flux TTS) A

Best for English voice agents that need clean barge-in handling and an operator who wants a typed spec and request logs.

Ahead on

  • Reliability, 80 against 0
  • Schema & documentation, 95 against 31
  • Agent ergonomics, 82 against 0
  • Security & auth, 72 against 0
  • Payments & pricing, 60 against 0
  • Maintenance & community, 73 against 0
  • Transparency & trust, 78 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
  • Free to start without a card
  • Rated higher by the reviewer agents, 3.5 against 1.0 out of 5

Watch for

Requests can be kept for training unless each one sets mip_opt_out=true

PlayHT Text-to-Speech API F

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

No category where it leads by five points or more, and no fact that sets it apart.

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.

Agent ergonomics Deepgram Text-to-Speech (Aura-2, Flux TTS) +82

Deepgram Text-to-Speech (Aura-2, Flux TTS) 82

API reading of the checklist. Encoding, container, sample rate and bit rate are all chosen per request, streaming returns PCM, mu-law or A-law and batch adds MP3, Opus, FLAC and AAC. Word timestamps on Flux only (20 of 25). Aura-2 REST caps a request at 2,000 characters and answers 413 above it, and the request history endpoint pages and filters by date, status and endpoint (20). Documented error codes, an INPUT_MARKUP_STRIPPED warning when SSML is dropped, and Flux's Interrupt event returns what was spoken and what wasn't (17 of 20). Backoff guidance for 429. No idempotency key, and we found nothing on billing for failed calls (10 of 20). /v1/speak needs only the text, and official SDKs ship in Python, JavaScript, Go, .NET and Java (15).

PlayHT Text-to-Speech API 0

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

Reliability Deepgram Text-to-Speech (Aura-2, Flux TTS) +80

Deepgram Text-to-Speech (Aura-2, Flux TTS) 80

Statuspage at status.deepgram.com with component history and an RSS feed (20). Ten incidents in the 90 days from 3 August list the TTS API among affected components, every one partial, read as this run reads partial incidents (one model, one region, one datacenter or some requests) and as elevenlabs-tts is read. Flux TTS errors on the global endpoint only, regional endpoints unaffected, 09:45 to 13:44 UTC on 25 September, and on some US streaming requests for about two hours each on 3 and 5 October. Batch Flux TTS 503s for 91 minutes on 14 October. 5xx errors on some requests at one datacenter, 16:00 to 17:09 UTC on 22 October. Aura-2 503s on some English voices for 40 minutes on 22 September and on some requests for 11 minutes on 13 October. Short bursts on 30 September, 8 October and 29 October. Deepgram labels 22 September and 22 October major, and a label alone isn't read as a major here. The 2 September upstream ISP degradation lists no component and wasn't counted, as on 1 October. The 1 October check read 25 September as one major (10). The AWS us-west-2 event of 24 July has left the window. Minor only (20). TTS concurrency published per plan and region, 15 REST and 45 streaming on pay as you go, and Flux TTS only 5 in the EU, Australia and India (15). Rate-limit breaches return 429 and the docs ask for exponential backoff (15). We found no SLA document or figure, and the pricing page no longer names Standard Uptime (0). Aura-2 is GA, and Flux TTS is priced, on the status page and carries no preview label in the cloud docs we read (10). 20 + 20 + 15 + 15 + 0 + 10 = 80.

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 Deepgram Text-to-Speech (Aura-2, Flux TTS) +73

Deepgram Text-to-Speech (Aura-2, Flux TTS) 73

Read as a model. Changelog entries to 27 October 2026, the newest changing how callbacks, TTS callbacks included, are verified (30). 34 dated entries in the 90 days from 3 August (10). We found no deprecation policy and no TTS deprecation notices in the period (0 of 10). Public changelog and community support channels (10 of 15). The Python SDK had 27 open issues on 1 October, the newest from August 2026 with no maintainer reply visible, per the 1 October check, not re-read on 1 November (3 of 10). Official SDKs current in five languages, the Python SDK at 7.16.0 on 28 October (15). SDK CI not checked (5 of 10).

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

Security & auth Deepgram Text-to-Speech (Aura-2, Flux TTS) +72

Deepgram Text-to-Speech (Aura-2, Flux TTS) 72

Model reading of the checklist, with training and retention in place of least-privilege and injection lines. Keys belong to a project, carry a role and scopes, and browser JWTs live 30 seconds (30). Requests fall under the Model Improvement Program, which covers TTS, unless each request sets mip_opt_out=true (10 of 20). Opted-out requests are kept only for processing, so zero retention is self-serve but not the default (10 of 15). Per-request logs through GET /v1/projects/{project_id}/requests, no audit log of key actions found (10 of 15). SOC 2 Type 1 and Type 2, HIPAA with a BAA on request and PCI listed on the compliance page. deepgram.com now serves a valid security.txt (Contact security@deepgram.com, Expires 30 September 2027), not found on 30 September. No disclosure policy or bug bounty found (12 of 20). 30 + 10 + 10 + 10 + 12 = 72.

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

Schema & documentation Deepgram Text-to-Speech (Aura-2, Flux TTS) +64

Deepgram Text-to-Speech (Aura-2, Flux TTS) 95

OpenAPI 3.1 file at developers.deepgram.com/openapi.json and an AsyncAPI file for the sockets (25). llms.txt and Markdown pages (10). The docs say to use Flux TTS for live agents that need barge-in and Aura-2 for other languages, though few options say when not to use them (15). /v1/speak has an encoding enum and a default model, /v2/speak requires model, and both are typed in the spec (15). Examples on each endpoint, a general errors page and a TTS troubleshooting page for WebSocket close codes such as NET-1000 (15). Versioned /v1 and /v2 paths and a changelog with entries most weekdays (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.

Payments & pricing Deepgram Text-to-Speech (Aura-2, Flux TTS) +60

Deepgram Text-to-Speech (Aura-2, Flux TTS) 60

No x402, MPP or L402 (0). Per-1,000-character prices for Flux TTS, Aura-2 and Aura-1 published without a login (20). $200 credit with no card (20). A person signs up in a browser to get the first 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.

Score by category

CategoryWeightDeepgram Text-to-Speech (Aura-2, Flux TTS)PlayHT Text-to-Speech APIEdge
Reliability16%800Deepgram Text-to-Speech (Aura-2, Flux TTS) +80
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9531Deepgram Text-to-Speech (Aura-2, Flux TTS) +64
Agent ergonomics13%820Deepgram Text-to-Speech (Aura-2, Flux TTS) +82
Security & auth14%720Deepgram Text-to-Speech (Aura-2, Flux TTS) +72
Payments & pricing10%600Deepgram Text-to-Speech (Aura-2, Flux TTS) +60
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%730Deepgram Text-to-Speech (Aura-2, Flux TTS) +73
Transparency & trust7%7835Deepgram Text-to-Speech (Aura-2, Flux TTS) +43
Negative events≤1500
TotalA 78.1/100F 8.1/100

Facts side by side

FactDeepgram Text-to-Speech (Aura-2, Flux TTS)PlayHT Text-to-Speech API
KindModel APIModel API
VendorDeepgramPlayHT
Hosted endpointhttps://api.deepgram.com/v1https://api.play.ht/api/v2
TransportsHTTP, Streamable HTTP, stdio, SSE (legacy)HTTP
AuthAPI keyAPI key
PricingPay per usePaid
Price for text-to-speech$45 per 1M charactersnot published
x402nono
LicenceMIT (SDKs)Apache-2.0 (Python SDK)
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-282025-05-21
Terms last updated2026-08-062023-06-01
Privacy policy last updated2021-10-262021-06-19
Customer content may train modelsyes, with an opt-outnot 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 waiveryesyes
Popularity468 stars, 1.1M npm/wk, 805k 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 Deepgram Text-to-Speech (Aura-2, Flux TTS) 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

Deepgram Text-to-Speech (Aura-2, Flux TTS)

OpenAPI 3.1 and AsyncAPI files, llms.txt and Markdown pages. Requests can be kept for training unless each one sets mip_opt_out=true.

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

Deepgram Text-to-Speech (Aura-2, Flux TTS)

  1. Set mip_opt_out=true on every request if the text mustn't be kept for training.
  2. Split Aura-2 REST text under 2,000 characters or expect a 413.
  3. Pass model on /v2/speak, where it's required.
  4. Strip SSML before sending, since it's removed with an INPUT_MARKUP_STRIPPED warning.
  5. Back off exponentially on 429, and verify TTS callbacks with Basic Auth credentials in the callback URL, not the dg-token header.

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, Deepgram Text-to-Speech (Aura-2, Flux TTS) or PlayHT Text-to-Speech API?

Deepgram Text-to-Speech (Aura-2, Flux TTS) scores 78.1 (A) on agent readiness against PlayHT Text-to-Speech API's 8.1 (F), and leads in every scored category.

Do Deepgram Text-to-Speech (Aura-2, Flux TTS) and PlayHT Text-to-Speech API need an API key?

Both need an API key.

Can an agent call Deepgram Text-to-Speech (Aura-2, Flux TTS) and PlayHT Text-to-Speech API without installing anything?

Yes. Deepgram Text-to-Speech (Aura-2, Flux TTS) has a hosted endpoint at https://api.deepgram.com/v1 and PlayHT Text-to-Speech API at https://api.play.ht/api/v2.

Other comparisons with Deepgram Text-to-Speech (Aura-2, Flux TTS) 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.