Only 38 characters of your documentation survive without JavaScript, and that is the version an agent reads.

https://docs.crowdin.com served 38 characters of text to a plain fetch. The check passes at 2,000, which is about one screen of prose.

7/ 13

A · Discovery: 3/5
B · Agent entry: 2/4
C · Registration: 0/1
D · Provisioning: 1/1
E · Integration: 1/2

of the 13 points that apply to you and we could measure · 4 of 17 were not scored

You 7 · category median 10 · best deepl.com 12 · 15 deterministic HTTP checks, published formula

Pass it onEmail it LinkedIn

Fix this first

+4points, taking 7/13 to 11/13, past weglot.com

This is the whole list: everything we could measure and you do not pass. Another 4 points sit behind checks we could not evaluate on your domain, and each of those lines below says what would make it measurable.

1
llms.txt publishedminutes · +1
Publish /llms.txt: a markdown list linking your quickstart, API reference, pricing and package name. It is the cheapest file on this list.
2
Agent entry pointan afternoon · +2
Publish /agent-signup.md: the path from nothing to a working key, written as steps for a machine rather than a tour for a person. Ours is at /agent-signup.md if you want a worked example, and it says plainly that we have nothing to sign up for.
3
Machine-readable API descriptionan afternoon · +1
Publish an OpenAPI file at /openapi.json, or serve markdown when a client sends Accept: text/markdown. Either one stops agents guessing your API.

Then, when you have room

Docs readable without JavaScript a project · +1Server-render the docs or mirror them as markdown. A plain fetch gets 38 characters, which reads as an empty product.
Signup reachable without a browser a project · +1Let https://app.crowdin.com/signup render its form in server HTML and stop refusing non-browser requests to it.

Take it with you

6 of the checks an agent depends on, crowdin.com does not pass.

Send yourself the list above with the checks that cost the most, and a permanent link. Whoever owns the fix is usually not the person who ran the scan.

One email with the report, and one follow-up asking what you did with it. No newsletter, no sequence. Delete on request at hello@letagentsin.com.

None of this tells you whether an agent picked you

Everything above is a file an agent could read. Whether one actually chose you is a different measurement, and we have not run it on crowdin.com. What we have run it on is a rich text editor vendor: six agents, one brief, six isolated copies of a real codebase. All six picked the same competitor, and the vendor being studied was never named, not even on a rejection list, while the runs named and dismissed ten alternatives between them. In an earlier round, run before we isolated the copies, it was named twice and struck off both times in four words: Fully commercial, licence key required. That study is about them, not about you. It is here because it is the difference between a file and a decision.

Read the audits in full What the same run on crowdin.com costs

Against translation and localization

You are 5 of 6 in a category where a developer is trying to ship the same product in a language nobody on the team speaks.

1
deepl.com
12/16
2
weglot.com
9/13
3
lokalise.com
11/16
4
phrase.com
11/16
5
crowdin.comyou
7/13
6
tolgee.io
7/14

Where competitors pass and crowdin.com does not

Docs readable without JavaScriptdeepl.com · lokalise.com · phrase.com · weglot.com · tolgee.io
llms.txt publisheddeepl.com · lokalise.com · phrase.com · weglot.com
Machine-readable API descriptiondeepl.com · lokalise.com · phrase.com · weglot.com
Signup reachable without a browserdeepl.com · phrase.com

Only domains we have actually scanned appear here, so the ranking is a floor: a competitor missing from the list has not been measured, not beaten.

By stage

DiscoveryCan an agent find and read you?

3/5

Agent entryIs there a door built for a machine?

2/4

RegistrationCan an agent get an account?

0/1

ProvisioningCan it get credentials without a human?

1/1

IntegrationCan it ship working code?

1/2

Every check

Each line is one HTTP observation with a published rule, so you can rerun any of them yourself. Most are the same tomorrow if you are: the two that are not are the bot gate and the pricing page, which answer inconsistently on their own, which is why those run more than once and say so when the tries disagreed. PASS and PART are counted. UNMEASURED means we could not evaluate it, N/A means it does not apply to a product like yours, and neither is in the score or its denominator. See the formula

A · Discovery

PASS
Answers an agent user-agentAnswered 200 to LetAgentsIn/1.0 (+https://letagentsin.com/methodology)
FAIL
llms.txt publishedNo llms.txt at any of the 6 locations probedA curated map of your docs is the cheapest way to control what an agent reads first. Worth one point and not more: in eighteen isolated agent runs across four categories, not one cited llms.txt among its sources, and an independent ninety-day measurement published by Otterly in February 2026 found it served 84 requests against 62,100 AI-bot visits.
FAIL
Docs readable without JavaScriptOnly 38 characters render without JSMost agents fetch HTML, they do not run your bundle. An empty shell reads as an empty product.
PASS
On-demand agents not blockedNo on-demand agent is blocked
N/A
Paths robots.txt points at answerrobots.txt names no concrete path, only patterns or nothing, so there is no claim to check
PASS
No punishing crawl delayNo Crawl-delay applies to the agents we check

B · Agent entry

FAIL
Agent entry pointNone of the 9 known agent entry paths returns a file rather than your page shellA markdown file written for a machine turns a guessing game into a procedure it can follow.
PASS
OAuth dynamic client registrationregistration_endpoint published, but none of the 2 advertised grants (authorization_code, refresh_token) finishes without a person at a browser
PASS
MCP surfaceLive MCP endpoint at https://mcp.crowdin.com/mcp, answered 401 with an auth challenge

C · Registration

UNMEASURED
No CAPTCHA in the signup HTMLUnmeasurable: the signup form at https://app.crowdin.com/signup is not in the server HTML, so its gates are not eitherServer-render the form, or tell us the endpoint it posts to, and the gates become visible to us and to an agent.
FAIL
Signup reachable without a browserhttps://app.crowdin.com/signup is reachable, but its form needs JavaScriptIf a bare HTTP request gets a 403, the agent never sees the form at all.

D · Provisioning

UNMEASURED
Programmatic key provisioningUnmeasurable: only 1 documentation page could be read, which is too little to conclude anythingLink your API reference from your docs index or from llms.txt and this becomes measurable.
PASS
Free tier or no-card trial stated in textFree tier or no-card signals at https://crowdin.com/pricing: "free trial", "free account", "Open Source project, sign up for a free"

E · Integration

PASS
Typed SDK on the registry@crowdin/crowdin-api-client@1.56.3 ships types, matched from the registry by who publishes it rather than by a link on your site
FAIL
Machine-readable API descriptionNo OpenAPI spec at the 5 usual paths, none declared by https://docs.crowdin.com, and no markdown negotiationAn OpenAPI file or markdown negotiation lets an agent read your API instead of guessing it.Point at your spec from your docs page with rel="service-desc" and an agent finds it without guessing.

What we discovered on the way

Docs: https://docs.crowdin.com · found on a subdomain
Pricing: https://crowdin.com/pricing · linked from the site
Signup: https://app.crowdin.com/signup · found on a subdomain
npm package: @crowdin/crowdin-api-client (registry guess)
GitHub: not found
Package licence: MIT
Crawl-delay: none
Content-Signal: none
Blocked on-demand agents: none