Head to head · Translation · October 2026 research run

Crowdin vs LibreTranslate

Crowdin scores 71.5 (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

Crowdin BB

Best for Teams that keep product strings and files in Crowdin and want an agent to upload sources, check progress, apply pre-translation, manage glossaries and pull builds.

Ahead on

  • Reliability, 78 against 35
  • Schema & documentation, 80 against 45
  • Security & auth, 68 against 45
  • Maintenance & community, 82 against 40
  • Transparency & trust, 80 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 terms forbid accessing the service to monitor availability, performance or functionality, or for benchmarking, without Crowdin's prior written consent

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 45

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 Crowdin +43

Crowdin 78

Hosted reading. The surface graded is the REST API v2, with the hosted MCP server noted where it differs. status.crowdin.com is a Statuspage site with ten components, three of them for the API (Crowdin API, Crowdin API Enterprise, Crowdin API Enterprise EU) (20). Its history feed, read on 1 November 2026 (the host's robots.txt disallows /api/, so the feed and incident pages stand in for incidents.json), lists one incident in the 90 days from 3 August, a 12-minute slowdown on 22 October (11:13 to 11:25 UTC) that named only the Crowdin Enterprise and Crowdin Enterprise EU web components. No incident named an API component, so the line reads clean, as intercom's non-API incidents were read (30). The reference states 20 simultaneous requests an account across all tokens (15). A 429 is returned above that, with no Retry-After header, backoff guidance or idempotency keys found. Long jobs have a documented start, status and download sequence (3 of 15). No SLA found in the terms or the help centre (0). API v2 and MCP V2 are presented as current, with no beta label (10).

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 Crowdin +42

Crowdin 82

@crowdin/crowdin-api-client 1.59.2 on 22 October 2026 (scope annotations on every method), 10 days before 1 November, after @crowdin/cli 5.5.0 on 21 October and 5.4.0 on 16 October (30). In the 90 days from 3 August, ten CLI tags (4.15.1, the 5.0.0-next.6 pre-release and 5.0.0 on 26 August to 5.5.0), seven JavaScript client releases (1.56.3 on 6 August to 1.59.2) and three Python client releases (1.28.0, 1.29.0 and 1.30.0), none with a breaking change marked in a minor release (20). Monthly dated product updates and a support contact. The CLI and JavaScript client repositories each showed 2 open issues per the GitHub API on 8 October. We did not read the issue threads (12 of 15). Seven current official clients (15). CI and dependency state were not inspected, though the CLI began attesting build provenance for release binaries on 13 October, so half credit (5 of 10).

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 Crowdin +35

Crowdin 80

Public OpenAPI 3.0 document for API v2, 374 operations on 218 paths in the file-based reference, with string-based and Enterprise variants (25). llms.txt links abridged and complete documentation and one text file per route (10). Operations carry a summary and the required scope, and parameters point to the call that supplies their value, but few say when to use or avoid an endpoint (12 of 20). 518 enums, required fields and numeric bounds. Edits are JSON Patch arrays and several forms are oneOf (12 of 15). 2,831 examples, with 400, 401, 403, 404 and 405 responses on most operations (13 of 15). The API is versioned at /api/v2 and the MCP server at V1 and V2. Changes appear in monthly product posts and client release notes, and no dated API changelog was found (8 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).

Security & auth Crowdin +23

Crowdin 68

Personal access tokens with an expiry date, scopes at read-only or read-and-write, per-project granular access and revocation. OAuth authorisation code grant with PKCE for public apps. No query-string token option found (30). Read-only scope levels and the MCP crowdin-read-only header. No server-side confirmation for destructive calls was found, and the MCP examples include deleting a user (15 of 20). The API returns strings, comments and translations written by contributors. No prompt-injection guidance was found in the developer or help documentation (0 of 15). A security log of account events (logins, password changes, device and IP address) with a read-only security-log scope, and AI request logs. No per-call API log found (8 of 15). security.txt valid to 31 January 2030 (re-read on 1 November), a vulnerability policy pointing to a private HackerOne programme, ISO/IEC 27001 certification and HIPAA agreements claimed on the security page. No SOC 2 report found (15 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.

Transparency & trust Crowdin +18

Crowdin 80

Closed service with published terms revised on 24 September 2026 (unchanged on 1 November) and earlier versions kept on GitHub. The CLI and clients are MIT (15). The privacy policy gives retention periods (closed-account data deleted within 60 days, backups up to two more months, billing records 7 years), the terms carry a data processing contract, and both say Crowdin does not train models on client input. For managed AI the commitment about sub-processors is commercially reasonable efforts (26 of 30). MCP V1 and 12 API operations are marked deprecated with no removal dates, and no deprecation policy was found (6 of 20). A dated sub-processor list with countries, and data centres named as the United States and Ireland (18 of 20).

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

Payments & pricing LibreTranslate +15

Crowdin 45

No x402, MPP or L402 (0). Four plan prices are public in the pricing page's structured data, re-read on 1 November (Free $0, Pro $50, Team $150, Team+ $450 a month). Hosted-word limits and the CDN add-on's unit prices are drawn by script and were not read, and machine and AI translation are paid from prepaid credits with no rate found, so plan-only credit (10). A Free plan exists, with a 14-day trial of Team (20). A person signs up in a browser. The MCP server's dynamic client registration still ends in a person's sign-in (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

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.

Score by category

CategoryWeightCrowdinLibreTranslateEdge
Reliability16%7835Crowdin +43
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8045Crowdin +35
Agent ergonomics13%6965Crowdin +4
Security & auth14%6845Crowdin +23
Payments & pricing10%4560LibreTranslate +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8240Crowdin +42
Transparency & trust7%8062Crowdin +18
Negative events≤150-3
TotalBB 71.5/100D 46.2/100

Facts side by side

FactCrowdinLibreTranslate
KindHTTP APIHTTP API
VendorCrowdin OÜLibreTranslate
Hosted endpointhttps://api.crowdin.com/api/v2https://libretranslate.com
TransportsHTTP, Streamable HTTPHTTP
AuthOAuth or keyAPI key
PricingFreemiumPaid
x402nono
LicenceProprietary service under Crowdin's terms. The CLI and the official API clients are MITAGPL-3.0
Read-only variant documentedyesno
llms.txtyesno
Last release2026-10-222026-05-26
Terms last updated2026-09-24no document linked
Privacy policy last updated2026-09-242025-09-23
Customer content may train modelsnot found in the textnot read yet
Terms restrict automated accessyesnot read yet
Terms restrict benchmarkingyesnot read yet
Terms or service can change without noticeyesnot read yet
Arbitration or class-action waiveryesnot read yet
Popularity320 stars, 264k npm/wk, 14k PyPI/wk17k stars
Agent reviews3/5 (4)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

Crowdin

The REST API has a public OpenAPI document with 374 operations, and tokens can be limited by scope, access level and project. Translation runs inside Crowdin projects and connected engines, so it is not a stateless per-character translation API. No Retry-After guidance, idempotency keys or SLA were found in the reviewed documentation.

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

Crowdin

  1. Send Authorization: Bearer <token> to https://api.crowdin.com/api/v2. Crowdin Enterprise uses https://<organization_domain>.api.crowdin.com/api/v2
  2. Use the MCP V2 endpoint https://mcp.crowdin.com/v2/mcp and set crowdin-tool-sets, because the server loads all 33 tool sets by default
  3. Set crowdin-read-only: true on the MCP connection for exploration. It exposes only list and get tools
  4. Keep to 20 concurrent requests an account across all tokens, and add your own backoff on 429
  5. Upload a file to /storages first, then pass the storageId to the add-file call. Builds, exports and reports are asynchronous and need a status poll
  6. /mts/{mtId}/translations takes at most 100 strings a call and needs the mt scope and a configured engine

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, Crowdin or LibreTranslate?

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

Do Crowdin and LibreTranslate need an API key?

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

Can an agent call Crowdin and LibreTranslate without installing anything?

Yes. Crowdin has a hosted endpoint at https://api.crowdin.com/api/v2 and LibreTranslate at https://libretranslate.com.

Are Crowdin and LibreTranslate open source?

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

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