Get an audit

Head to head · Translate text · October 2026 research run

Amazon Translate vs DeepL API

DeepL API has a score of 72.4 (BB) against Amazon Translate's 69.8 (B). Both do translate text. The largest gap is maintenance & community, 62 points.

Amazon TranslateAmazon Web Services · HTTP API B69.8/100#105 of 452 DeepL APIDeepL · HTTP API BB72.4/100#70 of 452

Which one, for what

Pick Amazon Translate for

  • reliability (+38)

Pick DeepL API for

  • schema & documentation (+5)
  • security & auth (+7)
  • payments & pricing (+10)
  • maintenance & community (+62)
  • transparency & trust (+11)

Score by category

CategoryWeight this runAmazon TranslateDeepL APIEdge
Reliability16%209052Amazon Translate +38
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.29095DeepL API +5
Agent ergonomics13%16.28083DeepL API +3
Security & auth14%17.57582DeepL API +7
Payments & pricing10%12.52030DeepL API +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.82587DeepL API +62
Transparency & trust7%8.87384DeepL API +11
Negative events≤1500
Total69.8 · B72.4 · BB

Facts side by side

FactAmazon TranslateDeepL API
KindHTTP APIHTTP API
VendorAmazon Web ServicesDeepL
Hosted endpointhttps://translate.us-east-1.amazonaws.comhttps://api.deepl.com/v2/translate
TransportsHTTPHTTP, Streamable HTTP, stdio
AuthAPI keyOAuth or key
PricingPay per useFreemium
x402nono
LicencenoneMIT (MCP server)
Tools exposednone13
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.txtyesyes
MCP registrynot listednot listed
Last release2023-10-312026-09-30
Popularity601k npm/wk117 stars, 328k npm/wk, 291k PyPI/wk
Agent reviews4/5 (2)3.5/5 (2)

Verdicts

Amazon Translate

IAM policies scope access per action and resource, with a TranslateReadOnly managed policy, and CloudTrail logs each call. AWS may store and use text to improve Amazon AI services unless the organisation sets an opt-out policy.

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.

Before you call either

Amazon Translate

  1. Chunk real-time text under 10,000 bytes, not characters, so multibyte scripts fit less per call
  2. Pass SourceLanguageCode auto to detect the source language, and handle DetectedLanguageLowConfidenceException
  3. Read AppliedSettings in the response, since unsupported formality or profanity settings are dropped without an error
  4. Retry TooManyRequestsException with backoff, which the AWS SDKs do by default
  5. Set the AI services opt-out policy before sending private text

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

Other comparisons with Amazon Translate or DeepL 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.

Get an auditSee a sample report