# Google Cloud Text-to-Speech vs Smallest.ai Lightning TTS

> Google Cloud Text-to-Speech scores 66.9 (B) to Smallest.ai Lightning TTS's 64.4 (B) for text-to-speech. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/google-cloud-tts-vs-smallest-lightning-tts
- Markdown: https://www.anchorterminal.com/compare/google-cloud-tts-vs-smallest-lightning-tts.md (~5,450 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 Smallest.ai Lightning TTS's 64.4 (B), and leads in 3 of 7 scored categories. Smallest.ai Lightning TTS leads on schema & documentation, agent ergonomics, payments & pricing and maintenance & community. Both do text-to-speech.

- 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
- Smallest.ai Lightning TTS: grade B, 64.4/100, rank #471 of 1510. Markdown https://www.anchorterminal.com/tools/smallest-lightning-tts.md · JSON https://www.anchorterminal.com/api/v1/tools/smallest-lightning-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 58
- Security & auth, 80 against 52
- Transparency & trust, 87 against 70

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

### Smallest.ai Lightning TTS (B)

Good for: Low-latency speech for voice agents, with English, Hindi code-switching and Indic voices.

Ahead on:
- Schema & documentation, 92 against 80
- Agent ergonomics, 72 against 65
- Payments & pricing, 40 against 20
- Maintenance & community, 68 against 25

Watch for: `lightning_v3.1`, the default model, retires on 30 November 2026 after a 2 November notice, and clones made on it stop working


## Why the edge

### Maintenance & community: Smallest.ai Lightning TTS +43

- 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.
- Smallest.ai Lightning TTS (68): Read as a model. The newest Lightning changelog entry is dated 2 November 2026 (the v3.1 retirement notice), after a preview checkpoint on 29 October (30). Dated Lightning entries on 10, 23 and 28 August, 29 September, 14, 17 and 29 October and 2 November count, less 5 for churn, because the default model retires 28 days after its notice and clones made on it stop working (15 of 20). Public changelog, email support and a Discord server, with no evidence read of how they answer (10 of 15). The Python SDK `smallestai` 5.14.0 dates from 7 October, but the npm Node SDK has not been published since May 2025 (8 of 15). The Python SDK repository runs CI and release workflows, but has no licence file (5 of 10). Total 68.

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

- 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.
- Smallest.ai Lightning TTS (52): Model reading of the checklist, with training and retention in place of the least-privilege and injection lines. Plain `sk_` keys per organisation, shown once, revoked at once and deletable, with one key per environment advised. The docs say a key grants full account access, and no scope is offered. Short-lived access tokens (`wat_`, 30 to 900 seconds) cover only inference routes and can't mint tokens (22 of 30). The error reference documents the key as a `?token=` query parameter for browser WebSockets, and the token guide passes access tokens as `?api_key=` on the STT socket, so 10 off (12 of 30). The terms (21 October 2026) say Smallest won't use user content or input to train or improve its services. The privacy policy (18 September 2026) lists improving the services with machine learning as a use of usage data and doesn't address uploaded audio or text either way (15 of 20). Zero data retention and the `x-expire-content` header are Enterprise only, or a $1,000 a month HIPAA add-on on pay as you go. Other plans keep content readable in logs and the dashboard, with no retention period published (5 of 15). Usage is tracked per key, request rows sit in a dashboard log viewer, and every response carries `x-request-id`. No audit log of key actions was found (10 of 15). security.txt is valid to 31 December 2026 and the site footer claims SOC 2, GDPR and HIPAA compliance, while the pricing page lists SOC 2 compliance only on Enterprise. No bug bounty, disclosure policy or public advisories found (10 of 20). Total 52.

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

- 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.
- Smallest.ai Lightning TTS (58): BetterStack status page at status.smallest.ai with components for the Global, India and USA APIs (one health check covers the Agents and Models APIs), docs, the app and Electron, and per-component history (20). In the 90 days from 8 August the health checks on the shared API failed in all three regions on 9, 10, 13, 14 and 15 September (about 8, 21, 33, 17 and 64 minutes of flapping), in the Global and India regions on 11 and 17 September (12 minutes each), and in the USA region alone on 1, 3, 5, 12, 21 and 30 September (6 to 62 minutes) and 6 October (12 minutes). Outages in every region at once are read as wide errors, so several majors (0). Limits are published with numbers but disagree. The limits page says one TTS request at a time per account with up to five sockets, the Lightning v3.1 Pro card says 10 concurrent and the pricing page says 15 streams and 100 requests a minute on pay as you go (8 of 15). 429 is documented with exponential backoff from 500 ms to 30 s and Retry-After when present, and the limits page tells clients to expect 429s at the concurrency ceiling (15). An infrastructure SLA of 99.99 per cent is named for Enterprise only, with no terms, and the terms disclaim any availability commitment (5 of 10). `lightning_v3.1_pro` is stable and only the dated checkpoint is preview (10). 20 + 0 + 8 + 15 + 5 + 10 = 58.

### Payments & pricing: Smallest.ai Lightning TTS +20

- 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.
- Smallest.ai Lightning TTS (40): No x402, MPP or L402 (0). Per-character prices for both models published without a login (20). Pay as you go starts with $10 of trial credits, which the terms also describe, and no page says a card is needed to claim them, read as inworld-tts's free plan was (20). A person signs up in a browser at app.smallest.ai and creates the key in the dashboard, and top-ups go to a card on file (0). Total 40.

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

- 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.
- Smallest.ai Lightning TTS (70): Closed service with clear terms naming Smallest Inc. under California law (15). The ZDR page is specific about what each mode keeps, but the terms' no-training clause and the privacy policy's machine-learning use of usage data sit side by side, the privacy policy gives no retention periods, and the policy doesn't mention the DPA a footer link points to (15 of 30). A deprecations page gives statuses, dates and migration steps, and earlier models answer 410 with a pointer. The notice for the default `lightning_v3.1`, dated 2 November, gives 28 days before voices change and v3.1 clones stop working, and the terms let Smallest discontinue services without notice (12 of 20). Two regions named (Mumbai and Oregon) with region-pinned hosts, and only Google Analytics and Fullstory named among third parties, with no sub-processor list found (10 of 20). Total 52.

### Schema & documentation: Smallest.ai Lightning TTS +12

- 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.
- Smallest.ai Lightning TTS (92): OpenAPI 3.1 for the sync and SSE routes and AsyncAPI 2.6 for the WebSocket, with request and event schemas (25). llms.txt and a Markdown copy of every page (10). A transport guide, model cards and the compare page say which model and transport suit which job, but changelog entries correct the language lists and enums the docs and spec carried (15 of 20). Typed fields with enums for model, sample rate, language and output format, an 8,000-character limit and pattern rules on `session_id` and `request_id` (14 of 15). Examples in curl, Python and JavaScript, with error bodies on the reference and a shared error page (13 of 15). Versioned `/v1` paths, a dated Lightning changelog and dated preview checkpoints (15). Total 92.

## Score by category

| Category | Weight | Google Cloud Text-to-Speech | Smallest.ai Lightning TTS | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 85 | 58 | Google Cloud Text-to-Speech +27 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 80 | 92 | Smallest.ai Lightning TTS +12 |
| Agent ergonomics | 13% (16.2 this run) | 65 | 72 | Smallest.ai Lightning TTS +7 |
| Security & auth | 14% (17.5 this run) | 80 | 52 | Google Cloud Text-to-Speech +28 |
| Payments & pricing | 10% (12.5 this run) | 20 | 40 | Smallest.ai Lightning TTS +20 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 25 | 68 | Smallest.ai Lightning TTS +43 |
| Transparency & trust | 7% (8.8 this run) | 87 | 70 | Google Cloud Text-to-Speech +17 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **66.9 · B** | **64.4 · B** | |

## Facts side by side

| Fact | Google Cloud Text-to-Speech | Smallest.ai Lightning TTS |
| --- | --- | --- |
| Kind | Model API | Model API |
| Vendor | Google Cloud | Smallest AI |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | HTTP | HTTP, websocket |
| Auth | OAuth | API key |
| Pricing | Pay per use | Pay per use |
| Price for text-to-speech | $10 per 1M tokens | not published |
| x402 | no | no |
| Tools exposed | 0 | 0 |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| Last release | 2025-12-30 | 2026-11-02 |
| Terms last updated | 2026-09-02 | no date given |
| Privacy policy last updated | 2026-10-01 | no date given |
| 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 | not found in the text |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | yes |

## What the same task costs

| Task | Google Cloud Text-to-Speech | Smallest.ai Lightning TTS |
| --- | --- | --- |
| Narrate a 9,000-character script | $0.04 to $1.44 | $0.16 to $0.18 |

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

**Smallest.ai Lightning TTS.** Lightning streams speech over HTTP, SSE or WebSocket with OpenAPI and AsyncAPI files and public prices of $0.175 to $0.195 per 10,000 characters. The default model retires on 30 November with 28 days' notice, published concurrency limits disagree, and the shared API failed in every region on five days in September.

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

### Smallest.ai Lightning TTS

1. Always send `"model": "lightning_v3.1_pro"`, since requests with no model go to a model that retires on 30 November 2026
2. Pick voices from `GET /waves/v1/lightning-v3.1-pro/get_voices`, because the v3.1 and v3.1 Pro catalogues differ
3. Keep each request under 8,000 characters and split longer text
4. Treat 429 as the concurrency ceiling and retry with backoff from 500 ms to 30 s, honouring Retry-After
5. Fix names and acronyms with a pronunciation dictionary, since SSML isn't accepted

## Questions

### Which is better for AI agents, Google Cloud Text-to-Speech or Smallest.ai Lightning TTS?

Google Cloud Text-to-Speech scores 66.9 (B) on agent readiness against Smallest.ai Lightning TTS's 64.4 (B), and leads in 3 of 7 scored categories. Smallest.ai Lightning TTS leads on schema & documentation, agent ergonomics, payments & pricing and maintenance & community.

### Do Google Cloud Text-to-Speech and Smallest.ai Lightning TTS need an API key?

Google Cloud Text-to-Speech uses an OAuth sign-in. Smallest.ai Lightning TTS needs an API key.

### Can an agent call Google Cloud Text-to-Speech and Smallest.ai Lightning TTS without installing anything?

No hosted endpoint is listed for Google Cloud Text-to-Speech. No hosted endpoint is listed for Smallest.ai Lightning TTS.


## For agents

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

## Other comparisons with Google Cloud Text-to-Speech or Smallest.ai Lightning TTS

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