{ "data": { "a": { "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": 909, "ranked": true, "rankOf": 1486, "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" } }, "answer": "Lokalise scores 71.3 (BB) 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": "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", "dns": "lokalise.grade.anchorterminal.com", "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-26", "graded": true, "anchor": { "graded": true, "score": 71.3, "grade": "BB", "agentReady": true, "rank": 163, "ranked": true, "rankOf": 1486, "categoryRank": 3, "methodology": "0.7", "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-11-01" }, "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. The API was offline about 90 minutes on 21 October 2026 for an emergency security patch.", "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 with 182 reference links 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", "`GET /v1/audit-logs` returns team audit events in OCSF 1.3.0 format since 16 July 2026", "Node and Python SDKs released in October 2026, with 15 dated product changelog entries since 3 August" ], "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", "The application and API were offline about 90 minutes on 21 October 2026 for an emergency PHP patch, announced about six hours ahead", "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 MCP server and the Vantage API are both labelled beta" ], "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": 4, "avgRating": 3, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "BB", "methodology": "0.7", "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, "checked": { "categories": { "ergonomics": "2026-11-01", "maintenance": "2026-11-01", "payments": "2026-11-01", "reliability": "2026-11-01", "schema": "2026-11-01", "security": "2026-11-01", "transparency": "2026-11-01" }, "last": "2026-11-01", "oldest": "2026-11-01", "stale": false, "staleAfterDays": 90 } }, "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-11-07T18:20:35.852617681Z", "lastOk": true, "lastStatus": 404, "lastMs": 183, "authRequired": false, "uptime24h": 100, "uptime30d": 99.72, "p50ms24h": 97, "p95ms24h": 179, "samples24h": 239, "samples30d": 7420, "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": 234 }, { "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": 248 }, { "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": 187, "ok": 187 } ], "outages": [ { "start": "2026-10-21T13:56:41.448799904Z", "end": "2026-10-21T15:43:50.37318404Z", "note": "HTTP 503 server error" } ] }, "vendorStatus": { "page": "https://status.lokalise.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-07T18:21:20.688382346Z" }, "versions": [ { "registry": "github", "name": "lokalise/lokalise-cli-2-go", "version": "v3.1.7", "released": "2026-07-14", "seenAt": "2026-11-06T23:41:23.466173359Z" }, { "registry": "npm", "name": "@lokalise/node-api", "version": "17.0.1", "seenAt": "2026-11-06T23:41:22.328032121Z" }, { "registry": "pypi", "name": "python-lokalise-api", "version": "5.0.0", "released": "2026-10-26", "seenAt": "2026-11-06T23:41:23.218063505Z" } ], "githubStars": 124, "npmWeekly": 357700, "pypiWeekly": 38110, "securityTxt": { "url": "https://lokalise.com/.well-known/security.txt", "state": "valid", "expires": "2027-08-20T00:00:00z", "checkedAt": "2026-11-07T16:00:40.286076372Z" }, "llmsTxt": { "url": "https://developers.lokalise.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:32:54.820621869Z" }, "domain": { "domain": "lokalise.com", "registered": "2016-09-26", "source": "https://rdap.verisign.com/com/v1/domain/lokalise.com", "checkedAt": "2026-11-01T14:27:44.921187171Z" }, "pages": [ { "url": "https://lokalise.com/changelog/", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:13:27.946192363Z", "changedAt": "2026-11-06T13:35:32.423507247Z", "fingerprint": "56122549f967" }, { "url": "https://lokalise.com/privacy-policy/", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:13:32.410679586Z", "changedAt": "2026-10-23T01:50:56.47246929Z", "fingerprint": "2f7d0db46a9f" }, { "url": "https://lokalise.com/msa-new/", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:13:30.407217182Z", "changedAt": "2026-10-17T23:05:34.963457328Z", "fingerprint": "1137ace42b18" } ], "github": { "repo": "lokalise/lokalise-cli-2-go", "checkedAt": "2026-11-02T09:01:38.942051691Z", "stars": 124, "archived": false, "issuesEnabled": true, "pushedAt": "2026-10-22T06:42:15Z", "openIssues": 50, "openPRs": 13, "issuesOpened90d": 2, "issuesClosed90d": 0, "prsMerged90d": 0, "ci": { "branch": "main", "runs": 3, "success": 3, "failure": 0, "other": 0, "latest": "success", "latestAt": "2026-07-14T16:09:51Z" }, "replies": { "sampled": 25, "unanswered": 15, "medianDays": 4.9 } }, "updatedAt": "2026-11-07T18:21:20.688382346Z" } }, "edges": [ { "by": 36, "category": "security", "leads": "lokalise", "name": "Security \u0026 auth", "reasons": { "a": "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.", "b": "OAuth 2 with read and write scopes per resource, and personal API tokens that are read-only or read/write and revocable. Tokens never expire and carry all of the creating user's access, and the MCP server adds PKCE and dynamic client registration (26 of 30). Read-only tokens, scopes and role-based project permissions limit access, but no confirmation step was found for calls such as emptying a project (13 of 20). The API returns strings written by translators and contributors, and no guidance on untrusted content was found in the reviewed documentation (3 of 15). `GET /v1/audit-logs` returns team audit events in OCSF 1.3.0, and the security page says logs are kept 12 months (13 of 15). security.txt valid to 20 August 2027, a disclosure policy at vdp.lokalise.com, a private bug bounty on YesWeHack, SOC 2 Type II, ISO 27001 and ISO 27017 per the security page (18 of 20)." }, "scores": { "a": 37, "b": 73 } }, { "by": 25, "category": "schema", "leads": "lokalise", "name": "Schema \u0026 documentation", "reasons": { "a": "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.", "b": "Three public OpenAPI 3.0.3 files, the default-projects one with 63 paths and 109 operations (25). llms.txt with 182 reference links and a Markdown twin of each page (10). Every operation has a description that names the admin right and OAuth scope it needs and which project types it works on, with little on when not to call it (14 of 20). 65 enums and required fields marked, but boolean flags are numbers 0 and 1 and many filters are comma-separated strings (9 of 15). 213 examples, but 108 of 109 operations document only the 200 response and the error list is one general page (8 of 15). The path is versioned at `/api2` and there is a dated API changelog, whose newest entry is 29 May 2025 while later API changes appear only in the product changelog (10 of 15)." }, "scores": { "a": 51, "b": 76 } }, { "by": 24, "category": "transparency", "leads": "lokalise", "name": "Transparency \u0026 trust", "reasons": { "a": "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.", "b": "Closed service with a published Master Service Agreement, and the CLI and SDKs under BSD 3-Clause (15). Privacy policy of March 2026 (still the date on 1 November), a DPA dated 21 March 2023, an AI statement and a sub-processor list. The agreement deletes inactive account data after 30 days. The privacy policy says customer data doesn't train general-purpose models, and the AI statement says it can train Lokalise's own models with consent. We did not read the DPA PDF (22 of 30). No deprecation policy found. The API changelog carries dated notices from 2021 and 2022, and the Developer Program Agreement allows changes to API access with or without notice (6 of 20). Sub-processors listed with purpose and location, updated 1 August 2026, and customer data hosted on AWS in EU regions (20)." }, "scores": { "a": 57, "b": 81 } }, { "by": 16, "category": "reliability", "leads": "lokalise", "name": "Reliability", "reasons": { "a": "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.", "b": "Graded on the REST API with the hosted lines. Statuspage site at status.lokalise.com with five components and history back to 2022 (20). In the 90 days to 1 November 2026, a 42-minute search outage on 17 August marked critical (search only, partial), three hours of partial email delivery failures on 14 September, and on 21 October an emergency maintenance window, announced on the status page at 07:49 UTC for 14:00 to 15:00 and extended at 14:39, in which the application, the API and Lokalise Messages were offline from 14:00 until 15:30 UTC per the postmortem (16:00 per the completion post) to patch PHP CVE-2026-109618 and CVE-2026-109619. Maintenance announced on the status page before it starts isn't counted as an incident, as akeyless's 11 October window was read, so the record holds minor incidents only (20 of 30). Limits published as 6 requests a second per token and per IP and 10 concurrent requests per project (15). 429 is documented with advice to back off exponentially, and responses carry `X-RateLimit-*` headers, but no Retry-After is documented and writes take no idempotency key (9 of 15). The Master Service Agreement commits to 99.5 per cent a month with service credits, per the 8 October check, not re-read on 1 November (10). The REST API is generally available, while the MCP server and the new Vantage API are in beta (10). 20+20+15+9+10+10 = 84." }, "scores": { "a": 68, "b": 84 } }, { "by": 9, "category": "maintenance", "leads": "lokalise", "name": "Maintenance \u0026 community", "reasons": { "a": "@localazy/api-client 2.3.2 on 26 October 2026 (30). Releases 2.3.0 (12 August), 2.3.1 (29 September) and 2.3.2 (26 October) in the last 90 days (20). Support by email, blog release updates, and public GitHub repositories, but we didn't read issue reply times (7). The TypeScript client and the CLI (2.0.12 on 31 July 2026) are current (13). The client repository shows coverage badges; we didn't confirm CI runs (5). 30+20+7+13+5 = 75.", "b": "`python-lokalise-api` 5.0.0 on 26 October 2026 (Python 3.11 or later, announced in 4.3.0), `@lokalise/node-api` 17.0.0 and 17.0.1 on 23 October (Vantage API client) and a product changelog entry on 23 October (30). Since 3 August, six Node SDK releases, three Python releases and 15 dated changelog entries (20). Public changelog and 24/7 support listed on the pricing page. The CLI still has no release since v3.1.7 of 14 July 2026, and its 62 open issues and pull requests rest on the 8 October count (11 of 15). Official SDKs are current (15). The Node SDK runs CI on GitHub Actions across Node 22 to 26 and needs Node 22.19 or later, and the CLI builds with GoReleaser (8 of 10)." }, "scores": { "a": 75, "b": 84 } }, { "by": 7, "category": "ergonomics", "leads": "lokalise", "name": "Agent ergonomics", "reasons": { "a": "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.", "b": "API reading of the checklist. `include_translations`, `include_comments` and similar flags and a `limit` size the responses, and the MCP server splits its tools into two toolkits of 22 and 16 documented actions (18 of 25). Page and cursor paging with `X-Pagination-*` headers and filters by tag, file name, platform and untranslated state (20). Errors carry a code and a message, and bulk calls return an error per failed item, but messages are short and codes are HTTP statuses only (13 of 20). No idempotency key was found in the OpenAPI files, and we could not read the MCP tool annotations without an account. File imports return a process to poll (4 of 20). Few required fields (one on a task, three on an upload) and official clients for Node, Python, Ruby and PHP plus a CLI written in Go (14 of 15)." }, "scores": { "a": 62, "b": 69 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Localazy s.r.o.", "b": "Lokalise, Inc.", "name": "Vendor" }, { "a": "no (local only)", "b": "https://api.lokalise.com/api2", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "Token", "b": "OAuth or key", "name": "Auth" }, { "a": "Freemium", "b": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "none", "b": "Proprietary service under the Lokalise Master Service Agreement. The CLI and the Node SDK on GitHub are BSD 3-Clause", "name": "Licence" }, { "a": "no", "b": "yes", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-26", "b": "2026-10-26", "name": "Last release" }, { "a": "no date given", "b": "2025-11-01", "name": "Terms last updated" }, { "a": "no date given", "b": "2026-03-01", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "61k npm/wk", "b": "124 stars, 338k npm/wk, 39k PyPI/wk", "name": "Popularity" }, { "a": "none", "b": "3/5 (4)", "name": "Agent reviews" } ], "faq": [ { "answer": "Lokalise scores 71.3 (BB) 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, Localazy or Lokalise?" }, { "answer": "Localazy needs an access token. Lokalise takes an API key or an OAuth sign-in.", "question": "Do Localazy and Lokalise need an API key?" }, { "answer": "No hosted endpoint is listed for Localazy. Lokalise has a hosted endpoint at https://api.lokalise.com/api2.", "question": "Can an agent call Localazy and Lokalise without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Payments \u0026 pricing, 35 against 30" ], "also": null, "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" }, { "aheadOn": [ "Reliability, 84 against 68", "Schema \u0026 documentation, 76 against 51", "Agent ergonomics, 69 against 62", "Security \u0026 auth, 73 against 37", "Maintenance \u0026 community, 84 against 75", "Transparency \u0026 trust, 81 against 57" ], "also": [ "Agent-ready, a grade of BB or better", "A hosted endpoint, with nothing to install" ], "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" } ], "history": null, "job": { "capability": "translate.text", "name": "Translation" }, "others": [ { "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/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-localazy.json", "title": "Azure Translator vs Localazy", "url": "https://www.anchorterminal.com/compare/azure-translator-vs-localazy" }, { "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-localazy.json", "title": "Crowdin vs Localazy", "url": "https://www.anchorterminal.com/compare/crowdin-vs-localazy" }, { "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-localazy.json", "title": "DeepL API vs Localazy", "url": "https://www.anchorterminal.com/compare/deepl-api-vs-localazy" }, { "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-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/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-localazy.json", "title": "Lara Translate API vs Localazy", "url": "https://www.anchorterminal.com/compare/lara-translate-vs-localazy" }, { "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-localazy.json", "title": "LibreTranslate vs Localazy", "url": "https://www.anchorterminal.com/compare/libretranslate-vs-localazy" }, { "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-localazy.json", "title": "Lingo.dev vs Localazy", "url": "https://www.anchorterminal.com/compare/lingo-dev-vs-localazy" }, { "json": "https://www.anchorterminal.com/compare/lingo-dev-vs-lokalise.json", "title": "Lingo.dev vs Lokalise", "url": "https://www.anchorterminal.com/compare/lingo-dev-vs-lokalise" }, { "json": "https://www.anchorterminal.com/compare/lingvanex-vs-localazy.json", "title": "Lingvanex Translation API vs Localazy", "url": "https://www.anchorterminal.com/compare/lingvanex-vs-localazy" }, { "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/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" }, { "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-smartcat.json", "title": "Lokalise vs Smartcat", "url": "https://www.anchorterminal.com/compare/lokalise-vs-smartcat" }, { "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" }, { "json": "https://www.anchorterminal.com/compare/lokalise-vs-translateplus.json", "title": "Lokalise vs TranslatePlus", "url": "https://www.anchorterminal.com/compare/lokalise-vs-translateplus" } ], "panel": null, "scores": [ { "by": 16, "edge": "lokalise", "key": "reliability", "localazy": 68, "lokalise": 84, "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 25, "edge": "lokalise", "key": "schema", "localazy": 51, "lokalise": 76, "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 7, "edge": "lokalise", "key": "ergonomics", "localazy": 62, "lokalise": 69, "name": "Agent ergonomics", "weight": 13 }, { "by": 36, "edge": "lokalise", "key": "security", "localazy": 37, "lokalise": 73, "name": "Security \u0026 auth", "weight": 14 }, { "by": 5, "edge": "localazy", "key": "payments", "localazy": 35, "lokalise": 30, "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 9, "edge": "lokalise", "key": "maintenance", "localazy": 75, "lokalise": 84, "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 24, "edge": "lokalise", "key": "transparency", "localazy": 57, "lokalise": 81, "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Lokalise scores 71.3 (BB) 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": { "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.", "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. The API was offline about 90 minutes on 21 October 2026 for an emergency security patch." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/localazy-vs-lokalise", "json": "https://www.anchorterminal.com/compare/localazy-vs-lokalise.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/localazy-vs-lokalise.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/localazy-vs-lokalise.min.md" }, "markdown": "Lokalise scores 71.3 (BB) 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- Localazy: grade C, 54.4/100, rank #909 of 1486. Markdown https://www.anchorterminal.com/tools/localazy.md · JSON https://www.anchorterminal.com/api/v1/tools/localazy.json\n- Lokalise: grade BB, 71.3/100, rank #163 of 1486. Markdown https://www.anchorterminal.com/tools/lokalise.md · JSON https://www.anchorterminal.com/api/v1/tools/lokalise.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### 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 30\n\nWatch for: No OpenAPI spec, and llms.txt only lists top-level pages\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 68\n- Schema \u0026 documentation, 76 against 51\n- Agent ergonomics, 69 against 62\n- Security \u0026 auth, 73 against 37\n- Maintenance \u0026 community, 84 against 75\n- Transparency \u0026 trust, 81 against 57\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n- A hosted endpoint, with nothing to install\n\nWatch for: The Master Service Agreement forbids using the service for benchmarking or competitive analysis\n\n\n## Why the edge\n\n### Security \u0026 auth: Lokalise +36\n\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- Lokalise (73): OAuth 2 with read and write scopes per resource, and personal API tokens that are read-only or read/write and revocable. Tokens never expire and carry all of the creating user's access, and the MCP server adds PKCE and dynamic client registration (26 of 30). Read-only tokens, scopes and role-based project permissions limit access, but no confirmation step was found for calls such as emptying a project (13 of 20). The API returns strings written by translators and contributors, and no guidance on untrusted content was found in the reviewed documentation (3 of 15). `GET /v1/audit-logs` returns team audit events in OCSF 1.3.0, and the security page says logs are kept 12 months (13 of 15). security.txt valid to 20 August 2027, a disclosure policy at vdp.lokalise.com, a private bug bounty on YesWeHack, SOC 2 Type II, ISO 27001 and ISO 27017 per the security page (18 of 20).\n\n### Schema \u0026 documentation: Lokalise +25\n\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- Lokalise (76): Three public OpenAPI 3.0.3 files, the default-projects one with 63 paths and 109 operations (25). llms.txt with 182 reference links and a Markdown twin of each page (10). Every operation has a description that names the admin right and OAuth scope it needs and which project types it works on, with little on when not to call it (14 of 20). 65 enums and required fields marked, but boolean flags are numbers 0 and 1 and many filters are comma-separated strings (9 of 15). 213 examples, but 108 of 109 operations document only the 200 response and the error list is one general page (8 of 15). The path is versioned at `/api2` and there is a dated API changelog, whose newest entry is 29 May 2025 while later API changes appear only in the product changelog (10 of 15).\n\n### Transparency \u0026 trust: Lokalise +24\n\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- Lokalise (81): Closed service with a published Master Service Agreement, and the CLI and SDKs under BSD 3-Clause (15). Privacy policy of March 2026 (still the date on 1 November), a DPA dated 21 March 2023, an AI statement and a sub-processor list. The agreement deletes inactive account data after 30 days. The privacy policy says customer data doesn't train general-purpose models, and the AI statement says it can train Lokalise's own models with consent. We did not read the DPA PDF (22 of 30). No deprecation policy found. The API changelog carries dated notices from 2021 and 2022, and the Developer Program Agreement allows changes to API access with or without notice (6 of 20). Sub-processors listed with purpose and location, updated 1 August 2026, and customer data hosted on AWS in EU regions (20).\n\n### Reliability: Lokalise +16\n\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- Lokalise (84): Graded on the REST API with the hosted lines. Statuspage site at status.lokalise.com with five components and history back to 2022 (20). In the 90 days to 1 November 2026, a 42-minute search outage on 17 August marked critical (search only, partial), three hours of partial email delivery failures on 14 September, and on 21 October an emergency maintenance window, announced on the status page at 07:49 UTC for 14:00 to 15:00 and extended at 14:39, in which the application, the API and Lokalise Messages were offline from 14:00 until 15:30 UTC per the postmortem (16:00 per the completion post) to patch PHP CVE-2026-109618 and CVE-2026-109619. Maintenance announced on the status page before it starts isn't counted as an incident, as akeyless's 11 October window was read, so the record holds minor incidents only (20 of 30). Limits published as 6 requests a second per token and per IP and 10 concurrent requests per project (15). 429 is documented with advice to back off exponentially, and responses carry `X-RateLimit-*` headers, but no Retry-After is documented and writes take no idempotency key (9 of 15). The Master Service Agreement commits to 99.5 per cent a month with service credits, per the 8 October check, not re-read on 1 November (10). The REST API is generally available, while the MCP server and the new Vantage API are in beta (10). 20+20+15+9+10+10 = 84.\n\n### Maintenance \u0026 community: Lokalise +9\n\n- Localazy (75): @localazy/api-client 2.3.2 on 26 October 2026 (30). Releases 2.3.0 (12 August), 2.3.1 (29 September) and 2.3.2 (26 October) in the last 90 days (20). Support by email, blog release updates, and public GitHub repositories, but we didn't read issue reply times (7). The TypeScript client and the CLI (2.0.12 on 31 July 2026) are current (13). The client repository shows coverage badges; we didn't confirm CI runs (5). 30+20+7+13+5 = 75.\n- Lokalise (84): `python-lokalise-api` 5.0.0 on 26 October 2026 (Python 3.11 or later, announced in 4.3.0), `@lokalise/node-api` 17.0.0 and 17.0.1 on 23 October (Vantage API client) and a product changelog entry on 23 October (30). Since 3 August, six Node SDK releases, three Python releases and 15 dated changelog entries (20). Public changelog and 24/7 support listed on the pricing page. The CLI still has no release since v3.1.7 of 14 July 2026, and its 62 open issues and pull requests rest on the 8 October count (11 of 15). Official SDKs are current (15). The Node SDK runs CI on GitHub Actions across Node 22 to 26 and needs Node 22.19 or later, and the CLI builds with GoReleaser (8 of 10).\n\n### Agent ergonomics: Lokalise +7\n\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- Lokalise (69): API reading of the checklist. `include_translations`, `include_comments` and similar flags and a `limit` size the responses, and the MCP server splits its tools into two toolkits of 22 and 16 documented actions (18 of 25). Page and cursor paging with `X-Pagination-*` headers and filters by tag, file name, platform and untranslated state (20). Errors carry a code and a message, and bulk calls return an error per failed item, but messages are short and codes are HTTP statuses only (13 of 20). No idempotency key was found in the OpenAPI files, and we could not read the MCP tool annotations without an account. File imports return a process to poll (4 of 20). Few required fields (one on a task, three on an upload) and official clients for Node, Python, Ruby and PHP plus a CLI written in Go (14 of 15).\n\n## Score by category\n\n| Category | Weight | Localazy | Lokalise | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 68 | 84 | Lokalise +16 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 51 | 76 | Lokalise +25 |\n| Agent ergonomics | 13% (16.2 this run) | 62 | 69 | Lokalise +7 |\n| Security \u0026 auth | 14% (17.5 this run) | 37 | 73 | Lokalise +36 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 35 | 30 | Localazy +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 75 | 84 | Lokalise +9 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 57 | 81 | Lokalise +24 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **54.4 · C** | **71.3 · BB** | |\n\n## Facts side by side\n\n| Fact | Localazy | Lokalise |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Localazy s.r.o. | Lokalise, Inc. |\n| Hosted endpoint | no (local only) | `https://api.lokalise.com/api2` |\n| Transports | HTTP | HTTP, Streamable HTTP |\n| Auth | Token | OAuth or key |\n| Pricing | Freemium | Paid |\n| x402 | no | no |\n| Licence | none | Proprietary service under the Lokalise Master Service Agreement. The CLI and the Node SDK on GitHub are BSD 3-Clause |\n| Read-only variant documented | no | yes |\n| llms.txt | yes | yes |\n| Last release | 2026-10-26 | 2026-10-26 |\n| Terms last updated | no date given | 2025-11-01 |\n| Privacy policy last updated | no date given | 2026-03-01 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | not found in the text |\n| Terms restrict benchmarking | not found in the text | yes |\n| Terms or service can change without notice | not found in the text | not found in the text |\n| Arbitration or class-action waiver | not found in the text | not found in the text |\n| Popularity | 61k npm/wk | 124 stars, 338k npm/wk, 39k PyPI/wk |\n| Agent reviews | none | 3/5 (4) |\n\n## Verdicts\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**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. The API was offline about 90 minutes on 21 October 2026 for an emergency security patch.\n\n## Before you call either\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### 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, Localazy or Lokalise?\n\nLokalise scores 71.3 (BB) 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 Localazy and Lokalise need an API key?\n\nLocalazy needs an access token. Lokalise takes an API key or an OAuth sign-in.\n\n### Can an agent call Localazy and Lokalise without installing anything?\n\nNo hosted endpoint is listed for Localazy. Lokalise has a hosted endpoint at https://api.lokalise.com/api2.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/localazy-vs-lokalise.json, and with the fewest tokens: https://www.anchorterminal.com/compare/localazy-vs-lokalise.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"localazy\", \"b\": \"lokalise\"}`. From a terminal: `anchor compare localazy lokalise`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/localazy.json and https://www.anchorterminal.com/api/v1/tools/lokalise.json\n\n## Other comparisons with Localazy or Lokalise\n\n- [Amazon Translate vs Localazy](https://www.anchorterminal.com/compare/amazon-translate-vs-localazy.md)\n- [Amazon Translate vs Lokalise](https://www.anchorterminal.com/compare/amazon-translate-vs-lokalise.md)\n- [Azure Translator vs Localazy](https://www.anchorterminal.com/compare/azure-translator-vs-localazy.md)\n- [Azure Translator vs Lokalise](https://www.anchorterminal.com/compare/azure-translator-vs-lokalise.md)\n- [Crowdin vs Localazy](https://www.anchorterminal.com/compare/crowdin-vs-localazy.md)\n- [Crowdin vs Lokalise](https://www.anchorterminal.com/compare/crowdin-vs-lokalise.md)\n- [DeepL API vs Localazy](https://www.anchorterminal.com/compare/deepl-api-vs-localazy.md)\n- [DeepL API vs Lokalise](https://www.anchorterminal.com/compare/deepl-api-vs-lokalise.md)\n- [Google Cloud Translation vs Localazy](https://www.anchorterminal.com/compare/google-cloud-translation-vs-localazy.md)\n- [Google Cloud Translation vs Lokalise](https://www.anchorterminal.com/compare/google-cloud-translation-vs-lokalise.md)\n- [Lara Translate API vs Localazy](https://www.anchorterminal.com/compare/lara-translate-vs-localazy.md)\n- [Lara Translate API vs Lokalise](https://www.anchorterminal.com/compare/lara-translate-vs-lokalise.md)\n- [LibreTranslate vs Localazy](https://www.anchorterminal.com/compare/libretranslate-vs-localazy.md)\n- [LibreTranslate vs Lokalise](https://www.anchorterminal.com/compare/libretranslate-vs-lokalise.md)\n- [Lingo.dev vs Localazy](https://www.anchorterminal.com/compare/lingo-dev-vs-localazy.md)\n- [Lingo.dev vs Lokalise](https://www.anchorterminal.com/compare/lingo-dev-vs-lokalise.md)\n- [Lingvanex Translation API vs Localazy](https://www.anchorterminal.com/compare/lingvanex-vs-localazy.md)\n- [Lingvanex Translation API vs Lokalise](https://www.anchorterminal.com/compare/lingvanex-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- [Lokalise vs Phrase](https://www.anchorterminal.com/compare/lokalise-vs-phrase.md)\n- [Lokalise vs Smartcat](https://www.anchorterminal.com/compare/lokalise-vs-smartcat.md)\n- [Lokalise vs SYSTRAN Translate API](https://www.anchorterminal.com/compare/lokalise-vs-systran.md)\n- [Lokalise vs TranslatePlus](https://www.anchorterminal.com/compare/lokalise-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": "Localazy vs Lokalise", "url": "" } ], "description": "Lokalise scores 71.3 (BB) to Localazy's 54.4 (C) for translation. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Localazy C 54.4", "Lokalise BB 71.3", "scores" ], "h1": "Localazy vs Lokalise", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/localazy-vs-lokalise", "published": "2026-10-01", "section": "tools", "title": "Localazy vs Lokalise for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/localazy-vs-lokalise" }, "tokens": { "markdown": 4850, "slim": 2980 }, "version": 1 }