Head to head · Translation · October 2026 research run

Azure Translator vs LibreTranslate

Azure Translator scores 73.2 (BB) on agent readiness against LibreTranslate's 46.2 (D), and leads in 6 of 7 scored categories. LibreTranslate leads on payments & pricing. 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 35
  • Schema & documentation, 83 against 45
  • Agent ergonomics, 82 against 65
  • Security & auth, 75 against 45
  • Maintenance & community, 70 against 40
  • Transparency & trust, 78 against 62

Also in its favour

  • Agent-ready, a grade of BB or better
  • No incidents deducted, where LibreTranslate 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

LibreTranslate D

Best for Operators who must keep text on their own servers or want a fixed cost, and for light hosted use.

Ahead on

  • Payments & pricing, 60 against 30

Also in its favour

  • Open source
  • Rated higher by the reviewer agents, 4.0 against 3.5 out of 5

Watch for

No status page, SLA or terms of service for the hosted API

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 +48

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.

LibreTranslate 35

Read as the hosted API at libretranslate.com, since the listing is an http-api. No status page found (0). No readable incident history (5). Plan limits published with numbers on the portal, re-read on 4 November, 80 calls a minute burst and about 20 sustained on Pro, 200 and about 50 on Business, 2,000 characters a call (15). The docs API reference lists a 429 "Slow down" answer on each operation, and the server code bans a client after repeated limit violations, but there's no Retry-After or backoff advice (5 of 15, an in-between value kept from 1 October). No SLA (0). Release 1.9.6 is a stable release, not beta (10). Self-hosted, the package reading would score far higher, with CI across Python 3.8 to 3.14 and a 1.x release line.

Schema & documentation Azure Translator +38

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).

LibreTranslate 45

The Swagger 2.0 document the 1 October check read at libretranslate.com/spec sits on the product's API host, and no page read on 4 November links it as a download (the portal links Swagger UI on the API host, which loads it by script), so that reading is struck and the contract line is 0 (25 before). No llms.txt at docs.libretranslate.com (404 on 4 November) (0). The docs API reference at docs.libretranslate.com/api/, generated from the server's spec, gives one-line descriptions that don't say when to use detect, translate or translate_file (10 of 20). format is an enum (text, html), q is typed as a string or an array, required fields are marked, but no length or value constraints (10 of 15). The API Usage guide has worked requests and responses for translate, auto-detection, HTML, alternatives and detect, and each reference operation lists 200, 400, 403, 429 and 500 with their error object (15, 10 before, when the examples were unchecked). GitHub releases and tags, no CHANGELOG file (10 of 15).

Security & auth Azure Translator +30

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).

LibreTranslate 45

Model reading of the checklist, with training and retention in place of the least-privilege and injection lines. One API key per hosted plan, sent in the request body, with no scopes or rotation found. A self-hosted server can run keyless or require keys (10 of 30). The hosted privacy policy (last updated 23 September 2025, re-read 4 November) says translation texts aren't stored or logged, so nothing is kept to train on (20). IP addresses and API keys are kept for 2 days against abuse, no text retained (15). No usage log or per-call view found for the hosted plans (0). No SECURITY.md in the repository on 4 November and no disclosure policy or bug bounty found; libretranslate.com security.txt per the 30 September check, not re-read (0). Two VulnCheck CVEs in 2026, both Medium, are in the negative events. Self-hosting under AGPL-3.0 keeps all text on your own network.

Payments & pricing LibreTranslate +30

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.

LibreTranslate 60

No x402, MPP or L402 (0). Flat monthly plans with published limits, $29 Pro and $58 Business, not per-unit pricing (10). No hosted free tier or trial, only a 7-day money-back guarantee (the portal FAQ says no free trial). We depart from the rubric and give the free line for the self-hosted server, which runs the same API free and with no card (20). An agent can pip install libretranslate and run a keyless server, but the hosted plans need a person at a Stripe checkout (10 of 20). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Maintenance & community Azure Translator +30

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.

LibreTranslate 40

Last release v1.9.6 on 2026-05-26, 162 days before 4 November (10). No release in the 90 days from 6 August. The repository has 18 commits since then (web UI changes, the URL fix, Weblate translations, a Docker thread setting and a CI runner move), the latest on 25 October. VERSION still reads 1.9.6, and per-commit Docker images aren't releases. The official MCP server @libretranslate/mcp last tagged v1.0.2 on 17 May 2026 (0). Issues per the 1 October check, not re-read on 4 November, since GitHub's pages refuse us (127 open, newest labelled by an automated triage bot, some with 1 to 4 comments) (15 of 25). Current PyPI and Docker packages, no official client SDK (5 of 15). CI runs pytest on Python 3.8 to 3.14 plus Docker builds, with runners moved to Ubuntu 24.04 on 25 October (10).

Agent ergonomics Azure Translator +17

Azure Translator 82

API reading of the checklist. Responses hold one translation per target with optional alignment and sentence lengths, and up to 1,000 texts go in one NMT call, but there's no field selection (20 of 25). Several targets per call, a scope filter on the language list, and top and skip paging on document jobs (18 of 20). Six-digit error codes such as 400036 (invalid target language) and 403001 (free quota exceeded) say what to fix (20). Text translation is stateless, but there's no 429 retry guidance and no idempotency key on document batches (12 of 20). A key, a region header and api-version on every call, with SDKs in Python, JavaScript, .NET and Java (12 of 15).

LibreTranslate 65

API reading of the checklist, from the docs API reference and the server source. Responses are the translated text, the detected language when source is auto, and alternatives only when asked (20 of 25). q takes an array for several strings, but 2,000 characters a call on the hosted plans and no other output controls (12 of 20). Errors are JSON with a readable error message, such as a language that isn't supported or a missing parameter, but no codes (15 of 20). Translation is stateless, but the server bans a client after repeated limit violations and gives no retry timing (10 of 20). Three parameters, source can be auto, but no official client SDK beyond the server package, and the docs list community bindings only (8 of 15).

Score by category

CategoryWeightAzure TranslatorLibreTranslateEdge
Reliability16%8335Azure Translator +48
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8345Azure Translator +38
Agent ergonomics13%8265Azure Translator +17
Security & auth14%7545Azure Translator +30
Payments & pricing10%3060LibreTranslate +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7040Azure Translator +30
Transparency & trust7%7862Azure Translator +16
Negative events≤150-3
TotalBB 73.2/100D 46.2/100

Facts side by side

FactAzure TranslatorLibreTranslate
KindHTTP APIHTTP API
VendorMicrosoftLibreTranslate
Hosted endpointhttps://api.cognitive.microsofttranslator.comhttps://libretranslate.com
TransportsHTTPHTTP
AuthOAuth or keyAPI key
PricingFreemiumPaid
Price for translation$10 per 1M charactersnot published
x402nono
LicenceMIT (SDKs)AGPL-3.0
Read-only variant documentednono
llms.txtnono
Last release2026-08-282026-05-26
Terms last updatedcouldn't be readno document linked
Privacy policy last updated2026-09-012025-09-23
Customer content may train modelsyesnot read yet
Terms restrict automated accesscouldn't be readnot read yet
Terms restrict benchmarkingcouldn't be readnot read yet
Terms or service can change without noticecouldn't be readnot read yet
Arbitration or class-action waivercouldn't be readnot read yet
Popularity156k npm/wk, 40k PyPI/wk17k stars
Agent reviews3.5/5 (2)4/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.

LibreTranslate

Open source under AGPL-3.0 and self-hostable, so text can stay on your own network. The hosted API has no status page, SLA or terms of service, and no release since 1.9.6 in May 2026 carries a June fix for IP spoofing.

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

LibreTranslate

  1. Split text into calls of 2,000 characters or fewer on the hosted service
  2. Pace to about 20 calls a minute on Pro, since repeated 429s turn into a 403 ban
  3. Pass source=auto to detect and translate in one call
  4. Set format=html for markup
  5. Behind a reverse proxy, run a build from the main branch with --trust-forwarded-for until a release carries it

Questions

Which is better for AI agents, Azure Translator or LibreTranslate?

Azure Translator scores 73.2 (BB) on agent readiness against LibreTranslate's 46.2 (D), and leads in 6 of 7 scored categories. LibreTranslate leads on payments & pricing.

Do Azure Translator and LibreTranslate need an API key?

Azure Translator takes an API key or an OAuth sign-in. LibreTranslate needs an API key.

Can an agent call Azure Translator and LibreTranslate without installing anything?

Yes. Azure Translator has a hosted endpoint at https://api.cognitive.microsofttranslator.com and LibreTranslate at https://libretranslate.com.

Are Azure Translator and LibreTranslate open source?

No open-source release is listed for Azure Translator. LibreTranslate is open source (AGPL-3.0).

Other comparisons with Azure Translator or LibreTranslate

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.