You publish files for machines to read, but nothing that tells one how to become a customer.

None of the nine known agent entry paths answered, including /agent-signup.md and /.well-known/agent-access.json. Reading is solved on your site; joining is not.

9/ 14

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

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

You 9 · category median 10 · best auth0.com 14 · 15 deterministic HTTP checks, published formula

Pass it onEmail it LinkedIn

Fix this first

+3points, taking 9/14 to 12/14, past logto.io, workos.com, clerk.com

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

1
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.
2
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

OAuth dynamic client registration a project · +1Your OAuth metadata is already published and has no registration_endpoint in it. Adding that one field is the whole change: RFC 7591 is the only standard way an agent registers itself without a human.
Signup reachable without a browser a project · +1Let https://app.kinde.com/register render its form in server HTML and stop refusing non-browser requests to it.

Take it with you

5 of the checks an agent depends on, kinde.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 kinde.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 kinde.com costs

Against authentication as a service

You are 5 of 7 in a category where a developer is trying to add login without owning password resets forever.

1
auth0.com
14/16
2
logto.io
10/13
3
workos.com
10/14
4
clerk.com
10/15
5
kinde.comyou
9/14
6
stytch.com
9/14
7
supertokens.com
8/14

Where competitors pass and kinde.com does not

Machine-readable API descriptionauth0.com · clerk.com · workos.com · stytch.com · supertokens.com
OAuth dynamic client registrationauth0.com · workos.com
Signup reachable without a browserauth0.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?

5/5

Agent entryIs there a door built for a machine?

0/3

RegistrationCan an agent get an account?

0/1

ProvisioningCan it get credentials without a human?

3/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)
PASS
llms.txt publishedllms.txt and llms-full.txt present at https://www.kinde.com/llms.txt and https://docs.kinde.com/llms.txt and https://docs.kinde.com/llms-full.txt, and the 12 links we sampled across both files all answer
PASS
Docs readable without JavaScript19,045 characters of text without JS, on https://docs.kinde.com/authenticate/about-auth/about-authentication/ rather than on https://docs.kinde.com/
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 registrationOAuth metadata published, but no registration_endpoint in itRFC 7591 is the only standard path by which an agent can register itself without a human.
UNMEASURED
MCP surfaceUnmeasurable: every JSON-RPC POST we sent came back with an empty 2xx, including one to a path nobody registered, so what answered was your edge rather than your serverNothing for you to do if your server is reachable from other networks. Whether an MCP server is there becomes measurable from a network your edge does not intercept.

C · Registration

UNMEASURED
No CAPTCHA in the signup HTMLUnmeasurable: the signup form at https://app.kinde.com/register 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.kinde.com/register is reachable, but its form needs JavaScriptIf a bare HTTP request gets a 403, the agent never sees the form at all.

D · Provisioning

PASS
Programmatic key provisioning2 of 7 provisioning phrases across the 7 documents we read: "management api", "account api"
PASS
Free tier or no-card trial stated in textFree tier or no-card signals at https://www.kinde.com/pricing/: "No credit card", "Free plan", "$0"

E · Integration

PASS
Typed SDK on the registry@kinde-oss/kinde-auth-nextjs@2.13.1 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.kinde.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.kinde.com/ · from your llms.txt
Pricing: https://www.kinde.com/pricing/ · linked from the site
Signup: https://app.kinde.com/register · linked from the site
npm package: @kinde-oss/kinde-auth-nextjs (registry guess)
GitHub: luukhaijes/kinde-angular
Package licence: MIT
Crawl-delay: none
Content-Signal: none
Blocked on-demand agents: none