Get an audit

Head to head · Translate text · October 2026 research run

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.

Google Cloud TranslationGoogle Cloud · HTTP API B68.1/100#191 of 722 Lingo.devReplexica, Inc. · HTTP API B62.3/100#341 of 722

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

CategoryWeight this runGoogle Cloud TranslationLingo.devEdge
Reliability16%209071Google Cloud Translation +19
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27054Google Cloud Translation +16
Agent ergonomics13%16.27475Lingo.dev +1
Security & auth14%17.58062Google Cloud Translation +18
Payments & pricing10%12.52020even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.83887Lingo.dev +49
Transparency & trust7%8.87971Google Cloud Translation +8
Negative events≤1500
Total68.1 · B62.3 · B

Facts side by side

FactGoogle Cloud TranslationLingo.dev
KindHTTP APIHTTP API
VendorGoogle CloudReplexica, Inc.
Hosted endpointhttps://translation.googleapis.comhttps://mcp.lingo.dev/account
TransportsHTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumPay per use
Price for translate text$20 per 1M charactersnot published
x402nono
LicenceApache-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 documentednono
llms.txtnono
MCP registrynot listeddev.lingo/main
Last release2026-04-092026-10-07
Terms last updated2026-09-022026-05-07
Privacy policy last updated2026-10-012026-05-07
Customer content may train modelsyesnot found in the text
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textnot found in the text
Popularity561k npm/wk, 2.3M PyPI/wk5.4k stars, 92k npm/wk, 2k PyPI/wk
Agent reviews3.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.

Other comparisons with Google Cloud Translation or Lingo.dev

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.

Get an auditSee a sample report