Head to head · Translation · October 2026 research run

Azure Translator vs DeepL API

Azure Translator scores 73.2 (BB) on agent readiness against DeepL API's 71 (BB), and leads in 1 of 7 scored categories. DeepL API leads on schema & documentation, security & auth, payments & pricing and maintenance & community. Both do translation.

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

Which one, for what

Azure Translator BB

Best for Azure shops that want cheap NMT at volume, Entra ID auth and a choice of an LLM per request for tone and gender.

Ahead on

  • Reliability, 83 against 52

Also in its favour

  • No incidents deducted, where DeepL API loses 3 points for them

Watch for

The 2026-06-06 schema breaks v3.0 clients and drops BreakSentence and dictionary lookups from the spec

DeepL API BB

Best for Agents that need terminology control, formality and document layout kept, in European and Asian languages, and teams that want an MCP server today.

Ahead on

  • Schema & documentation, 95 against 83
  • Security & auth, 82 against 75
  • Payments & pricing, 45 against 30
  • Maintenance & community, 87 against 70

Also in its favour

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

Watch for

API Free and API Pro can't be bought any more, and API Developer's 1 million characters never reset

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.

Reliability Azure Translator +31

Azure Translator 83

Azure status page with post-incident reviews (20). The 90-day window now starts on 3 August. No review in it names Translator. The 29 September 2026 review covers intermittent failures and 500 and 503 errors for Azure OpenAI, Foundry and Azure AI services in Sweden Central from 10:03 to 15:58 UTC, which may touch Translator resources and LLM deployments there, one region and partial, so minor. The 30 September to 1 October gateway review covers networking services and doesn't name Translator. The public page lists only broad incidents (20). Limits published with numbers, 1,000 texts and 50,000 characters a request and hourly caps from 2 million characters on F0 to 200 million on S4 (15). 429 has three documented sub-codes (429000 to 429002) and the limits page asks for load spread across the hour, but there's no Retry-After or backoff guidance for 429, re-read on 1 November. Retry advice exists only for 408 and 503. Text translation has no side effects, so a retry is safe (8 of 15). The old Cognitive Services SLA address now redirects to Microsoft's Online Services SLA, a download we didn't open (10). API 2026-06-06 is GA (10). Same window reading as the Azure Speech, Key Vault and Blob Storage listings on 1 November.

DeepL API 52

Status page at status.deepl.com, which the changelog says became one combined page with an API view on 16 July 2026 (20). The page renders only in a browser, and /history, the Statuspage JSON path and an RSS feed all return the same empty application shell on 1 November, so we couldn't read its incidents. That's our limit, not a finding, but the rubric gives 5 for history we can't read (5). Request size limits are published (128 KiB a request, 16 KiB of headers) and plan character caps, and the error-handling guide says there is no fixed request-per-second figure because the service adjusts to load (5 of 15). 429 and 529 mean wait and resend, 456 means a usage limit was reached, and the guide says to retry 429 and 5xx with exponential backoff and jitter, to honour Retry-After when a response includes one and to log X-Trace-ID. It doesn't say which responses carry Retry-After, and document uploads take no idempotency key (12 of 15). No SLA found for self-serve plans (0). The text and document APIs are GA (10).

Maintenance & community DeepL API +17

Azure Translator 70

Read as a closed service with official SDKs, as the other Azure listings are. The newest release that changes the client is Java text 2.0.3 on 28 August 2026 (a custom-endpoint fix), 65 days before 1 November (20). The Java text and document libraries' 2.0.4 and 2.0.2 (6 October) and 2.1.0 (30 October) only raise azure-core and azure-core-http-netty, per their changelogs and tags. Releases that don't change the service or the client count half on the 90-day line and don't set the recency line, as this run read Amazon Transcribe's and Amazon SNS's SDK tags. Well over three dated releases in the 90 days from 3 August even so, among them .NET document 3.0.0 and JavaScript document 1.0.0 on 5 August, Java text 2.0.2 on 18 August and 2.0.3 on 28 August (20). Public What's New page (updated 8 August), Microsoft Q&A and GitHub issue trackers on the SDK repositories, which we didn't read (10 of 15). Official SDKs current in Python, JavaScript, .NET and Java, with text 2.0.0 for Python, JavaScript and .NET from 28 and 29 May 2026 (15). The SDKs live in the azure-sdk monorepos, CI not checked (5 of 10). Release dates are from the release tags and changelogs, since PyPI and npm didn't resolve from our shell on 1 November. 20+20+10+15+5 = 70.

DeepL API 87

Changelog entries on 28 and 29 October 2026 (30). 19 dated changelog entries on 15 days since 3 August and 15 deepl-mcp-server releases in the same window, the newest 1.3.15 on 14 October (20). Public changelog, support centre and an issue triage workflow on the MCP repository, but we didn't read the GitHub issues (12 of 15). Official SDKs current, the MCP server pins deepl-node 1.28.1 (15). The MCP server runs CI on every push, with Renovate keeping dependencies current (latest update 30 October) (10).

Payments & pricing DeepL API +15

Azure Translator 30

No x402, MPP or L402 (0). Per-million-character prices published without a login, readable through the Azure Retail Prices API since the pricing page needs JavaScript (20). F0 gives 2 million characters a month, but an Azure subscription 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.

DeepL API 45

No x402, MPP or L402 (0). The plan structure is public, but the per-character rates sit on a pricing page that renders only in a browser and that we couldn't read, so plan-only credit (10). API Developer gives 1,000,000 characters in total with no card, per the 30 September check (20). A person signs up in a browser for a key, and the hosted MCP needs a DeepL account login (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Schema & documentation DeepL API +12

Azure Translator 83

OpenAPI documents for text translation 3.0 and 2026-06-06 are public in Azure/azure-rest-api-specs, with examples on each operation (25). No llms.txt found on learn.microsoft.com (0). Operation descriptions state purpose, and the overview says to pick NMT or an LLM by quality, cost and scenario, but not when to avoid either (15 of 20). Enums for profanityAction, textType, tone and gender, required fields marked, but the LLM deploymentName is a free string (13 of 15). Examples in the spec and a status-code page with six-digit error codes and their meanings (15). Dated api-version values and a What's New page (15).

DeepL API 95

OpenAPI 3 document (version 3.14.0, 45 paths on 1 November), synced from DeepL's docs to the DeepLcom/openapi repository (last sync 28 October 2026) and served at developers.deepl.com (25). llms.txt with 144 links and agent instructions, plus a keyless docs MCP server since 3 June 2026 (10). Operation descriptions say what each call does, and the docs say when to pick latency_optimized or quality_optimized, though not when to avoid an endpoint (15 of 20). Enums for formality, tag handling, model type and sentence splitting, with required fields marked (15). /v2/translate documents 11 response codes including 429, 456 and 529, with examples throughout (15). Versioned paths (v1, v2, v3) and a dated changelog (15).

Security & auth DeepL API +7

Azure Translator 75

Model reading of the checklist, with training and retention in place of the least-privilege and injection lines. Resource keys, 10-minute bearer tokens, or Microsoft Entra ID with the Cognitive Services User role and managed identities (30), less 10 because the authentication reference documents passing the key in a Subscription-Key query parameter (20). The data privacy page says text translation doesn't store customer data, which leaves nothing to train on, but we didn't find an explicit training statement there (15 of 20). Text isn't stored and documents are hard-deleted after processing. LLM translation runs through your own Foundry deployment, whose retention terms we didn't check (12 of 15). Azure Monitor and the activity log record resource actions, per-request logging not confirmed (10 of 15). MSRC disclosure policy, Azure bounty programme, SOC 2 and ISO 27001 reports. The microsoft.com security.txt passed its Expires date on 2026-09-23 and still carries it on 1 November. An MSRC search on 1 November lists no CVE for the Translator service (18 of 20).

DeepL API 82

Model reading of the checklist, with training and retention in place of the least-privilege and injection lines. Keys go only in the Authorization header since query and body auth were switched off in January and February 2026. API Key Permissions, GA on 24 June 2026, scope a key to chosen endpoints, the Admin API creates, labels and deactivates developer keys, and the hosted MCP signs in with OAuth (30). DeepL says paid-plan texts aren't used for training without consent, while free services may keep content for a limited time to train models. The privacy policy doesn't say which side API Developer keys fall on (15 of 20). Paid-plan texts are deleted once the job is done, document translation runs on DeepL's own infrastructure in the EEA (12 of 15). Usage reports by key and custom reporting tag, and a trace ID per call, but no audit log of key use found (10 of 15). security.txt PGP-signed and valid to 2026-12-01 per the 30 September check, a security@deepl.com address in the repositories and SOC 2 Type II claimed. No bug bounty found (15 of 20).

Score by category

CategoryWeightAzure TranslatorDeepL APIEdge
Reliability16%8352Azure Translator +31
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8395DeepL API +12
Agent ergonomics13%8283DeepL API +1
Security & auth14%7582DeepL API +7
Payments & pricing10%3045DeepL API +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7087DeepL API +17
Transparency & trust7%7881DeepL API +3
Negative events≤150-3
TotalBB 73.2/100BB 71/100

Facts side by side

FactAzure TranslatorDeepL API
KindHTTP APIHTTP API
VendorMicrosoftDeepL
Hosted endpointhttps://api.cognitive.microsofttranslator.comhttps://api.deepl.com/v2/translate
TransportsHTTPHTTP, Streamable HTTP, stdio
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
Price for translation$10 per 1M charactersnot published
x402nono
LicenceMIT (SDKs)MIT (MCP server)
Tools exposednone13
Read-only variant documentednono
llms.txtnoyes
Last release2026-08-282026-10-29
Terms last updatedcouldn't be read2026-08-01
Privacy policy last updated2026-09-012026-09-01
Customer content may train modelsyesyes
Terms restrict automated accesscouldn't be readyes
Terms restrict benchmarkingcouldn't be readyes
Terms or service can change without noticecouldn't be readnot found in the text
Arbitration or class-action waivercouldn't be readnot found in the text
Popularity156k npm/wk, 40k PyPI/wk117 stars, 328k npm/wk, 291k PyPI/wk
Agent reviews3.5/5 (2)3.5/5 (2)

The panel on both

The 2 reviewers who reviewed both split evenly.

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

Azure Translator

$10 per million characters pay as you go, 2 million free a month on F0, commitment overage down to $5.50. The 2026-06-06 schema breaks v3.0 clients and drops BreakSentence and dictionary lookups from the spec.

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

Azure Translator

  1. Send Ocp-Apim-Subscription-Region with the key for a regional resource
  2. Pin api-version=3.0 until your client handles the 2026-06-06 inputs and value shape
  3. Batch up to 1,000 strings a call rather than one call per string
  4. Spread load across the hour, since the character caps are hourly and bursts get 429
  5. Treat 403001 as the free quota running out, not a permissions error

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
  6. Set input_conversion_options=version:1,json-placeholders:translate on JSON documents only if placeholders should be translated; they're kept verbatim by default

Questions

Which is better for AI agents, Azure Translator or DeepL API?

Azure Translator scores 73.2 (BB) on agent readiness against DeepL API's 71 (BB), and leads in 1 of 7 scored categories. DeepL API leads on schema & documentation, security & auth, payments & pricing and maintenance & community.

Do Azure Translator and DeepL API need an API key?

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

Can an agent call Azure Translator and DeepL API without installing anything?

Yes. Azure Translator has a hosted endpoint at https://api.cognitive.microsofttranslator.com and DeepL API at https://api.deepl.com/v2/translate.

Other comparisons with Azure Translator 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.