# Deepgram Text-to-Speech (Aura-2, Flux TTS) vs Google Cloud Text-to-Speech

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

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

Deepgram Text-to-Speech (Aura-2, Flux TTS) scores 75.6 (BB) on agent readiness against Google Cloud Text-to-Speech's 66.9 (B), and leads in 4 of 7 scored categories. Google Cloud Text-to-Speech leads on reliability, security & auth and transparency & trust. Both do text-to-speech.

- Deepgram Text-to-Speech (Aura-2, Flux TTS): grade BB, 75.6/100, rank #58 of 1486. Markdown https://www.anchorterminal.com/tools/deepgram-tts.md · JSON https://www.anchorterminal.com/api/v1/tools/deepgram-tts.json
- 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
- 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

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

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

Ahead on:
- Schema & documentation, 95 against 80
- Agent ergonomics, 82 against 65
- Payments & pricing, 40 against 20
- Maintenance & community, 73 against 25

Also in its favour:
- Agent-ready, a grade of BB or better
- A hosted endpoint, with nothing to install
- Runs on your own machine
- Free to start without a card

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

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

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


## Why the edge

### Maintenance & community: Deepgram Text-to-Speech (Aura-2, Flux TTS) +48

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

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

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

### Agent ergonomics: Deepgram Text-to-Speech (Aura-2, Flux TTS) +17

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

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

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

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

- Deepgram Text-to-Speech (Aura-2, Flux TTS) (78): Closed service with clear terms, SDKs MIT (15). The docs describe training by default under the Model Improvement Program and EU, Australian and Indian endpoints, while the privacy policy (last updated 26 October 2021, re-read on 1 November 2026) says data sits on US servers and doesn't mention the program (15 of 30). Breaking corrections are flagged in the changelog, but we found no deprecation policy (10 of 20). Sub-processor list and four regional endpoints (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.

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

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

## Score by category

| Category | Weight | Deepgram Text-to-Speech (Aura-2, Flux TTS) | Google Cloud Text-to-Speech | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 80 | 85 | Google Cloud Text-to-Speech +5 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 95 | 80 | Deepgram Text-to-Speech (Aura-2, Flux TTS) +15 |
| Agent ergonomics | 13% (16.2 this run) | 82 | 65 | Deepgram Text-to-Speech (Aura-2, Flux TTS) +17 |
| Security & auth | 14% (17.5 this run) | 72 | 80 | Google Cloud Text-to-Speech +8 |
| Payments & pricing | 10% (12.5 this run) | 40 | 20 | Deepgram Text-to-Speech (Aura-2, Flux TTS) +20 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 73 | 25 | Deepgram Text-to-Speech (Aura-2, Flux TTS) +48 |
| Transparency & trust | 7% (8.8 this run) | 78 | 87 | Google Cloud Text-to-Speech +9 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **75.6 · BB** | **66.9 · B** | |

## Facts side by side

| Fact | Deepgram Text-to-Speech (Aura-2, Flux TTS) | Google Cloud Text-to-Speech |
| --- | --- | --- |
| Kind | Model API | Model API |
| Vendor | Deepgram | Google Cloud |
| Hosted endpoint | `https://api.deepgram.com/v1` | no (local only) |
| Transports | HTTP, Streamable HTTP, stdio, SSE (legacy) | HTTP |
| Auth | API key | OAuth |
| Pricing | Pay per use | Pay per use |
| Price for text-to-speech | $45 per 1M characters | $10 per 1M tokens |
| x402 | no | no |
| Licence | MIT (SDKs) | none |
| Tools exposed | none | 0 |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| Last release | 2026-10-28 | 2025-12-30 |
| Terms last updated | 2026-08-06 | 2026-09-02 |
| Privacy policy last updated | 2021-10-26 | 2026-10-01 |
| Customer content may train models | yes, with an opt-out | yes |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | 468 stars, 1.1M npm/wk, 805k PyPI/wk | none |
| Agent reviews | 3.5/5 (2) | none |

## What the same task costs

| Task | Deepgram Text-to-Speech (Aura-2, Flux TTS) | Google Cloud Text-to-Speech |
| --- | --- | --- |
| Narrate a 9,000-character script | $0.13 to $0.41 | $0.04 to $1.44 |

## How the scores have moved

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

- +2.8 on 1 November 2026: security, correction
- +0.1 on 27 October 2026: checklist
- -0.3 on 8 October 2026: checklist

### Google Cloud Text-to-Speech

No score change since it was listed.

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

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

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

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

Deepgram Text-to-Speech (Aura-2, Flux TTS) scores 75.6 (BB) on agent readiness against Google Cloud Text-to-Speech's 66.9 (B), and leads in 4 of 7 scored categories. Google Cloud Text-to-Speech leads on reliability, security & auth and transparency & trust.

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

Deepgram Text-to-Speech (Aura-2, Flux TTS) needs an API key. Google Cloud Text-to-Speech uses an OAuth sign-in.

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

Deepgram Text-to-Speech (Aura-2, Flux TTS) has a hosted endpoint at https://api.deepgram.com/v1. No hosted endpoint is listed for Google Cloud Text-to-Speech.


## For agents

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

## Other comparisons with Deepgram Text-to-Speech (Aura-2, Flux TTS) or Google Cloud Text-to-Speech

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