Hanko vs Twilio
Hanko scores higher on the AgentReady, 48/100 against 47/100. They differ on 10 of the 41 signals. Which ones decides whether an agent can adopt them without a person watching.
What each one is
Hanko. Hanko is an open-source authentication and user management platform for modern web and mobile apps.
Twilio. Twilio is a customer engagement platform that provides APIs and tools for communications, authentication, customer data management, and AI-powered conversations across multiple channels.
Where Hanko is ahead
Hanko passes llms-full.txt / full agent docs, and Twilio does not. That is discover, whether an agent can find the product at all without being told it exists.
It also holds understand: pricing understandable. Twilio misses it.
And on adopt, self-service signup, free trial or free allowance and fast time to first request. Twilio misses those.
Finally, on operate, structured, predictable output. Twilio misses it.
Where Twilio is ahead
Twilio passes clear product positioning, 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: structured api reference. Hanko misses it.
And on adopt, agent-compatible signup flow and cli available. Hanko misses those.
What neither does
Both fail mcp discoverable, openapi / spec quality, authentication documented, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented, no mandatory sales call, programmatic credential creation, mcp integration available, 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. Twilio leads 80 to 73. Hanko misses clear product positioning, mcp discoverable; Twilio misses llms-full.txt / full agent docs, mcp discoverable.
Understand. Twilio leads 31 to 23. Hanko misses structured api reference, openapi / spec quality, authentication documented, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented; Twilio misses openapi / spec quality, authentication documented, pricing understandable, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented.
Adopt. Hanko leads 50 to 40. Hanko misses no mandatory sales call, agent-compatible signup flow, programmatic credential creation, cli available, mcp integration available; Twilio misses self-service signup, no mandatory sales call, programmatic credential creation, free trial or free allowance, fast time to first request, mcp integration available.
Operate is whether an agent can run against it in production and recover when a call fails. Hanko leads 47 to 35. Hanko misses machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, agent compatibility verified; Twilio misses structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, agent compatibility verified.
Pricing
Hanko starts at $29/month and has a free tier. Twilio does not publish one.
| Hanko plans | Twilio plans |
|---|---|
| Starter Free | - |
| Pro $29/month + $0.01 per monthly active user > 10,000 | - |
Signal by signal
| Signal | Hanko | Twilio |
|---|---|---|
| AgentReady | 48 | 47 |
| Discovery | 73 | 80 |
| Understanding | 23 | 31 |
| Adoption | 50 | 40 |
| Operability | 47 | 35 |
| Public API | Yes | Yes |
| MCP server | No | Unknown |
| OpenAPI spec | Unknown | Yes |
| CLI | Unknown | Yes |
| llms.txt | Yes | Yes |
| Self-serve signup | Yes | Unknown |
| Free tier | Yes | Unknown |
Which to pick
Hanko clears more of the signals an agent needs, so it is the safer default for unattended use. Full profiles: Hanko and Twilio. Alternatives to each: Hanko, Twilio.
An agent can fetch this as data: POST /v1/compare {"slugs": ["hanko", "twilio"]}