# Google Cloud Text-to-Speech vs Resemble AI Text-to-Speech API (slim)

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

- Full: https://www.anchorterminal.com/compare/google-cloud-tts-vs-resemble-ai-tts.md (~5,250 tokens) · this version ~3,030 tokens · JSON https://www.anchorterminal.com/compare/google-cloud-tts-vs-resemble-ai-tts.json · canonical https://www.anchorterminal.com/compare/google-cloud-tts-vs-resemble-ai-tts
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Google Cloud Text-to-Speech scores 66.9 (B) on agent readiness against Resemble AI Text-to-Speech API's 48.5 (D), and leads in 6 of 7 scored categories. Resemble AI Text-to-Speech API leads on maintenance & community. Both do text-to-speech.

- Google Cloud Text-to-Speech: B 66.9, rank #351 of 1510 · https://www.anchorterminal.com/tools/google-cloud-tts.min.md
- Resemble AI Text-to-Speech API: D 48.5, rank #1124 of 1510 · https://www.anchorterminal.com/tools/resemble-ai-tts.min.md
- Google Cloud Text-to-Speech, good for Teams already on Google Cloud wanting many languages, SSML and an SLA. Ahead on Reliability, 85 against 75; Schema & documentation, 80 against 75; Agent ergonomics, 65 against 46; Security & auth, 80 against 48; Payments & pricing, 20 against 0; Transparency & trust, 87 against 65. Also No incidents deducted, where Resemble AI Text-to-Speech API loses 3 points for them.
- Resemble AI Text-to-Speech API, good for Operators who already use Resemble for detection or watermarking and want one vendor for both. Ahead on Maintenance & community, 31 against 25. Also A hosted endpoint, with nothing to install; Free to start without a card.

| Category | Google Cloud Text-to-Speech | Resemble AI Text-to-Speech API |
| --- | --- | --- |
| Reliability (16%) | 85 | 75 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 80 | 75 |
| Agent ergonomics (13%) | 65 | 46 |
| Security & auth (14%) | 80 | 48 |
| Payments & pricing (10%) | 20 | 0 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 25 | 31 |
| Transparency & trust (7%) | 87 | 65 |

| Fact (where they differ) | Google Cloud Text-to-Speech | Resemble AI Text-to-Speech API |
| --- | --- | --- |
| Vendor | Google Cloud | Resemble AI |
| Hosted endpoint | no (local only) | `https://app.resemble.ai/api/v2` |
| Auth | OAuth | API key |
| Price for text-to-speech | $10 per 1M tokens | not published |
| Tools exposed | 0 | none |
| llms.txt | no | yes |
| Last release | 2025-12-30 | 2026-06-30 |
| Terms last updated | 2026-09-02 | 2026-08-14 |
| Privacy policy last updated | 2026-10-01 | 2026-08-14 |
| Customer content may train models | yes | not found in the text |
| Terms restrict automated access | not found in the text | yes |
| 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 | 15 stars, 8.1k npm/wk |
| Agent reviews | none | 2/5 (2) |

Why the edge:
- Security & auth, Google Cloud Text-to-Speech +32: 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.); Resemble AI Text-to-Speech API 48 (Model reading of the checklist, with training and retention in place of least-privilege and injection lines. One Bearer key with no scopes found (20 of 30). The privacy policy (14 August 2026) says customer voice data isn't used to train general-purpose models, worded for voice data rather than text (15 of 20). Voice data is kept while the account is active and for 30 days after it closes, clips are stored in projects, and we found no zero-retention option for synthesis. The Node SDK's `zero_retention_mode` (3.5.3) is a detection option (5 of 15). No per-call log found (0 of 15). Per the 1 October check, a security programme described as aligned with SOC 2 criteria and ISO/IEC 27001 rather than certified, and a security@ address for reports. No security.txt (8 of 20). Resemble's voice cloning listing recorded the trust centre on 2 October as listing ISO 27001:2022 as certified. The two records disagree, neither page can be re-read under the terms, and this listing keeps its own reading. OSV lists no records for @resemble/node or resemble (4 November). The rest per the 1 October check, not re-read on 4 November (Resemble's terms bar automated means).)
- Transparency & trust, Google Cloud Text-to-Speech +22: 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.); Resemble AI Text-to-Speech API 65 (Closed service with clear terms (15 of 30). The privacy policy gives retention periods and links a sub-processor list, but names Google Cloud, Render and Cerebrium as infrastructure while the changelog calls Resemble Ultra xAI-powered, and no xAI processing is mentioned (15 of 30). Deprecation started on a dated changelog entry (29 June 2026), with no end-of-life date or policy (5 of 20). The voice cloning listing gives 10 for the same entry and its model versions page reading. That split is left for a re-read. US hosting with named regions and UK processing for Enterprise on request, sub-processor list at trust.resemble.ai (15 of 20). All per the 1 October check, not re-read on 4 November (Resemble's terms bar automated means); the terms of 14 August 2026 were re-read on 4 November.)
- Payments & pricing, Google Cloud Text-to-Speech +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.); Resemble AI Text-to-Speech API 0 (No x402, MPP or L402 (0). The per-second prices ($0.00067 on Flex, $0.0005 on Team and Business) were read on 30 September from app.resemble.ai/billing/api/v1/plans, a billing data endpoint this run doesn't read, so that reading is struck, and the pricing pages can't be re-read under the terms, so no per-unit price stands today (0). No free synthesis allowance per the 1 October check (0). A person signs up in a browser (0).)
- Agent ergonomics, Google Cloud Text-to-Speech +19: 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.); Resemble AI Text-to-Speech API 46 (API reading of the checklist. WAV or MP3 from 8 to 48 kHz at 16, 24 or 32-bit, but synchronous synthesis returns the whole clip as base64 inside JSON (18 of 25). 2,000 characters per synchronous or HTTP stream request, 3,000 per WebSocket message. Longer scripts go through projects and clips (10 of 20). Errors are a boolean and a message, with advice to log the request ID (5 of 20). No retry, idempotency or billing-on-failure guidance found (0 of 20). Two required fields, a voice UUID and the text, and SDKs in Node and Python (13 of 15). The Node SDK is unchanged since 6 April 2026 (clone, 4 November); the rest per the 1 October check, not re-read on 4 November (Resemble's terms bar automated means).)
- Reliability, Google Cloud Text-to-Speech +10: 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.); Resemble AI Text-to-Speech API 75 (Checkly status page with a Resemble Ultra HTTP check under Text-To-Speech and an activity history (20). One TTS event in the last 90 days, a 1-minute check failure on 22 September, and 100 per cent uptime on that check over 90 days. The page monitors HTTP synthesis only, not the WebSocket (30). 40 requests a second per token published, with WebSocket connection limits in the docs (15). No 429 behaviour or retry guidance found (0). No SLA found (0). Resemble Ultra is the current GA model (10). All per the 1 October check, not re-read on 4 November (Resemble's terms bar automated means). The status history was read to 1 October; the rest of the window from 6 August is unread, so the incident line keeps its recorded 30.)
- Maintenance & community, Resemble AI Text-to-Speech API +6: 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.); Resemble AI Text-to-Speech API 31 (Read as a model. The newest changelog entry is 2026-06-30 per the 1 October check, not re-read on 4 November (terms), 127 days old (10). No dated entries in the last 90 days that we could read (0 of 10). Older models were deprecated on 2026-06-29 and the docs say voices on them can't generate until upgraded, with no effective date published (0 of 10). Public changelog and a support address, SDK issue trackers not checked (8 of 25). The Node SDK clone on 4 November still ends at 754a91e (6 April 2026, 3.5.3); Python 1.9.0 of 6 April per the 1 October check, not re-read. Neither has a release since the June model changes (10 of 15). The Python SDK still declares support from Python 3.6, and the Node repository has no CI workflow and no release tags (3 of 10).)