Agent readiness · Translation and localization
lokalise.com
11 of 16 measurable points under formula 9.2, measured on 2026-08-12. 15 checks exist; each is one HTTP request with a published rule, so every sentence below can be rerun and argued with.
A · Discovery
- PASSAnswers an agent user-agentAnswered 200 to LetAgentsIn/1.0 (+https://letagentsin.com/methodology)
- PASSllms.txt publishedllms.txt present at https://lokalise.com/llms.txt and https://docs.lokalise.com/llms.txt, and the 12 links we sampled across the file all answer
- PASSDocs readable without JavaScript5,061 characters of text without JS, on https://docs.lokalise.com/en/articles/2329387-two-factor-authentication rather than on https://docs.lokalise.com/en/
- PASSOn-demand agents not blockedNo on-demand agent is blocked
- N/APaths robots.txt points at answerrobots.txt names no concrete path, only patterns or nothing, so there is no claim to check
- PASSNo punishing crawl delayNo Crawl-delay applies to the agents we check
B · Agent entry
- FAILAgent entry pointNone of the 9 known agent entry paths returns a file rather than your page shell
- PASSOAuth dynamic client registrationregistration_endpoint published, but none of the 2 advertised grants (authorization_code, refresh_token) finishes without a person at a browser
- PASSMCP surfaceLive MCP endpoint at https://mcp.lokalise.com/mcp, answered 401 with an auth challenge
C · Registration
- FAILNo CAPTCHA in the signup HTMLrecaptcha appears in the signup page's server HTML, even though the form itself is assembled by JavaScript
- FAILSignup reachable without a browserhttps://app.lokalise.com/signup is reachable, but its form needs JavaScript
D · Provisioning
- PARTProgrammatic key provisioning1 of 7 provisioning phrases across the 6 documents we read: "account api"
- PASSFree tier or no-card trial stated in textFree tier or no-card signals at https://lokalise.com/pricing/: "no credit card", "Try it free"
E · Integration
- PASSTyped SDK on the registry@lokalise/node-api@16.3.0 ships types, matched from the registry by who publishes it rather than by a link on your site
- PASSMachine-readable API descriptionDocs serve markdown to machines, at https://docs.lokalise.com/en/articles/1929556-api-and-ota-tokens.md
Tell me when this changes
The failures here are the kind nobody notices. An edge rule that starts refusing agents changes nothing a person sees in a browser, so the first sign is usually an integration that quietly stopped working. We rescan weekly and write only when a verdict moves.
This page is the newest scan we hold for lokalise.com and changes when we rescan. It is not a judgement of the product: we measure whether an unattended run can get through, not whether the thing is any good. The whole corpus is published as JSON and CSV.