Google Cloud Text-to-Speech vs MiniMax Speech (T2A)

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.

MiniMax Speech (T2A) 36

Model reading of the checklist, with training and retention in place of the least-privilege and injection lines. Plain API keys with no scopes found, and leaked keys may be disabled (20 of 30). The terms (effective 30 March 2026), as read for minimax-voice-cloning on 4 November, let MiniMax use input and generated content to operate, maintain, develop and improve its services, with no opt-out found, and the privacy policy rules out only training to profile or target consumers (5 of 20). The speech docs call every interface stateless, and no retention period for submitted text or generated audio was found (5 of 15). Responses carry usage_characters and a trace ID, with no audit log (6 of 15). No security.txt, disclosure policy, bug bounty or certification found (0 of 20). Total 36.

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.

MiniMax Speech (T2A) 65

Closed API with clear terms under Singapore law naming Nanonoble Pte. Ltd., and MIT MCP servers (15 of 30). Terms and privacy policy agree that inputs may be used to improve services and that data sits in a United States data centre, with no retention period, as on minimax-voice-cloning (8 of 30). The API release notes carry a dated legacy notice of 20 June 2025 for the old text-to-voice API with service continuing, and older speech models stay accepted, with no written policy or notice period (15 of 20). Data location stated as the United States and an EU representative named, third parties only by category (10 of 20). Total 48.

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.

MiniMax Speech (T2A) 38

Read as a model, as minimax-voice-cloning is. The newest dated change touching speech is the MCP servers' August update, minimax-mcp-js 0.0.18 on 21 August 2026, 77 days before 6 November, and Speech 2.8 dates from 23 January 2026 (20 of 30). No dated API entries in the last 90 days (0). Support by email and Discord, not tested (6 of 15). No official SDK for speech; the MCP servers expose text_to_audio and list_voices (8 of 15). The Python MCP server has tests and moved to version 2 of the MCP SDK in August, with no CI workflow (4 of 10). Total 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.

MiniMax Speech (T2A) 75

Atlassian Statuspage at status.minimax.io with a Text-to-Speech component (20). Its history, re-read on 6 November, shows three incidents in the 90 days from 8 August, all titled elevated errors and labelled major, 22 minutes on 28 September, 3 minutes on 16 October and 2 minutes on 19 October, and none in November. Elevated errors with no fuller scope are read as partial, as on minimax-api and minimax-voice-cloning, so minor only (20). T2A is limited to 60 requests a minute, with higher limits on audio subscriptions (15). Error codes 1002 and 2045 say to retry later and avoid sudden increases, with no Retry-After or backoff figures (10 of 15). No SLA (0). No beta or preview label on T2A (10). 20 + 20 + 15 + 10 + 0 + 10 = 75.

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.

MiniMax Speech (T2A) 56

API reading of the checklist. Audio comes back hex-encoded inside JSON by default, with subtitles opt-in and format, bitrate and sample rate settable (15 of 25). Voices are listed by type through POST /v1/get_voice, which has no pagination and returns 300+ system voices for all (10 of 20). Errors come as numeric codes in base_resp with a short remedy for each, inside responses documented only as 200 (13 of 20). No idempotency key, and the MCP tools carry no read-only or destructive annotations (10 of 20). Two required fields. No official SDK for speech, with MCP servers in Python and JavaScript (8 of 15). Total 56.