# Lokalise > 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. - Canonical: https://www.anchorterminal.com/tools/lokalise - Markdown: https://www.anchorterminal.com/tools/lokalise.md (~7,900 tokens) - Slim: https://www.anchorterminal.com/tools/lokalise.min.md (~1,880 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/lokalise.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-08 ## Overview **Grade BB · 71.3/100 · rank #115 of 722 · #3 in Translation · agent-ready · confidence medium** ## Assessment 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. ## Facts | Field | Value | | --- | --- | | Vendor | Lokalise, Inc. (https://lokalise.com) | | Kind | HTTP API | | Category | Translation (https://www.anchorterminal.com/categories/translation) | | Transport | HTTP, Streamable HTTP | | Endpoint | `https://api.lokalise.com/api2` | | Auth | OAuth or key · 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 ($149 / mo) · 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). | | x402 | No · No x402, MPP or L402 in the developer docs, the OpenAPI files or the pricing page (checked 2026-10-08). | | Licence | Proprietary service under the Lokalise Master Service Agreement. The CLI and the Node SDK on GitHub are BSD 3-Clause | | Packages | npm: `@lokalise/node-api`; pypi: `python-lokalise-api`; go: `github.com/lokalise/lokalise-cli-2-go` | | Source | https://github.com/lokalise/lokalise-cli-2-go | | Docs | https://developers.lokalise.com | | llms.txt | https://developers.lokalise.com/llms.txt | | Last release | 2026-10-05 | | GitHub stars | 124 (as of 2026-10-08) | | npm downloads / week | 337,721 | | PyPI downloads / week | 39,399 | | API | REST at `https://api.lokalise.com/api2`, OpenAPI 3.0.3. Default projects (63 paths, 109 operations), projects with branches, and OTA. `GET /v1/audit-logs` sits outside `/api2` | | MCP server | Hosted, in beta. `https://mcp.lokalise.com/mcp/project-management` (22 documented actions) and `https://mcp.lokalise.com/mcp/software-development` (16). OAuth 2 with PKCE and dynamic client registration, or an API token in the `apikey` header | | Credentials | Personal API tokens, read-only or read/write, no expiry, revocable in the profile. OAuth 2 authorisation code grant for the API, with apps registered through Lokalise support and access tokens lasting about 60 minutes | | Rate limits | 6 requests a second per token and per IP, 10 concurrent requests per project. Responses carry `X-RateLimit-Limit`, `X-RateLimit-Remaining` and `X-RateLimit-Reset` (observed on 8 October 2026) | | Pagination | `limit` (default 100, maximum 5,000, 500 on keys) and `page`, with `X-Pagination-*` headers. Cursor paging on keys, translations, projects and glossary terms | | Errors | JSON `error` object with `code` and `message`. Bulk calls return an `errors` array per failed item. 429 on rate limits | | Files | `/files/upload` queues an import and returns a process to poll. `/files/download` covers up to 10,000 key-language pairs, `/files/async-download` the rest | | Translation engines | `automatic_translation` tasks with `translation_engine` of `ai` (default), `deepl` or `google`. Human translation through `/teams/{team_id}/orders` | | SDKs and CLI | `@lokalise/node-api` 16.6.0 (21 September 2026), `python-lokalise-api` 4.3.0 (5 October 2026), Ruby and PHP clients per the docs, and the `lokalise2` CLI v3.1.7 (14 July 2026), BSD 3-Clause | | Plans | Explorer $149, Growth $379 and Advanced $1,049 a month billed yearly, Enterprise by quote. 14-day trial at Enterprise level with no card | | SLA | 99.5 per cent a calendar month in the Master Service Agreement, with service credits in Annex B. Trial access has no service levels | | Certifications | SOC 2 Type II, ISO 27001 and ISO 27017 per lokalise.com/product/security. Private bug bounty on YesWeHack and a disclosure policy at vdp.lokalise.com | | Data location | Customer data on AWS in EU regions per the security page. Sub-processor list updated 1 August 2026, with locations | | Status | status.lokalise.com on Statuspage, five components (Lokalise.com, API, App, OTA, Messages) | | 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 | | JSON | https://www.anchorterminal.com/api/v1/tools/lokalise.json | ## Score breakdown (methodology v0.4, October 2026 research run) Assessed 2026-10-08 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 84 | 16.8 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 76 | 12.3 | | Agent ergonomics | 13% | 16.2 | 69 | 11.2 | | Security & auth | 14% | 17.5 | 73 | 12.8 | | Payments & pricing | 10% | 12.5 | 30 | 3.8 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 84 | 7.3 | | Transparency & trust (editorial 63, provenance 98) | 7% | 8.8 | 81 | 7.1 | | Negative events | up to −15 | up to −15 | none recorded | 0 | | **Total** | | | | **71.3 → BB** | ### Why each score - Reliability 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). Two incidents in the 90 days to 8 October 2026, a 42-minute search outage on 17 August marked critical and three hours of partial email delivery failures on 14 September marked major, neither an hour of the core API down (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 (10). The REST API is generally available, while the MCP server is in beta (10). - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 76: Three public OpenAPI 3.0.3 files, the default-projects one with 63 paths and 109 operations (25). llms.txt with about 160 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). - Agent ergonomics 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). - Security & auth 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). - Payments & pricing 30: No x402, MPP or L402 (0). Plan prices are public at $149, $379 and $1,049 a month billed yearly, with no per-unit price for processed words on the page we read, so plan-only credit (10). A 14-day trial with no card (20). A person signs up in a browser, and the MCP server's dynamic client registration still ends in a Lokalise account login (0). - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 84: `python-lokalise-api` 4.3.0 on 5 October 2026, `@lokalise/node-api` 16.6.0 on 21 September and a product changelog entry on 1 October (30). Seven Node SDK releases and twelve changelog entries since 6 July (20). Public changelog and 24/7 support listed on the pricing page. The Node SDK has 1 open issue, while the CLI has 62 open issues and pull requests and went from May 2025 to July 2026 without a release (11 of 15). Official SDKs are current (15). The Node SDK runs CI on GitHub Actions and needs Node 22.19 or later, and the CLI builds with GoReleaser (8 of 10). - Transparency & trust 81: Closed service with a published Master Service Agreement, and the CLI and SDKs under BSD 3-Clause (15). Privacy policy of March 2026, 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). Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (16 items): https://www.anchorterminal.com/fixes/lokalise.md (JSON https://www.anchorterminal.com/fixes/lokalise.json) ### What we couldn't check - unchecked: the MCP server's tool definitions and annotations, which need a Lokalise account to list. The counts of 22 and 16 come from the help centre table of actions. - unchecked: plan allowances (processed words, seats, projects) and monthly-billing prices, which the pricing page draws by script. - unchecked: the DPA PDF and Annex B of the Master Service Agreement (service credits), which we did not read. - unchecked: the AI sub-processor list at lokalise.com/ai-subprocessor-list and its retention periods. - Which plans include API access is not stated on the pages we read. The MCP article says teams on a plan with API access, and the changelog of 23 September 2026 says the MCP server is available on all plans. - The lead's category is machine translation. Lokalise is a translation management system that runs AI and machine translation as tasks, so it sits in this category as the nearest fit, with no synchronous translate call. - The Master Service Agreement forbids benchmarking or competitive analysis, which matters before our probes run. Recorded as a fact, with no deduction. - The help centre calls the MCP server beta, while the product page shows no beta label. ### Sources - docs index for agents: (seen 2026-10-08) - API introduction and OpenAPI links: (seen 2026-10-08) - OpenAPI file, default projects: (seen 2026-10-08) - authentication: (seen 2026-10-08) - rate limits: (seen 2026-10-08) - errors: (seen 2026-10-08) - pagination: (seen 2026-10-08) - API changelog: (seen 2026-10-08) - audit logs endpoint: (seen 2026-10-08) - MCP server setup article: (seen 2026-10-08) - MCP OAuth metadata: (seen 2026-10-08) - API tokens article: (seen 2026-10-08) - pricing: (seen 2026-10-08) - product changelog: (seen 2026-10-08) - status incidents: (seen 2026-10-08) - Master Service Agreement: (seen 2026-10-08) - User and Trial Access Terms of Service: (seen 2026-10-08) - Developer Program Agreement: (seen 2026-10-08) - privacy policy: (seen 2026-10-08) - DPA page: (seen 2026-10-08) - AI statement: (seen 2026-10-08) - sub-processors: (seen 2026-10-08) - security page: (seen 2026-10-08) - security.txt: (seen 2026-10-08) - CLI repository: (seen 2026-10-08) - Node SDK repository: (seen 2026-10-08) - npm registry: (seen 2026-10-08) - PyPI: (seen 2026-10-08) ## Who's behind it (provenance 98/100, checked 2026-10-08) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | Lokalise, Inc. | 20/20 | | Domain age | lokalise.com, registered 2016-09-26 (10 years) | 15/15 | | Endpoint on the vendor's domain | api.lokalise.com | 15/15 | | Terms of service | read, states 7 of the 7 things a reader expects, and has 1 clause that costs points | 8/10 | | Privacy policy | read, states 8 of the 8 things a reader expects | 10/10 | | Status page | status.lokalise.com | 10/10 | | Changelog | published | 10/10 | | security.txt | valid | 10/10 | 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. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service** (https://lokalise.com/msa-new/), read 2026-10-08, dated 2025-11-01, states 7 of the 7 things a reader expects. - To know. Restricts benchmarking or competitive use (costs points). "(c) use or access the Platform or Services for the purpose of developing, offering, or operating any website, platform, large-scale language model, product, or service that is competitive with Lokalise, or for benchmarking or competitive analysis;" - To know. Says access can be ended without notice or for any reason. "Lokalise may, without prior notice and at its sole discretion, suspend the Services or block access to the Platform, without prejudice to any other remedies available under applicable law." - Gives the date it was last updated. Last updated 2025-11-01. - Names the governing law or courts. The law of the State of Delaware. - States a limit on its liability. Capped at the fees paid in the 12 months before the claim. - Says how changes to the terms are announced. Gives thirty days of notice before a change. - Also in the text (2026-10-08). Annual and multi-year plans renew automatically unless either party gives notice of non-renewal at least 90 days before the renewal date. "Annual and multi-year Plans along with Add-ons and Bundles shall automatically renew on the following day of the last day of the Term (“Renewal Date”), unless either Party provides written or in Platform notice of non-renewal at least ninety (90) days prior to the Renewal Date." - Also in the text (2026-10-08). Lokalise may use the customer's name and logo for marketing unless the customer opts out in writing. "The Customer agrees that Lokalise may use the Customer’s name and logo for marketing purposes and free trial references unless the Customer opts out by providing written notice." - Also in the text (2026-10-08). Lokalise may permanently delete the data of an inactive or suspended account after 30 days of inactivity. "Lokalise reserves the right to permanently delete inactive or suspended account data after thirty (30) days of inactivity, subject to applicable laws and retention obligations." **Privacy policy** (https://lokalise.com/privacy-policy/), read 2026-10-08, dated 2026-03-01, states 8 of the 8 things a reader expects. - To know. Says it sells personal data or shares it for advertising. "These services may involve sharing limited identifiers (such as hashed email addresses or similar identifiers) with advertising partners in order to measure campaign performance and deliver targeted advertising to business audiences." - Gives the date it was last updated. Last updated 2026-03-01. - Gives a privacy contact. privacy@lokalise.com. - Says where data is transferred or stored. Relies on the Data Privacy Framework. - Also in the text (2026-10-08). Personal or confidential information typed into a free-text AI chat message or prompt may be sent to the LLM provider. "However, if a user voluntarily includes personal data, sensitive information, or other confidential information in a free-text chat message or prompt, that content may be transmitted to the relevant LLM provider as part of the request in order to provide the AI feature." - Also in the text (2026-10-08). Lokalise says it does not train general-purpose AI models on data submitted through its AI tools unless this is disclosed and authorised by the customer or user. "We do not use Customer Data or Personal Data submitted through these features to train general-purpose AI models, except as expressly disclosed otherwise and authorised by the Customer or user." ## Live (updated 2026-10-08 22:39 UTC) - Right now: up, HTTP 404, 89 ms, checked 2026-10-08 22:39 UTC (get on `https://api.lokalise.com/api2`) - Uptime 24h 100.0% (36 probes) · 30 days 100.0% (36 probes) · p50 91 ms · p95 146 ms - Vendor status page: none, All Systems Operational - Always current: https://www.anchorterminal.com/api/v1/live/lokalise.json ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## Prices | Item | Price | Unit | Note | | --- | --- | --- | --- | | Explorer | $149 | per month (plan) | billed yearly | | Growth | $379 | per month (plan) | billed yearly | | Advanced | $1049 | per month (plan) | billed yearly | Across all listings: https://www.anchorterminal.com/prices/index.md ## 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 ## Before you call it (notes for agents) 1. 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. 2. Stay under 6 requests a second per token and 10 concurrent requests per project. On 429, back off exponentially and read `X-RateLimit-Reset`. 3. Use a read-only token for reads. A read/write token can call `PUT /projects/{project_id}/empty`, which deletes every key and translation. 4. Use `pagination=cursor` on `/keys` and `/translations`, with `limit` at most 500 on keys, and follow `X-Pagination-Next-Cursor`. 5. 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`. ## Connect Install: ```bash brew tap lokalise/cli-2 brew install lokalise2 ``` First request: ```bash curl "https://api.lokalise.com/api2/projects?limit=5" -H "X-Api-Token: $LOKALISE_API_TOKEN" ``` Claude Code: ```bash claude mcp add lokalise_pm --transport http https://mcp.lokalise.com/mcp/project-management ``` MCP client configuration: ```json { "lokalise_pm": { "url": "https://mcp.lokalise.com/mcp/project-management" }, "lokalise_sd": { "url": "https://mcp.lokalise.com/mcp/software-development" } } ``` Through letme (picks today, calling later): https://letme.dev/lokalise. letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | Azure Translator | BB | 72 | 97 | translate.text, translate.documents, translate.glossary | no | https://www.anchorterminal.com/tools/azure-translator.md | | DeepL API | BB | 72 | 98 | translate.text, translate.documents, translate.glossary | no | https://www.anchorterminal.com/tools/deepl-api.md | | Crowdin | B | 69.6 | 153 | translate.text, translate.documents, translate.glossary | no | https://www.anchorterminal.com/tools/crowdin.md | | Amazon Translate | B | 69.5 | 154 | translate.text, translate.documents, translate.glossary | no | https://www.anchorterminal.com/tools/amazon-translate.md | | Google Cloud Translation | B | 68.1 | 191 | translate.text, translate.documents, translate.glossary | no | https://www.anchorterminal.com/tools/google-cloud-translation.md | | Phrase | B | 64.2 | 285 | translate.text, translate.documents, translate.glossary | no | https://www.anchorterminal.com/tools/phrase.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - The REST API's three OpenAPI 3.0.3 files are linked from the reference introduction, and the default-projects file has 63 paths and 109 operations (source: ) - Rate limits are 6 requests a second per token and per IP and 10 concurrent requests per project, answered with 429 (source: ) - The hosted MCP server has two endpoints, `https://mcp.lokalise.com/mcp/project-management` and `https://mcp.lokalise.com/mcp/software-development`, and the help centre article labels it beta (source: ) - The changelog entry of 23 September 2026 says the MCP server is available on all plans (source: ) - Automatic translation tasks run on Lokalise AI, DeepL or Google through `task_type: automatic_translation` and `translation_engine` (source: ) - The Master Service Agreement, last updated November 2025, commits to 99.5 per cent monthly uptime and forbids use for benchmarking or competitive analysis (source: ) - status.lokalise.com lists two incidents in the 90 days to 8 October 2026, a 42-minute search outage on 17 August and three hours of partial email delivery failures on 14 September (source: ) - The AI statement, updated September 2026, says customer content can train Lokalise's own models such as AI Scoring where the customer consents through the AI Addendum, and is not shared with LLM providers for their training (source: ) ## Compare - [Amazon Translate vs Lokalise](https://www.anchorterminal.com/compare/amazon-translate-vs-lokalise.md): B 69.5 vs BB 71.3 - [Azure Translator vs Lokalise](https://www.anchorterminal.com/compare/azure-translator-vs-lokalise.md): BB 72 vs BB 71.3 - [Crowdin vs Lokalise](https://www.anchorterminal.com/compare/crowdin-vs-lokalise.md): B 69.6 vs BB 71.3 - [DeepL API vs Lokalise](https://www.anchorterminal.com/compare/deepl-api-vs-lokalise.md): BB 72 vs BB 71.3 - [Google Cloud Translation vs Lokalise](https://www.anchorterminal.com/compare/google-cloud-translation-vs-lokalise.md): B 68.1 vs BB 71.3 - [Lara Translate API vs Lokalise](https://www.anchorterminal.com/compare/lara-translate-vs-lokalise.md): C 61.3 vs BB 71.3 - [LibreTranslate vs Lokalise](https://www.anchorterminal.com/compare/libretranslate-vs-lokalise.md): D 49.8 vs BB 71.3 - [Lingo.dev vs Lokalise](https://www.anchorterminal.com/compare/lingo-dev-vs-lokalise.md): B 62.3 vs BB 71.3 - [Lingvanex Translation API vs Lokalise](https://www.anchorterminal.com/compare/lingvanex-vs-lokalise.md): F 37 vs BB 71.3 - [Lokalise vs Phrase](https://www.anchorterminal.com/compare/lokalise-vs-phrase.md): BB 71.3 vs B 64.2 - [Lokalise vs SYSTRAN Translate API](https://www.anchorterminal.com/compare/lokalise-vs-systran.md): BB 71.3 vs E 40 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on lokalise.com or one of its subdomains, or the README of github.com/lokalise/lokalise-cli-2-go. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "lokalise", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html Lokalise on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![Lokalise on Anchor Terminal](https://www.anchorterminal.com/badges/lokalise.svg)](https://www.anchorterminal.com/tools/lokalise) ``` Plain link: ```html Lokalise on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Lokalise is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/lokalise-dark.png - Light: https://www.anchorterminal.com/assets/share/lokalise-light.png