{ "data": { "a": { "slug": "lokalise", "name": "Lokalise", "vendor": "Lokalise, Inc.", "vendorUrl": "https://lokalise.com", "kind": "http-api", "category": "translation", "summary": "Lokalise is a hosted translation management system for software strings, documents and marketing content. Agents reach it through a REST API, the `lokalise2` CLI, SDKs in four languages and a hosted MCP server in beta.", "url": "https://www.anchorterminal.com/tools/lokalise", "markdownUrl": "https://www.anchorterminal.com/tools/lokalise.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/lokalise.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/lokalise.json", "repo": "https://github.com/lokalise/lokalise-cli-2-go", "license": "Proprietary service under the Lokalise Master Service Agreement. The CLI and the Node SDK on GitHub are BSD 3-Clause", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://api.lokalise.com/api2", "packages": [ { "registry": "npm", "name": "@lokalise/node-api" }, { "registry": "pypi", "name": "python-lokalise-api" }, { "registry": "go", "name": "github.com/lokalise/lokalise-cli-2-go" } ], "auth": "mixed", "authNotes": "Self-serve. A user creates a personal API token under Profile settings, read-only or read/write, and sends it in the `X-Api-Token` header. Tokens don't expire, can be deleted, and carry the creating user's project access. OAuth 2 for the API needs an app registered through Lokalise support, with scopes such as `read_keys` and `write_projects`. The MCP server takes OAuth with dynamic client registration, or an API token in the `apikey` header.", "pricing": "paid", "pricingNotes": "Explorer $149, Growth $379 and Advanced $1,049 a month billed yearly, Enterprise by quote. Monthly-billing prices load only in a browser and were not read. Every plan starts with a 14-day trial with no card, so an agent can start without a contract. There is no free plan except for open-source non-profit projects on request. The MCP article says API access depends on the plan, and the page did not show which plans include it (checked 2026-10-08).", "priceSummary": "$149 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the developer docs, the OpenAPI files or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 124, "npmWeekly": 337721, "pypiWeekly": 39399, "asOf": "2026-10-08" }, "docsUrl": "https://developers.lokalise.com", "llmsTxt": "https://developers.lokalise.com/llms.txt", "openapi": "https://developers.lokalise.com/openapi/lokalise-api-without-branches.yml", "capabilities": [ "translate.text", "translate.glossary", "translate.documents" ], "tags": [ "hosted", "official", "closed-source", "mcp", "oauth", "openapi", "llms-txt", "webhooks", "cli", "typescript", "python", "no-card", "status-page", "soc2" ], "lastRelease": "2026-10-05", "graded": true, "anchor": { "graded": true, "score": 71.3, "grade": "BB", "agentReady": true, "rank": 115, "ranked": true, "rankOf": 722, "categoryRank": 3, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 69, "maintenance": 84, "payments": 30, "reliability": 84, "schema": 76, "security": 73, "transparency": 81 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "The REST API has public OpenAPI files, Markdown docs, published rate limits, read-only tokens, scoped OAuth and an audit log endpoint. Access needs a paid plan after a 14-day trial, a person signs up in a browser, and the Master Service Agreement forbids benchmarking. No idempotency keys or deprecation policy were found in the reviewed documentation.", "bestFor": "Agents that manage localisation work, such as adding keys, uploading and exporting string files, keeping a glossary and starting AI or machine translation tasks for a team that already uses Lokalise.", "strengths": [ "Three public OpenAPI 3.0.3 files, llms.txt and a Markdown twin of every reference page", "Rate limits published as 6 requests a second per token and per IP, with 10 concurrent requests per project", "API tokens are read-only or read/write, and OAuth 2 carries read and write scopes per resource", "The MCP server signs in with OAuth, PKCE and dynamic client registration, and lists 22 scopes", "`GET /v1/audit-logs` returns team audit events in OCSF 1.3.0 format since 16 July 2026" ], "weaknesses": [ "The Master Service Agreement forbids using the service for benchmarking or competitive analysis", "No free plan. Explorer is $149 a month billed yearly after a 14-day trial without a card", "No idempotency keys in the OpenAPI files, though the errors page mentions an idempotent key under 409", "API tokens never expire and carry every permission of the user who made them", "The Developer Program Agreement lets Lokalise change or end API access with or without notice", "The MCP server is labelled beta in the help centre article" ], "agentNotes": [ "Send the token in the `X-Api-Token` header to `https://api.lokalise.com/api2`. OAuth access tokens go in `Authorization: Bearer` and expire after about 60 minutes.", "Stay under 6 requests a second per token and 10 concurrent requests per project. On 429, back off exponentially and read `X-RateLimit-Reset`.", "Use a read-only token for reads. A read/write token can call `PUT /projects/{project_id}/empty`, which deletes every key and translation.", "Use `pagination=cursor` on `/keys` and `/translations`, with `limit` at most 500 on keys, and follow `X-Pagination-Next-Cursor`.", "Projects above 10,000 key-language pairs need `/files/async-download`. Poll `/processes/{process_id}` for the bundle URL, and do the same after `/files/upload`." ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "BB", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 71.3 } ], "editorialScores": { "ergonomics": 69, "maintenance": 84, "payments": 30, "reliability": 84, "schema": 76, "security": 73, "transparency": 63 }, "provenanceScore": 98 }, "connect": { "install": "brew tap lokalise/cli-2\nbrew install lokalise2", "http": "curl \"https://api.lokalise.com/api2/projects?limit=5\" -H \"X-Api-Token: $LOKALISE_API_TOKEN\"", "claudeCode": "claude mcp add lokalise_pm --transport http https://mcp.lokalise.com/mcp/project-management", "config": { "lokalise_pm": { "url": "https://mcp.lokalise.com/mcp/project-management" }, "lokalise_sd": { "url": "https://mcp.lokalise.com/mcp/software-development" } } }, "letme": { "capability": "https://letme.dev/translate.text", "tool": "https://letme.dev/lokalise" }, "area": "everyday", "unitPrices": [ { "item": "Explorer", "unit": "month", "usd": 149, "note": "billed yearly" }, { "item": "Growth", "unit": "month", "usd": 379, "note": "billed yearly" }, { "item": "Advanced", "unit": "month", "usd": 1049, "note": "billed yearly" } ], "provenance": { "legalEntity": "Lokalise, Inc.", "domain": "lokalise.com", "domainRegistered": "2016-09-26", "endpointOnVendorDomain": true, "terms": "https://lokalise.com/msa-new/", "privacy": "https://lokalise.com/privacy-policy/", "statusPage": "https://status.lokalise.com", "changelog": "https://lokalise.com/changelog/", "securityTxt": "valid", "checked": "2026-10-08", "notes": [ "The Master Service Agreement (last updated November 2025) names Lokalise, Inc., a Delaware company at 3500 South DuPont Highway, Suite BZ-101, Dover, DE 19901. It governs paid subscriptions.", "Trial and individual users fall under the User and Trial Access Terms of Service at https://lokalise.com/terms-of-service/ (November 2025). API integrations published in the app library fall under the Developer Program Agreement at https://lokalise.com/dev-hub-terms/, which shows no date.", "The privacy policy (last updated March 2026) covers the website, platform and services, and says Lokalise is the processor for customer data.", "The API answers at api.lokalise.com and the MCP server at mcp.lokalise.com.", "https://lokalise.com/.well-known/security.txt gives vdp.lokalise.com and security@lokalise.com as contacts and expires on 20 August 2027.", "RDAP for lokalise.com gives a registration date of 2016-09-26." ], "score": 98 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/lokalise.json", "live": { "slug": "lokalise", "probe": { "target": "https://api.lokalise.com/api2", "method": "get", "lastAt": "2026-10-08T21:53:26.189197119Z", "lastOk": true, "lastStatus": 404, "lastMs": 146, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 91, "p95ms24h": 146, "samples24h": 28, "samples30d": 28, "days": [ { "date": "2026-10-08", "probes": 28, "ok": 28 } ] }, "vendorStatus": { "page": "https://status.lokalise.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-08T21:58:01.399678507Z" }, "updatedAt": "2026-10-08T21:58:01.399678507Z" } }, "answer": "Lokalise scores 71.3 (BB) on agent readiness against SYSTRAN Translate API's 40 (E), and leads in 6 of 7 scored categories. SYSTRAN Translate API leads on payments \u0026 pricing.", "b": { "slug": "systran", "name": "SYSTRAN Translate API", "vendor": "SYSTRAN (ChapsVision)", "vendorUrl": "https://www.systransoft.com", "kind": "http-api", "category": "translation", "summary": "Machine translation API from SYSTRAN, part of ChapsVision, for text and files in 55 languages, with user dictionaries, translation memories and translation profiles. Access needs an API key or OAuth token on a paid or trial subscription.", "url": "https://www.anchorterminal.com/tools/systran", "markdownUrl": "https://www.anchorterminal.com/tools/systran.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/systran.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/systran.json", "license": "Proprietary service under the SYSTRAN Translate PRO terms and conditions", "transports": [ "http" ], "remoteUrl": "https://api-translate.systran.net", "packages": [], "auth": "mixed", "authNotes": "An API key or an OAuth access token, both issued from the SYSTRAN Translate account. Keys go in `Authorization: Key \u003capi_key\u003e` or, as a documented option, in a `?key=` query parameter. Tokens come from client credentials or PKCE and go in `Authorization: Bearer`. Access is self-serve. A person signs up in a browser, and the API works only on the API, Premium or Infinite plans or the trial. No key scopes were found.", "pricing": "usage", "pricingNotes": "€14.99 per 1 million characters, billed monthly, on the developer pricing page (https://www.systransoft.com/pricing/developers/). A 14-day trial includes 500,000 characters and needs no credit card, so an agent's owner can start without a contract. The terms say API characters are billed by use above a minimum monthly commitment, whose size they don't state, and that prices are in dollars for North America. Enterprise plans are sold through sales.", "priceSummary": "Pay per use", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the API reference, the pricing page or the terms (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://docs.systran.net/translateAPI/en/", "capabilities": [ "translate.text", "translate.documents", "translate.glossary", "translate.detect" ], "tags": [ "hosted", "closed-source", "api-key", "oauth", "usage-priced", "free-trial", "no-card", "eu", "iso27001", "sla", "async-jobs", "batch", "enterprise" ], "lastRelease": "2023-06-16", "graded": true, "anchor": { "graded": true, "score": 40, "grade": "E", "agentReady": false, "rank": 691, "ranked": true, "rankOf": 722, "categoryRank": 11, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 54, "maintenance": 4, "payments": 40, "reliability": 25, "schema": 42, "security": 55, "transparency": 51 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "Five documented REST APIs cover text, files, dictionaries, translation memories and profiles, with a Google-compatible mode and a public price of €14.99 per million characters. The reference pages date from June 2023, and no changelog, status page, rate limit, SDK or downloadable OpenAPI file was found. The terms bar benchmark tests and automated use beyond human volumes.", "bestFor": "Teams that want European Union hosting, user dictionaries and translation memories applied through profiles, or the same API on an on-premises SYSTRAN server.", "strengths": [ "Text, file, dictionary, corpus and profile APIs, 60 documented operations in all, plus a mode that mirrors Google Translate v2 paths", "€14.99 per million characters is published without a login, and the 14-day trial of 500,000 characters needs no credit card", "The terms say content is destroyed once the translation is done, with a 72-hour encrypted exception for error analysis", "The terms place all stored data on servers in the European Union and promise one month's notice before a move", "The terms promise backward-compatible API changes and one month's email notice before an old API version is switched off" ], "weaknesses": [ "The terms forbid benchmark tests and automated access that exceeds normal human volumes, which matters for any agent workload", "No status page, changelog, llms.txt, SDK or downloadable OpenAPI file was found, and the reference pages were last modified on 16 June 2023", "No request rate limit, 429 response or retry guidance is documented. Only 400 and 500 appear in the reference", "The API key may travel in the URL as `?key=`, and no key scopes were found", "No privacy policy for the product. The terms link to a legal notice that points to ChapsVision's group policy" ], "agentNotes": [ "Send the key as `Authorization: Key \u003capi_key\u003e` and avoid the documented `?key=` query option, which puts the secret in URLs and logs", "Expect HTTP 400, not 401, when credentials are missing. The body reads `No key / credentials provided`", "Call `/translation/file/translate` with `async=true` for large files, then poll `/translation/file/status` and fetch `/translation/file/result` with the returned `requestId`", "Apply dictionaries and translation memories through a profile and pass its UUID as `profile`. `withDictionary` and `withCorpus` are deprecated", "Read the terms before automating. They bar benchmark tests and request volumes beyond normal human use, and SYSTRAN may throttle or suspend access" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "E", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 40 } ], "editorialScores": { "ergonomics": 54, "maintenance": 4, "payments": 40, "reliability": 25, "schema": 42, "security": 55, "transparency": 47 }, "provenanceScore": 54 }, "connect": { "http": "curl -X POST \"https://api-translate.systran.net/translation/text/translate?source=auto\u0026target=fr\u0026input=The%20table%20is%20booked%20for%20seven.\" \\\n -H \"Authorization: Key $SYSTRAN_API_KEY\"" }, "letme": { "capability": "https://letme.dev/translate.text", "tool": "https://letme.dev/systran" }, "area": "everyday", "provenance": { "legalEntity": "SYSTRAN SAS", "domain": "systran.net", "domainRegistered": "1997-09-08", "endpointOnVendorDomain": true, "terms": "https://www.systransoft.com/systran/terms-of-service-translate-pro/", "privacy": "", "statusPage": "", "changelog": "", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "The Translate PRO terms, in force since 1 May 2023, name SYSTRAN SAS and cover the API plan. The site's legal notice names Chapsvision SAS, 4 rue du Port aux Vins, 92150 Suresnes, as publisher.", "No privacy policy for the product was found, so the field is left out. The address the terms give, www.systransoft.com/systran/privacy-policy/, is a legal notice that links to ChapsVision's group policy at www.chapsvision.com/privacy-policies/.", "The API, the docs, the web app and the OpenID server are on systran.net (registered 1997-09-08 per RDAP). Marketing, pricing and terms are on systransoft.com (registered 1996-11-28).", "www.systransoft.com/.well-known/security.txt returns 404, and the API host returns its JSON error for that path.", "No status page or API changelog was found. Enterprise customers have separate terms at www.systransoft.com/systran/terms-of-service-translate-enterprise/." ], "score": 54 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/systran.json", "live": { "slug": "systran", "probe": { "target": "https://api-translate.systran.net", "method": "get", "lastAt": "2026-10-08T21:53:35.266972075Z", "lastOk": true, "lastStatus": 400, "lastMs": 91, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 93, "p95ms24h": 165, "samples24h": 28, "samples30d": 28, "days": [ { "date": "2026-10-08", "probes": 28, "ok": 28 } ] }, "updatedAt": "2026-10-08T21:53:35.266972075Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Lokalise, Inc.", "b": "SYSTRAN (ChapsVision)", "name": "Vendor" }, { "a": "https://api.lokalise.com/api2", "b": "https://api-translate.systran.net", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP", "b": "HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth or key", "name": "Auth" }, { "a": "Paid", "b": "Pay per use", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under the Lokalise Master Service Agreement. The CLI and the Node SDK on GitHub are BSD 3-Clause", "b": "Proprietary service under the SYSTRAN Translate PRO terms and conditions", "name": "Licence" }, { "a": "yes", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "no", "name": "llms.txt" }, { "a": "2026-10-05", "b": "2023-06-16", "name": "Last release" }, { "a": "2025-11-01", "b": "no date given", "name": "Terms last updated" }, { "a": "2026-03-01", "b": "no document linked", "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": "yes", "name": "Terms restrict automated access" }, { "a": "yes", "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": "124 stars, 338k npm/wk, 39k PyPI/wk", "b": "none", "name": "Popularity" } ], "faq": [ { "answer": "Lokalise scores 71.3 (BB) on agent readiness against SYSTRAN Translate API's 40 (E), and leads in 6 of 7 scored categories. SYSTRAN Translate API leads on payments \u0026 pricing.", "question": "Which is better for AI agents, Lokalise or SYSTRAN Translate API?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do Lokalise and SYSTRAN Translate API need an API key?" }, { "answer": "Yes. Lokalise has a hosted endpoint at https://api.lokalise.com/api2 and SYSTRAN Translate API at https://api-translate.systran.net.", "question": "Can an agent call Lokalise and SYSTRAN Translate API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 84 against 25", "Schema \u0026 documentation, 76 against 42", "Agent ergonomics, 69 against 54", "Security \u0026 auth, 73 against 55", "Maintenance \u0026 community, 84 against 4", "Transparency \u0026 trust, 81 against 51" ], "also": [ "Agent-ready, a grade of BB or better" ], "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" }, { "aheadOn": [ "Payments \u0026 pricing, 40 against 30" ], "also": null, "goodFor": "Teams that want European Union hosting, user dictionaries and translation memories applied through profiles, or the same API on an on-premises SYSTRAN server.", "slug": "systran", "watchFor": "The terms forbid benchmark tests and automated access that exceeds normal human volumes, which matters for any agent workload" } ], "job": { "capability": "translate.text", "name": "Translate text" }, "others": [ { "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/amazon-translate-vs-systran.json", "title": "Amazon Translate vs SYSTRAN Translate API", "url": "https://www.anchorterminal.com/compare/amazon-translate-vs-systran" }, { "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/azure-translator-vs-systran.json", "title": "Azure Translator vs SYSTRAN Translate API", "url": "https://www.anchorterminal.com/compare/azure-translator-vs-systran" }, { "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/crowdin-vs-systran.json", "title": "Crowdin vs SYSTRAN Translate API", "url": "https://www.anchorterminal.com/compare/crowdin-vs-systran" }, { "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/deepl-api-vs-systran.json", "title": "DeepL API vs SYSTRAN Translate API", "url": "https://www.anchorterminal.com/compare/deepl-api-vs-systran" }, { "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/google-cloud-translation-vs-systran.json", "title": "Google Cloud Translation vs SYSTRAN Translate API", "url": "https://www.anchorterminal.com/compare/google-cloud-translation-vs-systran" }, { "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/lara-translate-vs-systran.json", "title": "Lara Translate API vs SYSTRAN Translate API", "url": "https://www.anchorterminal.com/compare/lara-translate-vs-systran" }, { "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/libretranslate-vs-systran.json", "title": "LibreTranslate vs SYSTRAN Translate API", "url": "https://www.anchorterminal.com/compare/libretranslate-vs-systran" }, { "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-systran.json", "title": "Lingo.dev vs SYSTRAN Translate API", "url": "https://www.anchorterminal.com/compare/lingo-dev-vs-systran" }, { "json": "https://www.anchorterminal.com/compare/lingvanex-vs-lokalise.json", "title": "Lingvanex Translation API vs Lokalise", "url": "https://www.anchorterminal.com/compare/lingvanex-vs-lokalise" }, { "json": "https://www.anchorterminal.com/compare/lingvanex-vs-systran.json", "title": "Lingvanex Translation API vs SYSTRAN Translate API", "url": "https://www.anchorterminal.com/compare/lingvanex-vs-systran" }, { "json": "https://www.anchorterminal.com/compare/lokalise-vs-phrase.json", "title": "Lokalise vs Phrase", "url": "https://www.anchorterminal.com/compare/lokalise-vs-phrase" }, { "json": "https://www.anchorterminal.com/compare/phrase-vs-systran.json", "title": "Phrase vs SYSTRAN Translate API", "url": "https://www.anchorterminal.com/compare/phrase-vs-systran" } ], "scores": [ { "by": 59, "edge": "lokalise", "key": "reliability", "lokalise": 84, "name": "Reliability", "systran": 25, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 34, "edge": "lokalise", "key": "schema", "lokalise": 76, "name": "Schema \u0026 documentation", "systran": 42, "weight": 13 }, { "by": 15, "edge": "lokalise", "key": "ergonomics", "lokalise": 69, "name": "Agent ergonomics", "systran": 54, "weight": 13 }, { "by": 18, "edge": "lokalise", "key": "security", "lokalise": 73, "name": "Security \u0026 auth", "systran": 55, "weight": 14 }, { "by": 10, "edge": "systran", "key": "payments", "lokalise": 30, "name": "Payments \u0026 pricing", "systran": 40, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 80, "edge": "lokalise", "key": "maintenance", "lokalise": 84, "name": "Maintenance \u0026 community", "systran": 4, "weight": 7 }, { "by": 30, "edge": "lokalise", "key": "transparency", "lokalise": 81, "name": "Transparency \u0026 trust", "systran": 51, "weight": 7 } ], "summary": "Lokalise scores 71.3 (BB) on agent readiness against SYSTRAN Translate API's 40 (E), and leads in 6 of 7 scored categories. SYSTRAN Translate API leads on payments \u0026 pricing. Both do translate text.", "verdicts": { "lokalise": "The REST API has public OpenAPI files, Markdown docs, published rate limits, read-only tokens, scoped OAuth and an audit log endpoint. Access needs a paid plan after a 14-day trial, a person signs up in a browser, and the Master Service Agreement forbids benchmarking. No idempotency keys or deprecation policy were found in the reviewed documentation.", "systran": "Five documented REST APIs cover text, files, dictionaries, translation memories and profiles, with a Google-compatible mode and a public price of €14.99 per million characters. The reference pages date from June 2023, and no changelog, status page, rate limit, SDK or downloadable OpenAPI file was found. The terms bar benchmark tests and automated use beyond human volumes." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/lokalise-vs-systran", "json": "https://www.anchorterminal.com/compare/lokalise-vs-systran.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/lokalise-vs-systran.md", "slim": "https://www.anchorterminal.com/compare/lokalise-vs-systran.min.md" }, "markdown": "Lokalise scores 71.3 (BB) on agent readiness against SYSTRAN Translate API's 40 (E), and leads in 6 of 7 scored categories. SYSTRAN Translate API leads on payments \u0026 pricing. Both do translate text.\n\n- Lokalise: grade BB, 71.3/100, rank #115 of 722. Markdown https://www.anchorterminal.com/tools/lokalise.md · JSON https://www.anchorterminal.com/api/v1/tools/lokalise.json\n- SYSTRAN Translate API: grade E, 40/100, rank #691 of 722. Markdown https://www.anchorterminal.com/tools/systran.md · JSON https://www.anchorterminal.com/api/v1/tools/systran.json\n\n## Which one, for what\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 25\n- Schema \u0026 documentation, 76 against 42\n- Agent ergonomics, 69 against 54\n- Security \u0026 auth, 73 against 55\n- Maintenance \u0026 community, 84 against 4\n- Transparency \u0026 trust, 81 against 51\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n\nWatch for: The Master Service Agreement forbids using the service for benchmarking or competitive analysis\n\n### SYSTRAN Translate API (E)\n\nGood for: Teams that want European Union hosting, user dictionaries and translation memories applied through profiles, or the same API on an on-premises SYSTRAN server.\n\nAhead on:\n- Payments \u0026 pricing, 40 against 30\n\nWatch for: The terms forbid benchmark tests and automated access that exceeds normal human volumes, which matters for any agent workload\n\n\n## Score by category\n\n| Category | Weight | Lokalise | SYSTRAN Translate API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 84 | 25 | Lokalise +59 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 76 | 42 | Lokalise +34 |\n| Agent ergonomics | 13% (16.2 this run) | 69 | 54 | Lokalise +15 |\n| Security \u0026 auth | 14% (17.5 this run) | 73 | 55 | Lokalise +18 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 40 | SYSTRAN Translate API +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 84 | 4 | Lokalise +80 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 81 | 51 | Lokalise +30 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **71.3 · BB** | **40 · E** | |\n\n## Facts side by side\n\n| Fact | Lokalise | SYSTRAN Translate API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Lokalise, Inc. | SYSTRAN (ChapsVision) |\n| Hosted endpoint | `https://api.lokalise.com/api2` | `https://api-translate.systran.net` |\n| Transports | HTTP, Streamable HTTP | HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Paid | Pay per use |\n| x402 | no | no |\n| Licence | Proprietary service under the Lokalise Master Service Agreement. The CLI and the Node SDK on GitHub are BSD 3-Clause | Proprietary service under the SYSTRAN Translate PRO terms and conditions |\n| Read-only variant documented | yes | no |\n| llms.txt | yes | no |\n| Last release | 2026-10-05 | 2023-06-16 |\n| Terms last updated | 2025-11-01 | no date given |\n| Privacy policy last updated | 2026-03-01 | no document linked |\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 | yes |\n| Terms restrict benchmarking | yes | 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 | 124 stars, 338k npm/wk, 39k PyPI/wk | none |\n\n## Verdicts\n\n**Lokalise.** The REST API has public OpenAPI files, Markdown docs, published rate limits, read-only tokens, scoped OAuth and an audit log endpoint. Access needs a paid plan after a 14-day trial, a person signs up in a browser, and the Master Service Agreement forbids benchmarking. No idempotency keys or deprecation policy were found in the reviewed documentation.\n\n**SYSTRAN Translate API.** Five documented REST APIs cover text, files, dictionaries, translation memories and profiles, with a Google-compatible mode and a public price of €14.99 per million characters. The reference pages date from June 2023, and no changelog, status page, rate limit, SDK or downloadable OpenAPI file was found. The terms bar benchmark tests and automated use beyond human volumes.\n\n## Before you call either\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### SYSTRAN Translate API\n\n1. Send the key as `Authorization: Key \u003capi_key\u003e` and avoid the documented `?key=` query option, which puts the secret in URLs and logs\n2. Expect HTTP 400, not 401, when credentials are missing. The body reads `No key / credentials provided`\n3. Call `/translation/file/translate` with `async=true` for large files, then poll `/translation/file/status` and fetch `/translation/file/result` with the returned `requestId`\n4. Apply dictionaries and translation memories through a profile and pass its UUID as `profile`. `withDictionary` and `withCorpus` are deprecated\n5. Read the terms before automating. They bar benchmark tests and request volumes beyond normal human use, and SYSTRAN may throttle or suspend access\n\n## Questions\n\n### Which is better for AI agents, Lokalise or SYSTRAN Translate API?\n\nLokalise scores 71.3 (BB) on agent readiness against SYSTRAN Translate API's 40 (E), and leads in 6 of 7 scored categories. SYSTRAN Translate API leads on payments \u0026 pricing.\n\n### Do Lokalise and SYSTRAN Translate API need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call Lokalise and SYSTRAN Translate API without installing anything?\n\nYes. Lokalise has a hosted endpoint at https://api.lokalise.com/api2 and SYSTRAN Translate API at https://api-translate.systran.net.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/lokalise-vs-systran.json, and with the fewest tokens: https://www.anchorterminal.com/compare/lokalise-vs-systran.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"lokalise\", \"b\": \"systran\"}`. From a terminal: `anchor compare lokalise systran`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/lokalise.json and https://www.anchorterminal.com/api/v1/tools/systran.json\n\n## Other comparisons with Lokalise or SYSTRAN Translate API\n\n- [Amazon Translate vs Lokalise](https://www.anchorterminal.com/compare/amazon-translate-vs-lokalise.md)\n- [Amazon Translate vs SYSTRAN Translate API](https://www.anchorterminal.com/compare/amazon-translate-vs-systran.md)\n- [Azure Translator vs Lokalise](https://www.anchorterminal.com/compare/azure-translator-vs-lokalise.md)\n- [Azure Translator vs SYSTRAN Translate API](https://www.anchorterminal.com/compare/azure-translator-vs-systran.md)\n- [Crowdin vs Lokalise](https://www.anchorterminal.com/compare/crowdin-vs-lokalise.md)\n- [Crowdin vs SYSTRAN Translate API](https://www.anchorterminal.com/compare/crowdin-vs-systran.md)\n- [DeepL API vs Lokalise](https://www.anchorterminal.com/compare/deepl-api-vs-lokalise.md)\n- [DeepL API vs SYSTRAN Translate API](https://www.anchorterminal.com/compare/deepl-api-vs-systran.md)\n- [Google Cloud Translation vs Lokalise](https://www.anchorterminal.com/compare/google-cloud-translation-vs-lokalise.md)\n- [Google Cloud Translation vs SYSTRAN Translate API](https://www.anchorterminal.com/compare/google-cloud-translation-vs-systran.md)\n- [Lara Translate API vs Lokalise](https://www.anchorterminal.com/compare/lara-translate-vs-lokalise.md)\n- [Lara Translate API vs SYSTRAN Translate API](https://www.anchorterminal.com/compare/lara-translate-vs-systran.md)\n- [LibreTranslate vs Lokalise](https://www.anchorterminal.com/compare/libretranslate-vs-lokalise.md)\n- [LibreTranslate vs SYSTRAN Translate API](https://www.anchorterminal.com/compare/libretranslate-vs-systran.md)\n- [Lingo.dev vs Lokalise](https://www.anchorterminal.com/compare/lingo-dev-vs-lokalise.md)\n- [Lingo.dev vs SYSTRAN Translate API](https://www.anchorterminal.com/compare/lingo-dev-vs-systran.md)\n- [Lingvanex Translation API vs Lokalise](https://www.anchorterminal.com/compare/lingvanex-vs-lokalise.md)\n- [Lingvanex Translation API vs SYSTRAN Translate API](https://www.anchorterminal.com/compare/lingvanex-vs-systran.md)\n- [Lokalise vs Phrase](https://www.anchorterminal.com/compare/lokalise-vs-phrase.md)\n- [Phrase vs SYSTRAN Translate API](https://www.anchorterminal.com/compare/phrase-vs-systran.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-08", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Lokalise vs SYSTRAN Translate API", "url": "" } ], "description": "Lokalise scores 71.3 (BB) on agent readiness against SYSTRAN Translate API's 40 (E), and leads in 6 of 7 scored categories. SYSTRAN Translate API leads on payments \u0026 pricing. Both do translate text. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "Lokalise BB 71.3", "SYSTRAN Translate API E 40", "scores" ], "h1": "Lokalise vs SYSTRAN Translate API", "image": "https://www.anchorterminal.com/assets/og/compare-lokalise-vs-systran.png", "path": "/compare/lokalise-vs-systran", "published": "2026-10-01", "section": "tools", "title": "Lokalise vs SYSTRAN Translate API for AI agents, BB 71.3 vs E 40", "toc": null, "updated": "2026-10-08", "url": "https://www.anchorterminal.com/compare/lokalise-vs-systran" }, "tokens": { "markdown": 2500, "slim": 730 }, "version": 1 }