{ "data": { "a": { "slug": "lingo-dev", "name": "Lingo.dev", "vendor": "Replexica, Inc.", "vendorUrl": "https://lingo.dev", "kind": "http-api", "category": "translation", "summary": "Lingo.dev is a hosted AI translation platform from Replexica, Inc. Customers configure engines with glossaries, brand voices, rules and a model per language pair, then call them through a REST API, a CLI or a hosted MCP server.", "url": "https://www.anchorterminal.com/tools/lingo-dev", "markdownUrl": "https://www.anchorterminal.com/tools/lingo-dev.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/lingo-dev.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/lingo-dev.json", "repo": "https://github.com/lingodotdev/lingo.dev", "license": "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", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://mcp.lingo.dev/account", "packages": [ { "registry": "npm", "name": "@lingo.dev/cli" }, { "registry": "npm", "name": "lingo.dev" }, { "registry": "npm", "name": "@lingo.dev/_sdk" }, { "registry": "pypi", "name": "lingodotdev" } ], "auth": "mixed", "authNotes": "The REST API takes an API key in the `X-API-Key` header. A person creates the key in the dashboard after a browser signup, with no review or sales step. Personal keys exist on every plan and carry their creator's access. Organisation keys with their own role and engine scope need the Enterprise plan. The MCP server signs in through a browser with OAuth (authorisation code, PKCE, dynamic client registration) and the user picks one organisation on the consent screen. No OAuth scopes are published.", "pricing": "usage", "pricingNotes": "Usage is billed from prepaid credits with auto-reload. Lingo.dev charges $2 per million output tokens on top of the LLM provider's price, which is passed through with no markup, plus $0.50 per engine a month and $0.01 per AI review run. Sandbox has a $0 base and 100,000 tokens a day, so an agent's owner can start without a contract. Production is $99 a month with 5 million tokens a day, and Enterprise is custom. No free usage allowance was found, and whether signup needs a card could not be read without an account (https://lingo.dev/en/pricing, checked 2026-10-08).", "priceSummary": "$99 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the API docs or the pricing page. The API's 402 status means the organisation's credit limit was reached and carries no payment instructions (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 5402, "npmWeekly": 91991, "pypiWeekly": 1975, "asOf": "2026-10-08" }, "docsUrl": "https://lingo.dev/en/docs/api", "registryName": "dev.lingo/main", "capabilities": [ "translate.text", "translate.glossary", "translate.detect", "translate.formality" ], "tags": [ "hosted", "usage-priced", "prepaid", "mcp", "oauth", "api-key", "cli", "webhooks", "async-jobs", "typescript", "python", "closed-source", "status-page", "soc2", "enterprise" ], "lastRelease": "2026-10-07", "graded": true, "anchor": { "graded": true, "score": 62.3, "grade": "B", "agentReady": false, "rank": 341, "ranked": true, "rankOf": 722, "categoryRank": 8, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 75, "maintenance": 87, "payments": 20, "reliability": 71, "schema": 54, "security": 62, "transparency": 71 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "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, its `llms.txt` is one line, and scoped keys, roles and audit logs are limited to the Enterprise plan.", "bestFor": "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.", "strengths": [ "Glossary terms, per-locale brand voice and rules apply on every call, sync or async, through one configured engine", "Each sync response reports the model used, token counts and cost in USD", "Async jobs take up to 100 target locales, an `idempotencyKey`, signed webhooks and cursor paging with `limit` up to 100", "The hosted MCP server signs in with OAuth, PKCE and dynamic client registration, with no key to paste", "Public prices, a weekly changelog since March 2026 and an OpenStatus page with incident history" ], "weaknesses": [ "No public OpenAPI file was found, `llms.txt` holds one title line and docs pages have no Markdown version", "Organisation keys with their own role and engine scope, RBAC and audit logs are Enterprise only. On other plans every member is an Owner", "The status page lists two partial API outages in 90 days, on 18 July 2026 (closed after 19 hours) and 22 September 2026 (1 hour 50 minutes)", "Errors carry a status code and a free-text `message`, with no machine-readable code and no `Retry-After` documented", "The privacy policy points to lingo.dev/security for sub-processors, and that page returned 404 on 8 October 2026" ], "agentNotes": [ "Send `X-API-Key` to 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/localize` for one language pair and `POST /jobs/localization` with an `idempotencyKey` for 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.cost` on 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" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 62.3 } ], "editorialScores": { "ergonomics": 75, "maintenance": 87, "payments": 20, "reliability": 71, "schema": 54, "security": 62, "transparency": 51 }, "provenanceScore": 91 }, "connect": { "install": "npm install -g @lingo.dev/cli", "http": "curl -X POST https://api.lingo.dev/process/localize \\\n -H \"X-API-Key: your_api_key\" \\\n -H \"Content-Type: application/json\" \\\n -d '{\"engineId\": \"eng_abc123\", \"sourceLocale\": \"en\", \"targetLocale\": \"de\", \"data\": {\"greeting\": \"Hello\"}}'", "claudeCode": "claude mcp add lingo --transport http https://mcp.lingo.dev/account --scope user", "config": { "lingo": { "type": "http", "url": "https://mcp.lingo.dev/account" } } }, "letme": { "capability": "https://letme.dev/translate.text", "tool": "https://letme.dev/lingo-dev" }, "area": "everyday", "unitPrices": [ { "item": "Lingo.dev infrastructure fee", "unit": "1m-tokens", "usd": 2, "note": "Computed from output tokens. The LLM provider's price is added with no markup" }, { "item": "Production plan base", "unit": "month", "usd": 99, "note": "5 million tokens a day. Sandbox base is $0 with 100,000 a day" }, { "item": "Each engine", "unit": "month", "usd": 0.5, "note": "Per engine on Sandbox and Production" }, { "item": "AI review run", "unit": "call", "usd": 0.01, "note": "Per run" } ], "provenance": { "legalEntity": "Replexica, Inc.", "domain": "lingo.dev", "domainRegistered": "2021-05-03", "endpointOnVendorDomain": true, "terms": "https://lingo.dev/en/legal/terms", "privacy": "https://lingo.dev/en/legal/privacy", "statusPage": "https://status.lingo.dev", "changelog": "https://lingo.dev/en/changelog", "securityTxt": "valid", "checked": "2026-10-08", "notes": [ "The terms of service (last updated 7 May 2026) cover the website, the platform, the APIs, the CLI and the MCP server, name Replexica Inc. and Lingo.dev (Replexica, Inc), and are governed by Delaware law.", "The privacy policy (last updated 7 May 2026) covers the website and the platform, including content submitted for translation.", "The API answers at api.lingo.dev and the MCP server at mcp.lingo.dev, both on the vendor's domain.", "lingo.dev/.well-known/security.txt gives security@lingo.dev, a canonical URL and a disclosure policy with a safe-harbour promise. It has no Expires field.", "RDAP for lingo.dev gives a registration date of 2021-05-03. The site footer says the company is headquartered in San Francisco. No street address was found in the terms or the privacy policy.", "The privacy policy says the sub-processor list is kept in the Data Processing Agreement and at lingo.dev/security. That URL returned 404 on 8 October 2026 and no published DPA was found." ], "score": 91 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/lingo-dev.json", "live": { "slug": "lingo-dev", "probe": { "target": "https://mcp.lingo.dev/account", "method": "get", "lastAt": "2026-10-08T21:12:14.053179587Z", "lastOk": true, "lastStatus": 401, "lastMs": 707, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 958, "p95ms24h": 1336, "samples24h": 21, "samples30d": 21, "days": [ { "date": "2026-10-08", "probes": 21, "ok": 21 } ] }, "vendorStatus": { "page": "https://status.lingo.dev", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-08T19:38:45.164350131Z" }, "updatedAt": "2026-10-08T21:12:14.053179587Z" } }, "answer": "Lingo.dev scores 62.3 (B) on agent readiness against Lingvanex Translation API's 37 (F), and leads in every scored category.", "b": { "slug": "lingvanex", "name": "Lingvanex Translation API", "vendor": "Lingvanex", "vendorUrl": "https://lingvanex.com/products/translationapi/", "kind": "http-api", "category": "translation", "summary": "Cloud machine translation API for text and HTML in about 110 languages, with auto-detection and transliteration, from a vendor that also sells on-premise translation servers.", "url": "https://www.anchorterminal.com/tools/lingvanex", "markdownUrl": "https://www.anchorterminal.com/tools/lingvanex.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/lingvanex.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/lingvanex.json", "transports": [ "http" ], "remoteUrl": "https://api-b2b.backenster.com/b1/api/v3", "packages": [ { "registry": "pypi", "name": "lingvanex" } ], "auth": "api-key", "authNotes": "`Authorization: Bearer \u003ckey\u003e` header. The key comes from the account panel after you add a payment method.", "pricing": "usage", "pricingNotes": "$5 per million characters. The API product page gives $3 per million for a pre-purchase of 1 billion characters or more and on-premise servers from $200 a month (https://lingvanex.com/products/translationapi/). The text API page gives $1 per million above 20 million, and on-premise at $10 a day as well as from $200 a month (https://lingvanex.com/services/translate-text-api/). A free trial is advertised with no amount stated, and a payment method comes before the API key.", "priceSummary": "Pay per use", "where": "hosted", "x402": { "level": "no", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": 3, "asOf": "2026-09-30" }, "docsUrl": "https://docs.lingvanex.com/reference/overview", "openapi": "https://api.swaggerhub.com/apis/Lingvanex/lingvanex-b2b-api/1.0.0", "capabilities": [ "translate.text", "translate.detect" ], "tags": [ "hosted", "closed-source", "openapi", "python", "card-required" ], "graded": true, "anchor": { "graded": true, "score": 37, "grade": "F", "agentReady": false, "rank": 702, "ranked": true, "rankOf": 722, "categoryRank": 12, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 50, "maintenance": 6, "payments": 15, "reliability": 40, "schema": 48, "security": 37, "transparency": 48 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": 0, "verdict": "$5 per million characters list price. Product pages disagree on bulk and on-premise prices.", "bestFor": "Bulk translation of non-sensitive text where price per character matters most, or buyers who want an on-premise server later.", "strengths": [ "$5 per million characters list price", "OpenAPI 3.0.3 document on SwaggerHub", "HTML mode, string arrays and transliteration in one call", "Better Stack status page for the Cloud API", "On-premise servers from the same vendor" ], "weaknesses": [ "Product pages disagree on bulk and on-premise prices", "The product page, privacy policy and API terms disagree on how long text is kept", "No published rate limits, and the terms let Lingvanex set them at its discretion", "No glossary or formality parameters, and only 200 and 403 documented", "No changelog, and the Python SDK hasn't changed since June 2024" ], "agentNotes": [ "Call the https:// server, not the http:// one the spec also lists", "Send `platform` as api on every call, since the spec marks it required", "Use locale codes such as en_GB and de_DE, not two-letter codes", "Check the `err` field on every response, since errors aren't only signalled by status code", "Send an array in `data` to translate several strings in one call" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 2.5, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "F", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 37 } ], "editorialScores": { "ergonomics": 50, "maintenance": 6, "payments": 15, "reliability": 40, "schema": 48, "security": 37, "transparency": 38 }, "provenanceScore": 57 }, "connect": { "http": "curl -X POST https://api-b2b.backenster.com/b1/api/v3/translate -H \"Authorization: Bearer $LINGVANEX_API_KEY\" \\\n -H \"Content-Type: application/json\" \\\n -d '{\"platform\":\"api\",\"from\":\"en_GB\",\"to\":\"de_DE\",\"data\":\"Your table is booked for seven.\"}'" }, "letme": { "capability": "https://letme.dev/translate.text", "tool": "https://letme.dev/lingvanex" }, "area": "everyday", "unitPrices": [ { "item": "Cloud API", "unit": "1m-chars", "usd": 5 }, { "item": "Cloud API, 1 billion pre-purchase", "unit": "1m-chars", "usd": 3, "note": "Another page quotes $1 per million above 20 million" } ], "provenance": { "legalEntity": "Nordicwise Limited", "domain": "lingvanex.com", "domainRegistered": "2016-12-28", "domainNote": "The API endpoint is on backenster.com (registered 2016-12-13). Its RDAP record doesn't name Lingvanex.", "endpointOnVendorDomain": false, "terms": "https://lingvanex.com/terms-of-use-of-api-lingvanex-translation/", "privacy": "https://lingvanex.com/privacy-policy/", "statusPage": "https://status.lingvanex.com", "changelog": "", "securityTxt": "unknown", "checked": "2026-10-01", "notes": [ "The API terms give Nordicwise Limited, 52 1st April, 7600 Athienou, Larnaca, Cyprus.", "robots.txt blocked our fetch of lingvanex.com/.well-known/security.txt on the 30 September check.", "The developer docs on docs.lingvanex.com render only in a browser.", "status.lingvanex.com is a Better Stack page with one Cloud API component." ], "score": 57 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/lingvanex.json", "live": { "slug": "lingvanex", "probe": { "target": "https://api-b2b.backenster.com/b1/api/v3", "method": "get", "lastAt": "2026-10-08T21:12:14.097026557Z", "lastOk": true, "lastStatus": 403, "lastMs": 73, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 143, "p95ms24h": 206, "samples24h": 271, "samples30d": 1955, "days": [ { "date": "2026-10-01", "probes": 109, "ok": 109 }, { "date": "2026-10-02", "probes": 248, "ok": 248 }, { "date": "2026-10-03", "probes": 271, "ok": 271 }, { "date": "2026-10-04", "probes": 272, "ok": 272 }, { "date": "2026-10-05", "probes": 272, "ok": 272 }, { "date": "2026-10-06", "probes": 272, "ok": 272 }, { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 239, "ok": 239 } ] }, "vendorStatus": { "page": "https://status.lingvanex.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-08T19:38:45.24075776Z" }, "versions": [ { "registry": "pypi", "name": "lingvanex", "version": "0.0.11", "released": "2024-06-24", "seenAt": "2026-10-08T16:18:55.392831585Z" } ], "pypiWeekly": 7, "securityTxt": { "url": "https://lingvanex.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-08T15:39:07.52265725Z" }, "domain": { "domain": "lingvanex.com", "registered": "2016-12-28", "source": "https://rdap.verisign.com/com/v1/domain/lingvanex.com", "checkedAt": "2026-10-04T13:07:22.742489173Z" }, "pages": [ { "url": "https://lingvanex.com/privacy-policy/", "kind": "privacy", "status": 304, "checkedAt": "2026-10-08T18:21:35.53352143Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "3f9363e612b5" }, { "url": "https://lingvanex.com/terms-of-use-of-api-lingvanex-translation/", "kind": "terms", "status": 304, "checkedAt": "2026-10-08T18:21:37.657662455Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "500498c858ff" } ], "updatedAt": "2026-10-08T21:12:14.097026557Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Replexica, Inc.", "b": "Lingvanex", "name": "Vendor" }, { "a": "https://mcp.lingo.dev/account", "b": "https://api-b2b.backenster.com/b1/api/v3", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP", "b": "HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "API key", "name": "Auth" }, { "a": "Pay per use", "b": "Pay per use", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "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", "b": "none", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "no", "name": "llms.txt" }, { "a": "dev.lingo/main", "b": "not listed", "name": "MCP registry" }, { "a": "2026-10-07", "b": "none", "name": "Last release" }, { "a": "2026-05-07", "b": "no date given", "name": "Terms last updated" }, { "a": "2026-05-07", "b": "2026-05-01", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "5.4k stars, 92k npm/wk, 2k PyPI/wk", "b": "3 PyPI/wk", "name": "Popularity" }, { "a": "none", "b": "2.5/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "Lingo.dev scores 62.3 (B) on agent readiness against Lingvanex Translation API's 37 (F), and leads in every scored category.", "question": "Which is better for AI agents, Lingo.dev or Lingvanex Translation API?" }, { "answer": "Lingo.dev takes an API key or an OAuth sign-in. Lingvanex Translation API needs an API key.", "question": "Do Lingo.dev and Lingvanex Translation API need an API key?" }, { "answer": "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.", "question": "Can an agent call Lingo.dev and Lingvanex Translation API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 71 against 40", "Schema \u0026 documentation, 54 against 48", "Agent ergonomics, 75 against 50", "Security \u0026 auth, 62 against 37", "Payments \u0026 pricing, 20 against 15", "Maintenance \u0026 community, 87 against 6", "Transparency \u0026 trust, 71 against 48" ], "also": null, "goodFor": "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.", "slug": "lingo-dev", "watchFor": "No public OpenAPI file was found, `llms.txt` holds one title line and docs pages have no Markdown version" }, { "aheadOn": null, "also": null, "goodFor": "Bulk translation of non-sensitive text where price per character matters most, or buyers who want an on-premise server later.", "slug": "lingvanex", "watchFor": "Product pages disagree on bulk and on-premise prices" } ], "job": { "capability": "translate.text", "name": "Translate text" }, "others": [ { "json": "https://www.anchorterminal.com/compare/amazon-translate-vs-lingo-dev.json", "title": "Amazon Translate vs Lingo.dev", "url": "https://www.anchorterminal.com/compare/amazon-translate-vs-lingo-dev" }, { "json": "https://www.anchorterminal.com/compare/amazon-translate-vs-lingvanex.json", "title": "Amazon Translate vs Lingvanex Translation API", "url": "https://www.anchorterminal.com/compare/amazon-translate-vs-lingvanex" }, { "json": "https://www.anchorterminal.com/compare/azure-translator-vs-lingo-dev.json", "title": "Azure Translator vs Lingo.dev", "url": "https://www.anchorterminal.com/compare/azure-translator-vs-lingo-dev" }, { "json": "https://www.anchorterminal.com/compare/azure-translator-vs-lingvanex.json", "title": "Azure Translator vs Lingvanex Translation API", "url": "https://www.anchorterminal.com/compare/azure-translator-vs-lingvanex" }, { "json": "https://www.anchorterminal.com/compare/crowdin-vs-lingo-dev.json", "title": "Crowdin vs Lingo.dev", "url": "https://www.anchorterminal.com/compare/crowdin-vs-lingo-dev" }, { "json": "https://www.anchorterminal.com/compare/crowdin-vs-lingvanex.json", "title": "Crowdin vs Lingvanex Translation API", "url": "https://www.anchorterminal.com/compare/crowdin-vs-lingvanex" }, { "json": "https://www.anchorterminal.com/compare/deepl-api-vs-lingo-dev.json", "title": "DeepL API vs Lingo.dev", "url": "https://www.anchorterminal.com/compare/deepl-api-vs-lingo-dev" }, { "json": "https://www.anchorterminal.com/compare/deepl-api-vs-lingvanex.json", "title": "DeepL API vs Lingvanex Translation API", "url": "https://www.anchorterminal.com/compare/deepl-api-vs-lingvanex" }, { "json": "https://www.anchorterminal.com/compare/google-cloud-translation-vs-lingo-dev.json", "title": "Google Cloud Translation vs Lingo.dev", "url": "https://www.anchorterminal.com/compare/google-cloud-translation-vs-lingo-dev" }, { "json": "https://www.anchorterminal.com/compare/google-cloud-translation-vs-lingvanex.json", "title": "Google Cloud Translation vs Lingvanex Translation API", "url": "https://www.anchorterminal.com/compare/google-cloud-translation-vs-lingvanex" }, { "json": "https://www.anchorterminal.com/compare/lara-translate-vs-lingo-dev.json", "title": "Lara Translate API vs Lingo.dev", "url": "https://www.anchorterminal.com/compare/lara-translate-vs-lingo-dev" }, { "json": "https://www.anchorterminal.com/compare/lara-translate-vs-lingvanex.json", "title": "Lara Translate API vs Lingvanex Translation API", "url": "https://www.anchorterminal.com/compare/lara-translate-vs-lingvanex" }, { "json": "https://www.anchorterminal.com/compare/libretranslate-vs-lingo-dev.json", "title": "LibreTranslate vs Lingo.dev", "url": "https://www.anchorterminal.com/compare/libretranslate-vs-lingo-dev" }, { "json": "https://www.anchorterminal.com/compare/libretranslate-vs-lingvanex.json", "title": "LibreTranslate vs Lingvanex Translation API", "url": "https://www.anchorterminal.com/compare/libretranslate-vs-lingvanex" }, { "json": "https://www.anchorterminal.com/compare/lingo-dev-vs-lokalise.json", "title": "Lingo.dev vs Lokalise", "url": "https://www.anchorterminal.com/compare/lingo-dev-vs-lokalise" }, { "json": "https://www.anchorterminal.com/compare/lingo-dev-vs-phrase.json", "title": "Lingo.dev vs Phrase", "url": "https://www.anchorterminal.com/compare/lingo-dev-vs-phrase" }, { "json": "https://www.anchorterminal.com/compare/lingo-dev-vs-systran.json", "title": "Lingo.dev vs SYSTRAN Translate API", "url": "https://www.anchorterminal.com/compare/lingo-dev-vs-systran" }, { "json": "https://www.anchorterminal.com/compare/lingvanex-vs-lokalise.json", "title": "Lingvanex Translation API vs Lokalise", "url": "https://www.anchorterminal.com/compare/lingvanex-vs-lokalise" }, { "json": "https://www.anchorterminal.com/compare/lingvanex-vs-phrase.json", "title": "Lingvanex Translation API vs Phrase", "url": "https://www.anchorterminal.com/compare/lingvanex-vs-phrase" }, { "json": "https://www.anchorterminal.com/compare/lingvanex-vs-systran.json", "title": "Lingvanex Translation API vs SYSTRAN Translate API", "url": "https://www.anchorterminal.com/compare/lingvanex-vs-systran" } ], "scores": [ { "by": 31, "edge": "lingo-dev", "key": "reliability", "lingo-dev": 71, "lingvanex": 40, "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 6, "edge": "lingo-dev", "key": "schema", "lingo-dev": 54, "lingvanex": 48, "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 25, "edge": "lingo-dev", "key": "ergonomics", "lingo-dev": 75, "lingvanex": 50, "name": "Agent ergonomics", "weight": 13 }, { "by": 25, "edge": "lingo-dev", "key": "security", "lingo-dev": 62, "lingvanex": 37, "name": "Security \u0026 auth", "weight": 14 }, { "by": 5, "edge": "lingo-dev", "key": "payments", "lingo-dev": 20, "lingvanex": 15, "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 81, "edge": "lingo-dev", "key": "maintenance", "lingo-dev": 87, "lingvanex": 6, "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 23, "edge": "lingo-dev", "key": "transparency", "lingo-dev": 71, "lingvanex": 48, "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Lingo.dev scores 62.3 (B) on agent readiness against Lingvanex Translation API's 37 (F), and leads in every scored category. Both do translate text.", "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, its `llms.txt` is one line, and scoped keys, roles and audit logs are limited to the Enterprise plan.", "lingvanex": "$5 per million characters list price. Product pages disagree on bulk and on-premise prices." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/lingo-dev-vs-lingvanex", "json": "https://www.anchorterminal.com/compare/lingo-dev-vs-lingvanex.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/lingo-dev-vs-lingvanex.md", "slim": "https://www.anchorterminal.com/compare/lingo-dev-vs-lingvanex.min.md" }, "markdown": "Lingo.dev scores 62.3 (B) on agent readiness against Lingvanex Translation API's 37 (F), and leads in every scored category. Both do translate text.\n\n- Lingo.dev: grade B, 62.3/100, rank #341 of 722. Markdown https://www.anchorterminal.com/tools/lingo-dev.md · JSON https://www.anchorterminal.com/api/v1/tools/lingo-dev.json\n- Lingvanex Translation API: grade F, 37/100, rank #702 of 722. Markdown https://www.anchorterminal.com/tools/lingvanex.md · JSON https://www.anchorterminal.com/api/v1/tools/lingvanex.json\n\n## Which one, for what\n\n### Lingo.dev (B)\n\nGood 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.\n\nAhead on:\n- Reliability, 71 against 40\n- Schema \u0026 documentation, 54 against 48\n- Agent ergonomics, 75 against 50\n- Security \u0026 auth, 62 against 37\n- Payments \u0026 pricing, 20 against 15\n- Maintenance \u0026 community, 87 against 6\n- Transparency \u0026 trust, 71 against 48\n\nWatch for: No public OpenAPI file was found, `llms.txt` holds one title line and docs pages have no Markdown version\n\n### Lingvanex Translation API (F)\n\nGood for: Bulk translation of non-sensitive text where price per character matters most, or buyers who want an on-premise server later.\n\nWatch for: Product pages disagree on bulk and on-premise prices\n\n\n## Score by category\n\n| Category | Weight | Lingo.dev | Lingvanex Translation API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 71 | 40 | Lingo.dev +31 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 54 | 48 | Lingo.dev +6 |\n| Agent ergonomics | 13% (16.2 this run) | 75 | 50 | Lingo.dev +25 |\n| Security \u0026 auth | 14% (17.5 this run) | 62 | 37 | Lingo.dev +25 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 20 | 15 | Lingo.dev +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 87 | 6 | Lingo.dev +81 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 71 | 48 | Lingo.dev +23 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **62.3 · B** | **37 · F** | |\n\n## Facts side by side\n\n| Fact | Lingo.dev | Lingvanex Translation API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Replexica, Inc. | Lingvanex |\n| Hosted endpoint | `https://mcp.lingo.dev/account` | `https://api-b2b.backenster.com/b1/api/v3` |\n| Transports | HTTP, Streamable HTTP | HTTP |\n| Auth | OAuth or key | API key |\n| Pricing | Pay per use | Pay per use |\n| x402 | no | no |\n| 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 |\n| Read-only variant documented | no | no |\n| llms.txt | no | no |\n| MCP registry | `dev.lingo/main` | not listed |\n| Last release | 2026-10-07 | none |\n| Terms last updated | 2026-05-07 | no date given |\n| Privacy policy last updated | 2026-05-07 | 2026-05-01 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | yes | not found in the text |\n| Terms restrict benchmarking | not found in the text | not found in the text |\n| Terms or service can change without notice | yes | not found in the text |\n| Arbitration or class-action waiver | not found in the text | not found in the text |\n| Popularity | 5.4k stars, 92k npm/wk, 2k PyPI/wk | 3 PyPI/wk |\n| Agent reviews | none | 2.5/5 (2) |\n\n## Verdicts\n\n**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, its `llms.txt` is one line, and scoped keys, roles and audit logs are limited to the Enterprise plan.\n\n**Lingvanex Translation API.** $5 per million characters list price. Product pages disagree on bulk and on-premise prices.\n\n## Before you call either\n\n### Lingo.dev\n\n1. Send `X-API-Key` to https://api.lingo.dev and keep the key server-side. On non-Enterprise plans a personal key reaches every engine its creator can\n2. Use `POST /process/localize` for one language pair and `POST /jobs/localization` with an `idempotencyKey` for several. Pipeline stages run on async jobs only\n3. Treat 402 (credit limit) and 429 (daily token quota) as limits to report, not to retry. Retry 500 with backoff\n4. Read `usage.cost` on each sync response to track spend. Sandbox stops at 100,000 tokens a day\n5. 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\n\n### Lingvanex Translation API\n\n1. Call the https:// server, not the http:// one the spec also lists\n2. Send `platform` as api on every call, since the spec marks it required\n3. Use locale codes such as en_GB and de_DE, not two-letter codes\n4. Check the `err` field on every response, since errors aren't only signalled by status code\n5. Send an array in `data` to translate several strings in one call\n\n## Questions\n\n### Which is better for AI agents, Lingo.dev or Lingvanex Translation API?\n\nLingo.dev scores 62.3 (B) on agent readiness against Lingvanex Translation API's 37 (F), and leads in every scored category.\n\n### Do Lingo.dev and Lingvanex Translation API need an API key?\n\nLingo.dev takes an API key or an OAuth sign-in. Lingvanex Translation API needs an API key.\n\n### Can an agent call Lingo.dev and Lingvanex Translation API without installing anything?\n\nYes. 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.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/lingo-dev-vs-lingvanex.json, and with the fewest tokens: https://www.anchorterminal.com/compare/lingo-dev-vs-lingvanex.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"lingo-dev\", \"b\": \"lingvanex\"}`. From a terminal: `anchor compare lingo-dev lingvanex`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/lingo-dev.json and https://www.anchorterminal.com/api/v1/tools/lingvanex.json\n\n## Other comparisons with Lingo.dev or Lingvanex Translation API\n\n- [Amazon Translate vs Lingo.dev](https://www.anchorterminal.com/compare/amazon-translate-vs-lingo-dev.md)\n- [Amazon Translate vs Lingvanex Translation API](https://www.anchorterminal.com/compare/amazon-translate-vs-lingvanex.md)\n- [Azure Translator vs Lingo.dev](https://www.anchorterminal.com/compare/azure-translator-vs-lingo-dev.md)\n- [Azure Translator vs Lingvanex Translation API](https://www.anchorterminal.com/compare/azure-translator-vs-lingvanex.md)\n- [Crowdin vs Lingo.dev](https://www.anchorterminal.com/compare/crowdin-vs-lingo-dev.md)\n- [Crowdin vs Lingvanex Translation API](https://www.anchorterminal.com/compare/crowdin-vs-lingvanex.md)\n- [DeepL API vs Lingo.dev](https://www.anchorterminal.com/compare/deepl-api-vs-lingo-dev.md)\n- [DeepL API vs Lingvanex Translation API](https://www.anchorterminal.com/compare/deepl-api-vs-lingvanex.md)\n- [Google Cloud Translation vs Lingo.dev](https://www.anchorterminal.com/compare/google-cloud-translation-vs-lingo-dev.md)\n- [Google Cloud Translation vs Lingvanex Translation API](https://www.anchorterminal.com/compare/google-cloud-translation-vs-lingvanex.md)\n- [Lara Translate API vs Lingo.dev](https://www.anchorterminal.com/compare/lara-translate-vs-lingo-dev.md)\n- [Lara Translate API vs Lingvanex Translation API](https://www.anchorterminal.com/compare/lara-translate-vs-lingvanex.md)\n- [LibreTranslate vs Lingo.dev](https://www.anchorterminal.com/compare/libretranslate-vs-lingo-dev.md)\n- [LibreTranslate vs Lingvanex Translation API](https://www.anchorterminal.com/compare/libretranslate-vs-lingvanex.md)\n- [Lingo.dev vs Lokalise](https://www.anchorterminal.com/compare/lingo-dev-vs-lokalise.md)\n- [Lingo.dev vs Phrase](https://www.anchorterminal.com/compare/lingo-dev-vs-phrase.md)\n- [Lingo.dev vs SYSTRAN Translate API](https://www.anchorterminal.com/compare/lingo-dev-vs-systran.md)\n- [Lingvanex Translation API vs Lokalise](https://www.anchorterminal.com/compare/lingvanex-vs-lokalise.md)\n- [Lingvanex Translation API vs Phrase](https://www.anchorterminal.com/compare/lingvanex-vs-phrase.md)\n- [Lingvanex Translation API vs SYSTRAN Translate API](https://www.anchorterminal.com/compare/lingvanex-vs-systran.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-08", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Lingo.dev vs Lingvanex Translation API", "url": "" } ], "description": "Lingo.dev scores 62.3 (B) on agent readiness against Lingvanex Translation API's 37 (F), and leads in every scored category. Both do translate text. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "Lingo.dev B 62.3", "Lingvanex Translation API F 37", "scores" ], "h1": "Lingo.dev vs Lingvanex Translation API", "image": "https://www.anchorterminal.com/assets/og/compare-lingo-dev-vs-lingvanex.png", "path": "/compare/lingo-dev-vs-lingvanex", "published": "2026-10-01", "section": "tools", "title": "Lingo.dev vs Lingvanex Translation API for AI agents, B 62.3 vs F 37", "toc": null, "updated": "2026-10-08", "url": "https://www.anchorterminal.com/compare/lingo-dev-vs-lingvanex" }, "tokens": { "markdown": 2300, "slim": 730 }, "version": 1 }