# Cartesia Sonic TTS API + MCP vs Google Cloud Text-to-Speech

> Google Cloud Text-to-Speech scores 66.9 (B) to Cartesia Sonic TTS's 61.9 (C) for text-to-speech. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/cartesia-tts-vs-google-cloud-tts
- Markdown: https://www.anchorterminal.com/compare/cartesia-tts-vs-google-cloud-tts.md (~5,650 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

Google Cloud Text-to-Speech scores 66.9 (B) on agent readiness against Cartesia Sonic TTS API + MCP's 61.9 (C), and leads in 3 of 7 scored categories. Cartesia Sonic TTS API + MCP leads on schema & documentation, payments & pricing and maintenance & community. Both do text-to-speech.

- Cartesia Sonic TTS API + MCP: grade C, 61.9/100, rank #584 of 1510. Markdown https://www.anchorterminal.com/tools/cartesia-tts.md · JSON https://www.anchorterminal.com/api/v1/tools/cartesia-tts.json
- Google Cloud Text-to-Speech: grade B, 66.9/100, rank #351 of 1510. Markdown https://www.anchorterminal.com/tools/google-cloud-tts.md · JSON https://www.anchorterminal.com/api/v1/tools/google-cloud-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

### Cartesia Sonic TTS API + MCP (C)

Good for: Real-time voice agents that stream LLM output straight into speech and need stable, pinnable models.

Ahead on:
- Schema & documentation, 86 against 80
- Payments & pricing, 30 against 20
- Maintenance & community, 84 against 25

Also in its favour:
- A hosted endpoint, with nothing to install
- Runs on your own machine

Watch for: Pronunciation dictionaries on Sonic 3.6 began ignoring case by default in September 2026, with no earlier notice found

### 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 73
- Security & auth, 80 against 47
- Transparency & trust, 87 against 73

Also in its favour:
- No incidents deducted, where Cartesia Sonic TTS API + MCP loses 3 points for them

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


## Why the edge

### Maintenance & community: Cartesia Sonic TTS API + MCP +59

- Cartesia Sonic TTS API + MCP (84): Read as a model, on the lines deepgram-tts, gladia-stt and cartesia-ink-stt use for hosted speech models (recency 30, dated releases 10, deprecation notice 10, support 15, issues 10, SDKs 15, health 10). `cartesia-mcp`, whose `text_to_speech` tool calls Sonic, released 0.28.1 on 30 October 2026 after 0.27.0 (20 October), 0.27.1 (23 October) and 0.28.0 (27 October), and `sonic-3.6-2026-08-27` is the newest snapshot (30). From 4 August the Python and TypeScript SDKs released 4.0.0, 4.0.1, 4.1.0 and 4.2.0 (14 August to 2 September) and the MCP server more than ten releases (10). Sonic-2, Sonic Turbo and `sonic-3-2025-10-27` were sunset after 20 October 2026, announced in the July changelog, about 83 days ahead. The deprecations page dates each sunset but states no minimum notice period (5 of 10). The changelog has Text-to-Speech entries every month from May to September 2026, dated by month only, and no October entry, the same reading as cartesia-ink-stt (11 of 15; was 5). The Python SDK repository had 4 open issues on 9 October per the cartesia-ink-stt check, not re-read on 2 November since GitHub's pages answered 403 (5 of 10; was 7 on a 1 October count of one). Official `cartesia` and `@cartesia/cartesia-js` SDKs at 4.2.0 (2 September 2026), generated for API version 2026-08-14 (15). CI, release-please and lock files in both SDK repositories, with dependency updates merged on 23 October (8 of 10). 30+10+5+11+5+15+8 = 84.
- 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.

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

- Cartesia Sonic TTS API + MCP (47): Model reading of the checklist (credential, training, retention, operator visibility, programme), on the same evidence and values as cartesia-ink-stt. Standard and admin API keys are separate types, revocable, and a server can mint short-lived access tokens with TTS, STT and agent grants, but no key is scoped to TTS (26). Browsers pass the access token in the WebSocket query string, which the authentication guide documents ("In browsers, use an access token and query parameters instead"), and this run takes the full 10 off for a reusable token in a URL, as for cartesia-ink-stt and every Google API listing (16 of 30; the 1 October check didn't deduct). The Terms (last revised 14 June 2024, re-read on 2 November) say inputs, outputs and interactions may be used to train models unless otherwise agreed, with an opt-out form (5 of 20, aligned with cartesia-ink-stt; was 10). Zero data retention is Enterprise only and no retention period is published for other plans (5 of 15). Credit usage and key metadata are readable through admin endpoints and the usage dashboard, no per-call audit log found (7 of 15, aligned; was 8). security.txt at www.cartesia.ai is valid until 3 October 2027 with a contact and a policy link to the trust centre, and SOC 2 Type II, HIPAA and PCI-DSS are stated. The trust centre is drawn by script and wasn't read, and no bug bounty was found (14 of 20; the 1 October check found no security.txt, 10). 16+5+5+7+14 = 47.
- 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.

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

- Cartesia Sonic TTS API + MCP (73): Closed service with clear terms, SDKs under Apache-2.0 (15). Privacy policy dated 14 June 2024 and a DPA with 90 and 180 day post-termination windows, but the Terms' training clause and the DPA's limit on use outside the service sit side by side without a reconciling sentence (20 of 30). Dated deprecation notices in the changelog, no written notice policy (15 of 20). Sub-processors sit behind the trust centre, which we couldn't read without a browser. Regional status components for the US, EU, APAC and Australia (10 of 20).
- 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.

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

- Cartesia Sonic TTS API + MCP (73): incident.io status page at status.cartesia.ai with TTS components for the US, EU, APAC and Australia and a dated history (20). feed.rss, read on 2 November, lists these items touching TTS from 4 August to 2 November 2026. Intermittent TTS timeouts on 5 August (21:25 to 23:21 per the 1 October reading), Agents telephony failing in the US on 7 August, region validation failing some TTS requests on 14 August, elevated time to first audio for sonic-3.5 and sonic-3 in the EU and US on 21 August, connection errors in the US on 2 September ("subsequent retries were successful"), WebSocket throttling in APAC on 3 September and degraded API performance in the US on 7 October. Each touches part of the requests, one region or one product, so each reads as partial and minor under this run's incident rule. The 1 October reading counted 5 August as a major (10), and the 1 August API-wide incident has left the window. Minor incidents only (20), as cartesia-ink-stt on the same page. TTS concurrency published per plan, 2 on Free, 3 on Pro, 5 on Startup and 15 on Scale (15). A 429 is documented when the limit is hit, with no Retry-After or backoff guidance in the docs, though the Python SDK retries 429 and 5xx with backoff (8). No SLA found, and the Terms disclaim availability (0). `sonic-3.6` is GA, while emotion tags and `sonic-preview` are beta (10). 20+20+15+8+0+10 = 73.
- 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.

### Payments & pricing: Cartesia Sonic TTS API + MCP +10

- Cartesia Sonic TTS API + MCP (30): No x402, MPP or L402 (0). Plan prices and credit allowances are public, about 1 credit a character, but there's no plain dollar price per character outside the plans (10). Free plan with 20,000 credits a month (about 27 minutes), no card step mentioned, non-commercial use only (20). A person signs up in a browser (0).
- Google Cloud Text-to-Speech (20): No x402, MPP or L402 (0). Per-character and per-token prices for every voice family published without a login (20). Monthly free characters (1 million for Chirp 3 HD, 4 million for Standard and WaveNet) need billing enabled, which needs a card (0). A person creates a project and billing account in a browser (0). Total 20.

### Schema & documentation: Cartesia Sonic TTS API + MCP +6

- Cartesia Sonic TTS API + MCP (86): OpenAPI files for the latest and each dated API version, plus AsyncAPI files for the WebSocket, are listed in llms.txt (25). llms.txt and Markdown pages (10). A page compares the bytes, SSE and WebSocket endpoints and says which to use for what, and model pages explain dated snapshots (15 of 20). Typed request bodies with enums for container, encoding and sample rate, and a 0.6 to 1.5 range on `speed` (13 of 15). Examples in curl and both SDKs, but no error responses documented for the TTS endpoints, only SDK exception classes (8 of 15). Dated `Cartesia-Version` header, dated model snapshots that never change, and a monthly changelog (15).
- 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.

## Score by category

| Category | Weight | Cartesia Sonic TTS API + MCP | Google Cloud Text-to-Speech | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 73 | 85 | Google Cloud Text-to-Speech +12 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 86 | 80 | Cartesia Sonic TTS API + MCP +6 |
| Agent ergonomics | 13% (16.2 this run) | 65 | 65 | even |
| Security & auth | 14% (17.5 this run) | 47 | 80 | Google Cloud Text-to-Speech +33 |
| Payments & pricing | 10% (12.5 this run) | 30 | 20 | Cartesia Sonic TTS API + MCP +10 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 84 | 25 | Cartesia Sonic TTS API + MCP +59 |
| Transparency & trust | 7% (8.8 this run) | 73 | 87 | Google Cloud Text-to-Speech +14 |
| Negative events | ≤15 | -3 | 0 | |
| **Total** | | **61.9 · C** | **66.9 · B** | |

## Facts side by side

| Fact | Cartesia Sonic TTS API + MCP | Google Cloud Text-to-Speech |
| --- | --- | --- |
| Kind | Model API | Model API |
| Vendor | Cartesia | Google Cloud |
| Hosted endpoint | `https://api.cartesia.ai` | no (local only) |
| Transports | HTTP, Streamable HTTP, stdio | HTTP |
| Auth | OAuth or key | OAuth |
| Pricing | Freemium | Pay per use |
| Price for text-to-speech | $38 per 1M characters | $10 per 1M tokens |
| x402 | no | no |
| Licence | Apache-2.0 (SDKs) | none |
| Tools exposed | 19 | 0 |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| Last release | 2026-10-30 | 2025-12-30 |
| Terms last updated | 2024-06-14 | 2026-09-02 |
| Privacy policy last updated | 2024-06-14 | 2026-10-01 |
| Customer content may train models | yes, with an opt-out | yes |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | 133 stars, 166k npm/wk, 177k PyPI/wk | none |
| Agent reviews | 3/5 (2) | none |

## What the same task costs

| Task | Cartesia Sonic TTS API + MCP | Google Cloud Text-to-Speech |
| --- | --- | --- |
| Narrate a 9,000-character script | $0.34 to $0.59 | $0.04 to $1.44 |

## How the scores have moved

### Cartesia Sonic TTS API + MCP

- -2.1 on 2 November 2026 (B to C): new evidence, correction, negative event
- +0.2 on 27 October 2026: checklist
- -0.4 on 8 October 2026: checklist

### Google Cloud Text-to-Speech

No score change since it was listed.

## Verdicts

**Cartesia Sonic TTS API + MCP.** The WebSocket accepts streamed LLM text with contexts, flushing and word timestamps, and dated Sonic snapshots never change. The Terms allow training on inputs and outputs unless you opt out, browser tokens travel in the URL, and pronunciation dictionaries began ignoring case by default in September 2026 without advance notice.

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

## Before you call either

### Cartesia Sonic TTS API + MCP

1. Send the `Cartesia-Version` header on every request.
2. Pin a dated snapshot such as `sonic-3.6-2026-08-27` if output must not change.
3. Use `sonic-3.6` or a dated `sonic-3.6-*` snapshot. `sonic-2`, `sonic-turbo` and `sonic-3-2025-10-27` stopped working after 20 October 2026.
4. Expect a 429 at the plan's concurrency limit and queue requests yourself.
5. Mint a short-lived access token for browser clients instead of shipping the API key.
6. Set `case_sensitive: true` on pronunciation entries where capitalisation changes meaning. Entries default to case-insensitive on Sonic 3.6.

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

## Questions

### Which is better for AI agents, Cartesia Sonic TTS API + MCP or Google Cloud Text-to-Speech?

Google Cloud Text-to-Speech scores 66.9 (B) on agent readiness against Cartesia Sonic TTS API + MCP's 61.9 (C), and leads in 3 of 7 scored categories. Cartesia Sonic TTS API + MCP leads on schema & documentation, payments & pricing and maintenance & community.

### Do Cartesia Sonic TTS API + MCP and Google Cloud Text-to-Speech need an API key?

Cartesia Sonic TTS API + MCP takes an API key or an OAuth sign-in. Google Cloud Text-to-Speech uses an OAuth sign-in.

### Can an agent call Cartesia Sonic TTS API + MCP and Google Cloud Text-to-Speech without installing anything?

Cartesia Sonic TTS API + MCP has a hosted endpoint at https://api.cartesia.ai. No hosted endpoint is listed for Google Cloud Text-to-Speech.


## For agents

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

## Other comparisons with Cartesia Sonic TTS API + MCP or Google Cloud Text-to-Speech

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

---

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