Head to head · Speech tts · October 2026 research run

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

Deepgram Text-to-Speech (Aura-2, Flux TTS) has a score of 73 (BB) against PlayHT Text-to-Speech API's 4.2 (F). Both do speech tts. The largest gap is agent ergonomics, 82 points.

Which one, for what

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

  • reliability (+70)
  • schema & documentation (+64)
  • agent ergonomics (+82)
  • security & auth (+70)
  • payments & pricing (+40)
  • maintenance & community (+73)
  • transparency & trust (+39)

Pick PlayHT Text-to-Speech API for

No category where it leads by five points or more.

Score by category

CategoryWeight this runDeepgram Text-to-Speech (Aura-2, Flux TTS)PlayHT Text-to-Speech APIEdge
Reliability16%20700Deepgram Text-to-Speech (Aura-2, Flux TTS) +70
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.29531Deepgram Text-to-Speech (Aura-2, Flux TTS) +64
Agent ergonomics13%16.2820Deepgram Text-to-Speech (Aura-2, Flux TTS) +82
Security & auth14%17.5700Deepgram Text-to-Speech (Aura-2, Flux TTS) +70
Payments & pricing10%12.5400Deepgram Text-to-Speech (Aura-2, Flux TTS) +40
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.8730Deepgram Text-to-Speech (Aura-2, Flux TTS) +73
Transparency & trust7%8.87536Deepgram Text-to-Speech (Aura-2, Flux TTS) +39
Negative events≤150-4
Total73 · BB4.2 · F

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
x402nono
LicenceMIT (SDKs)Apache-2.0 (Python SDK)
Tools exposednonenone
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listednot listed
Last release2026-09-292025-05-21
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)

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. api.play.ht doesn't resolve, so every call fails.

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 keep traffic in one project.

PlayHT Text-to-Speech API

  1. Don't call api.play.ht, it doesn't resolve.
  2. Ignore docs.play.ht code samples, they describe a closed service.
  3. Map PlayDialog or Play 3.0 Mini work to another TTS listing before writing code.

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.