{ "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": "Lokalise scores 71.3 (BB) on agent readiness against Lingo.dev's 62.3 (B), and leads in 5 of 7 scored categories. Lingo.dev leads on agent ergonomics.", "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": "Replexica, Inc.", "b": "Lokalise, Inc.", "name": "Vendor" }, { "a": "https://mcp.lingo.dev/account", "b": "https://api.lokalise.com/api2", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth or key", "name": "Auth" }, { "a": "Pay per use", "b": "Paid", "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": "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": "dev.lingo/main", "b": "not listed", "name": "MCP registry" }, { "a": "2026-10-07", "b": "2026-10-05", "name": "Last release" }, { "a": "2026-05-07", "b": "2025-11-01", "name": "Terms last updated" }, { "a": "2026-05-07", "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": "yes", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "yes", "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": "124 stars, 338k npm/wk, 39k PyPI/wk", "name": "Popularity" } ], "faq": [ { "answer": "Lokalise scores 71.3 (BB) on agent readiness against Lingo.dev's 62.3 (B), and leads in 5 of 7 scored categories. Lingo.dev leads on agent ergonomics.", "question": "Which is better for AI agents, Lingo.dev or Lokalise?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do Lingo.dev and Lokalise need an API key?" }, { "answer": "Yes. Lingo.dev has a hosted endpoint at https://mcp.lingo.dev/account and Lokalise at https://api.lokalise.com/api2.", "question": "Can an agent call Lingo.dev and Lokalise without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Agent ergonomics, 75 against 69" ], "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": [ "Reliability, 84 against 71", "Schema \u0026 documentation, 76 against 54", "Security \u0026 auth, 73 against 62", "Payments \u0026 pricing, 30 against 20", "Transparency \u0026 trust, 81 against 71" ], "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-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-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-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-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-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-lokalise.json", "title": "Crowdin vs Lokalise", "url": "https://www.anchorterminal.com/compare/crowdin-vs-lokalise" }, { "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-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-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-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-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-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-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-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-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/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": 13, "edge": "lokalise", "key": "reliability", "lingo-dev": 71, "lokalise": 84, "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 22, "edge": "lokalise", "key": "schema", "lingo-dev": 54, "lokalise": 76, "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 6, "edge": "lingo-dev", "key": "ergonomics", "lingo-dev": 75, "lokalise": 69, "name": "Agent ergonomics", "weight": 13 }, { "by": 11, "edge": "lokalise", "key": "security", "lingo-dev": 62, "lokalise": 73, "name": "Security \u0026 auth", "weight": 14 }, { "by": 10, "edge": "lokalise", "key": "payments", "lingo-dev": 20, "lokalise": 30, "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 3, "edge": "lingo-dev", "key": "maintenance", "lingo-dev": 87, "lokalise": 84, "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 10, "edge": "lokalise", "key": "transparency", "lingo-dev": 71, "lokalise": 81, "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Lokalise scores 71.3 (BB) on agent readiness against Lingo.dev's 62.3 (B), and leads in 5 of 7 scored categories. Lingo.dev leads on agent ergonomics. 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.", "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/lingo-dev-vs-lokalise", "json": "https://www.anchorterminal.com/compare/lingo-dev-vs-lokalise.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/lingo-dev-vs-lokalise.md", "slim": "https://www.anchorterminal.com/compare/lingo-dev-vs-lokalise.min.md" }, "markdown": "Lokalise scores 71.3 (BB) on agent readiness against Lingo.dev's 62.3 (B), and leads in 5 of 7 scored categories. Lingo.dev leads on agent ergonomics. 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- 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### 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- Agent ergonomics, 75 against 69\n\nWatch for: No public OpenAPI file was found, `llms.txt` holds one title line and docs pages have no Markdown version\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 71\n- Schema \u0026 documentation, 76 against 54\n- Security \u0026 auth, 73 against 62\n- Payments \u0026 pricing, 30 against 20\n- Transparency \u0026 trust, 81 against 71\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 | Lingo.dev | Lokalise | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 71 | 84 | Lokalise +13 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 54 | 76 | Lokalise +22 |\n| Agent ergonomics | 13% (16.2 this run) | 75 | 69 | Lingo.dev +6 |\n| Security \u0026 auth | 14% (17.5 this run) | 62 | 73 | Lokalise +11 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 20 | 30 | Lokalise +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 87 | 84 | Lingo.dev +3 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 71 | 81 | Lokalise +10 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **62.3 · B** | **71.3 · BB** | |\n\n## Facts side by side\n\n| Fact | Lingo.dev | Lokalise |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Replexica, Inc. | Lokalise, Inc. |\n| Hosted endpoint | `https://mcp.lingo.dev/account` | `https://api.lokalise.com/api2` |\n| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Pay per use | Paid |\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 | 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| MCP registry | `dev.lingo/main` | not listed |\n| Last release | 2026-10-07 | 2026-10-05 |\n| Terms last updated | 2026-05-07 | 2025-11-01 |\n| Privacy policy last updated | 2026-05-07 | 2026-03-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 | yes |\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 | 124 stars, 338k npm/wk, 39k PyPI/wk |\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**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### 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### 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, Lingo.dev or Lokalise?\n\nLokalise scores 71.3 (BB) on agent readiness against Lingo.dev's 62.3 (B), and leads in 5 of 7 scored categories. Lingo.dev leads on agent ergonomics.\n\n### Do Lingo.dev and Lokalise need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call Lingo.dev and Lokalise without installing anything?\n\nYes. Lingo.dev has a hosted endpoint at https://mcp.lingo.dev/account and Lokalise at https://api.lokalise.com/api2.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/lingo-dev-vs-lokalise.json, and with the fewest tokens: https://www.anchorterminal.com/compare/lingo-dev-vs-lokalise.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"lingo-dev\", \"b\": \"lokalise\"}`. From a terminal: `anchor compare lingo-dev lokalise`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/lingo-dev.json and https://www.anchorterminal.com/api/v1/tools/lokalise.json\n\n## Other comparisons with Lingo.dev or Lokalise\n\n- [Amazon Translate vs Lingo.dev](https://www.anchorterminal.com/compare/amazon-translate-vs-lingo-dev.md)\n- [Amazon Translate vs Lokalise](https://www.anchorterminal.com/compare/amazon-translate-vs-lokalise.md)\n- [Azure Translator vs Lingo.dev](https://www.anchorterminal.com/compare/azure-translator-vs-lingo-dev.md)\n- [Azure Translator vs Lokalise](https://www.anchorterminal.com/compare/azure-translator-vs-lokalise.md)\n- [Crowdin vs Lingo.dev](https://www.anchorterminal.com/compare/crowdin-vs-lingo-dev.md)\n- [Crowdin vs Lokalise](https://www.anchorterminal.com/compare/crowdin-vs-lokalise.md)\n- [DeepL API vs Lingo.dev](https://www.anchorterminal.com/compare/deepl-api-vs-lingo-dev.md)\n- [DeepL API vs Lokalise](https://www.anchorterminal.com/compare/deepl-api-vs-lokalise.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 Lokalise](https://www.anchorterminal.com/compare/google-cloud-translation-vs-lokalise.md)\n- [Lara Translate API vs Lingo.dev](https://www.anchorterminal.com/compare/lara-translate-vs-lingo-dev.md)\n- [Lara Translate API vs Lokalise](https://www.anchorterminal.com/compare/lara-translate-vs-lokalise.md)\n- [LibreTranslate vs Lingo.dev](https://www.anchorterminal.com/compare/libretranslate-vs-lingo-dev.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 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- [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": "Lingo.dev vs Lokalise", "url": "" } ], "description": "Lokalise scores 71.3 (BB) on agent readiness against Lingo.dev's 62.3 (B), and leads in 5 of 7 scored categories. Lingo.dev leads on agent ergonomics. Both do translate text. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "Lingo.dev B 62.3", "Lokalise BB 71.3", "scores" ], "h1": "Lingo.dev vs Lokalise", "image": "https://www.anchorterminal.com/assets/og/compare-lingo-dev-vs-lokalise.png", "path": "/compare/lingo-dev-vs-lokalise", "published": "2026-10-01", "section": "tools", "title": "Lingo.dev vs Lokalise for AI agents, B 62.3 vs BB 71.3", "toc": null, "updated": "2026-10-08", "url": "https://www.anchorterminal.com/compare/lingo-dev-vs-lokalise" }, "tokens": { "markdown": 2450, "slim": 780 }, "version": 1 }