Get an audit

Head to head · Translate text · October 2026 research run

Google Cloud Translation vs Lokalise

Lokalise scores 71.3 (BB) on agent readiness against Google Cloud Translation's 68.1 (B), and leads in 4 of 7 scored categories. Google Cloud Translation leads on reliability, agent ergonomics and security & auth. Both do translate text.

Google Cloud TranslationGoogle Cloud · HTTP API B68.1/100#191 of 722 LokaliseLokalise, Inc. · HTTP API BB71.3/100#115 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 84
  • Agent ergonomics, 74 against 69
  • Security & auth, 80 against 73

Watch for

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

Lokalise BB

Good for Agents that manage localisation work, such as adding keys, uploading and exporting string files, keeping a glossary and starting AI or machine translation tasks for a team that already uses Lokalise.

Ahead on

  • Schema & documentation, 76 against 70
  • Payments & pricing, 30 against 20
  • Maintenance & community, 84 against 38

Also in its favour

  • Agent-ready, a grade of BB or better
  • Free to start without a card

Watch for

The Master Service Agreement forbids using the service for benchmarking or competitive analysis

Score by category

CategoryWeight this runGoogle Cloud TranslationLokaliseEdge
Reliability16%209084Google Cloud Translation +6
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27076Lokalise +6
Agent ergonomics13%16.27469Google Cloud Translation +5
Security & auth14%17.58073Google Cloud Translation +7
Payments & pricing10%12.52030Lokalise +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.83884Lokalise +46
Transparency & trust7%8.87981Lokalise +2
Negative events≤1500
Total68.1 · B71.3 · BB

Facts side by side

FactGoogle Cloud TranslationLokalise
KindHTTP APIHTTP API
VendorGoogle CloudLokalise, Inc.
Hosted endpointhttps://translation.googleapis.comhttps://api.lokalise.com/api2
TransportsHTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumPaid
Price for translate text$20 per 1M charactersnot published
x402nono
LicenceApache-2.0 (SDKs)Proprietary service under the Lokalise Master Service Agreement. The CLI and the Node SDK on GitHub are BSD 3-Clause
Read-only variant documentednoyes
llms.txtnoyes
Last release2026-04-092026-10-05
Terms last updated2026-09-022025-11-01
Privacy policy last updated2026-10-012026-03-01
Customer content may train modelsyesnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity561k npm/wk, 2.3M PyPI/wk124 stars, 338k npm/wk, 39k 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.

Lokalise

The REST API has public OpenAPI files, Markdown docs, published rate limits, read-only tokens, scoped OAuth and an audit log endpoint. Access needs a paid plan after a 14-day trial, a person signs up in a browser, and the Master Service Agreement forbids benchmarking. No idempotency keys or deprecation policy were found in the reviewed documentation.

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

Lokalise

  1. Send the token in the X-Api-Token header to https://api.lokalise.com/api2. OAuth access tokens go in Authorization: Bearer and expire after about 60 minutes.
  2. Stay under 6 requests a second per token and 10 concurrent requests per project. On 429, back off exponentially and read X-RateLimit-Reset.
  3. Use a read-only token for reads. A read/write token can call PUT /projects/{project_id}/empty, which deletes every key and translation.
  4. Use pagination=cursor on /keys and /translations, with limit at most 500 on keys, and follow X-Pagination-Next-Cursor.
  5. Projects above 10,000 key-language pairs need /files/async-download. Poll /processes/{process_id} for the bundle URL, and do the same after /files/upload.

Questions

Which is better for AI agents, Google Cloud Translation or Lokalise?

Lokalise scores 71.3 (BB) on agent readiness against Google Cloud Translation's 68.1 (B), and leads in 4 of 7 scored categories. Google Cloud Translation leads on reliability, agent ergonomics and security & auth.

Do Google Cloud Translation and Lokalise need an API key?

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

Can an agent call Google Cloud Translation and Lokalise without installing anything?

Yes. Google Cloud Translation has a hosted endpoint at https://translation.googleapis.com and Lokalise at https://api.lokalise.com/api2.

Other comparisons with Google Cloud Translation or Lokalise

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