Head to head · Translation · October 2026 research run

LibreTranslate vs Lingvanex Translation API

LibreTranslate scores 46.2 (D) on agent readiness against Lingvanex Translation API's 32.3 (F), and leads in every scored category. Both do translation.

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

Which one, for what

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

  • Reliability, 35 against 30
  • Schema & documentation, 45 against 23
  • Agent ergonomics, 65 against 45
  • Payments & pricing, 60 against 23
  • Maintenance & community, 40 against 6
  • Transparency & trust, 62 against 51

Also in its favour

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

Watch for

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

Lingvanex Translation API F

Best for Bulk translation of non-sensitive text where price per character matters most, or buyers who want an on-premise server later.

Also in its favour

  • No incidents deducted, where LibreTranslate loses 3 points for them

Watch for

Five full Cloud API outages of 9 to 20 minutes between 31 August and 15 October 2026

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.

Payments & pricing LibreTranslate +37

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.

Lingvanex Translation API 23

No x402, MPP or L402 (0). $5 per million characters is published, but the two product pages give different volume prices, $3 per million for a 1 billion pre-purchase on one and $1 per million above 20 million on the other (15 of 20). A free trial is advertised with no amount, and both pages put a payment method before the API key (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): 15 is 23.

Maintenance & community LibreTranslate +34

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

Lingvanex Translation API 6

No dated API change, release note or changelog found (0). Nothing dated in the last 90 days (0). Support contact on the site, no public changelog or issue tracker found (3 of 15). The only SDK is the Python package 0.0.11 from 2024-06-24 (3 of 15). No public CI (0).

Schema & documentation LibreTranslate +22

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

Lingvanex Translation API 23

The OpenAPI document recorded on 1 October came from SwaggerHub's registry API, which no page we read links (the developer docs are drawn by script), so that reading is struck and no machine-readable contract counts (0). docs.lingvanex.com/llms.txt answers 404 (0). Lingvanex's own PHP client README on GitHub describes both operations, getLanguages and translate, and every parameter, but not when to use HTML mode or transliteration (5 of 20). It names to as required, the locale-code format and html as the one translateMode value, with no types or schema (8 of 15, the earlier partial held). PHP examples for both calls, no error responses documented (5 of 15). A v3 path, no changelog found (5 of 15).

Agent ergonomics LibreTranslate +20

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

Lingvanex Translation API 45

API reading of the checklist. Responses carry the result, plus transliteration fields when asked for, per the vendor README (20 of 25). data takes a string or an array, but no request size limit is published (10 of 20). No error responses are documented in the pages and README read; the err field and 403 came from the struck OpenAPI reading (0 of 20). Translation is stateless, but there's no retry guidance (10 of 20). Locale codes such as en_GB rather than two-letter codes, a required platform value, and a Python package 0.0.11 from June 2024 and a PHP library, both from 2024 (5 of 15).

Transparency & trust LibreTranslate +11

LibreTranslate 62

Open source under AGPL-3.0 (30). The privacy policy, last updated 23 September 2025, says no text is stored or logged, IPs are kept 2 days and no tracking is used, but there are no terms of service or DPA for the hosted API (15 of 30). No deprecation policy or dated notices found (0). We found no telemetry in the server code. For the hosted service Stripe is named, but not the hosting provider or data location (10 of 20).

Lingvanex Translation API 51

Closed service under API terms that name Nordicwise Limited of Larnaca, Cyprus, but carry no date or governing law (10 of 15). Three data statements disagree on how long text is kept, immediately deleted, 24 to 72 hours, or as long as technically required (8 of 30). The API terms promise 4 weeks' written notice before a deprecated version is switched off (10 of 20). The privacy policy, updated 1 May 2026, lists more than 30 recipients including Google, Amazon Web Services, Cloudflare, Stripe, OpenAI and Anthropic, without data locations or which ones see API text (10 of 20).

Reliability LibreTranslate +5

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.

Lingvanex Translation API 30

Better Stack status page at status.lingvanex.com with one Cloud API component, uptime bars for 30, 60 and 90 days and an incident list (20). Inside the 90 days from 12 August it lists five "Cloud API is down" incidents, on 31 August (20 minutes), 10 September (9), 9 October (11), 14 October (14) and 15 October (16). Each took down the whole and only component, so each reads as a major outage however short, and three or more give 0 (0). No rate limits published. The API terms say Lingvanex sets limits at its sole discretion (0). No 429 or retry guidance found (0). Under the terms the APIs come as is, with availability disclaimed, so no SLA (0). The cloud API isn't marked beta (10).

Score by category

CategoryWeightLibreTranslateLingvanex Translation APIEdge
Reliability16%3530LibreTranslate +5
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%4523LibreTranslate +22
Agent ergonomics13%6545LibreTranslate +20
Security & auth14%4542LibreTranslate +3
Payments & pricing10%6023LibreTranslate +37
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%406LibreTranslate +34
Transparency & trust7%6251LibreTranslate +11
Negative events≤15-30
TotalD 46.2/100F 32.3/100

Facts side by side

FactLibreTranslateLingvanex Translation API
KindHTTP APIHTTP API
VendorLibreTranslateLingvanex
Hosted endpointhttps://libretranslate.comhttps://api-b2b.backenster.com/b1/api/v3
TransportsHTTPHTTP
AuthAPI keyAPI key
PricingPaidPay per use
x402nono
LicenceAGPL-3.0none
Read-only variant documentednono
llms.txtnono
Last release2026-05-26none
Terms last updatedno document linkedno date given
Privacy policy last updated2025-09-232026-05-01
Customer content may train modelsnot read yetnot found in the text
Terms restrict automated accessnot read yetnot found in the text
Terms restrict benchmarkingnot read yetnot found in the text
Terms or service can change without noticenot read yetnot found in the text
Arbitration or class-action waivernot read yetnot found in the text
Popularity17k starsnone
Agent reviews4/5 (2)2.5/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate LibreTranslate higher.

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

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.

Lingvanex Translation API

$5 per million characters list price and a status page with an incident list. Five full Cloud API outages between 31 August and 15 October 2026, no published contract or error list we could read, and product pages that disagree on bulk prices and retention.

Before you call either

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

Lingvanex Translation API

  1. Send platform as api on every call, as the vendor's examples do
  2. Use locale codes such as en_GB and de_DE, not two-letter codes
  3. Omit from to auto-detect the source language
  4. Send an array in data to translate several strings in one call
  5. Retry a failed call after a pause; the status page shows short full outages

Questions

Which is better for AI agents, LibreTranslate or Lingvanex Translation API?

LibreTranslate scores 46.2 (D) on agent readiness against Lingvanex Translation API's 32.3 (F), and leads in every scored category.

Do LibreTranslate and Lingvanex Translation API need an API key?

Both need an API key.

Can an agent call LibreTranslate and Lingvanex Translation API without installing anything?

Yes. LibreTranslate has a hosted endpoint at https://libretranslate.com and Lingvanex Translation API at https://api-b2b.backenster.com/b1/api/v3.

Are LibreTranslate and Lingvanex Translation API open source?

LibreTranslate is open source (AGPL-3.0). No open-source release is listed for Lingvanex Translation API.

Other comparisons with LibreTranslate or Lingvanex Translation 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.