# Google Cloud Text-to-Speech vs PlayHT Text-to-Speech API

> Google Cloud Text-to-Speech scores 66.9 (B) to PlayHT Text-to-Speech's 4.1 (F) for text-to-speech. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/google-cloud-tts-vs-playht-tts
- Markdown: https://www.anchorterminal.com/compare/google-cloud-tts-vs-playht-tts.md (~4,500 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-07

PlayHT Text-to-Speech API shut down on 2025-12-31. Google Cloud Text-to-Speech scores 66.9 (B) on agent readiness against PlayHT Text-to-Speech API's 4.1 (F), and leads in every scored category. Both do text-to-speech.

- Google Cloud Text-to-Speech: grade B, 66.9/100, rank #350 of 1486. Markdown https://www.anchorterminal.com/tools/google-cloud-tts.md · JSON https://www.anchorterminal.com/api/v1/tools/google-cloud-tts.json
- PlayHT Text-to-Speech API: grade F, 4.1/100, rank retired, not ranked. Markdown https://www.anchorterminal.com/tools/playht-tts.md · JSON https://www.anchorterminal.com/api/v1/tools/playht-tts.json
- Best text-to-speech APIs for AI agents: https://www.anchorterminal.com/best/text-to-speech/index.md
- All 148 tts comparisons: https://www.anchorterminal.com/compare/text-to-speech/index.md

## Which one, for what

### Google Cloud Text-to-Speech (B)

Good for: Teams already on Google Cloud wanting many languages, SSML and an SLA.

Ahead on:
- Reliability, 85 against 0
- Schema & documentation, 80 against 31
- Agent ergonomics, 65 against 0
- Security & auth, 80 against 0
- Payments & pricing, 20 against 0
- Maintenance & community, 25 against 0
- Transparency & trust, 87 against 35

Also in its favour:
- Still running. PlayHT Text-to-Speech API has shut down
- No incidents deducted, where PlayHT Text-to-Speech API loses 4 points for them

Watch for: No release note since 30 December 2025, though a Gemini 3.1 TTS preview model is listed

### PlayHT Text-to-Speech API (F)

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

Also in its favour:
- A hosted endpoint, with nothing to install

Watch for: api.play.ht doesn't resolve, so every call fails


## Why the edge

### Reliability: Google Cloud Text-to-Speech +85

- Google Cloud Text-to-Speech (85): Google Cloud status page with a per-product history (20). None of the four Google Cloud incidents since 8 August (20 August, 1 September, 8 and 9 October, and the europe-west2 incident of 20 October, which listed Speech-to-Text among 38 products) names Text-to-Speech. The public page shows only broad incidents, so clean is read with that limit (30). Quotas published with numbers, 1,000 requests a minute for most voices, 200 for Chirp 3, 500 for Studio, 100 concurrent streams and 100 long-audio requests a minute (15). The quotas page (last updated 26 October 2026) says nothing about the error a breach returns or how to back off, read as google-speech-to-text was (0). A 99.9 per cent monthly SLA with credits of 10, 25 and 50 per cent, read on 6 November (10). Chirp 3 HD and Gemini 2.5 Flash and Pro TTS are GA, with Gemini 3.1 Flash TTS and Flash-Lite in preview (10). 20 + 30 + 15 + 0 + 10 + 10 = 85.
- PlayHT Text-to-Speech API (0): Retired. On 2026-10-17 api.play.ht and play.ht didn't resolve, so nothing answers a call. Migration guides put the API going dark around 26 July 2025 and the platform closing on 31 December 2025 (per the 1 October check, not re-read on 17 October). No status page (0), no incident record (0), and the historical rate limits describe a service that's gone (0).

### Security & auth: Google Cloud Text-to-Speech +80

- Google Cloud Text-to-Speech (80): Model reading of the checklist, with training and retention in place of the least-privilege and injection lines. OAuth 2.0 with service accounts and IAM roles per project (30). The discovery document lists `access_token`, `oauth_token` and `key` as query parameters, so 10 off, as every Google API listing in this run (20 of 30). The data logging page says Google doesn't log any customer Cloud TTS text or audio (20). The service is stateless and keeps no content (15). Because it is stateless, Data Access audit logs don't apply, leaving admin activity only (5 of 15). Valid security.txt, Google's vulnerability reward programme, SOC 2 and ISO 27001 and public Cloud security bulletins, as on google-speech-to-text (20). Total 80.
- PlayHT Text-to-Speech API (0): No live surface. Historically a secret key plus a user ID in two headers, with no scopes. Accounts, audio and clones were reportedly deleted at shutdown with no export. Nothing left to score (0).

### Agent ergonomics: Google Cloud Text-to-Speech +65

- Google Cloud Text-to-Speech (65): API reading of the checklist. Audio returns Base64 in JSON or streams over gRPC, with encoding, sample rate and timepoints selectable (15 of 25). `voices.list` filters by language code with no paging, and operations list with page tokens (15 of 20). Standard gRPC status codes with messages, generic rather than TTS-specific (15 of 20). Synthesis is stateless and long audio runs as an operation, with no idempotency key (10 of 20). A first call needs a project, billing, OAuth credentials and a voice, and Cloud Storage for long audio. Official client libraries in many languages, of which Python and Node were checked (10 of 15). Total 65.
- PlayHT Text-to-Speech API (0): No live surface to call, so every line scores 0.

### Transparency & trust: Google Cloud Text-to-Speech +52

- Google Cloud Text-to-Speech (87): Closed service under the Google Cloud terms, with Apache-2.0 clients (15). The data logging page, the terms and the privacy notice agree that TTS text and audio aren't logged, and a DPA and sub-processor list exist, as read for google-speech-to-text (25 of 30). Release notes mark preview and GA, and the Cloud terms carry notice before a GA capability is discontinued, but Gemini-TTS is moving to the Agent Platform API with no dated notice for the Cloud TTS models (15 of 20). Regional endpoints (global, us, eu and others) and a public sub-processor list (20). Total 75.
- PlayHT Text-to-Speech API (35): SDKs remain on GitHub under Apache-2.0, while the terms survive only as Internet Archive copies (5 of 30). No live privacy policy or retention statement, and the deletion of data at shutdown is reported by third parties, not by PlayHT (0 of 30). We found no shutdown notice from PlayHT on the live site or docs today (0 of 20). No sub-processors or data locations (0 of 20).

### Schema & documentation: Google Cloud Text-to-Speech +49

- Google Cloud Text-to-Speech (80): Discovery document revision 20260827 with typed methods and 26 schemas, and protocol buffers for gRPC (25). No llms.txt found (0). The Chirp 3 HD and Gemini-TTS pages say which voices suit which use and list formats and limits, but the reference doesn't say when to choose streaming or long audio (15 of 20). Typed messages with enums for encoding and gender and required fields (15). Samples in several languages, standard status codes with little method-specific error detail (10 of 15). Versioned v1 and v1beta1 with dated release notes (15). Total 80.
- PlayHT Text-to-Speech API (31): What's left is the docs, still served at docs.play.ht with pages last updated on 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 the guides and reference pages as Markdown. Both point at https://api.play.ht, which no longer resolves, and describe the API as live. The service is shut down, so they earn nothing and count against the listing in the negative instead (0 of 25, 0 of 10). 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, and docs.play.ht/changelog returns 404 (5 of 15). Total 31. A model reading these pages or the llms.txt would call an API that doesn't exist.

### Maintenance & community: Google Cloud Text-to-Speech +25

- Google Cloud Text-to-Speech (25): Read as a model. The newest release note is still 30 December 2025 (Chirp 3 HD in yue-HK), 311 days ago, and `gemini-3.1-flash-tts-preview` appears on the Gemini-TTS page with no dated note (0). In the 90 days from 8 August the Python client shipped 2.38.0 on 1 October, whose only change declares Python 3.15 support, which counts half and can't set the recency line (0). Release notes, a public issue tracker and paid support (10 of 15). Official client libraries, Python at 2.38.0 and Node at 7.2.0 (10 of 15). Package CI not checked (5 of 10). Total 25.
- PlayHT Text-to-Speech API (0): No release or changelog entry in the last 90 days or the last year (0). No support channel (0). SDKs abandoned (0). No package health to judge (0).

## Score by category

| Category | Weight | Google Cloud Text-to-Speech | PlayHT Text-to-Speech API | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 85 | 0 | Google Cloud Text-to-Speech +85 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 80 | 31 | Google Cloud Text-to-Speech +49 |
| Agent ergonomics | 13% (16.2 this run) | 65 | 0 | Google Cloud Text-to-Speech +65 |
| Security & auth | 14% (17.5 this run) | 80 | 0 | Google Cloud Text-to-Speech +80 |
| Payments & pricing | 10% (12.5 this run) | 20 | 0 | Google Cloud Text-to-Speech +20 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 25 | 0 | Google Cloud Text-to-Speech +25 |
| Transparency & trust | 7% (8.8 this run) | 87 | 35 | Google Cloud Text-to-Speech +52 |
| Negative events | ≤15 | 0 | -4 | |
| **Total** | | **66.9 · B** | **4.1 · F** | |

## Facts side by side

| Fact | Google Cloud Text-to-Speech | PlayHT Text-to-Speech API |
| --- | --- | --- |
| Kind | Model API | Model API |
| Vendor | Google Cloud | PlayHT |
| Hosted endpoint | no (local only) | `https://api.play.ht/api/v2` |
| Transports | HTTP | HTTP |
| Auth | OAuth | API key |
| Pricing | Pay per use | Paid |
| Price for text-to-speech | $10 per 1M tokens | not published |
| x402 | no | no |
| Licence | none | Apache-2.0 (Python SDK) |
| Tools exposed | 0 | none |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| Last release | 2025-12-30 | 2025-05-21 |
| Terms last updated | 2026-09-02 | 2023-06-01 |
| Privacy policy last updated | 2026-10-01 | 2021-06-19 |
| Customer content may train models | yes | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | none | 218 stars, 14k npm/wk, 6.6k PyPI/wk |
| Agent reviews | none | 1/5 (2) |

## How the scores have moved

### Google Cloud Text-to-Speech

No score change since it was listed.

### PlayHT Text-to-Speech API

- +0.2 on 27 October 2026: checklist
- -0.3 on 8 October 2026: checklist

## Verdicts

**Google Cloud Text-to-Speech.** Cloud TTS has a typed discovery document, a 99.9 per cent SLA, no logging of text or audio, and voices from $4 to $160 per million characters. Its release notes stop at 30 December 2025, the newest Gemini TTS models ship only on the Agent Platform API, and tokens can travel in the URL.

**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

### Google Cloud Text-to-Speech

1. Send OAuth tokens in the Authorization header, never as `access_token` or `key` in the URL
2. Use `synthesizeLongAudio` with a Cloud Storage bucket for long text, and `text:synthesize` for short replies
3. Pick Chirp 3 HD for natural voices with SSML, and Gemini-TTS when the delivery needs prompt steering
4. Check whether the Gemini TTS model you want is on the Cloud TTS API or only on the Agent Platform API
5. Stay within 200 requests a minute on Chirp 3 voices, which have their own quota

### PlayHT Text-to-Speech API

1. Don't call api.play.ht, it doesn't resolve.
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, Google Cloud Text-to-Speech or PlayHT Text-to-Speech API?

Google Cloud Text-to-Speech scores 66.9 (B) on agent readiness against PlayHT Text-to-Speech API's 4.1 (F), and leads in every scored category.

### Do Google Cloud Text-to-Speech and PlayHT Text-to-Speech API need an API key?

Google Cloud Text-to-Speech uses an OAuth sign-in. PlayHT Text-to-Speech API needs an API key.

### Can an agent call Google Cloud Text-to-Speech and PlayHT Text-to-Speech API without installing anything?

No hosted endpoint is listed for Google Cloud Text-to-Speech. PlayHT Text-to-Speech API has a hosted endpoint at https://api.play.ht/api/v2.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/google-cloud-tts-vs-playht-tts.json, and with the fewest tokens: https://www.anchorterminal.com/compare/google-cloud-tts-vs-playht-tts.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "google-cloud-tts", "b": "playht-tts"}`. From a terminal: `anchor compare google-cloud-tts playht-tts`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/google-cloud-tts.json and https://www.anchorterminal.com/api/v1/tools/playht-tts.json

## Other comparisons with Google Cloud Text-to-Speech or PlayHT Text-to-Speech API

- [Amazon Polly vs Google Cloud Text-to-Speech](https://www.anchorterminal.com/compare/amazon-polly-vs-google-cloud-tts.md)
- [Amazon Polly vs PlayHT Text-to-Speech API](https://www.anchorterminal.com/compare/amazon-polly-vs-playht-tts.md)
- [Azure AI Speech text-to-speech vs Google Cloud Text-to-Speech](https://www.anchorterminal.com/compare/azure-text-to-speech-vs-google-cloud-tts.md)
- [Azure AI Speech text-to-speech vs PlayHT Text-to-Speech API](https://www.anchorterminal.com/compare/azure-text-to-speech-vs-playht-tts.md)
- [Cartesia Sonic TTS API + MCP vs Google Cloud Text-to-Speech](https://www.anchorterminal.com/compare/cartesia-tts-vs-google-cloud-tts.md)
- [Cartesia Sonic TTS API + MCP vs PlayHT Text-to-Speech API](https://www.anchorterminal.com/compare/cartesia-tts-vs-playht-tts.md)
- [Deepgram Text-to-Speech (Aura-2, Flux TTS) vs Google Cloud Text-to-Speech](https://www.anchorterminal.com/compare/deepgram-tts-vs-google-cloud-tts.md)
- [Deepgram Text-to-Speech (Aura-2, Flux TTS) vs PlayHT Text-to-Speech API](https://www.anchorterminal.com/compare/deepgram-tts-vs-playht-tts.md)
- [ElevenLabs Text to Speech API + MCP vs Google Cloud Text-to-Speech](https://www.anchorterminal.com/compare/elevenlabs-tts-vs-google-cloud-tts.md)
- [ElevenLabs Text to Speech API + MCP vs PlayHT Text-to-Speech API](https://www.anchorterminal.com/compare/elevenlabs-tts-vs-playht-tts.md)
- [Fish Audio TTS API vs Google Cloud Text-to-Speech](https://www.anchorterminal.com/compare/fish-audio-tts-vs-google-cloud-tts.md)
- [Fish Audio TTS API vs PlayHT Text-to-Speech API](https://www.anchorterminal.com/compare/fish-audio-tts-vs-playht-tts.md)
- [Google Cloud Text-to-Speech vs HeyGen Voice](https://www.anchorterminal.com/compare/google-cloud-tts-vs-heygen-voice.md)
- [Google Cloud Text-to-Speech vs Inworld Realtime TTS-2](https://www.anchorterminal.com/compare/google-cloud-tts-vs-inworld-tts.md)
- [Google Cloud Text-to-Speech vs MiniMax Speech (T2A)](https://www.anchorterminal.com/compare/google-cloud-tts-vs-minimax-speech.md)
- [Google Cloud Text-to-Speech vs Murf TTS API + MCP](https://www.anchorterminal.com/compare/google-cloud-tts-vs-murf-tts.md)
- [Google Cloud Text-to-Speech vs Resemble AI Text-to-Speech API](https://www.anchorterminal.com/compare/google-cloud-tts-vs-resemble-ai-tts.md)
- [Google Cloud Text-to-Speech vs Rime TTS API + MCP](https://www.anchorterminal.com/compare/google-cloud-tts-vs-rime-tts.md)
- [Google Cloud Text-to-Speech vs Smallest.ai Lightning TTS](https://www.anchorterminal.com/compare/google-cloud-tts-vs-smallest-lightning-tts.md)
- [Google Cloud Text-to-Speech vs Soniox Text-to-Speech](https://www.anchorterminal.com/compare/google-cloud-tts-vs-soniox-tts.md)
- [HeyGen Voice vs PlayHT Text-to-Speech API](https://www.anchorterminal.com/compare/heygen-voice-vs-playht-tts.md)
- [Inworld Realtime TTS-2 vs PlayHT Text-to-Speech API](https://www.anchorterminal.com/compare/inworld-tts-vs-playht-tts.md)
- [MiniMax Speech (T2A) vs PlayHT Text-to-Speech API](https://www.anchorterminal.com/compare/minimax-speech-vs-playht-tts.md)
- [Murf TTS API + MCP vs PlayHT Text-to-Speech API](https://www.anchorterminal.com/compare/murf-tts-vs-playht-tts.md)
- [PlayHT Text-to-Speech API vs Resemble AI Text-to-Speech API](https://www.anchorterminal.com/compare/playht-tts-vs-resemble-ai-tts.md)
- [PlayHT Text-to-Speech API vs Rime TTS API + MCP](https://www.anchorterminal.com/compare/playht-tts-vs-rime-tts.md)
- [PlayHT Text-to-Speech API vs Smallest.ai Lightning TTS](https://www.anchorterminal.com/compare/playht-tts-vs-smallest-lightning-tts.md)
- [PlayHT Text-to-Speech API vs Soniox Text-to-Speech](https://www.anchorterminal.com/compare/playht-tts-vs-soniox-tts.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp