Auth0 vs Hanko
Auth0 scores higher on the AgentReady, 63/100 against 48/100. They differ on 11 of the 41 signals. Which ones decides whether an agent can adopt them without a person watching.
What each one is
Auth0. Auth0 minimizes drop-off with frictionless experiences and stops fraud behind the scenes, carrying trusted context seamlessly across owned and AI-assisted touchpoints.
Hanko. Hanko is an open-source authentication and user management platform for modern web and mobile apps.
Where Auth0 is ahead
Auth0 passes clear product positioning and mcp discoverable, and Hanko does not. That is discover, whether an agent can find the product at all without being told it exists.
It also holds understand: authentication documented and limits / constraints documented. Hanko misses those.
And on adopt, no mandatory sales call, agent-compatible signup flow, cli available and mcp integration available. Hanko misses those.
Where Hanko is ahead
Hanko passes pricing understandable, and Auth0 does not. That is understand, whether an agent can read the docs and work out how the API behaves before calling it.
It also holds adopt: free trial or free allowance. Auth0 misses it.
And on operate, structured, predictable output. Auth0 misses it.
What neither does
Both fail structured api reference, openapi / spec quality, request examples provided, response examples provided, errors and status codes documented, programmatic credential creation, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, agent compatibility verified. If your agent needs any of those, you will be building it yourself either way.
Score, pillar by pillar
The AgentReady splits into four pillars, scored separately, because a product can be easy to find and still impossible to adopt.
Discover. Auth0 leads 100 to 73. Auth0 misses nothing; Hanko misses clear product positioning, mcp discoverable.
Understand. Auth0 leads 31 to 23. Auth0 misses structured api reference, openapi / spec quality, pricing understandable, request examples provided, response examples provided, errors and status codes documented; Hanko misses structured api reference, openapi / spec quality, authentication documented, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented.
Adopt is whether an agent can get a key and make its first successful call without a human in the loop. Auth0 leads 85 to 50. Auth0 misses programmatic credential creation, free trial or free allowance; Hanko misses no mandatory sales call, agent-compatible signup flow, programmatic credential creation, cli available, mcp integration available.
Operate. Hanko leads 47 to 35. Auth0 misses structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, agent compatibility verified; Hanko misses machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, agent compatibility verified.
Pricing
Auth0 does not publish a machine-readable starting price. Hanko starts at $29/month and has a free tier.
| Auth0 plans | Hanko plans |
|---|---|
| - | Starter Free |
| - | Pro $29/month + $0.01 per monthly active user > 10,000 |
Signal by signal
| Signal | Auth0 | Hanko |
|---|---|---|
| AgentReady | 63 | 48 |
| Discovery | 100 | 73 |
| Understanding | 31 | 23 |
| Adoption | 85 | 50 |
| Operability | 35 | 47 |
| Public API | Yes | Yes |
| MCP server | Yes | No |
| OpenAPI spec | Unknown | Unknown |
| CLI | Yes | Unknown |
| llms.txt | Yes | Yes |
| Self-serve signup | Yes | Yes |
| Free tier | Unknown | Yes |
Which to pick
Auth0 clears more of the signals an agent needs, so it is the safer default for unattended use. Full profiles: Auth0 and Hanko. Alternatives to each: Auth0, Hanko.
An agent can fetch this as data: POST /v1/compare {"slugs": ["auth0", "hanko"]}