Head to head · Translation · October 2026 research run

Lara Translate API vs LibreTranslate

Lara Translate API scores 64.7 (B) on agent readiness against LibreTranslate's 46.2 (D), and leads in 4 of 7 scored categories. LibreTranslate leads on security & auth. Both do translation.

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

Which one, for what

Lara Translate API B

Best for Agents that localise for one brand and need glossaries, translation memories and style instructions on every call, especially from an MCP client.

Ahead on

  • Reliability, 80 against 35
  • Schema & documentation, 74 against 45
  • Agent ergonomics, 77 against 65
  • Maintenance & community, 83 against 40

Also in its favour

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

Watch for

Texts may be used for model improvement unless a request sets noTrace

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

  • Security & auth, 45 against 40

Also in its favour

  • Open source
  • Rated higher by the reviewer agents, 4.0 against 3.0 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 Lara Translate API +45

Lara Translate API 80

Atlassian Statuspage at status.laratranslate.com with Lara Translation API as its own component (20). Its history feed, read on 2 November, lists seven incidents, the latest on 16 January 2026, so the page posts incidents and none falls in the 90 days from 4 August (30). Rate limits published, 1,000 characters a second and 10,000 a month on the free tier, 10,000 characters a second on paid plans (15). No documented status code for a breached limit and no retry or backoff advice (0). The terms state a guaranteed uptime of 98 per cent or higher, with refunds at Translated's discretion, which is weaker than a credit schedule (5 of 10). The SDKs and hosted MCP are GA. The raw REST API is on request only (10). 20 + 30 + 15 + 0 + 5 + 10 = 80.

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.

Maintenance & community Lara Translate API +43

Lara Translate API 83

@translated/lara-mcp 2.1.2 (29 October 2026, a docs release) and 2.1.1 (23 October), and Python SDK 1.17.1 (28 October 2026, reasoning effort), by repository tags (30). Since 4 August the MCP server tagged 2.0.0, 2.0.1, 2.1.0, 2.1.1 and 2.1.2, the Python SDK 1.12.1 to 1.17.1 (nine tags), and the Lara CLI 1.6.1 to 1.7.2 (four), so well over three at half weight (20). No public API changelog and we didn't read the GitHub issues. Support runs through support@laratranslate.com and a knowledge base (8 of 15). Official SDKs current in five languages, Python, Node.js, Java, PHP and Go, all tagged in October (15). The MCP server runs tests on every push and pull request, and 2.1.0 pinned dependencies against three advisories (10). 30 + 20 + 8 + 15 + 10 = 83.

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

Schema & documentation Lara Translate API +29

Lara Translate API 74

No public OpenAPI. The official MCP server publishes typed JSON Schema inputs and output schemas on all 22 tools, which is the contract an agent sees (20 of 25). llms.txt with about 30 entries (10). Tool descriptions say to call list_glossaries or list_memories first to resolve names, to send one target language per call, and to add instructions only when needed (18 of 20). Inputs typed with ID formats (gls_*, mem_*), a maximum of 10 glossaries and 20-word instructions, but language codes are free strings (13 of 15). SDK examples, and the SDKs raise typed errors for authentication, quota and validation, but no error code list was found (8 of 15). No public API changelog. The MCP repository and package versions are the only dated record (5 of 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).

Agent ergonomics Lara Translate API +12

Lara Translate API 77

MCP reading of the checklist. 22 tools, three for translation, detection and the language list, 8 for translation memories and 11 for glossaries, with no read-only subset or toolsets (15). Translate takes an array of text blocks with a translatable flag per block, but list tools show no paging controls (12 of 20). Since 2.0.0 tool failures come back as isError results with messages instead of protocol errors (15 of 20). Every tool sets readOnlyHint, destructiveHint and idempotentHint, with deletes, updates and imports marked destructive (20). Translate needs only text and a target, and SDKs exist for Python, Node.js, Java, PHP and Go (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).

Security & auth LibreTranslate +5

Lara Translate API 40

Model reading of the checklist, with training and retention in place of the least-privilege and injection lines, as the other translation listings are read. An access key ID and secret that the SDKs use to sign each request, and OAuth with a Lara account on the hosted MCP. No key scopes found (20). The developer docs say requests run in Learning Mode by default, so text may be stored and used for model improvement, and Incognito is opted into per request with noTrace (5 of 20). Learning Mode stores translation and context texts for as long as needed to improve the model unless deletion is requested. Incognito keeps text in memory only, and account content is deleted within 90 days of cancellation (5 of 15). No audit log or per-call usage view found (0). laratranslate.com has no security.txt (404 on 2 November). Translated's trust centre lists ISO/IEC 27001:2022 (auditor named) and SOC 2 Type 1 with documents behind an access request, though its SOC 2 report entry says the Type I audit is still under way, and laratranslate.com's llms.txt states the ISO 27001:2022 certification. The trust centre links Translated's vulnerability disclosure policy, with safe harbour and rewards at Translated's discretion, but its scope lists translated.com, Matecat and Matesub, not Lara. Certifications alone take 10, as coinmarketcap-x402-api (10). 20 + 5 + 5 + 0 + 10 = 40.

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.

Score by category

CategoryWeightLara Translate APILibreTranslateEdge
Reliability16%8035Lara Translate API +45
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7445Lara Translate API +29
Agent ergonomics13%7765Lara Translate API +12
Security & auth14%4045LibreTranslate +5
Payments & pricing10%6060even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8340Lara Translate API +43
Transparency & trust7%6262even
Negative events≤15-3-3
TotalB 64.7/100D 46.2/100

Facts side by side

FactLara Translate APILibreTranslate
KindHTTP APIHTTP API
VendorTranslatedLibreTranslate
Hosted endpointhttps://mcp.laratranslate.com/v1https://libretranslate.com
TransportsHTTP, Streamable HTTP, stdioHTTP
AuthOAuth or keyAPI key
PricingFreemiumPaid
x402nono
LicenceMIT (MCP server and SDKs)AGPL-3.0
Tools exposed22none
Read-only variant documentednono
llms.txtyesno
Last release2026-10-282026-05-26
Terms last updatedno date givenno document linked
Privacy policy last updatedno date given2025-09-23
Customer content may train modelsyes, with an opt-outnot read yet
Terms restrict automated accessyesnot read yet
Terms restrict benchmarkingnot found in the textnot read yet
Terms or service can change without noticeyesnot read yet
Arbitration or class-action waivernot found in the textnot read yet
Popularity97 stars, 29k npm/wk, 1.7k PyPI/wk17k stars
Agent reviews3/5 (2)4/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates LibreTranslate higher, the other way from the total score.

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

Lara Translate API

Glossaries, translation memories, styles and instructions on every translate call, and no status incident posted since January 2026. Texts may be used for model improvement unless a request sets noTrace, and the Python SDK removed a model attribute in a patch release without notice.

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

Lara Translate API

  1. Set noTrace on every request that carries private text, since storage for model improvement is the default
  2. Leave reasoning off unless the text needs it. It moves the call to Lara Think at $2,499 per million characters
  3. Resolve glossary and memory names to gls_* and mem_* IDs with the list tools before translating
  4. Send one target language per translate call
  5. Merge short documents, since each file bills at least 20,000 characters
  6. Set DO_NOT_TRACK=1 when running @translated/lara-mcp locally if usage metrics shouldn't leave the machine. Since 2.1.0 they are on by default

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, Lara Translate API or LibreTranslate?

Lara Translate API scores 64.7 (B) on agent readiness against LibreTranslate's 46.2 (D), and leads in 4 of 7 scored categories. LibreTranslate leads on security & auth.

Do Lara Translate API and LibreTranslate need an API key?

Lara Translate API takes an API key or an OAuth sign-in. LibreTranslate needs an API key.

Can an agent call Lara Translate API and LibreTranslate without installing anything?

Yes. Lara Translate API has a hosted endpoint at https://mcp.laratranslate.com/v1 and LibreTranslate at https://libretranslate.com.

Are Lara Translate API and LibreTranslate open source?

No open-source release is listed for Lara Translate API. LibreTranslate is open source (AGPL-3.0).

Other comparisons with Lara Translate API 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.