# Google Cloud Translation vs TranslatePlus (slim)

> Google Cloud Translation scores 69.9 (B) to TranslatePlus's 39.7 (E) for translation. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/google-cloud-translation-vs-translateplus.md (~5,450 tokens) · this version ~3,430 tokens · JSON https://www.anchorterminal.com/compare/google-cloud-translation-vs-translateplus.json · canonical https://www.anchorterminal.com/compare/google-cloud-translation-vs-translateplus
- 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 Translation scores 69.9 (B) on agent readiness against TranslatePlus's 39.7 (E), and leads in 6 of 7 scored categories. TranslatePlus leads on payments & pricing. Both do translation.

- Google Cloud Translation: B 69.9, rank #221 of 1510 · https://www.anchorterminal.com/tools/google-cloud-translation.min.md
- TranslatePlus: E 39.7, rank #1335 of 1510 · https://www.anchorterminal.com/tools/translateplus.min.md
- Google Cloud Translation, good for Agents on Google Cloud that want high quotas, clear data terms and a choice of NMT, LLM or adaptive translation with glossaries. Ahead on Reliability, 90 against 45; Schema & documentation, 70 against 52; Agent ergonomics, 74 against 61; Security & auth, 87 against 35; Maintenance & community, 38 against 10; Transparency & trust, 85 against 52. Also A hosted endpoint, with nothing to install; No incidents deducted, where TranslatePlus loses 3 points for them.
- TranslatePlus, good for Low-cost per-request translation of short strings, HTML, emails, subtitles and i18n files for small projects. Ahead on Payments & pricing, 30 against 20.

| Category | Google Cloud Translation | TranslatePlus |
| --- | --- | --- |
| Reliability (16%) | 90 | 45 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 70 | 52 |
| Agent ergonomics (13%) | 74 | 61 |
| Security & auth (14%) | 87 | 35 |
| Payments & pricing (10%) | 20 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 38 | 10 |
| Transparency & trust (7%) | 85 | 52 |

| Fact (where they differ) | Google Cloud Translation | TranslatePlus |
| --- | --- | --- |
| Vendor | Google Cloud | PetaBytes, Inc. |
| Hosted endpoint | `https://translation.googleapis.com` | no (local only) |
| Auth | OAuth or key | API key |
| Price for translation | $20 per 1M characters | not published |
| Licence | Apache-2.0 (SDKs) | none |
| Read-only variant documented | no | yes |
| llms.txt | no | yes |
| Last release | 2026-10-08 | 2026-01-11 |
| Terms last updated | 2026-09-02 | 2024-12-18 |
| Privacy policy last updated | 2026-10-01 | no date given |
| Customer content may train models | yes | not found in the text |
| Popularity | 561k npm/wk, 2.3M PyPI/wk | 6 npm/wk, 4 PyPI/wk |
| Agent reviews | 3.5/5 (2) | none |

Why the edge:
- Security & auth, Google Cloud Translation +52: Google Cloud Translation 87 (Model reading of the checklist, with training and retention in place of the least-privilege and injection lines, as the other translation listings are read. Advanced (v3) uses OAuth 2.0 from service accounts or Application Default Credentials, with a `cloud-translation` scope and IAM roles (30), less 10 because Basic (v2) documents the API key as a `key` query parameter. The OAuth token can travel in the URL as well. The v3 Discovery document (revision 20260901) lists `access_token`, `oauth_token` and `key` as query parameters, and on 1 November a v3 translateText request with no token answered 401 'Request is missing required authentication credential' while one with a made-up `?access_token=` answered 401 'Request had invalid authentication credentials', the test every Google API listing takes in this run. The checklist takes the 10 off once for a secret in a URL, so this adds no second deduction (20). The data usage FAQ (last updated 27 October) says Google doesn't use content sent to the API to train or improve Google Translation and won't share it with third parties (20). Text is held briefly in memory for the request. Glossaries are stored in your project, and Basic's global endpoint can't keep processing in one region (15). The audit logging page lists every v3 method by permission type, and translation calls write Data Access logs, which Google Cloud leaves off until the owner enables them. Basic (v2) isn't audit-logged, and calls to AutoML models aren't logged (12 of 15). google.com security.txt valid to 1 April 2030 and pointing to the vulnerability reward programme, and Google Cloud's ISO 27001 page names Cloud Translation in scope, both read on 1 November. That is the reading most Google Cloud listings take on this line (20). 20 + 20 + 15 + 12 + 20 = 87.); TranslatePlus 35 (One API key per account in the X-API-KEY header, which the docs say 'carries full access to your account's resources', and can be revoked in the dashboard (15). No scopes or read-only keys (5). Translations return the caller's own text, so little untrusted content (10). llms.txt claims request logging and an analytics dashboard, which we couldn't see without an account (5). translateplus.io/.well-known/security.txt returns 404 and no disclosure policy was found; llms.txt says 'SOC 2 compliant' and 'SOC 2 Type II certified infrastructure' with no report or auditor named (0). 15+5+10+5+0 = 35.)
- Reliability, Google Cloud Translation +45: Google Cloud Translation 90 (Google Cloud status page with a JSON incident feed, and Cloud Translation and AutoML Translation are products of their own in its product list (20). The feed read on 1 November holds eight incidents back to 27 February 2026, four of them since 3 August (20 August, 27 products in us-west1 and global; 1 September, network degradation in us-central1-b; 8 to 9 October, Cloud Storage in us-central1; 20 October, 38 products in europe-west2), and none lists Cloud Translation, so the 90 days from 3 August are clean, as Document AI and Model Armor read the same feed. The public page shows only broad incidents (30). Quotas published with numbers, 6,000,000 characters a minute per project, 300,000 requests a minute on v2, 6,000 on v3 and 900 for the Translation LLM, re-read on 1 November (page last updated 27 October) (15). Quota breaches come back as 403 with Daily Limit Exceeded or User Rate Limit Exceeded rather than 429, and the quotas page still gives no retry or backoff advice. Translation is stateless and only successful translations bill, so a retry is safe (5 of 15). 99.9 per cent monthly SLA for Basic, Advanced and AutoML Translation, per the 1 October check, not re-read on 1 November (10). Basic and Advanced are GA (10). 20 + 30 + 15 + 5 + 10 + 10 = 90.); TranslatePlus 45 (Hosted lines. status.translateplus.io is the vendor's own page; on 6 November 2026 it showed 'All systems unknown' and a last update of 22 January 2026, with data loading by script (5). No incident history to read (5). The rate-limits guide gives 100,000 requests a minute and 100,000,000 an hour per key, while llms.txt gives 50 requests a second on the Free plan, so limits are published but inconsistent (10). 429 returns a JSON detail message, responses carry X-RateLimit-Limit, -Remaining and -Reset, and the guide shows waiting for the reset with capped retries (15). No SLA. The terms say TranslatePlus strives for 99.9% uptime 'but do not guarantee uninterrupted service' (0). API v2 is the current, non-beta version (10). 5+5+10+15+0+10 = 45.)
- Transparency & trust, Google Cloud Translation +33: Google Cloud Translation 85 (Closed service under the Google Cloud terms, client libraries under Apache-2.0 (15). The data usage FAQ (last updated 27 October) agrees with the terms on in-memory processing, no training and no sharing, but doesn't cover the Translation LLM or adaptive translation (25 of 30). The Translation docs carry a deprecation page that applies the Google Cloud terms' discontinuation section and gives Translation Hub a deprecation date of 30 June 2025 and a shutdown date of 20 September 2026, and the release notes date the PBMT removal of 2021. The notice is for a neighbouring product rather than the API, and there is no per-version lifecycle page like Document AI's (16 of 20). Regional endpoints on Advanced for data location, global-only on Basic. Google Cloud's sub-processor list wasn't re-checked (15 of 20). 15 + 25 + 16 + 15 = 71.); TranslatePlus 52 (Editorial half only. Closed service under terms last updated 18 December 2024 that name PetaBytes, Inc. as a US corporation but give no address, governing law or courts (10). The terms say translation requests aren't permanently stored 'unless required by law', the privacy policy says 'unless required for caching or service improvement purposes', and the terms allow using anonymised usage data to improve the service (8). API v1 is kept as legacy, with no dated deprecation notice (5). No subprocessor list or data location found (0). 10+8+5+0 = 23.)
- Maintenance & community, Google Cloud Translation +28: Google Cloud Translation 38 (Read as a closed service with official SDKs. The last change to the API we found is still the adaptive `mime_type` field, in Node.js client 9.4.0 on 8 April 2026 and Python client 3.26.0 on 9 April, 206 days before 1 November, and the newest release note is 24 February 2026 (0). In the 90 days from 3 August there are seven client releases and no release note. Node.js `@google-cloud/translate` 10.0.0 (4 August, Node.js 22 floor), 10.0.1 (12 August, dependencies), 10.1.0 (8 September, a generator upgrade that only reformats the client code), 10.1.1 (28 September, package.json), 10.2.0 (7 October, a test script) and 10.3.0 (8 October, no change to the package beyond its version), and Python `google-cloud-translate` 3.28.0 (1 October, declares Python 3.15 support). None changes the service or the client's behaviour, so none can set the recency line. Releases that don't change the service count half on the 90-day line, and with no change to the service in the window that is half the line, as the Amazon SNS listing reads its version bumps and the AgentCore Code Interpreter listing its SDK releases (10 of 20). Release notes, Google Cloud support and the public issue tracker exist, but the notes have had one entry in the past year (8 of 15). Official client libraries current, Python for 3.10 to 3.15 and Node.js 22 or later (15). Libraries regenerate in the googleapis monorepos, CI not checked (5 of 10). 0 + 10 + 8 + 15 + 5 = 38.); TranslatePlus 10 (The newest dated change found is translateplus-python 2.0.7 and translateplus-js 2.0.1 on 11 January 2026, about ten months before this check, and the API changelog stops at 9 December 2024 (0). No release or dated change in the last 90 days (0). Support by email and a support portal; the status page hasn't updated since January (3). SDKs exist for four languages but haven't changed since January (5). Weekly downloads of 4 (PyPI) and 6 (npm) (2). 0+0+3+5+2 = 10.)
- Schema & documentation, Google Cloud Translation +18: Google Cloud Translation 70 (A public Discovery document for v3 (revision 20260901, unchanged on 1 November) and the protos behind the SDKs form the machine-readable contract (25). No llms.txt at docs.cloud.google.com/translate (0). The docs explain Basic against Advanced and NMT against the Translation LLM and adaptive translation, but not when to avoid each (15 of 20). Types and required fields in the Discovery document, but `model` is a resource path string and `mimeType` a free string rather than enums (10 of 15). REST pages carry examples and the quotas page documents the 403 messages, with errors otherwise in Google's generic error model (10 of 15). Versioned v2 and v3 and a release notes page, but the notes skip changes the SDK changelog shows, such as RefineText in November 2025 and an adaptive `mime_type` field in April 2026 (10 of 15).); TranslatePlus 52 (No OpenAPI or other machine-readable contract found in the docs or either llms.txt (0). llms.txt on the site and on docs.translateplus.io (10). Endpoint pages say what each call does, with little on when to choose HTML, email or i18n jobs over plain text (10). Required fields and per-plan character limits per request are documented, without enums for language codes beyond a supported-languages call (10). Code examples in several languages and an error-handling guide with status codes (12). Versioned /v1 and /v2 paths and a changelog, whose newest entry is 2.0.0 on 9 December 2024 (10). 0+10+10+10+12+10 = 52.)
- Agent ergonomics, Google Cloud Translation +13: Google Cloud Translation 74 (API reading of the checklist. Responses hold the translations and detected language, and a glossary call returns both the glossary and plain translations, which doubles the output (20 of 25). Many strings per request (128 on v2), glossary listing with page size, token and filter, batch jobs to Cloud Storage (18 of 20). Errors use Google's status and message format, but quota errors arrive as 403, so generic 429 retry logic misses them (12 of 20). Stateless translation and long-running batch operations, with no retry guidance on the quotas page (12 of 20). v3 needs a project and location path and treats input as HTML unless `mimeType` says otherwise. Client libraries in seven or more languages (12 of 15).); TranslatePlus 61 (API reading. Batch translation of up to 100 texts a call and separate HTML, email, subtitle and i18n job endpoints (16). Few output controls or filters (10). Errors are a `detail` string with HTTP status codes (12). No idempotency key for i18n jobs, though text translation is stateless (8). Official SDKs listed for Python, JavaScript and TypeScript, Java and PHP, with few required fields (15). 16+10+12+8+15 = 61.)