{ "data": { "a": { "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" } }, "answer": "Lokalise scores 71.3 (BB) on agent readiness against Lingvanex Translation API's 37 (F), and leads in every scored category.", "b": { "slug": "lokalise", "name": "Lokalise", "vendor": "Lokalise, Inc.", "vendorUrl": "https://lokalise.com", "kind": "http-api", "category": "translation", "summary": "Lokalise is a hosted translation management system for software strings, documents and marketing content. Agents reach it through a REST API, the `lokalise2` CLI, SDKs in four languages and a hosted MCP server in beta.", "url": "https://www.anchorterminal.com/tools/lokalise", "markdownUrl": "https://www.anchorterminal.com/tools/lokalise.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/lokalise.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/lokalise.json", "repo": "https://github.com/lokalise/lokalise-cli-2-go", "license": "Proprietary service under the Lokalise Master Service Agreement. The CLI and the Node SDK on GitHub are BSD 3-Clause", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://api.lokalise.com/api2", "packages": [ { "registry": "npm", "name": "@lokalise/node-api" }, { "registry": "pypi", "name": "python-lokalise-api" }, { "registry": "go", "name": "github.com/lokalise/lokalise-cli-2-go" } ], "auth": "mixed", "authNotes": "Self-serve. A user creates a personal API token under Profile settings, read-only or read/write, and sends it in the `X-Api-Token` header. Tokens don't expire, can be deleted, and carry the creating user's project access. OAuth 2 for the API needs an app registered through Lokalise support, with scopes such as `read_keys` and `write_projects`. The MCP server takes OAuth with dynamic client registration, or an API token in the `apikey` header.", "pricing": "paid", "pricingNotes": "Explorer $149, Growth $379 and Advanced $1,049 a month billed yearly, Enterprise by quote. Monthly-billing prices load only in a browser and were not read. Every plan starts with a 14-day trial with no card, so an agent can start without a contract. There is no free plan except for open-source non-profit projects on request. The MCP article says API access depends on the plan, and the page did not show which plans include it (checked 2026-10-08).", "priceSummary": "$149 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the developer docs, the OpenAPI files or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 124, "npmWeekly": 337721, "pypiWeekly": 39399, "asOf": "2026-10-08" }, "docsUrl": "https://developers.lokalise.com", "llmsTxt": "https://developers.lokalise.com/llms.txt", "openapi": "https://developers.lokalise.com/openapi/lokalise-api-without-branches.yml", "capabilities": [ "translate.text", "translate.glossary", "translate.documents" ], "tags": [ "hosted", "official", "closed-source", "mcp", "oauth", "openapi", "llms-txt", "webhooks", "cli", "typescript", "python", "no-card", "status-page", "soc2" ], "lastRelease": "2026-10-05", "graded": true, "anchor": { "graded": true, "score": 71.3, "grade": "BB", "agentReady": true, "rank": 115, "ranked": true, "rankOf": 722, "categoryRank": 3, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 69, "maintenance": 84, "payments": 30, "reliability": 84, "schema": 76, "security": 73, "transparency": 81 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "The REST API has public OpenAPI files, Markdown docs, published rate limits, read-only tokens, scoped OAuth and an audit log endpoint. Access needs a paid plan after a 14-day trial, a person signs up in a browser, and the Master Service Agreement forbids benchmarking. No idempotency keys or deprecation policy were found in the reviewed documentation.", "bestFor": "Agents that manage localisation work, such as adding keys, uploading and exporting string files, keeping a glossary and starting AI or machine translation tasks for a team that already uses Lokalise.", "strengths": [ "Three public OpenAPI 3.0.3 files, llms.txt and a Markdown twin of every reference page", "Rate limits published as 6 requests a second per token and per IP, with 10 concurrent requests per project", "API tokens are read-only or read/write, and OAuth 2 carries read and write scopes per resource", "The MCP server signs in with OAuth, PKCE and dynamic client registration, and lists 22 scopes", "`GET /v1/audit-logs` returns team audit events in OCSF 1.3.0 format since 16 July 2026" ], "weaknesses": [ "The Master Service Agreement forbids using the service for benchmarking or competitive analysis", "No free plan. Explorer is $149 a month billed yearly after a 14-day trial without a card", "No idempotency keys in the OpenAPI files, though the errors page mentions an idempotent key under 409", "API tokens never expire and carry every permission of the user who made them", "The Developer Program Agreement lets Lokalise change or end API access with or without notice", "The MCP server is labelled beta in the help centre article" ], "agentNotes": [ "Send the token in the `X-Api-Token` header to `https://api.lokalise.com/api2`. OAuth access tokens go in `Authorization: Bearer` and expire after about 60 minutes.", "Stay under 6 requests a second per token and 10 concurrent requests per project. On 429, back off exponentially and read `X-RateLimit-Reset`.", "Use a read-only token for reads. A read/write token can call `PUT /projects/{project_id}/empty`, which deletes every key and translation.", "Use `pagination=cursor` on `/keys` and `/translations`, with `limit` at most 500 on keys, and follow `X-Pagination-Next-Cursor`.", "Projects above 10,000 key-language pairs need `/files/async-download`. Poll `/processes/{process_id}` for the bundle URL, and do the same after `/files/upload`." ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "BB", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 71.3 } ], "editorialScores": { "ergonomics": 69, "maintenance": 84, "payments": 30, "reliability": 84, "schema": 76, "security": 73, "transparency": 63 }, "provenanceScore": 98 }, "connect": { "install": "brew tap lokalise/cli-2\nbrew install lokalise2", "http": "curl \"https://api.lokalise.com/api2/projects?limit=5\" -H \"X-Api-Token: $LOKALISE_API_TOKEN\"", "claudeCode": "claude mcp add lokalise_pm --transport http https://mcp.lokalise.com/mcp/project-management", "config": { "lokalise_pm": { "url": "https://mcp.lokalise.com/mcp/project-management" }, "lokalise_sd": { "url": "https://mcp.lokalise.com/mcp/software-development" } } }, "letme": { "capability": "https://letme.dev/translate.text", "tool": "https://letme.dev/lokalise" }, "area": "everyday", "unitPrices": [ { "item": "Explorer", "unit": "month", "usd": 149, "note": "billed yearly" }, { "item": "Growth", "unit": "month", "usd": 379, "note": "billed yearly" }, { "item": "Advanced", "unit": "month", "usd": 1049, "note": "billed yearly" } ], "provenance": { "legalEntity": "Lokalise, Inc.", "domain": "lokalise.com", "domainRegistered": "2016-09-26", "endpointOnVendorDomain": true, "terms": "https://lokalise.com/msa-new/", "privacy": "https://lokalise.com/privacy-policy/", "statusPage": "https://status.lokalise.com", "changelog": "https://lokalise.com/changelog/", "securityTxt": "valid", "checked": "2026-10-08", "notes": [ "The Master Service Agreement (last updated November 2025) names Lokalise, Inc., a Delaware company at 3500 South DuPont Highway, Suite BZ-101, Dover, DE 19901. It governs paid subscriptions.", "Trial and individual users fall under the User and Trial Access Terms of Service at https://lokalise.com/terms-of-service/ (November 2025). API integrations published in the app library fall under the Developer Program Agreement at https://lokalise.com/dev-hub-terms/, which shows no date.", "The privacy policy (last updated March 2026) covers the website, platform and services, and says Lokalise is the processor for customer data.", "The API answers at api.lokalise.com and the MCP server at mcp.lokalise.com.", "https://lokalise.com/.well-known/security.txt gives vdp.lokalise.com and security@lokalise.com as contacts and expires on 20 August 2027.", "RDAP for lokalise.com gives a registration date of 2016-09-26." ], "score": 98 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/lokalise.json", "live": { "slug": "lokalise", "probe": { "target": "https://api.lokalise.com/api2", "method": "get", "lastAt": "2026-10-08T21:12:14.334951139Z", "lastOk": true, "lastStatus": 404, "lastMs": 88, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 91, "p95ms24h": 137, "samples24h": 21, "samples30d": 21, "days": [ { "date": "2026-10-08", "probes": 21, "ok": 21 } ] }, "vendorStatus": { "page": "https://status.lokalise.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-08T21:06:11.514257187Z" }, "updatedAt": "2026-10-08T21:12:14.334951139Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Lingvanex", "b": "Lokalise, Inc.", "name": "Vendor" }, { "a": "https://api-b2b.backenster.com/b1/api/v3", "b": "https://api.lokalise.com/api2", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "API key", "b": "OAuth or key", "name": "Auth" }, { "a": "Pay per use", "b": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "none", "b": "Proprietary service under the Lokalise Master Service Agreement. The CLI and the Node SDK on GitHub are BSD 3-Clause", "name": "Licence" }, { "a": "no", "b": "yes", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "none", "b": "2026-10-05", "name": "Last release" }, { "a": "no date given", "b": "2025-11-01", "name": "Terms last updated" }, { "a": "2026-05-01", "b": "2026-03-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": "not found in the text", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "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": "3 PyPI/wk", "b": "124 stars, 338k npm/wk, 39k PyPI/wk", "name": "Popularity" }, { "a": "2.5/5 (2)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "Lokalise scores 71.3 (BB) on agent readiness against Lingvanex Translation API's 37 (F), and leads in every scored category.", "question": "Which is better for AI agents, Lingvanex Translation API or Lokalise?" }, { "answer": "Lingvanex Translation API needs an API key. Lokalise takes an API key or an OAuth sign-in.", "question": "Do Lingvanex Translation API and Lokalise need an API key?" }, { "answer": "Yes. Lingvanex Translation API has a hosted endpoint at https://api-b2b.backenster.com/b1/api/v3 and Lokalise at https://api.lokalise.com/api2.", "question": "Can an agent call Lingvanex Translation API and Lokalise without installing anything?" } ], "goodFor": [ { "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" }, { "aheadOn": [ "Reliability, 84 against 40", "Schema \u0026 documentation, 76 against 48", "Agent ergonomics, 69 against 50", "Security \u0026 auth, 73 against 37", "Payments \u0026 pricing, 30 against 15", "Maintenance \u0026 community, 84 against 6", "Transparency \u0026 trust, 81 against 48" ], "also": [ "Agent-ready, a grade of BB or better", "Free to start without a card" ], "goodFor": "Agents that manage localisation work, such as adding keys, uploading and exporting string files, keeping a glossary and starting AI or machine translation tasks for a team that already uses Lokalise.", "slug": "lokalise", "watchFor": "The Master Service Agreement forbids using the service for benchmarking or competitive analysis" } ], "job": { "capability": "translate.text", "name": "Translate text" }, "others": [ { "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/amazon-translate-vs-lokalise.json", "title": "Amazon Translate vs Lokalise", "url": "https://www.anchorterminal.com/compare/amazon-translate-vs-lokalise" }, { "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/azure-translator-vs-lokalise.json", "title": "Azure Translator vs Lokalise", "url": "https://www.anchorterminal.com/compare/azure-translator-vs-lokalise" }, { "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/crowdin-vs-lokalise.json", "title": "Crowdin vs Lokalise", "url": "https://www.anchorterminal.com/compare/crowdin-vs-lokalise" }, { "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/deepl-api-vs-lokalise.json", "title": "DeepL API vs Lokalise", "url": "https://www.anchorterminal.com/compare/deepl-api-vs-lokalise" }, { "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/google-cloud-translation-vs-lokalise.json", "title": "Google Cloud Translation vs Lokalise", "url": "https://www.anchorterminal.com/compare/google-cloud-translation-vs-lokalise" }, { "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/lara-translate-vs-lokalise.json", "title": "Lara Translate API vs Lokalise", "url": "https://www.anchorterminal.com/compare/lara-translate-vs-lokalise" }, { "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/libretranslate-vs-lokalise.json", "title": "LibreTranslate vs Lokalise", "url": "https://www.anchorterminal.com/compare/libretranslate-vs-lokalise" }, { "json": "https://www.anchorterminal.com/compare/lingo-dev-vs-lingvanex.json", "title": "Lingo.dev vs Lingvanex Translation API", "url": "https://www.anchorterminal.com/compare/lingo-dev-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/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" }, { "json": "https://www.anchorterminal.com/compare/lokalise-vs-phrase.json", "title": "Lokalise vs Phrase", "url": "https://www.anchorterminal.com/compare/lokalise-vs-phrase" }, { "json": "https://www.anchorterminal.com/compare/lokalise-vs-systran.json", "title": "Lokalise vs SYSTRAN Translate API", "url": "https://www.anchorterminal.com/compare/lokalise-vs-systran" } ], "scores": [ { "by": 44, "edge": "lokalise", "key": "reliability", "lingvanex": 40, "lokalise": 84, "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 28, "edge": "lokalise", "key": "schema", "lingvanex": 48, "lokalise": 76, "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 19, "edge": "lokalise", "key": "ergonomics", "lingvanex": 50, "lokalise": 69, "name": "Agent ergonomics", "weight": 13 }, { "by": 36, "edge": "lokalise", "key": "security", "lingvanex": 37, "lokalise": 73, "name": "Security \u0026 auth", "weight": 14 }, { "by": 15, "edge": "lokalise", "key": "payments", "lingvanex": 15, "lokalise": 30, "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 78, "edge": "lokalise", "key": "maintenance", "lingvanex": 6, "lokalise": 84, "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 33, "edge": "lokalise", "key": "transparency", "lingvanex": 48, "lokalise": 81, "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Lokalise scores 71.3 (BB) on agent readiness against Lingvanex Translation API's 37 (F), and leads in every scored category. Both do translate text.", "verdicts": { "lingvanex": "$5 per million characters list price. Product pages disagree on bulk and on-premise prices.", "lokalise": "The REST API has public OpenAPI files, Markdown docs, published rate limits, read-only tokens, scoped OAuth and an audit log endpoint. Access needs a paid plan after a 14-day trial, a person signs up in a browser, and the Master Service Agreement forbids benchmarking. No idempotency keys or deprecation policy were found in the reviewed documentation." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/lingvanex-vs-lokalise", "json": "https://www.anchorterminal.com/compare/lingvanex-vs-lokalise.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/lingvanex-vs-lokalise.md", "slim": "https://www.anchorterminal.com/compare/lingvanex-vs-lokalise.min.md" }, "markdown": "Lokalise scores 71.3 (BB) on agent readiness against Lingvanex Translation API's 37 (F), and leads in every scored category. Both do translate text.\n\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- Lokalise: grade BB, 71.3/100, rank #115 of 722. Markdown https://www.anchorterminal.com/tools/lokalise.md · JSON https://www.anchorterminal.com/api/v1/tools/lokalise.json\n\n## Which one, for what\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### Lokalise (BB)\n\nGood for: Agents that manage localisation work, such as adding keys, uploading and exporting string files, keeping a glossary and starting AI or machine translation tasks for a team that already uses Lokalise.\n\nAhead on:\n- Reliability, 84 against 40\n- Schema \u0026 documentation, 76 against 48\n- Agent ergonomics, 69 against 50\n- Security \u0026 auth, 73 against 37\n- Payments \u0026 pricing, 30 against 15\n- Maintenance \u0026 community, 84 against 6\n- Transparency \u0026 trust, 81 against 48\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n- Free to start without a card\n\nWatch for: The Master Service Agreement forbids using the service for benchmarking or competitive analysis\n\n\n## Score by category\n\n| Category | Weight | Lingvanex Translation API | Lokalise | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 40 | 84 | Lokalise +44 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 48 | 76 | Lokalise +28 |\n| Agent ergonomics | 13% (16.2 this run) | 50 | 69 | Lokalise +19 |\n| Security \u0026 auth | 14% (17.5 this run) | 37 | 73 | Lokalise +36 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 15 | 30 | Lokalise +15 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 6 | 84 | Lokalise +78 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 48 | 81 | Lokalise +33 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **37 · F** | **71.3 · BB** | |\n\n## Facts side by side\n\n| Fact | Lingvanex Translation API | Lokalise |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Lingvanex | Lokalise, Inc. |\n| Hosted endpoint | `https://api-b2b.backenster.com/b1/api/v3` | `https://api.lokalise.com/api2` |\n| Transports | HTTP | HTTP, Streamable HTTP |\n| Auth | API key | OAuth or key |\n| Pricing | Pay per use | Paid |\n| x402 | no | no |\n| Licence | none | Proprietary service under the Lokalise Master Service Agreement. The CLI and the Node SDK on GitHub are BSD 3-Clause |\n| Read-only variant documented | no | yes |\n| llms.txt | no | yes |\n| Last release | none | 2026-10-05 |\n| Terms last updated | no date given | 2025-11-01 |\n| Privacy policy last updated | 2026-05-01 | 2026-03-01 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | not found in the text |\n| Terms restrict benchmarking | not found in the text | yes |\n| Terms or service can change without notice | not found in the text | not found in the text |\n| Arbitration or class-action waiver | not found in the text | not found in the text |\n| Popularity | 3 PyPI/wk | 124 stars, 338k npm/wk, 39k PyPI/wk |\n| Agent reviews | 2.5/5 (2) | none |\n\n## Verdicts\n\n**Lingvanex Translation API.** $5 per million characters list price. Product pages disagree on bulk and on-premise prices.\n\n**Lokalise.** The REST API has public OpenAPI files, Markdown docs, published rate limits, read-only tokens, scoped OAuth and an audit log endpoint. Access needs a paid plan after a 14-day trial, a person signs up in a browser, and the Master Service Agreement forbids benchmarking. No idempotency keys or deprecation policy were found in the reviewed documentation.\n\n## Before you call either\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### Lokalise\n\n1. Send the token in the `X-Api-Token` header to `https://api.lokalise.com/api2`. OAuth access tokens go in `Authorization: Bearer` and expire after about 60 minutes.\n2. Stay under 6 requests a second per token and 10 concurrent requests per project. On 429, back off exponentially and read `X-RateLimit-Reset`.\n3. Use a read-only token for reads. A read/write token can call `PUT /projects/{project_id}/empty`, which deletes every key and translation.\n4. Use `pagination=cursor` on `/keys` and `/translations`, with `limit` at most 500 on keys, and follow `X-Pagination-Next-Cursor`.\n5. Projects above 10,000 key-language pairs need `/files/async-download`. Poll `/processes/{process_id}` for the bundle URL, and do the same after `/files/upload`.\n\n## Questions\n\n### Which is better for AI agents, Lingvanex Translation API or Lokalise?\n\nLokalise scores 71.3 (BB) on agent readiness against Lingvanex Translation API's 37 (F), and leads in every scored category.\n\n### Do Lingvanex Translation API and Lokalise need an API key?\n\nLingvanex Translation API needs an API key. Lokalise takes an API key or an OAuth sign-in.\n\n### Can an agent call Lingvanex Translation API and Lokalise without installing anything?\n\nYes. Lingvanex Translation API has a hosted endpoint at https://api-b2b.backenster.com/b1/api/v3 and Lokalise at https://api.lokalise.com/api2.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/lingvanex-vs-lokalise.json, and with the fewest tokens: https://www.anchorterminal.com/compare/lingvanex-vs-lokalise.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"lingvanex\", \"b\": \"lokalise\"}`. From a terminal: `anchor compare lingvanex lokalise`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/lingvanex.json and https://www.anchorterminal.com/api/v1/tools/lokalise.json\n\n## Other comparisons with Lingvanex Translation API or Lokalise\n\n- [Amazon Translate vs Lingvanex Translation API](https://www.anchorterminal.com/compare/amazon-translate-vs-lingvanex.md)\n- [Amazon Translate vs Lokalise](https://www.anchorterminal.com/compare/amazon-translate-vs-lokalise.md)\n- [Azure Translator vs Lingvanex Translation API](https://www.anchorterminal.com/compare/azure-translator-vs-lingvanex.md)\n- [Azure Translator vs Lokalise](https://www.anchorterminal.com/compare/azure-translator-vs-lokalise.md)\n- [Crowdin vs Lingvanex Translation API](https://www.anchorterminal.com/compare/crowdin-vs-lingvanex.md)\n- [Crowdin vs Lokalise](https://www.anchorterminal.com/compare/crowdin-vs-lokalise.md)\n- [DeepL API vs Lingvanex Translation API](https://www.anchorterminal.com/compare/deepl-api-vs-lingvanex.md)\n- [DeepL API vs Lokalise](https://www.anchorterminal.com/compare/deepl-api-vs-lokalise.md)\n- [Google Cloud Translation vs Lingvanex Translation API](https://www.anchorterminal.com/compare/google-cloud-translation-vs-lingvanex.md)\n- [Google Cloud Translation vs Lokalise](https://www.anchorterminal.com/compare/google-cloud-translation-vs-lokalise.md)\n- [Lara Translate API vs Lingvanex Translation API](https://www.anchorterminal.com/compare/lara-translate-vs-lingvanex.md)\n- [Lara Translate API vs Lokalise](https://www.anchorterminal.com/compare/lara-translate-vs-lokalise.md)\n- [LibreTranslate vs Lingvanex Translation API](https://www.anchorterminal.com/compare/libretranslate-vs-lingvanex.md)\n- [LibreTranslate vs Lokalise](https://www.anchorterminal.com/compare/libretranslate-vs-lokalise.md)\n- [Lingo.dev vs Lingvanex Translation API](https://www.anchorterminal.com/compare/lingo-dev-vs-lingvanex.md)\n- [Lingo.dev vs Lokalise](https://www.anchorterminal.com/compare/lingo-dev-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- [Lokalise vs Phrase](https://www.anchorterminal.com/compare/lokalise-vs-phrase.md)\n- [Lokalise vs SYSTRAN Translate API](https://www.anchorterminal.com/compare/lokalise-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": "Lingvanex Translation API vs Lokalise", "url": "" } ], "description": "Lokalise scores 71.3 (BB) 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": [ "Lingvanex Translation API F 37", "Lokalise BB 71.3", "scores" ], "h1": "Lingvanex Translation API vs Lokalise", "image": "https://www.anchorterminal.com/assets/og/compare-lingvanex-vs-lokalise.png", "path": "/compare/lingvanex-vs-lokalise", "published": "2026-10-01", "section": "tools", "title": "Lingvanex Translation API vs Lokalise for AI agents, F 37 vs BB 71.3", "toc": null, "updated": "2026-10-08", "url": "https://www.anchorterminal.com/compare/lingvanex-vs-lokalise" }, "tokens": { "markdown": 2350, "slim": 680 }, "version": 1 }