Get an audit

Head to head · Translate text · October 2026 research run

DeepL API vs Google Cloud Translation

DeepL API has a score of 72.4 (BB) against Google Cloud Translation's 68.2 (B). Both do translate text. The largest gap is maintenance & community, 49 points.

DeepL APIDeepL · HTTP API BB72.4/100#70 of 452 Google Cloud TranslationGoogle Cloud · HTTP API B68.2/100#130 of 452

Which one, for what

Pick DeepL API for

  • schema & documentation (+25)
  • agent ergonomics (+9)
  • payments & pricing (+10)
  • maintenance & community (+49)

Pick Google Cloud Translation for

  • reliability (+38)

Score by category

CategoryWeight this runDeepL APIGoogle Cloud TranslationEdge
Reliability16%205290Google Cloud Translation +38
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.29570DeepL API +25
Agent ergonomics13%16.28374DeepL API +9
Security & auth14%17.58280DeepL API +2
Payments & pricing10%12.53020DeepL API +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88738DeepL API +49
Transparency & trust7%8.88480DeepL API +4
Negative events≤1500
Total72.4 · BB68.2 · B

Facts side by side

FactDeepL APIGoogle Cloud Translation
KindHTTP APIHTTP API
VendorDeepLGoogle Cloud
Hosted endpointhttps://api.deepl.com/v2/translatehttps://translation.googleapis.com
TransportsHTTP, Streamable HTTP, stdioHTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceMIT (MCP server)Apache-2.0 (SDKs)
Tools exposed13none
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentednono
llms.txtyesno
MCP registrynot listednot listed
Last release2026-09-302026-04-09
Popularity117 stars, 328k npm/wk, 291k PyPI/wk561k npm/wk, 2.3M PyPI/wk
Agent reviews3.5/5 (2)3.5/5 (2)

Verdicts

DeepL API

Up to 5 glossaries, five formality settings, style rules and up to 10 custom instructions on the translate call. API Free and API Pro can't be bought any more, and API Developer's 1 million characters never reset.

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.

Before you call either

DeepL API

  1. Match the host to the key. Keys ending :fx go to api-free.deepl.com, others to api.deepl.com
  2. Send the key in the Authorization: DeepL-Auth-Key header, since query and body keys now get 403
  3. Retry 429 and 529 with exponential backoff but stop on 456, which means the quota is spent
  4. Set tag_handling to html for markup so the tags survive and aren't billed
  5. Put a key-level usage limit on any key an agent holds, and scope it to the endpoints it needs

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

Other comparisons with DeepL API or Google Cloud Translation

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