{ "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", "dns": "lingo-dev.grade.anchorterminal.com", "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-30", "graded": true, "anchor": { "graded": true, "score": 66.1, "grade": "B", "agentReady": false, "rank": 382, "ranked": true, "rankOf": 1510, "categoryRank": 8, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 75, "maintenance": 87, "payments": 20, "reliability": 81, "schema": 64, "security": 62, "transparency": 72 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-02" }, "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, 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, an `llms.txt` docs index and an OpenStatus page with incident history" ], "weaknesses": [ "No public OpenAPI file was found, docs pages have no Markdown version and error bodies carry only a free-text `message`", "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 new `@lingo.dev/cli` package has no public source and depends on `posthog-node`, and the older CLI sends usage events unless `DO_NOT_TRACK=1` is set", "No machine-readable error code and no `Retry-After` documented on 429 or 402 answers", "The privacy policy points to lingo.dev/security for sub-processors, and that page redirected to a 404 page on 2 November 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": 4, "avgRating": 3.3, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 66.1 } ], "editorialScores": { "ergonomics": 75, "maintenance": 87, "payments": 20, "reliability": 81, "schema": 64, "security": 62, "transparency": 51 }, "provenanceScore": 92, "checked": { "categories": { "ergonomics": "2026-11-02", "maintenance": "2026-11-02", "payments": "2026-11-02", "reliability": "2026-11-02", "schema": "2026-11-02", "security": "2026-11-02", "transparency": "2026-11-02" }, "last": "2026-11-02", "lastMoved": "2026-11-02", "oldest": "2026-11-02", "stale": false, "staleAfterDays": 90 } }, "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": 92 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/lingo-dev.json", "live": { "slug": "lingo-dev", "probe": { "target": "https://mcp.lingo.dev/account", "method": "get", "lastAt": "2026-11-07T22:56:06.084464117Z", "lastOk": true, "lastStatus": 401, "lastMs": 1705, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 907, "p95ms24h": 1705, "samples24h": 244, "samples30d": 7466, "days": [ { "date": "2026-10-08", "probes": 50, "ok": 50 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 249, "ok": 249 }, { "date": "2026-10-15", "probes": 253, "ok": 253 }, { "date": "2026-10-16", "probes": 252, "ok": 252 }, { "date": "2026-10-17", "probes": 253, "ok": 253 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 251, "ok": 251 }, { "date": "2026-10-29", "probes": 248, "ok": 248 }, { "date": "2026-10-30", "probes": 249, "ok": 249 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 250, "ok": 250 }, { "date": "2026-11-03", "probes": 248, "ok": 248 }, { "date": "2026-11-04", "probes": 246, "ok": 246 }, { "date": "2026-11-05", "probes": 185, "ok": 185 }, { "date": "2026-11-06", "probes": 241, "ok": 241 }, { "date": "2026-11-07", "probes": 233, "ok": 233 } ] }, "vendorStatus": { "page": "https://status.lingo.dev", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-07T04:47:59.978280384Z" }, "versions": [ { "registry": "github", "name": "lingodotdev/lingo.dev", "version": "@lingo.dev/_compiler@0.12.16", "released": "2026-10-26", "seenAt": "2026-11-06T23:40:00.32088548Z" }, { "registry": "mcp-registry", "name": "dev.lingo/main", "version": "1.0.0", "seenAt": "2026-11-07T18:16:28.95801333Z" }, { "registry": "npm", "name": "@lingo.dev/_sdk", "version": "0.17.4", "seenAt": "2026-11-06T23:39:56.913563105Z" }, { "registry": "npm", "name": "@lingo.dev/cli", "version": "1.18.0", "seenAt": "2026-11-06T23:39:54.700852676Z" }, { "registry": "npm", "name": "lingo.dev", "version": "0.138.11", "seenAt": "2026-11-06T23:39:54.928939137Z" }, { "registry": "pypi", "name": "lingodotdev", "version": "1.5.0", "released": "2026-03-07", "seenAt": "2026-11-06T23:40:00.073188478Z" } ], "githubStars": 5405, "npmWeekly": 2784, "pypiWeekly": 4067, "securityTxt": { "url": "https://lingo.dev/.well-known/security.txt", "state": "valid", "checkedAt": "2026-11-07T16:00:20.274523944Z" }, "domain": { "domain": "lingo.dev", "registered": "2021-05-03", "source": "https://pubapi.registry.google/rdap/domain/lingo.dev", "checkedAt": "2026-11-01T14:09:20.593506375Z" }, "pages": [ { "url": "https://lingo.dev/en/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:13:12.131830641Z", "changedAt": "2026-11-05T12:36:34.641341554Z", "fingerprint": "105e4422fcb5" }, { "url": "https://lingo.dev/en/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-11-07T14:13:18.379520546Z", "changedAt": "2026-11-07T14:13:18.379520546Z", "fingerprint": "cb829e248b57" }, { "url": "https://lingo.dev/en/legal/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:13:14.926164149Z", "changedAt": "2026-10-20T00:01:02.879823152Z", "fingerprint": "98f5d881f99e" }, { "url": "https://lingo.dev/en/legal/terms", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:13:16.504232791Z", "changedAt": "2026-10-20T00:01:04.348893283Z", "fingerprint": "47aa3ef2d139" } ], "github": { "repo": "lingodotdev/lingo.dev", "checkedAt": "2026-11-02T09:00:50.867887213Z", "stars": 5399, "archived": false, "issuesEnabled": true, "pushedAt": "2026-10-26T14:15:35Z", "openIssues": 16, "openPRs": 5, "issuesOpened90d": 4, "issuesClosed90d": 18, "prsMerged90d": 38, "ci": { "branch": "main", "runs": 50, "success": 22, "failure": 3, "other": 25, "latest": "skipped", "latestAt": "2026-10-26T14:11:16Z" }, "replies": { "sampled": 25, "unanswered": 4, "medianDays": 13.9 } }, "updatedAt": "2026-11-07T22:56:06.084464117Z" } }, "answer": "Lingo.dev scores 66.1 (B) on agent readiness against Localazy's 54.4 (C), and leads in 6 of 7 scored categories. Localazy leads on payments \u0026 pricing.", "b": { "slug": "localazy", "name": "Localazy", "vendor": "Localazy s.r.o.", "vendorUrl": "https://localazy.com", "kind": "http-api", "category": "translation", "summary": "Localazy is a Czech localisation platform for software teams, with a translation management system, AI and human translation, a CLI, a REST API for projects, keys, files and glossaries, and a translation CDN.", "url": "https://www.anchorterminal.com/tools/localazy", "markdownUrl": "https://www.anchorterminal.com/tools/localazy.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/localazy.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/localazy.json", "dns": "localazy.grade.anchorterminal.com", "repo": "https://github.com/localazy/api-client", "transports": [ "http" ], "packages": [ { "registry": "npm", "name": "@localazy/api-client" }, { "registry": "npm", "name": "@localazy/cli" } ], "auth": "pat", "authNotes": "Bearer tokens minted by a project owner at localazy.com/developer/tokens after a browser signup. Project tokens have read and write access to every endpoint of one project. Translation tokens reach only the AI Translation endpoint. Organisation tokens are a beta on request.", "pricing": "freemium", "pricingNotes": "Free plan for small projects. Professional $34, Autopilot $78 and Business $175 a month billed annually, each including monthly translation credits ($1 each). Localazy AI averages $0.005 a word. 14-day Business trial with no credit card.", "priceSummary": "$34 / mo", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the API docs or pricing (checked 2026-11-06). Plans and credits are paid by card through Stripe, or SEPA on request.", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": 61319, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://localazy.com/docs/api/introduction", "llmsTxt": "https://localazy.com/llms.txt", "capabilities": [ "translate.text", "translate.glossary", "translate.documents", "cms.localisation" ], "tags": [ "hosted", "freemium", "free-tier", "no-card", "free-trial", "cli", "typescript", "android", "ios", "status-page", "eu", "localisation", "beta", "closed-source" ], "lastRelease": "2026-10-26", "graded": true, "anchor": { "graded": true, "score": 54.4, "grade": "C", "agentReady": false, "rank": 915, "ranked": true, "rankOf": 1510, "categoryRank": 10, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 62, "maintenance": 75, "payments": 35, "reliability": 68, "schema": 51, "security": 37, "transparency": 57 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-06" }, "negative": 0, "verdict": "Localazy is a localisation platform whose REST API, CLI and AI Translation endpoint use project-scoped bearer tokens, with published limits, a free plan and a no-card trial. There's no OpenAPI spec, no 429 guidance, no security.txt or disclosure policy, and project tokens carry full read and write access.", "bestFor": "App and game teams that keep source strings in a TMS and want agents to push keys, pull translations or run AI translation with a glossary.", "strengths": [ "A translation-only token limits an agent to the AI Translation endpoint", "Rate and request limits published per plan, with daily import and fetch caps", "Free plan for small projects and a 14-day Business trial without a credit card", "Endpoint pages show token type, permission and role needed, with sample requests and errors", "TypeScript API client released 26 October 2026, plus a CLI and mobile libraries" ], "weaknesses": [ "No OpenAPI spec, and llms.txt only lists top-level pages", "Project tokens get read and write access to every endpoint of the project", "No security.txt, disclosure policy or certification found", "No 429 or retry guidance, and no SLA", "The AI Translation endpoint is in beta" ], "agentNotes": [ "Ask for a translation token when the task is only machine translation, rather than a project token", "Keep under 10 requests a second and the plan's daily import and fetch caps per project", "Use the Localazy CDN, not the API, to fetch translations in a live app", "Import at most 1,000 keys and 50 files a request, and don't run parallel imports into the same new file", "Check the account's credit balance before bulk AI translation, since each word uses credits" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 54.4 } ], "editorialScores": { "ergonomics": 62, "maintenance": 75, "payments": 35, "reliability": 68, "schema": 51, "security": 37, "transparency": 40 }, "provenanceScore": 73, "checked": { "categories": { "ergonomics": "2026-11-06", "maintenance": "2026-11-06", "payments": "2026-11-06", "reliability": "2026-11-06", "schema": "2026-11-06", "security": "2026-11-06", "transparency": "2026-11-06" }, "last": "2026-11-06", "oldest": "2026-11-06", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "npm install -g @localazy/cli", "http": "curl -H \"Authorization: Bearer $LOCALAZY_TOKEN\" https://api.localazy.com/projects" }, "letme": { "capability": "https://letme.dev/translate.text", "tool": "https://letme.dev/localazy" }, "area": "everyday", "unitPrices": [ { "item": "Professional plan, billed annually", "unit": "month", "usd": 34, "note": "1,000 source keys, 12,000 words of Localazy AI translation" }, { "item": "Business plan, billed annually", "unit": "month", "usd": 175, "note": "Monthly credits included" } ], "provenance": { "legalEntity": "Localazy s.r.o.", "domain": "localazy.com", "domainRegistered": "2018-04-24", "endpointOnVendorDomain": true, "terms": "https://localazy.com/terms-and-conditions", "privacy": "https://localazy.com/privacy-policy", "statusPage": "https://status.localazy.com", "changelog": "", "securityTxt": "none", "checked": "2026-11-06", "notes": [ "The terms name Localazy s.r.o., Mlýnská 326/13, 602 00 Brno, Czech Republic, company ID 09050451, registered at the Regional Court in Brno, under Czech law.", "robots.txt on localazy.com disallows ClaudeBot, GPTBot, Google-Extended, CCBot and Bytespider and allows Claude-User, Claude-SearchBot, ChatGPT-User and others by name; research continued on that basis, as the founder decided on 30 October 2026 (arcmira's precedent).", "localazy.com/.well-known/security.txt and /security return 404.", "No API changelog was found; localazy.com/changelog returns 404. Release updates appear as blog posts.", "RDAP gives localazy.com a registration date of 24 April 2018." ], "score": 73 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/localazy.json", "live": { "slug": "localazy", "vendorStatus": { "page": "https://status.localazy.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-07T04:48:00.405159441Z" }, "versions": [ { "registry": "github", "name": "localazy/api-client", "version": "2.3.2", "released": "2026-10-26", "seenAt": "2026-11-06T23:41:15.049514814Z" }, { "registry": "npm", "name": "@localazy/api-client", "version": "2.3.2", "seenAt": "2026-11-06T23:41:12.850780355Z" }, { "registry": "npm", "name": "@localazy/cli", "version": "2.0.12", "seenAt": "2026-11-06T23:41:13.725514176Z" } ], "githubStars": 3, "npmWeekly": 1211, "securityTxt": { "url": "https://localazy.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T15:59:35.625950014Z" }, "llmsTxt": { "url": "https://localazy.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:32:54.35604842Z" }, "pages": [ { "url": "https://localazy.com/privacy-policy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:13:22.759899743Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "3ab88891f9db" }, { "url": "https://localazy.com/terms-and-conditions", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:13:24.897447568Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "9d1fa669c0c4" } ], "updatedAt": "2026-11-07T15:59:35.625950014Z" } }, "edges": [ { "by": 25, "category": "security", "leads": "lingo-dev", "name": "Security \u0026 auth", "reasons": { "a": "The MCP server uses OAuth with PKCE and dynamic client registration and publishes no scopes. API keys are stored hashed, shown once and revoked by deletion. Personal keys carry their creator's full access, and keys with their own role and engine scope need Enterprise. No documented option puts a key in a URL (22 of 30). RBAC with 20 permissions exists on Enterprise only. On other plans every member is an Owner. The MCP server can create and revoke API keys and invite members with admin access by default, and no confirmation step is documented (8 of 20). Responses are translations of the caller's own content, while engine provisioning reads links the caller supplies. No injection guidance was found (7 of 15). Request logs with model, tokens and full input and output are on every plan. The append-only audit log, which records the acting user or key and the IP address, is Enterprise only (12 of 15). security.txt gives a contact and a disclosure policy with a safe-harbour promise and a maximum reward of a $50 gift card. The site states SOC 2 Type II, with the report available on Enterprise. No bug bounty or public advisories were found (13 of 20).", "b": "Bearer tokens in the Authorization header. A project token reaches every endpoint of one project with read and write access; a translation token reaches only the AI Translation endpoint; organisation tokens are in beta on request (20). The translation token is the only least-privilege option, and project tokens can delete keys and glossary items without a confirmation step (10). The API returns strings written by translators and contributors, with no guidance on untrusted content (5). No per-call log or audit trail for tokens found (2). localazy.com/.well-known/security.txt and /security return 404, and we found no disclosure policy or certification (0). 20+10+5+2+0 = 37." }, "scores": { "a": 62, "b": 37 } }, { "by": 15, "category": "payments", "leads": "localazy", "name": "Payments \u0026 pricing", "reasons": { "a": "No x402, MPP or L402. The API's 402 status reports a credit limit and carries no payment instructions (0). Unit prices are public without a login, $2 per million output tokens plus the model's cost with no markup, $0.50 per engine a month and $0.01 per AI review run (20). Sandbox has a $0 base price, but every translation is charged against prepaid credits and no free allowance or trial was found on the pricing page or in the docs (0). A person signs up in a browser. The CLI signs in with an emailed code and the MCP server with browser OAuth (0).", "b": "No x402, MPP or L402 (0). Plan prices are public ($34, $78 and $175 a month billed annually) and credits are $1 each, with Localazy AI at about $0.005 a word on average, so partial per-unit credit (15). A free plan for small projects and a 14-day Business trial with no credit card (20). A person signs up in a browser and mints tokens in the developer settings (0). 0+15+20+0 = 35." }, "scores": { "a": 20, "b": 35 } }, { "by": 15, "category": "transparency", "leads": "lingo-dev", "name": "Transparency \u0026 trust", "reasons": { "a": "The platform is closed under published terms. The legacy CLI, the JavaScript SDK, the compiler and the Python SDK are Apache-2.0, and the current `@lingo.dev/cli` package states no licence (18 of 30). The terms and the privacy policy agree that user content is not used to train AI models and that AI providers keep content for up to 30 days by default. The privacy policy gives translation data 30 days by default while the pricing page gives 7 days on Sandbox. The Data Processing Agreement the policy refers to is not published (17 of 30). The terms promise advance notice and migration instructions for breaking API changes without stating a period, and the older CLI's docs are kept under a legacy section (8 of 20). The terms name Supabase in Frankfurt and Cloudflare. The sub-processor page the privacy policy points to, lingo.dev/security, redirects to a 404 page (2 November), and the LLM providers are not listed as sub-processors on any page we read (8 of 20).", "b": "Editorial half only. Closed service under terms that name Localazy s.r.o. of Brno and Czech law; the CLI is BSD-3-Clause and the API client MIT (15). The privacy policy keeps data while the service is used and 24 months after, and includes a DPA, but says nothing on whether content sent to Localazy AI is used for training (15). No deprecation policy or dated notices found (0). The DPA links a list of suppliers and subprocessors on an external knowledge base we didn't read (10). 15+15+0+10 = 40." }, "scores": { "a": 72, "b": 57 } }, { "by": 13, "category": "reliability", "leads": "lingo-dev", "name": "Reliability", "reasons": { "a": "Hosted reading of the checklist, for the REST API and the hosted MCP server. status.lingo.dev runs on OpenStatus with WEB and API monitors and an events history (20). Between 4 August and 2 November the history lists one incident, a partial outage of the localization endpoint on 22 September 2026 from 22:09 to 23:59 UTC, in which 'a portion of localization requests' failed and other services were unaffected. Partial, so minor (20). The 18 July partial outage has left the window. Daily token quotas are published per plan, 100,000 on Sandbox and 5 million on Production, with no per-second request limit found (12 of 15). The errors page says to retry 500 with exponential backoff and not to retry 402 or 429, and async job creation takes an `idempotencyKey`. No `Retry-After` header is documented (12 of 15). The pricing page lists a 99.99% uptime SLA for Enterprise without publishing the document, and the terms say the company strives for 99.9% without a guarantee (7 of 10). Version 1.0 shipped on 15 March 2026 and nothing on the API pages is marked beta (10).", "b": "Hosted lines, for the REST API at api.localazy.com. Better Stack status page with Web, API, Public API, Payments and Connect API components and 30, 60 and 90-day uptime (20). The incidents page reports none for September, October or November 2026, but the Public API shows 99.805% uptime in one 30-day bucket, roughly an hour and a half of downtime with no incident posted, so the line is held below clean (25). Limits per plan of 100 requests a minute and 10 a second, plus daily import and fetch caps per project (15). No 429 or retry guidance found in the API docs (0). No SLA found on the pricing page or in the terms (0). The core API is GA; the AI Translation endpoint is marked beta (8). 20+25+15+0+0+8 = 68." }, "scores": { "a": 81, "b": 68 } }, { "by": 13, "category": "schema", "leads": "lingo-dev", "name": "Schema \u0026 documentation", "reasons": { "a": "No OpenAPI file was found. `https://api.lingo.dev/openapi.json` returns 404 and the docs link none. The open-source JavaScript SDK carries typed request schemas, and the MCP tool definitions can't be read without signing in (5 of 25). `llms.txt` now indexes the docs, pricing and guides, and `llms-full.txt` lists every docs page with a description, including 28 API reference pages, which render as server-side HTML. Docs pages have no Markdown version (10). The reference says what each endpoint is for and when to pick the sync call or async jobs (16 of 20). Parameters have types and limits, such as 1 to 100 target locales, 100 locked-key patterns and five job statuses, while `data` is a free-form object by design (11 of 15). Request and response examples are given in up to five languages, and one page lists seven status codes. Error bodies hold only a `message` string (12 of 15). A weekly changelog runs from 15 March to 30 October 2026. No API version in the path or a header was found (10 of 15).", "b": "No OpenAPI or other machine-readable contract was found (0). localazy.com/llms.txt is a six-link index of top-level pages, with no Markdown docs for agents (5). Each endpoint page states which token types can call it, whether write permission is needed and the minimum role, and the limits page says to use the CDN, not the API, for production fetches (14). Request bodies list required and optional fields with limits, such as 512 characters for a key and 1,000 for a comment (12). Sample requests, responses and error responses per endpoint (13). Docs pages carry 'last updated' dates and the blog posts dated release updates, but there's no API version or changelog (7). 0+5+14+12+13+7 = 51." }, "scores": { "a": 64, "b": 51 } }, { "by": 13, "category": "ergonomics", "leads": "lingo-dev", "name": "Agent ergonomics", "reasons": { "a": "API reading of the checklist. Sync responses return only the translated data, the model and a usage block, and job lists return summaries without output. The MCP server covers team, role, key and audit administration alongside translation, with no documented toolsets or read-only subset, and its tool count is unpublished (15 of 25). Job lists page by cursor with `limit` from 20 to 100 and filters for engine and status (20). Errors are keyed on seven status codes with retry advice for each group, but the body has no machine-readable code (15 of 20). Async job creation is idempotent with `idempotencyKey`. The sync call has no such key, and MCP annotations could not be read (12 of 20). A sync call needs three fields and falls back to the organisation's default engine. JavaScript and Python SDKs exist, though the Python one last shipped on 7 March 2026 and the docs site has no SDK section (13 of 15).", "b": "API reading. List endpoints return whole projects, files and keys with few output controls (13). Filtering by file, language and tags, and batch imports of up to 1,000 keys and 50 files a request (14). Error responses are documented per endpoint, with HTTP codes and messages (12). No idempotency keys, and the docs warn against parallel imports into the same new file (8). Official TypeScript API client, a CLI and Android and iOS libraries, with few required fields (15). 13+14+12+8+15 = 62." }, "scores": { "a": 75, "b": 62 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Replexica, Inc.", "b": "Localazy s.r.o.", "name": "Vendor" }, { "a": "https://mcp.lingo.dev/account", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP", "b": "HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "Token", "name": "Auth" }, { "a": "Pay per use", "b": "Freemium", "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": "yes", "name": "llms.txt" }, { "a": "dev.lingo/main", "b": "not listed", "name": "MCP registry" }, { "a": "2026-10-30", "b": "2026-10-26", "name": "Last release" }, { "a": "2026-05-07", "b": "no date given", "name": "Terms last updated" }, { "a": "2026-05-07", "b": "no date given", "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": "61k npm/wk", "name": "Popularity" }, { "a": "3.3/5 (4)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "Lingo.dev scores 66.1 (B) on agent readiness against Localazy's 54.4 (C), and leads in 6 of 7 scored categories. Localazy leads on payments \u0026 pricing.", "question": "Which is better for AI agents, Lingo.dev or Localazy?" }, { "answer": "Lingo.dev takes an API key or an OAuth sign-in. Localazy needs an access token.", "question": "Do Lingo.dev and Localazy need an API key?" }, { "answer": "Lingo.dev has a hosted endpoint at https://mcp.lingo.dev/account. No hosted endpoint is listed for Localazy.", "question": "Can an agent call Lingo.dev and Localazy without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 81 against 68", "Schema \u0026 documentation, 64 against 51", "Agent ergonomics, 75 against 62", "Security \u0026 auth, 62 against 37", "Maintenance \u0026 community, 87 against 75", "Transparency \u0026 trust, 72 against 57" ], "also": [ "A hosted endpoint, with nothing to install" ], "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, docs pages have no Markdown version and error bodies carry only a free-text `message`" }, { "aheadOn": [ "Payments \u0026 pricing, 35 against 20" ], "also": [ "Free to start without a card" ], "goodFor": "App and game teams that keep source strings in a TMS and want agents to push keys, pull translations or run AI translation with a glossary.", "slug": "localazy", "watchFor": "No OpenAPI spec, and llms.txt only lists top-level pages" } ], "history": { "lingo-dev": [ { "causes": [ "product", "correction" ], "date": "2026-11-02", "delta": 3.7, "from": 62.4, "fromGrade": "B", "to": 66.1, "toGrade": "B" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.1, "from": 62.3, "fromGrade": "B", "to": 62.4, "toGrade": "B" } ], "localazy": null }, "job": { "capability": "translate.text", "name": "Translation" }, "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-localazy.json", "title": "Amazon Translate vs Localazy", "url": "https://www.anchorterminal.com/compare/amazon-translate-vs-localazy" }, { "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-localazy.json", "title": "Azure Translator vs Localazy", "url": "https://www.anchorterminal.com/compare/azure-translator-vs-localazy" }, { "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-localazy.json", "title": "Crowdin vs Localazy", "url": "https://www.anchorterminal.com/compare/crowdin-vs-localazy" }, { "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-localazy.json", "title": "DeepL API vs Localazy", "url": "https://www.anchorterminal.com/compare/deepl-api-vs-localazy" }, { "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-localazy.json", "title": "Google Cloud Translation vs Localazy", "url": "https://www.anchorterminal.com/compare/google-cloud-translation-vs-localazy" }, { "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-localazy.json", "title": "Lara Translate API vs Localazy", "url": "https://www.anchorterminal.com/compare/lara-translate-vs-localazy" }, { "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-localazy.json", "title": "LibreTranslate vs Localazy", "url": "https://www.anchorterminal.com/compare/libretranslate-vs-localazy" }, { "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/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-smartcat.json", "title": "Lingo.dev vs Smartcat", "url": "https://www.anchorterminal.com/compare/lingo-dev-vs-smartcat" }, { "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/lingo-dev-vs-translateplus.json", "title": "Lingo.dev vs TranslatePlus", "url": "https://www.anchorterminal.com/compare/lingo-dev-vs-translateplus" }, { "json": "https://www.anchorterminal.com/compare/lingvanex-vs-localazy.json", "title": "Lingvanex Translation API vs Localazy", "url": "https://www.anchorterminal.com/compare/lingvanex-vs-localazy" }, { "json": "https://www.anchorterminal.com/compare/localazy-vs-lokalise.json", "title": "Localazy vs Lokalise", "url": "https://www.anchorterminal.com/compare/localazy-vs-lokalise" }, { "json": "https://www.anchorterminal.com/compare/localazy-vs-phrase.json", "title": "Localazy vs Phrase", "url": "https://www.anchorterminal.com/compare/localazy-vs-phrase" }, { "json": "https://www.anchorterminal.com/compare/localazy-vs-smartcat.json", "title": "Localazy vs Smartcat", "url": "https://www.anchorterminal.com/compare/localazy-vs-smartcat" }, { "json": "https://www.anchorterminal.com/compare/localazy-vs-systran.json", "title": "Localazy vs SYSTRAN Translate API", "url": "https://www.anchorterminal.com/compare/localazy-vs-systran" }, { "json": "https://www.anchorterminal.com/compare/localazy-vs-translateplus.json", "title": "Localazy vs TranslatePlus", "url": "https://www.anchorterminal.com/compare/localazy-vs-translateplus" } ], "panel": null, "scores": [ { "by": 13, "edge": "lingo-dev", "key": "reliability", "lingo-dev": 81, "localazy": 68, "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 13, "edge": "lingo-dev", "key": "schema", "lingo-dev": 64, "localazy": 51, "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 13, "edge": "lingo-dev", "key": "ergonomics", "lingo-dev": 75, "localazy": 62, "name": "Agent ergonomics", "weight": 13 }, { "by": 25, "edge": "lingo-dev", "key": "security", "lingo-dev": 62, "localazy": 37, "name": "Security \u0026 auth", "weight": 14 }, { "by": 15, "edge": "localazy", "key": "payments", "lingo-dev": 20, "localazy": 35, "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 12, "edge": "lingo-dev", "key": "maintenance", "lingo-dev": 87, "localazy": 75, "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 15, "edge": "lingo-dev", "key": "transparency", "lingo-dev": 72, "localazy": 57, "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Lingo.dev scores 66.1 (B) on agent readiness against Localazy's 54.4 (C), and leads in 6 of 7 scored categories. Localazy leads on payments \u0026 pricing. Both do translation.", "tasks": null, "tutorials": [], "verdicts": { "lingo-dev": "Lingo.dev suits teams that want glossary and tone control on every translation call, with a published fee of $2 per million output tokens and model costs passed through. It has no public OpenAPI file, and scoped keys, roles and audit logs are limited to the Enterprise plan.", "localazy": "Localazy is a localisation platform whose REST API, CLI and AI Translation endpoint use project-scoped bearer tokens, with published limits, a free plan and a no-card trial. There's no OpenAPI spec, no 429 guidance, no security.txt or disclosure policy, and project tokens carry full read and write access." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/lingo-dev-vs-localazy", "json": "https://www.anchorterminal.com/compare/lingo-dev-vs-localazy.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/lingo-dev-vs-localazy.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/lingo-dev-vs-localazy.min.md" }, "markdown": "Lingo.dev scores 66.1 (B) on agent readiness against Localazy's 54.4 (C), and leads in 6 of 7 scored categories. Localazy leads on payments \u0026 pricing. Both do translation.\n\n- Lingo.dev: grade B, 66.1/100, rank #382 of 1510. Markdown https://www.anchorterminal.com/tools/lingo-dev.md · JSON https://www.anchorterminal.com/api/v1/tools/lingo-dev.json\n- Localazy: grade C, 54.4/100, rank #915 of 1510. Markdown https://www.anchorterminal.com/tools/localazy.md · JSON https://www.anchorterminal.com/api/v1/tools/localazy.json\n- Best machine translation APIs for AI agents: https://www.anchorterminal.com/best/translation/index.md\n- All 105 translation comparisons: https://www.anchorterminal.com/compare/translation/index.md\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, 81 against 68\n- Schema \u0026 documentation, 64 against 51\n- Agent ergonomics, 75 against 62\n- Security \u0026 auth, 62 against 37\n- Maintenance \u0026 community, 87 against 75\n- Transparency \u0026 trust, 72 against 57\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n\nWatch for: No public OpenAPI file was found, docs pages have no Markdown version and error bodies carry only a free-text `message`\n\n### Localazy (C)\n\nGood for: App and game teams that keep source strings in a TMS and want agents to push keys, pull translations or run AI translation with a glossary.\n\nAhead on:\n- Payments \u0026 pricing, 35 against 20\n\nAlso in its favour:\n- Free to start without a card\n\nWatch for: No OpenAPI spec, and llms.txt only lists top-level pages\n\n\n## Why the edge\n\n### Security \u0026 auth: Lingo.dev +25\n\n- Lingo.dev (62): The MCP server uses OAuth with PKCE and dynamic client registration and publishes no scopes. API keys are stored hashed, shown once and revoked by deletion. Personal keys carry their creator's full access, and keys with their own role and engine scope need Enterprise. No documented option puts a key in a URL (22 of 30). RBAC with 20 permissions exists on Enterprise only. On other plans every member is an Owner. The MCP server can create and revoke API keys and invite members with admin access by default, and no confirmation step is documented (8 of 20). Responses are translations of the caller's own content, while engine provisioning reads links the caller supplies. No injection guidance was found (7 of 15). Request logs with model, tokens and full input and output are on every plan. The append-only audit log, which records the acting user or key and the IP address, is Enterprise only (12 of 15). security.txt gives a contact and a disclosure policy with a safe-harbour promise and a maximum reward of a $50 gift card. The site states SOC 2 Type II, with the report available on Enterprise. No bug bounty or public advisories were found (13 of 20).\n- Localazy (37): Bearer tokens in the Authorization header. A project token reaches every endpoint of one project with read and write access; a translation token reaches only the AI Translation endpoint; organisation tokens are in beta on request (20). The translation token is the only least-privilege option, and project tokens can delete keys and glossary items without a confirmation step (10). The API returns strings written by translators and contributors, with no guidance on untrusted content (5). No per-call log or audit trail for tokens found (2). localazy.com/.well-known/security.txt and /security return 404, and we found no disclosure policy or certification (0). 20+10+5+2+0 = 37.\n\n### Payments \u0026 pricing: Localazy +15\n\n- Lingo.dev (20): No x402, MPP or L402. The API's 402 status reports a credit limit and carries no payment instructions (0). Unit prices are public without a login, $2 per million output tokens plus the model's cost with no markup, $0.50 per engine a month and $0.01 per AI review run (20). Sandbox has a $0 base price, but every translation is charged against prepaid credits and no free allowance or trial was found on the pricing page or in the docs (0). A person signs up in a browser. The CLI signs in with an emailed code and the MCP server with browser OAuth (0).\n- Localazy (35): No x402, MPP or L402 (0). Plan prices are public ($34, $78 and $175 a month billed annually) and credits are $1 each, with Localazy AI at about $0.005 a word on average, so partial per-unit credit (15). A free plan for small projects and a 14-day Business trial with no credit card (20). A person signs up in a browser and mints tokens in the developer settings (0). 0+15+20+0 = 35.\n\n### Transparency \u0026 trust: Lingo.dev +15\n\n- Lingo.dev (72): The platform is closed under published terms. The legacy CLI, the JavaScript SDK, the compiler and the Python SDK are Apache-2.0, and the current `@lingo.dev/cli` package states no licence (18 of 30). The terms and the privacy policy agree that user content is not used to train AI models and that AI providers keep content for up to 30 days by default. The privacy policy gives translation data 30 days by default while the pricing page gives 7 days on Sandbox. The Data Processing Agreement the policy refers to is not published (17 of 30). The terms promise advance notice and migration instructions for breaking API changes without stating a period, and the older CLI's docs are kept under a legacy section (8 of 20). The terms name Supabase in Frankfurt and Cloudflare. The sub-processor page the privacy policy points to, lingo.dev/security, redirects to a 404 page (2 November), and the LLM providers are not listed as sub-processors on any page we read (8 of 20).\n- Localazy (57): Editorial half only. Closed service under terms that name Localazy s.r.o. of Brno and Czech law; the CLI is BSD-3-Clause and the API client MIT (15). The privacy policy keeps data while the service is used and 24 months after, and includes a DPA, but says nothing on whether content sent to Localazy AI is used for training (15). No deprecation policy or dated notices found (0). The DPA links a list of suppliers and subprocessors on an external knowledge base we didn't read (10). 15+15+0+10 = 40.\n\n### Reliability: Lingo.dev +13\n\n- Lingo.dev (81): Hosted reading of the checklist, for the REST API and the hosted MCP server. status.lingo.dev runs on OpenStatus with WEB and API monitors and an events history (20). Between 4 August and 2 November the history lists one incident, a partial outage of the localization endpoint on 22 September 2026 from 22:09 to 23:59 UTC, in which 'a portion of localization requests' failed and other services were unaffected. Partial, so minor (20). The 18 July partial outage has left the window. Daily token quotas are published per plan, 100,000 on Sandbox and 5 million on Production, with no per-second request limit found (12 of 15). The errors page says to retry 500 with exponential backoff and not to retry 402 or 429, and async job creation takes an `idempotencyKey`. No `Retry-After` header is documented (12 of 15). The pricing page lists a 99.99% uptime SLA for Enterprise without publishing the document, and the terms say the company strives for 99.9% without a guarantee (7 of 10). Version 1.0 shipped on 15 March 2026 and nothing on the API pages is marked beta (10).\n- Localazy (68): Hosted lines, for the REST API at api.localazy.com. Better Stack status page with Web, API, Public API, Payments and Connect API components and 30, 60 and 90-day uptime (20). The incidents page reports none for September, October or November 2026, but the Public API shows 99.805% uptime in one 30-day bucket, roughly an hour and a half of downtime with no incident posted, so the line is held below clean (25). Limits per plan of 100 requests a minute and 10 a second, plus daily import and fetch caps per project (15). No 429 or retry guidance found in the API docs (0). No SLA found on the pricing page or in the terms (0). The core API is GA; the AI Translation endpoint is marked beta (8). 20+25+15+0+0+8 = 68.\n\n### Schema \u0026 documentation: Lingo.dev +13\n\n- Lingo.dev (64): No OpenAPI file was found. `https://api.lingo.dev/openapi.json` returns 404 and the docs link none. The open-source JavaScript SDK carries typed request schemas, and the MCP tool definitions can't be read without signing in (5 of 25). `llms.txt` now indexes the docs, pricing and guides, and `llms-full.txt` lists every docs page with a description, including 28 API reference pages, which render as server-side HTML. Docs pages have no Markdown version (10). The reference says what each endpoint is for and when to pick the sync call or async jobs (16 of 20). Parameters have types and limits, such as 1 to 100 target locales, 100 locked-key patterns and five job statuses, while `data` is a free-form object by design (11 of 15). Request and response examples are given in up to five languages, and one page lists seven status codes. Error bodies hold only a `message` string (12 of 15). A weekly changelog runs from 15 March to 30 October 2026. No API version in the path or a header was found (10 of 15).\n- Localazy (51): No OpenAPI or other machine-readable contract was found (0). localazy.com/llms.txt is a six-link index of top-level pages, with no Markdown docs for agents (5). Each endpoint page states which token types can call it, whether write permission is needed and the minimum role, and the limits page says to use the CDN, not the API, for production fetches (14). Request bodies list required and optional fields with limits, such as 512 characters for a key and 1,000 for a comment (12). Sample requests, responses and error responses per endpoint (13). Docs pages carry 'last updated' dates and the blog posts dated release updates, but there's no API version or changelog (7). 0+5+14+12+13+7 = 51.\n\n### Agent ergonomics: Lingo.dev +13\n\n- Lingo.dev (75): API reading of the checklist. Sync responses return only the translated data, the model and a usage block, and job lists return summaries without output. The MCP server covers team, role, key and audit administration alongside translation, with no documented toolsets or read-only subset, and its tool count is unpublished (15 of 25). Job lists page by cursor with `limit` from 20 to 100 and filters for engine and status (20). Errors are keyed on seven status codes with retry advice for each group, but the body has no machine-readable code (15 of 20). Async job creation is idempotent with `idempotencyKey`. The sync call has no such key, and MCP annotations could not be read (12 of 20). A sync call needs three fields and falls back to the organisation's default engine. JavaScript and Python SDKs exist, though the Python one last shipped on 7 March 2026 and the docs site has no SDK section (13 of 15).\n- Localazy (62): API reading. List endpoints return whole projects, files and keys with few output controls (13). Filtering by file, language and tags, and batch imports of up to 1,000 keys and 50 files a request (14). Error responses are documented per endpoint, with HTTP codes and messages (12). No idempotency keys, and the docs warn against parallel imports into the same new file (8). Official TypeScript API client, a CLI and Android and iOS libraries, with few required fields (15). 13+14+12+8+15 = 62.\n\n## Score by category\n\n| Category | Weight | Lingo.dev | Localazy | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 81 | 68 | Lingo.dev +13 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 64 | 51 | Lingo.dev +13 |\n| Agent ergonomics | 13% (16.2 this run) | 75 | 62 | Lingo.dev +13 |\n| Security \u0026 auth | 14% (17.5 this run) | 62 | 37 | Lingo.dev +25 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 20 | 35 | Localazy +15 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 87 | 75 | Lingo.dev +12 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 72 | 57 | Lingo.dev +15 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **66.1 · B** | **54.4 · C** | |\n\n## Facts side by side\n\n| Fact | Lingo.dev | Localazy |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Replexica, Inc. | Localazy s.r.o. |\n| Hosted endpoint | `https://mcp.lingo.dev/account` | no (local only) |\n| Transports | HTTP, Streamable HTTP | HTTP |\n| Auth | OAuth or key | Token |\n| Pricing | Pay per use | Freemium |\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 | yes |\n| MCP registry | `dev.lingo/main` | not listed |\n| Last release | 2026-10-30 | 2026-10-26 |\n| Terms last updated | 2026-05-07 | no date given |\n| Privacy policy last updated | 2026-05-07 | no date given |\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 | 61k npm/wk |\n| Agent reviews | 3.3/5 (4) | none |\n\n## How the scores have moved\n\n### Lingo.dev\n\n- +3.7 on 2 November 2026: product, correction\n- +0.1 on 27 October 2026: checklist\n\n### Localazy\n\nNo score change since it was listed.\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, and scoped keys, roles and audit logs are limited to the Enterprise plan.\n\n**Localazy.** Localazy is a localisation platform whose REST API, CLI and AI Translation endpoint use project-scoped bearer tokens, with published limits, a free plan and a no-card trial. There's no OpenAPI spec, no 429 guidance, no security.txt or disclosure policy, and project tokens carry full read and write access.\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### Localazy\n\n1. Ask for a translation token when the task is only machine translation, rather than a project token\n2. Keep under 10 requests a second and the plan's daily import and fetch caps per project\n3. Use the Localazy CDN, not the API, to fetch translations in a live app\n4. Import at most 1,000 keys and 50 files a request, and don't run parallel imports into the same new file\n5. Check the account's credit balance before bulk AI translation, since each word uses credits\n\n## Questions\n\n### Which is better for AI agents, Lingo.dev or Localazy?\n\nLingo.dev scores 66.1 (B) on agent readiness against Localazy's 54.4 (C), and leads in 6 of 7 scored categories. Localazy leads on payments \u0026 pricing.\n\n### Do Lingo.dev and Localazy need an API key?\n\nLingo.dev takes an API key or an OAuth sign-in. Localazy needs an access token.\n\n### Can an agent call Lingo.dev and Localazy without installing anything?\n\nLingo.dev has a hosted endpoint at https://mcp.lingo.dev/account. No hosted endpoint is listed for Localazy.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/lingo-dev-vs-localazy.json, and with the fewest tokens: https://www.anchorterminal.com/compare/lingo-dev-vs-localazy.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"lingo-dev\", \"b\": \"localazy\"}`. From a terminal: `anchor compare lingo-dev localazy`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/lingo-dev.json and https://www.anchorterminal.com/api/v1/tools/localazy.json\n\n## Other comparisons with Lingo.dev or Localazy\n\n- [Amazon Translate vs Lingo.dev](https://www.anchorterminal.com/compare/amazon-translate-vs-lingo-dev.md)\n- [Amazon Translate vs Localazy](https://www.anchorterminal.com/compare/amazon-translate-vs-localazy.md)\n- [Azure Translator vs Lingo.dev](https://www.anchorterminal.com/compare/azure-translator-vs-lingo-dev.md)\n- [Azure Translator vs Localazy](https://www.anchorterminal.com/compare/azure-translator-vs-localazy.md)\n- [Crowdin vs Lingo.dev](https://www.anchorterminal.com/compare/crowdin-vs-lingo-dev.md)\n- [Crowdin vs Localazy](https://www.anchorterminal.com/compare/crowdin-vs-localazy.md)\n- [DeepL API vs Lingo.dev](https://www.anchorterminal.com/compare/deepl-api-vs-lingo-dev.md)\n- [DeepL API vs Localazy](https://www.anchorterminal.com/compare/deepl-api-vs-localazy.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 Localazy](https://www.anchorterminal.com/compare/google-cloud-translation-vs-localazy.md)\n- [Lara Translate API vs Lingo.dev](https://www.anchorterminal.com/compare/lara-translate-vs-lingo-dev.md)\n- [Lara Translate API vs Localazy](https://www.anchorterminal.com/compare/lara-translate-vs-localazy.md)\n- [LibreTranslate vs Lingo.dev](https://www.anchorterminal.com/compare/libretranslate-vs-lingo-dev.md)\n- [LibreTranslate vs Localazy](https://www.anchorterminal.com/compare/libretranslate-vs-localazy.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- [Lingo.dev vs Phrase](https://www.anchorterminal.com/compare/lingo-dev-vs-phrase.md)\n- [Lingo.dev vs Smartcat](https://www.anchorterminal.com/compare/lingo-dev-vs-smartcat.md)\n- [Lingo.dev vs SYSTRAN Translate API](https://www.anchorterminal.com/compare/lingo-dev-vs-systran.md)\n- [Lingo.dev vs TranslatePlus](https://www.anchorterminal.com/compare/lingo-dev-vs-translateplus.md)\n- [Lingvanex Translation API vs Localazy](https://www.anchorterminal.com/compare/lingvanex-vs-localazy.md)\n- [Localazy vs Lokalise](https://www.anchorterminal.com/compare/localazy-vs-lokalise.md)\n- [Localazy vs Phrase](https://www.anchorterminal.com/compare/localazy-vs-phrase.md)\n- [Localazy vs Smartcat](https://www.anchorterminal.com/compare/localazy-vs-smartcat.md)\n- [Localazy vs SYSTRAN Translate API](https://www.anchorterminal.com/compare/localazy-vs-systran.md)\n- [Localazy vs TranslatePlus](https://www.anchorterminal.com/compare/localazy-vs-translateplus.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-07", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Lingo.dev vs Localazy", "url": "" } ], "description": "Lingo.dev scores 66.1 (B) to Localazy's 54.4 (C) for translation. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Lingo.dev B 66.1", "Localazy C 54.4", "scores" ], "h1": "Lingo.dev vs Localazy", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/lingo-dev-vs-localazy", "published": "2026-10-01", "section": "tools", "title": "Lingo.dev vs Localazy for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/lingo-dev-vs-localazy" }, "tokens": { "markdown": 5000, "slim": 3130 }, "version": 1 }