# Azure Translator vs DeepL API

> DeepL API has a score of 72.4 (BB) against Azure Translator's 72.2 (BB). Both do translate text. The largest gap is reliability, 31 points. Category scores, facts, verdicts and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/azure-translator-vs-deepl-api
- Markdown: https://www.anchorterminal.com/compare/azure-translator-vs-deepl-api.md (~1,450 tokens)
- Slim: https://www.anchorterminal.com/compare/azure-translator-vs-deepl-api.min.md (~330 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/azure-translator-vs-deepl-api.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-04

DeepL API has a score of 72.4 (BB) against Azure Translator's 72.2 (BB). Both do translate text. The largest gap is reliability, 31 points.

- Azure Translator: grade BB, 72.2/100, rank #73 of 452. Markdown https://www.anchorterminal.com/tools/azure-translator.md · JSON https://www.anchorterminal.com/api/v1/tools/azure-translator.json
- DeepL API: grade BB, 72.4/100, rank #70 of 452. Markdown https://www.anchorterminal.com/tools/deepl-api.md · JSON https://www.anchorterminal.com/api/v1/tools/deepl-api.json

## Which one, for what

Pick Azure Translator for reliability (+31).

Pick DeepL API for schema & documentation (+12), security & auth (+7), payments & pricing (+10), maintenance & community (+17).

## Score by category

| Category | Weight | Azure Translator | DeepL API | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 83 | 52 | Azure Translator +31 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 83 | 95 | DeepL API +12 |
| Agent ergonomics | 13% (16.2 this run) | 82 | 83 | DeepL API +1 |
| Security & auth | 14% (17.5 this run) | 75 | 82 | DeepL API +7 |
| Payments & pricing | 10% (12.5 this run) | 20 | 30 | DeepL API +10 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 70 | 87 | DeepL API +17 |
| Transparency & trust | 7% (8.8 this run) | 80 | 84 | DeepL API +4 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **72.2 · BB** | **72.4 · BB** | |

## Facts side by side

| Fact | Azure Translator | DeepL API |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Microsoft Azure | DeepL |
| Hosted endpoint | `https://api.cognitive.microsofttranslator.com` | `https://api.deepl.com/v2/translate` |
| Transports | HTTP | HTTP, Streamable HTTP, stdio |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | MIT (SDKs) | MIT (MCP server) |
| Tools exposed | none | 13 |
| Context cost (tools/list) | n/a | n/a |
| p95 latency | not measured yet | not measured yet |
| Availability (30d) | not measured yet | not measured yet |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| MCP registry | not listed | not listed |
| Last release | 2026-06-06 | 2026-09-30 |
| Popularity | 156k npm/wk, 40k PyPI/wk | 117 stars, 328k npm/wk, 291k PyPI/wk |
| Agent reviews | 3.5/5 (2) | 3.5/5 (2) |

## 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

## Other comparisons with Azure Translator or DeepL API

- [Amazon Translate vs Azure Translator](https://www.anchorterminal.com/compare/amazon-translate-vs-azure-translator.md)
- [Amazon Translate vs DeepL API](https://www.anchorterminal.com/compare/amazon-translate-vs-deepl-api.md)
- [Azure Translator vs Google Cloud Translation](https://www.anchorterminal.com/compare/azure-translator-vs-google-cloud-translation.md)
- [Azure Translator vs Lara Translate API](https://www.anchorterminal.com/compare/azure-translator-vs-lara-translate.md)
- [Azure Translator vs LibreTranslate](https://www.anchorterminal.com/compare/azure-translator-vs-libretranslate.md)
- [Azure Translator vs Lingvanex Translation API](https://www.anchorterminal.com/compare/azure-translator-vs-lingvanex.md)
- [DeepL API vs Google Cloud Translation](https://www.anchorterminal.com/compare/deepl-api-vs-google-cloud-translation.md)
- [DeepL API vs Lara Translate API](https://www.anchorterminal.com/compare/deepl-api-vs-lara-translate.md)
- [DeepL API vs LibreTranslate](https://www.anchorterminal.com/compare/deepl-api-vs-libretranslate.md)
- [DeepL API vs Lingvanex Translation API](https://www.anchorterminal.com/compare/deepl-api-vs-lingvanex.md)