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

Azure AI Speech text-to-speech vs PlayHT Text-to-Speech API

PlayHT Text-to-Speech API shut down on 2025-12-31. Azure AI Speech text-to-speech scores 75.6 (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

Azure AI Speech text-to-speech BB

Best for Operators on Azure who need SSML control, many languages and voices, and enterprise access control.

Ahead on

  • Reliability, 90 against 0
  • Schema & documentation, 70 against 31
  • Agent ergonomics, 75 against 0
  • Security & auth, 90 against 0
  • Payments & pricing, 30 against 0
  • Maintenance & community, 80 against 0
  • Transparency & trust, 86 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.5 against 1.0 out of 5

Watch for

An Azure subscription needs a card, even for the free F0 tier

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.

Reliability Azure AI Speech text-to-speech +90

Azure AI Speech text-to-speech 90

Azure status page with post-incident reviews (20). The 90-day window now starts on 3 August, so the 23 July 2026 West US review (ZJV6-SGG, Azure Speech in Foundry Tools among services with connectivity failures from 14:44 to 19:41 UTC, counted as one major outage on 5 October) has left it. Two reviews remain on 1 November. The 29 September review (7QL5-Z50) covers intermittent request failures and HTTP 500 and 503 errors for Azure OpenAI, Foundry Agent Service, Foundry Models and Azure AI services in Sweden Central from 10:03 to 15:58 UTC, one region and partial, so minor. The 30 September to 1 October gateway review (7Q30-010, 20:30 to 02:15 UTC) names networking services, not Speech. Minor incidents only (20). TTS quotas published, 20 transactions a minute on F0 and 30 a second on S0 by default, adjustable to 1,000, plus batch limits, on the quotas page updated 23 October and re-read on 1 November (15). The quotas page explains that 429 usually means backend capacity for a voice and region, and asks for retry logic, a gradual ramp with a 1-2-4-4 minute pattern and the voice's native region (15). Covered by Microsoft's online services SLA, per the 1 October check (10). Neural and HD voices, the surface graded here, are GA. MAI-Voice-2.1 and MAI-Voice-2.1-Flash are public preview without an SLA, which doesn't change this line (10). 20 + 20 + 15 + 15 + 10 + 10 = 90.

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

Security & auth Azure AI Speech text-to-speech +90

Azure AI Speech text-to-speech 90

Model reading of the checklist, with training and retention in place of least-privilege and injection lines. Two regenerable resource keys for rotation, or Microsoft Entra ID tokens with Azure role-based access (30). Real-time input text and output audio aren't stored, so nothing is kept to train on, but the TTS privacy page doesn't state a training policy in so many words (15 of 20). Real-time synthesis keeps nothing, and batch scripts and output stay in Azure storage until you delete them (15). Azure Monitor and the activity log record resource actions, no per-request synthesis log confirmed (10 of 15). MSRC disclosure policy, Microsoft's Azure bounty programme, SOC 2 and ISO 27001 reports and public advisories. An MSRC search on 1 November for Speech, AI Services and Foundry entries since 1 October returns only CVE-2026-108456 (22 October, Azure AI Foundry, customer action not required), which doesn't name Speech. The microsoft.com security.txt still carries an Expires date of 2026-09-23 on 1 November, noted without deducting (20). Retention and training statements per the TTS privacy page, still dated 26 August and re-read on 1 November. 30 + 15 + 15 + 10 + 20 = 90.

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

Maintenance & community Azure AI Speech text-to-speech +80

Azure AI Speech text-to-speech 80

Read as a model. The newest dated text-to-speech change is MAI-Voice-2.1 and MAI-Voice-2.1-Flash entering public preview on 1 October 2026 (MAI voices page, updated 1 October), 31 days before 1 November (20). Speech SDK 1.52 (September 2026, on NuGet on 28 September) fixes an embedded TTS timeout and two TTS crashes with compressed audio, and 1.51.2 (August 2026, on NuGet on 20 August) fixes a crash on speech synthesis and a Java synthesis handle error, per Microsoft's release notes, so both are dated releases that change the synthesis client, as azure-translator's 2.0.3 client fix was counted. Speech SDK 1.53.0 (JavaScript tag of 21 October, on NuGet on 22 October) adds inline commit support for pushed audio input, the JavaScript diff touches only recognition code and the release notes have no 1.53 entry yet, so it counts half and doesn't set recency. Three dated text-to-speech changes in the 90 days from 3 August, MAI-Voice-2.1 on 1 October, SDK 1.52 and SDK 1.51.2 (20). Retirements follow Microsoft's published lifecycle policy with dated notices. The MAI model has turned over three times since March 2026 (MAI-Voice-1, MAI-Voice-2-Flash, MAI-Voice-2.1), and the MAI page dropped MAI-Voice-2-Flash without a dated notice, while the language list still carries it (10). Public release notes and Microsoft Q&A, SDK issue tracker not checked (10 of 25). Speech SDK current in eight languages (15). The SDK is a closed binary, so we can't see its CI (5 of 10). 20 + 20 + 10 + 10 + 15 + 5 = 80.

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 Azure AI Speech text-to-speech +75

Azure AI Speech text-to-speech 75

API reading of the checklist. More than 40 output formats chosen by header, from 8 kHz telephony to 48 kHz, and synthesis events in the SDK (23 of 25). The voice list returns the region's voices in one response with no paging documented, while batch jobs list with paging, and per-request limits are published (10 minutes of audio, 50 voice or audio tags, 64 KB per WebSocket turn) (15 of 20). The REST page lists 400, 401, 415, 429, 502 and 503 with likely causes, and the SDK returns cancellation details with error codes (15 of 20). Retry guidance for 429, no idempotency key on batch jobs (10 of 20). Every REST request needs an SSML body and four headers, including the output format and a User-Agent. Speech SDKs in eight languages (12 of 15). 23 + 15 + 15 + 10 + 12 = 75.

PlayHT Text-to-Speech API 0

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

Transparency & trust Azure AI Speech text-to-speech +51

Azure AI Speech text-to-speech 86

Closed service under Microsoft's product terms, with an MIT samples repository (15). The TTS privacy page (updated 26 August, re-read on 1 November), the privacy statement and the product terms agree on no storage for real-time synthesis and retention until deletion for batch (25 of 30). Dated retirements under Microsoft's lifecycle policy (20). Regions chosen per resource and a public sub-processor list (20). MAI-Voice previews run under the Azure preview supplemental terms. Product terms, the privacy statement and the sub-processor list per the 1 October check, not re-read on 1 November. 15 + 25 + 20 + 20 = 80.

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

Schema & documentation Azure AI Speech text-to-speech +39

Azure AI Speech text-to-speech 70

Real-time synthesis takes SSML, a W3C format with documented Azure extensions, and has no OpenAPI file. Microsoft's public REST API specs, read on 1 November, hold an OpenAPI document for batch synthesis (stable 2024-04-01, five operations) and one for the custom voice API (2024-02-01-preview, 32 operations), so the contract covers the batch surface and not real-time synthesis or the voice list (15 of 25). No llms.txt found, learn.microsoft.com/llms.txt answers 404 (0). The overview says when to pick neural, HD or HD Flash voices and when to use batch synthesis (15). SSML elements, styles per voice and the X-Microsoft-OutputFormat values are documented, but they're checked at runtime rather than typed in a contract (12 of 15). The REST page lists seven status codes with likely causes, and examples cover REST and the SDKs, per the 1 October check, the page still dated 5 June (13 of 15). Dated release notes and api-version values on batch synthesis (15). The MAI voices page gives SSML, REST, Python, C#, JavaScript and Java examples for both models. 15 + 0 + 15 + 12 + 13 + 15 = 70.

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

CategoryWeightAzure AI Speech text-to-speechPlayHT Text-to-Speech APIEdge
Reliability16%900Azure AI Speech text-to-speech +90
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7031Azure AI Speech text-to-speech +39
Agent ergonomics13%750Azure AI Speech text-to-speech +75
Security & auth14%900Azure AI Speech text-to-speech +90
Payments & pricing10%300Azure AI Speech text-to-speech +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%800Azure AI Speech text-to-speech +80
Transparency & trust7%8635Azure AI Speech text-to-speech +51
Negative events≤1500
TotalBB 75.6/100F 8.1/100

Facts side by side

FactAzure AI Speech text-to-speechPlayHT Text-to-Speech API
KindModel APIModel API
VendorMicrosoftPlayHT
Hosted endpointhttps://eastus.tts.speech.microsoft.com/cognitiveserviceshttps://api.play.ht/api/v2
TransportsHTTPHTTP
AuthOAuth or keyAPI key
PricingFreemiumPaid
x402nono
LicenceMIT (samples), SDK under Microsoft's own licenceApache-2.0 (Python SDK)
Read-only variant documentednono
llms.txtnoyes
Last release2026-10-012025-05-21
Terms last updatedcouldn't be read2023-06-01
Privacy policy last updated2026-09-012021-06-19
Customer content may train modelsyesnot found in the text
Terms restrict automated accesscouldn't be readnot found in the text
Terms restrict benchmarkingcouldn't be readyes
Terms or service can change without noticecouldn't be readyes
Arbitration or class-action waivercouldn't be readyes
Popularity3.5k stars, 476k npm/wk, 1M 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 Azure AI Speech 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

Azure AI Speech text-to-speech

Real-time synthesis keeps neither the input text nor the output audio. An Azure subscription needs a card, even for the free F0 tier.

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

Azure AI Speech text-to-speech

  1. Send SSML with <speak> and <voice>, and set X-Microsoft-OutputFormat and User-Agent.
  2. On 429 retry with backoff, and try the voice's home region or another region rather than asking for more quota.
  3. Keep each real-time request under 10 minutes of audio, or use batch synthesis.
  4. Use Entra ID tokens instead of resource keys where the agent runs inside Azure.
  5. Name a MAI voice with its model suffix, such as en-US-Harper:MAI-Voice-2.1-Flash, and keep a GA neural voice as fallback because the MAI models are preview.

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, Azure AI Speech text-to-speech or PlayHT Text-to-Speech API?

Azure AI Speech text-to-speech scores 75.6 (BB) on agent readiness against PlayHT Text-to-Speech API's 8.1 (F), and leads in every scored category.

Do Azure AI Speech text-to-speech and PlayHT Text-to-Speech API need an API key?

Azure AI Speech text-to-speech takes an API key or an OAuth sign-in. PlayHT Text-to-Speech API needs an API key.

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

Yes. Azure AI Speech text-to-speech has a hosted endpoint at https://eastus.tts.speech.microsoft.com/cognitiveservices and PlayHT Text-to-Speech API at https://api.play.ht/api/v2.

Other comparisons with Azure AI Speech text-to-speech 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.