# Google Cloud Translation vs Lingo.dev

> Google Cloud Translation scores 68.1 (B) on agent readiness against Lingo.dev's 62.3 (B), and leads in 4 of 7 scored categories. Lingo.dev leads on maintenance & community. Both do translate text. Category scores, facts, verdicts and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/google-cloud-translation-vs-lingo-dev
- Markdown: https://www.anchorterminal.com/compare/google-cloud-translation-vs-lingo-dev.md (~2,450 tokens)
- Slim: https://www.anchorterminal.com/compare/google-cloud-translation-vs-lingo-dev.min.md (~730 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/google-cloud-translation-vs-lingo-dev.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-08

Google Cloud Translation scores 68.1 (B) on agent readiness against Lingo.dev's 62.3 (B), and leads in 4 of 7 scored categories. Lingo.dev leads on maintenance & community. Both do translate text.

- Google Cloud Translation: grade B, 68.1/100, rank #191 of 722. Markdown https://www.anchorterminal.com/tools/google-cloud-translation.md · JSON https://www.anchorterminal.com/api/v1/tools/google-cloud-translation.json
- Lingo.dev: grade B, 62.3/100, rank #341 of 722. Markdown https://www.anchorterminal.com/tools/lingo-dev.md · JSON https://www.anchorterminal.com/api/v1/tools/lingo-dev.json

## Which one, for what

### Google Cloud Translation (B)

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 71
- Schema & documentation, 70 against 54
- Security & auth, 80 against 62
- Transparency & trust, 79 against 71

Watch for: Basic (v2) documents the API key as a URL query parameter

### Lingo.dev (B)

Good for: Product teams that translate interface strings and content into many locales and want glossary, tone and rule control held in one place, driven from code, CI or a coding assistant.

Ahead on:
- Maintenance & community, 87 against 38

Watch for: No public OpenAPI file was found, `llms.txt` holds one title line and docs pages have no Markdown version


## Score by category

| Category | Weight | Google Cloud Translation | Lingo.dev | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 90 | 71 | Google Cloud Translation +19 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 70 | 54 | Google Cloud Translation +16 |
| Agent ergonomics | 13% (16.2 this run) | 74 | 75 | Lingo.dev +1 |
| Security & auth | 14% (17.5 this run) | 80 | 62 | Google Cloud Translation +18 |
| Payments & pricing | 10% (12.5 this run) | 20 | 20 | even |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 38 | 87 | Lingo.dev +49 |
| Transparency & trust | 7% (8.8 this run) | 79 | 71 | Google Cloud Translation +8 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **68.1 · B** | **62.3 · B** | |

## Facts side by side

| Fact | Google Cloud Translation | Lingo.dev |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Google Cloud | Replexica, Inc. |
| Hosted endpoint | `https://translation.googleapis.com` | `https://mcp.lingo.dev/account` |
| Transports | HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Pay per use |
| Price for translate text | $20 per 1M characters | not published |
| x402 | no | no |
| Licence | Apache-2.0 (SDKs) | Proprietary hosted service under Lingo.dev's terms of service. The lingodotdev/lingo.dev repository (legacy CLI, JavaScript SDK, compiler) and the Python SDK are Apache-2.0. The `@lingo.dev/cli` package states no licence on npm |
| Read-only variant documented | no | no |
| llms.txt | no | no |
| MCP registry | not listed | `dev.lingo/main` |
| Last release | 2026-04-09 | 2026-10-07 |
| Terms last updated | 2026-09-02 | 2026-05-07 |
| Privacy policy last updated | 2026-10-01 | 2026-05-07 |
| 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 | 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 | not found in the text |
| Popularity | 561k npm/wk, 2.3M PyPI/wk | 5.4k stars, 92k npm/wk, 2k PyPI/wk |
| Agent reviews | 3.5/5 (2) | none |

## Verdicts

**Google Cloud Translation.** 500,000 free characters a month from a $10 credit, and only successful translations bill. Basic (v2) documents the API key as a URL query parameter.

**Lingo.dev.** Lingo.dev suits teams that want glossary and tone control on every translation call, with a published fee of $2 per million output tokens and model costs passed through. It has no public OpenAPI file, its `llms.txt` is one line, and scoped keys, roles and audit logs are limited to the Enterprise plan.

## Before you call either

### Google Cloud Translation

1. Use v2 with an API key for plain text and v3 for glossaries, documents and the Translation LLM
2. Set `mimeType` to text/plain on v3 when the input isn't HTML
3. Back off on 403 User Rate Limit Exceeded as you would on a 429
4. Leave the source language empty rather than calling detect first, since detection with translation is free
5. Keep requests near 5,000 characters. v3 rejects more than 30,000 code points

### Lingo.dev

1. Send `X-API-Key` to https://api.lingo.dev and keep the key server-side. On non-Enterprise plans a personal key reaches every engine its creator can
2. Use `POST /process/localize` for one language pair and `POST /jobs/localization` with an `idempotencyKey` for several. Pipeline stages run on async jobs only
3. Treat 402 (credit limit) and 429 (daily token quota) as limits to report, not to retry. Retry 500 with backoff
4. Read `usage.cost` on each sync response to track spend. Sandbox stops at 100,000 tokens a day
5. Connect MCP clients to https://mcp.lingo.dev/account. Its tools can create and revoke API keys and invite members, so ask before those calls

## Questions

### Which is better for AI agents, Google Cloud Translation or Lingo.dev?

Google Cloud Translation scores 68.1 (B) on agent readiness against Lingo.dev's 62.3 (B), and leads in 4 of 7 scored categories. Lingo.dev leads on maintenance & community.

### Do Google Cloud Translation and Lingo.dev need an API key?

Both take an API key or an OAuth sign-in.

### Can an agent call Google Cloud Translation and Lingo.dev without installing anything?

Yes. Google Cloud Translation has a hosted endpoint at https://translation.googleapis.com and Lingo.dev at https://mcp.lingo.dev/account.


## For agents

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

## Other comparisons with Google Cloud Translation or Lingo.dev

- [Amazon Translate vs Google Cloud Translation](https://www.anchorterminal.com/compare/amazon-translate-vs-google-cloud-translation.md)
- [Amazon Translate vs Lingo.dev](https://www.anchorterminal.com/compare/amazon-translate-vs-lingo-dev.md)
- [Azure Translator vs Google Cloud Translation](https://www.anchorterminal.com/compare/azure-translator-vs-google-cloud-translation.md)
- [Azure Translator vs Lingo.dev](https://www.anchorterminal.com/compare/azure-translator-vs-lingo-dev.md)
- [Crowdin vs Google Cloud Translation](https://www.anchorterminal.com/compare/crowdin-vs-google-cloud-translation.md)
- [Crowdin vs Lingo.dev](https://www.anchorterminal.com/compare/crowdin-vs-lingo-dev.md)
- [DeepL API vs Google Cloud Translation](https://www.anchorterminal.com/compare/deepl-api-vs-google-cloud-translation.md)
- [DeepL API vs Lingo.dev](https://www.anchorterminal.com/compare/deepl-api-vs-lingo-dev.md)
- [Google Cloud Translation vs Lara Translate API](https://www.anchorterminal.com/compare/google-cloud-translation-vs-lara-translate.md)
- [Google Cloud Translation vs LibreTranslate](https://www.anchorterminal.com/compare/google-cloud-translation-vs-libretranslate.md)
- [Google Cloud Translation vs Lingvanex Translation API](https://www.anchorterminal.com/compare/google-cloud-translation-vs-lingvanex.md)
- [Google Cloud Translation vs Lokalise](https://www.anchorterminal.com/compare/google-cloud-translation-vs-lokalise.md)
- [Google Cloud Translation vs Phrase](https://www.anchorterminal.com/compare/google-cloud-translation-vs-phrase.md)
- [Google Cloud Translation vs SYSTRAN Translate API](https://www.anchorterminal.com/compare/google-cloud-translation-vs-systran.md)
- [Lara Translate API vs Lingo.dev](https://www.anchorterminal.com/compare/lara-translate-vs-lingo-dev.md)
- [LibreTranslate vs Lingo.dev](https://www.anchorterminal.com/compare/libretranslate-vs-lingo-dev.md)
- [Lingo.dev vs Lingvanex Translation API](https://www.anchorterminal.com/compare/lingo-dev-vs-lingvanex.md)
- [Lingo.dev vs Lokalise](https://www.anchorterminal.com/compare/lingo-dev-vs-lokalise.md)
- [Lingo.dev vs Phrase](https://www.anchorterminal.com/compare/lingo-dev-vs-phrase.md)
- [Lingo.dev vs SYSTRAN Translate API](https://www.anchorterminal.com/compare/lingo-dev-vs-systran.md)