Head to head · Translation · October 2026 research run

Google Cloud Translation vs Lara Translate API

Google Cloud Translation scores 71.1 (BB) on agent readiness against Lara Translate API's 64.7 (B), and leads in 3 of 7 scored categories. Lara Translate API leads on payments & pricing and maintenance & community. Both do translation.

Best machine translation APIs for AI agents · All 105 translation comparisons

Which one, for what

Google Cloud Translation BB

Best 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 80
  • Security & auth, 87 against 40
  • Transparency & trust, 85 against 62

Also in its favour

  • Agent-ready, a grade of BB or better
  • Rated higher by the reviewer agents, 3.5 against 3.0 out of 5
  • No incidents deducted, where Lara Translate API loses 3 points for them

Watch for

Basic (v2) documents the API key as a URL query parameter, and both versions accept an OAuth token as ?access_token=

Lara Translate API B

Best for Agents that localise for one brand and need glossaries, translation memories and style instructions on every call, especially from an MCP client.

Ahead on

  • Payments & pricing, 60 against 30
  • Maintenance & community, 83 against 38

Also in its favour

  • Runs on your own machine
  • Free to start without a card

Watch for

Texts may be used for model improvement unless a request sets noTrace

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Security & auth Google Cloud Translation +47

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.

Lara Translate API 40

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. An access key ID and secret that the SDKs use to sign each request, and OAuth with a Lara account on the hosted MCP. No key scopes found (20). The developer docs say requests run in Learning Mode by default, so text may be stored and used for model improvement, and Incognito is opted into per request with noTrace (5 of 20). Learning Mode stores translation and context texts for as long as needed to improve the model unless deletion is requested. Incognito keeps text in memory only, and account content is deleted within 90 days of cancellation (5 of 15). No audit log or per-call usage view found (0). laratranslate.com has no security.txt (404 on 2 November). Translated's trust centre lists ISO/IEC 27001:2022 (auditor named) and SOC 2 Type 1 with documents behind an access request, though its SOC 2 report entry says the Type I audit is still under way, and laratranslate.com's llms.txt states the ISO 27001:2022 certification. The trust centre links Translated's vulnerability disclosure policy, with safe harbour and rewards at Translated's discretion, but its scope lists translated.com, Matecat and Matesub, not Lara. Certifications alone take 10, as coinmarketcap-x402-api (10). 20 + 5 + 5 + 0 + 10 = 40.

Maintenance & community Lara Translate API +45

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.

Lara Translate API 83

@translated/lara-mcp 2.1.2 (29 October 2026, a docs release) and 2.1.1 (23 October), and Python SDK 1.17.1 (28 October 2026, reasoning effort), by repository tags (30). Since 4 August the MCP server tagged 2.0.0, 2.0.1, 2.1.0, 2.1.1 and 2.1.2, the Python SDK 1.12.1 to 1.17.1 (nine tags), and the Lara CLI 1.6.1 to 1.7.2 (four), so well over three at half weight (20). No public API changelog and we didn't read the GitHub issues. Support runs through support@laratranslate.com and a knowledge base (8 of 15). Official SDKs current in five languages, Python, Node.js, Java, PHP and Go, all tagged in October (15). The MCP server runs tests on every push and pull request, and 2.1.0 pinned dependencies against three advisories (10). 30 + 20 + 8 + 15 + 10 = 83.

Payments & pricing Lara Translate API +30

Google Cloud Translation 30

No x402, MPP or L402 (0). Per-million-character and per-page prices for every model published without a login, re-read on 1 November (20). A $10 monthly credit covers 500,000 NMT characters, but a billing account needs a card (0). A person signs up in a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.

Lara Translate API 60

No x402, MPP or L402 (0). Per-million-character prices for Standard, Think and Prosa published in dollars and euros without a login (20). The Free plan includes 10,000 API characters a month with no credit card required (20). A person signs up in a browser, and the hosted MCP signs in with a Lara account (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Transparency & trust Google Cloud Translation +23

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.

Lara Translate API 62

Closed service under published terms, SDKs and MCP server under MIT (15). The terms describe Learning Mode storing texts to improve Lara's model, the developer docs say that's the default, and the privacy policy says some data isn't used for AI model training without making clear which. No retention period for Learning Mode texts (12 of 30). ModernMT's sunset is dated (keys work until 2026-12-31) with an endpoint map, and the terms promise 30 days' notice of material changes (15 of 20). The DPA points to a sub-processor and data location list we didn't open (10 of 20).

Reliability Google Cloud Translation +10

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.

Lara Translate API 80

Atlassian Statuspage at status.laratranslate.com with Lara Translation API as its own component (20). Its history feed, read on 2 November, lists seven incidents, the latest on 16 January 2026, so the page posts incidents and none falls in the 90 days from 4 August (30). Rate limits published, 1,000 characters a second and 10,000 a month on the free tier, 10,000 characters a second on paid plans (15). No documented status code for a breached limit and no retry or backoff advice (0). The terms state a guaranteed uptime of 98 per cent or higher, with refunds at Translated's discretion, which is weaker than a credit schedule (5 of 10). The SDKs and hosted MCP are GA. The raw REST API is on request only (10). 20 + 30 + 15 + 0 + 5 + 10 = 80.

Score by category

CategoryWeightGoogle Cloud TranslationLara Translate APIEdge
Reliability16%9080Google Cloud Translation +10
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7074Lara Translate API +4
Agent ergonomics13%7477Lara Translate API +3
Security & auth14%8740Google Cloud Translation +47
Payments & pricing10%3060Lara Translate API +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%3883Lara Translate API +45
Transparency & trust7%8562Google Cloud Translation +23
Negative events≤150-3
TotalBB 71.1/100B 64.7/100

Facts side by side

FactGoogle Cloud TranslationLara Translate API
KindHTTP APIHTTP API
VendorGoogle CloudTranslated
Hosted endpointhttps://translation.googleapis.comhttps://mcp.laratranslate.com/v1
TransportsHTTPHTTP, Streamable HTTP, stdio
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
Price for translation$20 per 1M charactersnot published
x402nono
LicenceApache-2.0 (SDKs)MIT (MCP server and SDKs)
Tools exposednone22
Read-only variant documentednono
llms.txtnoyes
Last release2026-10-082026-10-28
Terms last updated2026-09-02no date given
Privacy policy last updated2026-10-01no date given
Customer content may train modelsyesyes, with an opt-out
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/wk97 stars, 29k npm/wk, 1.7k PyPI/wk
Agent reviews3.5/5 (2)3/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Google Cloud Translation higher.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Google Cloud Translation

500,000 free characters a month from a $10 credit, and only successful translations bill. Advanced has per-method audit logs and regional endpoints. Basic (v2) documents the API key as a URL query parameter, quota errors arrive as 403 rather than 429, and the API itself hasn't changed since April 2026.

Lara Translate API

Glossaries, translation memories, styles and instructions on every translate call, and no status incident posted since January 2026. Texts may be used for model improvement unless a request sets noTrace, and the Python SDK removed a model attribute in a patch release without notice.

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. Send keys and tokens in headers, never as key or access_token in the URL, so they stay out of logs

Lara Translate API

  1. Set noTrace on every request that carries private text, since storage for model improvement is the default
  2. Leave reasoning off unless the text needs it. It moves the call to Lara Think at $2,499 per million characters
  3. Resolve glossary and memory names to gls_* and mem_* IDs with the list tools before translating
  4. Send one target language per translate call
  5. Merge short documents, since each file bills at least 20,000 characters
  6. Set DO_NOT_TRACK=1 when running @translated/lara-mcp locally if usage metrics shouldn't leave the machine. Since 2.1.0 they are on by default

Questions

Which is better for AI agents, Google Cloud Translation or Lara Translate API?

Google Cloud Translation scores 71.1 (BB) on agent readiness against Lara Translate API's 64.7 (B), and leads in 3 of 7 scored categories. Lara Translate API leads on payments & pricing and maintenance & community.

Do Google Cloud Translation and Lara Translate API need an API key?

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

Can an agent call Google Cloud Translation and Lara Translate API without installing anything?

Yes. Google Cloud Translation has a hosted endpoint at https://translation.googleapis.com and Lara Translate API at https://mcp.laratranslate.com/v1.

Other comparisons with Google Cloud Translation or Lara Translate API

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.