A hcaptcha challenge sits between an agent and an account it was ready to create.

https://plausible.io/register loads hcaptcha. There is no version of that an agent solves.

7/ 16

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

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

You 7 · category median 7.5 · best mixpanel.com 11 · 15 deterministic HTTP checks, published formula

Pass it onEmail it LinkedIn

Fix this first

+5points, taking 7/16 to 12/16, past mixpanel.com, amplitude.com, usefathom.com

This is the whole list: everything we could measure and you do not pass. Another 1 point sits 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
Programmatic key provisioningan afternoon · +2
Document how a key is created without opening a dashboard: management API, service account or CLI. If no such path exists, that gap is the finding, not the docs.

Cheap too, same week

No CAPTCHA in the signup HTML an afternoon · +1Trigger hcaptcha on a risk signal instead of on every signup, or open an API path to an account. A CAPTCHA is a hard stop, not a speed bump.
Machine-readable API description an afternoon · +1Publish 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

OAuth dynamic client registration a project · +1Publish OAuth authorization server metadata with an RFC 7591 registration_endpoint in it. It is the only standard way an agent registers itself without a human.
MCP surface a project · +1Wrap your top three API calls in an MCP server and declare it at /.well-known/mcp.json.

Take it with you

8 of the checks an agent depends on, plausible.io 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 plausible.io. 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 plausible.io costs

Against product analytics

You are 5 of 6 in a category where a developer is trying to find out what users actually do in the product.

1
mixpanel.com
11/14
2
amplitude.com
10/14
3
usefathom.com
8/14
4
posthog.com
7/13
5
plausible.ioyou
7/16
6
june.so
3/15

Where competitors pass and plausible.io does not

llms.txt publishedposthog.com · mixpanel.com · amplitude.com · usefathom.com
OAuth dynamic client registrationposthog.com · mixpanel.com · amplitude.com
MCP surfaceposthog.com · mixpanel.com · amplitude.com
Machine-readable API descriptionmixpanel.com · amplitude.com · usefathom.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?

4/5

Agent entryIs there a door built for a machine?

0/4

RegistrationCan an agent get an account?

1/2

ProvisioningCan it get credentials without a human?

1/3

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 4 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.
PASS
Docs readable without JavaScript5,980 characters of text without JS
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.
FAIL
OAuth dynamic client registrationNo OAuth metadata on any of the 8 hosts probed, including the usual auth and api subdomainsRFC 7591 is the only standard path by which an agent can register itself without a human.
FAIL
MCP surfaceNo MCP surface: nothing answered at mcp.plausible.io, mcp.plausible.io/mcp, mcp.plausible.io/v1/mcp, api.plausible.io/mcp, /mcp or /api/mcp, and no file mentions MCPAn MCP server turns your API from something an agent reads about into something it can call.

C · Registration

FAIL
No CAPTCHA in the signup HTMLhcaptcha appears in the signup page's server HTMLA CAPTCHA is a hard stop. Permissions after signup beat a gate before it.
PASS
Signup reachable without a browserForm renders in server HTML at https://plausible.io/register

D · Provisioning

FAIL
Programmatic key provisioningNone of the 7 provisioning phrases appears in the 4 documents we readDocumented key creation is the difference between a two-minute integration and a support ticket.
PASS
Free tier or no-card trial stated in textFree tier or no-card signals at https://plausible.io: "No credit card", "free trial"

E · Integration

PASS
Typed SDK on the registry@plausible-analytics/tracker@0.4.6 ships types
FAIL
Machine-readable API descriptionNo OpenAPI spec at the 5 usual paths, none declared by https://plausible.io/docs, 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://plausible.io/docs · linked from the site
Pricing: https://plausible.io · guessed path
Signup: https://plausible.io/register · linked from the site
npm package: @plausible-analytics/tracker
GitHub: plausible/analytics
Package licence: MIT
Crawl-delay: none
Content-Signal: none
Blocked on-demand agents: none