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

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

- Canonical: https://www.anchorterminal.com/compare/google-cloud-tts-vs-rime-tts
- Markdown: https://www.anchorterminal.com/compare/google-cloud-tts-vs-rime-tts.md (~5,250 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 Rime TTS API + MCP's 54.8 (C), and leads in 5 of 7 scored categories. Rime TTS API + MCP leads on 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
- Rime TTS API + MCP: grade C, 54.8/100, rank #896 of 1510. Markdown https://www.anchorterminal.com/tools/rime-tts.md · JSON https://www.anchorterminal.com/api/v1/tools/rime-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 47
- Schema & documentation, 80 against 59
- Agent ergonomics, 65 against 60
- Security & auth, 80 against 59
- Transparency & trust, 87 against 76

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

### Rime TTS API + MCP (C)

Good for: English and a handful of other languages in live voice agents where the operator cares most about data terms and price.

Ahead on:
- Payments & pricing, 40 against 20
- Maintenance & community, 70 against 25

Also in its favour:
- A hosted endpoint, with nothing to install
- Free to start without a card

Watch for: No OpenAPI file read, and the official SDKs are all 0.1.0 alpha


## Why the edge

### Maintenance & community: Rime TTS API + MCP +45

- 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.
- Rime TTS API + MCP (70): Read as a model, on the lines cartesia-tts and fish-audio-tts use for hosted speech models (recency 30, dated releases 10, deprecation notice 10, support 15, issues 10, SDKs 15, health 10). The changelog's newest entry is on-prem release `20261104` for Coda v2 and Mist v3 on 4 November 2026 (30). In the 90 days from 6 August, text-to-speech entries on 15 August, 25 August, 12 September, 25 September, 13 October, 28 October and 4 November, and SDK releases touching the TTS client (10). The terms of 29 October promise at least 30 days' notice before retiring a Model Version used on a paid plan, while Arcana's cloud retirement came 17 days after its 29 July notice (5 of 10, was 0). Public changelog with RSS and a support address (8 of 15). The SDK repository's issues couldn't be read (github.com answers 403), so the line stays absent (0). Official Rime SDKs in Python, Node.js, Go and Rust with TTS clients, newest python-v0.1.0-alpha.29 on 3 November, all alpha, read as rime-prism reads the same SDK (12 of 15, was 0). The SDK repository's checks workflow runs the tests with locked dependencies, results unread (5 of 10, was 0). 30+10+5+8+0+12+5 = 70.

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

- 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.
- Rime TTS API + MCP (47): status.rime.ai now redirects to www.rimestat.us, an incident.io page with a Text-to-speech API component and history since 30 August 2026 (20, was 10). Its feed lists two incidents in the 90 days from 6 August, "Text-to-speech APIs are partially degraded" on 3 and 5 September, both partial. The window before 30 August can't be read, and this run gives no credit for an unread part of the window, so the line keeps its recorded award (5). The errors page says synthesis concurrency depends on the plan and points to the pricing page, which on 4 November lists the Free, Flex, Scale and Enterprise plans with no concurrency or rate figure, and the WebSocket connection limit isn't published. The Starter figure of 20 concurrent generations is gone (0, was 10). The errors page says to back off on 429 and retry the upgrade after a delay, marks 500 and 502 as retryable and warns that retries bill as new synthesis. Synthesis writes nothing, so safe-retry guidance without idempotency keys earns 12 in this run, as soniox-tts, fish-audio-tts and rime-prism (12, was 15). SLAs are an Enterprise item, none published (0). Coda and Mist v3 are GA (10). 20+5+0+12+0+10 = 47.

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

- 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.
- Rime TTS API + MCP (59): No OpenAPI file (0). The Coda Protobuf quickstart says the `rime-api` package on PyPI carries `text_to_speech.proto` and `text_to_speech.asyncapi.yaml`, but pypi.org didn't resolve on 4 November, so the files weren't read and the line stays at 0 as never read. llms.txt with Markdown pages (10). The models page says which model suits what, and that a request without `modelId` goes to Mist v3 (15 of 20). Parameters are typed in reference tables (10 of 15). Examples on each endpoint and an errors page listing the messages for each status, as plain text (12 of 15). Dated changelog and versioned WebSocket paths (`/ws3`, `/ws2`), no API version header (12 of 15). 0+10+15+10+12+12 = 59.

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

- 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.
- Rime TTS API + MCP (59): Model reading of the checklist, with training and retention in place of least-privilege and injection lines. One Bearer key per request, sent as a header on WebSockets too, with no scopes or short-lived tokens, so browser apps need a server bridge (20 of 30). The terms effective 29 October 2026 (section 6.3(b)) grant Rime a perpetual licence to train its models on Free Plan customer data, excluding voice recordings and audio with a natural person's voice, with no opt-out found. Paid plans aren't covered by that licence, and the privacy policy says customer data isn't used for training unless agreed (10, was 20). Only character counts are kept by default, and request retention for support is an off-by-default dashboard switch since 2026-08-25 (15). No per-call log found (0 of 15). SOC 2 Type II since May 2025, HIPAA since February 2024 with an audit in March 2026, and a formal vulnerability disclosure programme linked from the security page. No security.txt or bug bounty, the same reading as rime-prism (14 of 20, was 10). 20+10+15+0+14 = 59.

### Payments & pricing: Rime TTS API + MCP +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.
- Rime TTS API + MCP (40): No x402, MPP or L402 (0). Per-minute prices published without a login, Mist v3 $0.030 and Coda v2 $0.050 a minute on Flex, $0.024 and $0.040 on Scale, metered by characters at about 1,000 a minute (20). Every account gets $50 of usage a month on the Free plan with no card (20). A person signs up in a browser (0). 0+20+20+0 = 40.

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

- 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.
- Rime TTS API + MCP (76): Closed service with clear terms, effective 29 October 2026, and the SDK under MIT (15). The privacy page and the changelog agree on character counts only and optional retention off by default. The new terms' Free Plan training licence contradicts the security page's "We never use customer text or audio to train our models", which is charged once as the misleading-claim deduction, so the line holds (22 of 30). The terms promise at least 30 days' notice before a paid plan's Model Version is retired, and Arcana's retirement in August came with 17 days' notice before that policy, the reading rime-prism takes (15, was 10). A sub-processor list names 12 companies with their services, all in the United States, and the cloud runs in US West and US East plus VPC and on-prem (18, was 8). 15+22+15+18 = 70.

## Score by category

| Category | Weight | Google Cloud Text-to-Speech | Rime TTS API + MCP | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 85 | 47 | Google Cloud Text-to-Speech +38 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 80 | 59 | Google Cloud Text-to-Speech +21 |
| Agent ergonomics | 13% (16.2 this run) | 65 | 60 | Google Cloud Text-to-Speech +5 |
| Security & auth | 14% (17.5 this run) | 80 | 59 | Google Cloud Text-to-Speech +21 |
| Payments & pricing | 10% (12.5 this run) | 20 | 40 | Rime TTS API + MCP +20 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 25 | 70 | Rime TTS API + MCP +45 |
| Transparency & trust | 7% (8.8 this run) | 87 | 76 | Google Cloud Text-to-Speech +11 |
| Negative events | ≤15 | 0 | -2 | |
| **Total** | | **66.9 · B** | **54.8 · C** | |

## Facts side by side

| Fact | Google Cloud Text-to-Speech | Rime TTS API + MCP |
| --- | --- | --- |
| Kind | Model API | Model API |
| Vendor | Google Cloud | Rime Labs |
| Hosted endpoint | no (local only) | `https://users.rime.ai` |
| Transports | HTTP | HTTP, Streamable HTTP |
| Auth | OAuth | API key |
| Pricing | Pay per use | Freemium |
| Price for text-to-speech | $10 per 1M tokens | not published |
| x402 | no | no |
| Tools exposed | 0 | 6 |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| Last release | 2025-12-30 | 2026-11-04 |
| 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 | yes |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | yes |
| Agent reviews | none | 3/5 (2) |

## How the scores have moved

### Google Cloud Text-to-Speech

No score change since it was listed.

### Rime TTS API + MCP

- -1.1 on 4 November 2026: terms, product, new evidence, correction, negative event
- +0.1 on 27 October 2026: new evidence
- -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.

**Rime TTS API + MCP.** Per-minute prices are public, $50 of free usage a month needs no card, and official SDKs now cover four languages, all alpha. Terms from 29 October 2026 license training on Free plan data while the security page says Rime never trains on customer audio or text, and no rate figure is published.

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

### Rime TTS API + MCP

1. Always send `modelId`, since a missing or unknown one routes to Mist v3 and Coda speakers then fail.
2. Keep HTTP requests under 1,000 characters or use the WebSocket.
3. Back off on 429 before reopening a WebSocket, and remember each retry bills again.
4. Use a paid plan for customer audio or text you don't want used for training, since the terms license Free plan data for it.
5. Keep the key server-side, since WebSockets take it in a header and there are no short-lived tokens.

## Questions

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

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

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

Google Cloud Text-to-Speech uses an OAuth sign-in. Rime TTS API + MCP needs an API key.

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

No hosted endpoint is listed for Google Cloud Text-to-Speech. Rime TTS API + MCP has a hosted endpoint at https://users.rime.ai.


## For agents

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

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

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