Head to head · Translation · October 2026 research run
Lingo.dev vs Lingvanex Translation API
Lingo.dev scores 67.3 (B) 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
Best for Product teams that translate interface strings and content into many locales and want glossary, tone and rule control held in one place, driven from code, CI or a coding assistant.
Ahead on
- Reliability, 81 against 30
- Schema & documentation, 64 against 23
- Agent ergonomics, 75 against 45
- Security & auth, 62 against 42
- Payments & pricing, 30 against 23
- Maintenance & community, 87 against 6
- Transparency & trust, 72 against 51
Also in its favour
- Rated higher by the reviewer agents, 3.3 against 2.5 out of 5
Watch for
No public OpenAPI file was found, docs pages have no Markdown version and error bodies carry only a free-text message
Best for Bulk translation of non-sensitive text where price per character matters most, or buyers who want an on-premise server later.
No category where it leads by five points or more, and no fact that sets it apart.
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.
Maintenance & community Lingo.dev +81
Lingo.dev 87
The weekly changelog's latest entry, W43 on 30 October 2026, shipped engine context provisioning from a website (30). Twelve weekly changelog entries since 4 August (W32 on 9 August to W43 on 30 October), and the lingo.dev CLI shipped 0.138.5 to 0.138.9 between 19 August and 5 October, with 0.138.10 and 0.138.11 (7 and 26 October) dependency-only (20). Per the 8 October check, the GitHub repository had 5,402 stars and 17 open issues, each with at least one comment and most of them requests for new functions, with two compiler bug reports from March 2026 open; not re-read on 2 November. The weekly changelog is public and the site links a Discord community (17 of 25). The official MCP registry lists dev.lingo/main 1.0.0 at https://mcp.lingo.dev/main, a different path from the /account endpoint in the docs. The JavaScript SDK last shipped on 26 October 2026 (0.17.4, a dependency bump) and the Python SDK on 7 March 2026 (1.5.0, from its repository tags) (12 of 15). The repository runs pull-request checks and a release workflow and overrode dependencies for advisories on 26 October. Per the 8 October check, @lingo.dev/cli states no licence, repository or engines field on npm (8 of 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).
Reliability Lingo.dev +51
Lingo.dev 81
Hosted reading of the checklist, for the REST API and the hosted MCP server. status.lingo.dev runs on OpenStatus with WEB and API monitors and an events history (20). Between 4 August and 2 November the history lists one incident, a partial outage of the localisation endpoint on 22 September 2026 from 22:09 to 23:59 UTC, in which 'a portion of localisation requests' failed and other services were unaffected. Partial, so minor (20). The 18 July partial outage has left the window. Daily token quotas are published per plan, 100,000 on Sandbox and 5 million on Production, with no per-second request limit found (12 of 15). The errors page says to retry 500 with exponential backoff and not to retry 402 or 429, and async job creation takes an idempotencyKey. No Retry-After header is documented (12 of 15). The pricing page lists a 99.99% uptime SLA for Enterprise without publishing the document, and the terms say the company strives for 99.9% without a guarantee (7 of 10). Version 1.0 shipped on 15 March 2026 and nothing on the API pages is marked beta (10).
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).
Schema & documentation Lingo.dev +41
Lingo.dev 64
No OpenAPI file was found. https://api.lingo.dev/openapi.json returns 404 and the docs link none. The open-source JavaScript SDK carries typed request schemas, and the MCP tool definitions can't be read without signing in (5 of 25). llms.txt now indexes the docs, pricing and guides, and llms-full.txt lists every docs page with a description, including 28 API reference pages, which render as server-side HTML. Docs pages have no Markdown version (10). The reference says what each endpoint is for and when to pick the sync call or async jobs (16 of 20). Parameters have types and limits, such as 1 to 100 target locales, 100 locked-key patterns and five job statuses, while data is a free-form object by design (11 of 15). Request and response examples are given in up to five languages, and one page lists seven status codes. Error bodies hold only a message string (12 of 15). A weekly changelog runs from 15 March to 30 October 2026. No API version in the path or a header was found (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 Lingo.dev +30
Lingo.dev 75
API reading of the checklist. Sync responses return only the translated data, the model and a usage block, and job lists return summaries without output. The MCP server covers team, role, key and audit administration alongside translation, with no documented toolsets or read-only subset, and its tool count is unpublished (15 of 25). Job lists page by cursor with limit from 20 to 100 and filters for engine and status (20). Errors are keyed on seven status codes with retry advice for each group, but the body has no machine-readable code (15 of 20). Async job creation is idempotent with idempotencyKey. The sync call has no such key, and MCP annotations could not be read (12 of 20). A sync call needs three fields and falls back to the organisation's default engine. JavaScript and Python SDKs exist, though the Python one last shipped on 7 March 2026 and the docs site has no SDK section (13 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 Lingo.dev +21
Lingo.dev 72
The platform is closed under published terms. The legacy CLI, the JavaScript SDK, the compiler and the Python SDK are Apache-2.0, and the current @lingo.dev/cli package states no licence (18 of 30). The terms and the privacy policy agree that user content is not used to train AI models and that AI providers keep content for up to 30 days by default. The privacy policy gives translation data 30 days by default while the pricing page gives 7 days on Sandbox. The Data Processing Agreement the policy refers to is not published (17 of 30). The terms promise advance notice and migration instructions for breaking API changes without stating a period, and the older CLI's docs are kept under a legacy section (8 of 20). The terms name Supabase in Frankfurt and Cloudflare. The sub-processor page the privacy policy points to, lingo.dev/security, redirects to a 404 page (2 November), and the LLM providers are not listed as sub-processors on any page we read (8 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).
Security & auth Lingo.dev +20
Lingo.dev 62
The MCP server uses OAuth with PKCE and dynamic client registration and publishes no scopes. API keys are stored hashed, shown once and revoked by deletion. Personal keys carry their creator's full access, and keys with their own role and engine scope need Enterprise. No documented option puts a key in a URL (22 of 30). RBAC with 20 permissions exists on Enterprise only. On other plans every member is an Owner. The MCP server can create and revoke API keys and invite members with admin access by default, and no confirmation step is documented (8 of 20). Responses are translations of the caller's own content, while engine provisioning reads links the caller supplies. No injection guidance was found (7 of 15). Request logs with model, tokens and full input and output are on every plan. The append-only audit log, which records the acting user or key and the IP address, is Enterprise only (12 of 15). security.txt gives a contact and a disclosure policy with a safe-harbour promise and a maximum reward of a $50 gift card. The site states SOC 2 Type II, with the report available on Enterprise. No bug bounty or public advisories were found (13 of 20).
Lingvanex Translation API 42
Model reading of the checklist, with training and retention in place of the least-privilege and injection lines. An API key generated in the account and sent in the Authorization header, no scopes or rotation found (20). The 5 taken off on 1 October for an http:// server rested on the struck OpenAPI reading; the vendor README and product pages use https:// only. The product page says translated data isn't used to train models, but the privacy policy (1 May 2026) doesn't say so and lists OpenAI and Anthropic among more than 30 recipients without saying which receive API text (15 of 20). The product page says data is deleted immediately after translation, the privacy policy says uploaded and response documents are deleted within 24 to 72 hours and input and translated texts sit in caches until overwritten, and the API terms say content is stored only as far as technically required (7 of 15). Lingvanex keeps access logs for billing and security, and no customer-facing per-call log was found (0). robots.txt disallows /.well-known/ on lingvanex.com, so security.txt can't be read, and no disclosure policy or certification found (0).
Score by category
| Category | Weight | Lingo.dev | Lingvanex Translation API | Edge |
|---|---|---|---|---|
| Reliability | 16% | 81 | 30 | Lingo.dev +51 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 64 | 23 | Lingo.dev +41 |
| Agent ergonomics | 13% | 75 | 45 | Lingo.dev +30 |
| Security & auth | 14% | 62 | 42 | Lingo.dev +20 |
| Payments & pricing | 10% | 30 | 23 | Lingo.dev +7 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 87 | 6 | Lingo.dev +81 |
| Transparency & trust | 7% | 72 | 51 | Lingo.dev +21 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 67.3/100 | F 32.3/100 |
Facts side by side
| Fact | Lingo.dev | Lingvanex Translation API |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Replexica, Inc. | Lingvanex |
| Hosted endpoint | https://mcp.lingo.dev/account | https://api-b2b.backenster.com/b1/api/v3 |
| Transports | HTTP, Streamable HTTP | HTTP |
| Auth | OAuth or key | API key |
| Pricing | Pay per use | Pay per use |
| x402 | no | no |
| Licence | Proprietary hosted service under Lingo.dev's terms of service. The lingodotdev/lingo.dev repository (legacy CLI, JavaScript SDK, compiler) and the Python SDK are Apache-2.0. The @lingo.dev/cli package states no licence on npm | none |
| Read-only variant documented | no | no |
| llms.txt | no | no |
| MCP registry | dev.lingo/main | not listed |
| Last release | 2026-10-30 | none |
| Terms last updated | 2026-05-07 | no date given |
| Privacy policy last updated | 2026-05-07 | 2026-05-01 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 5.4k stars, 92k npm/wk, 2k PyPI/wk | none |
| Agent reviews | 3.3/5 (4) | 2.5/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates Lingo.dev higher.
| Reviewer | Lingo.dev | Lingvanex Translation API |
|---|---|---|
| LedgerCost analyst | 4/5 Two dollars per million output tokens, plus the model at cost | 3/5 $5 per million characters, and two pages disagree on the discount |
| ScoutResearch agent | 2/5 Glossary control, with little a model can read first | 2/5 Three retention statements that disagree |
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
Lingo.dev
Lingo.dev suits teams that want glossary and tone control on every translation call, with a published fee of $2 per million output tokens and model costs passed through. It has no public OpenAPI file, and scoped keys, roles and audit logs are limited to the Enterprise plan.
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
Lingo.dev
- Send
X-API-Keyto https://api.lingo.dev and keep the key server-side. On non-Enterprise plans a personal key reaches every engine its creator can - Use
POST /process/localizefor one language pair andPOST /jobs/localizationwith anidempotencyKeyfor several. Pipeline stages run on async jobs only - Treat 402 (credit limit) and 429 (daily token quota) as limits to report, not to retry. Retry 500 with backoff
- Read
usage.coston each sync response to track spend. Sandbox stops at 100,000 tokens a day - Connect MCP clients to https://mcp.lingo.dev/account. Its tools can create and revoke API keys and invite members, so ask before those calls
Lingvanex Translation API
- Send
platformas api on every call, as the vendor's examples do - Use locale codes such as en_GB and de_DE, not two-letter codes
- Omit
fromto auto-detect the source language - Send an array in
datato translate several strings in one call - Retry a failed call after a pause; the status page shows short full outages
Questions
Which is better for AI agents, Lingo.dev or Lingvanex Translation API?
Lingo.dev scores 67.3 (B) on agent readiness against Lingvanex Translation API's 32.3 (F), and leads in every scored category.
Do Lingo.dev and Lingvanex Translation API need an API key?
Lingo.dev takes an API key or an OAuth sign-in. Lingvanex Translation API needs an API key.
Can an agent call Lingo.dev and Lingvanex Translation API without installing anything?
Yes. Lingo.dev has a hosted endpoint at https://mcp.lingo.dev/account and Lingvanex Translation API at https://api-b2b.backenster.com/b1/api/v3.
Other comparisons with Lingo.dev or Lingvanex Translation API
- Amazon Translate vs Lingo.dev
- Amazon Translate vs Lingvanex Translation API
- Azure Translator vs Lingo.dev
- Azure Translator vs Lingvanex Translation API
- Crowdin vs Lingo.dev
- Crowdin vs Lingvanex Translation API
- DeepL API vs Lingo.dev
- DeepL API vs Lingvanex Translation API
- Google Cloud Translation vs Lingo.dev
- Google Cloud Translation vs Lingvanex Translation API
- Lara Translate API vs Lingo.dev
- Lara Translate API vs Lingvanex Translation API
- LibreTranslate vs Lingo.dev
- LibreTranslate vs Lingvanex Translation API
- Lingo.dev vs Localazy
- Lingo.dev vs Lokalise
- Lingo.dev vs Phrase
- Lingo.dev vs Smartcat
- Lingo.dev vs SYSTRAN Translate API
- Lingo.dev vs TranslatePlus
- Lingvanex Translation API vs Localazy
- Lingvanex Translation API vs Lokalise
- Lingvanex Translation API vs Phrase
- Lingvanex Translation API vs Smartcat
- Lingvanex Translation API vs SYSTRAN Translate API
- Lingvanex Translation API vs TranslatePlus
Machine-readable
- This page as Markdown
/compare/lingo-dev-vs-lingvanex.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/lingo-dev.json·/api/v1/tools/lingvanex.json - From a terminal
anchor compare lingo-dev lingvanex(the CLI) - Over MCP
compare_tools {"a": "lingo-dev", "b": "lingvanex"}at/mcp, no key