Compare

Bump vs Hanko

Bump scores higher on the AgentReady, 52/100 against 48/100. They differ on 15 of the 41 signals. Which ones decides whether an agent can adopt them without a person watching.

What each one is

Bump. Bump.sh is a platform for API documentation and MCP (Model Context Protocol) servers that automatically generates docs and production-ready MCP servers from OpenAPI, AsyncAPI, and Arazzo specifications.

Hanko. Hanko is an open-source authentication and user management platform for modern web and mobile apps.

Where Bump is ahead

Bump 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: structured api reference and authentication documented. Hanko misses those.

And on adopt, cli available and mcp integration available. Hanko misses those.

Finally, on operate, retry behavior documented. Hanko misses it.

Where Hanko is ahead

Hanko passes clear canonical domain, llms.txt published and llms-full.txt / full agent docs, and Bump 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. Bump misses it.

And on adopt, self-service signup, free trial or free allowance and fast time to first request. Bump misses those.

Finally, on operate, structured, predictable output. Bump misses it.

What neither does

Both fail openapi / spec quality, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented, no mandatory sales call, agent-compatible signup flow, programmatic credential creation, machine-readable errors, 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. Bump leads 80 to 73. Bump misses clear canonical domain, llms.txt published, llms-full.txt / full agent docs; Hanko misses clear product positioning, mcp discoverable.

Understand is whether an agent can read the docs and work out how the API behaves before calling it. Bump leads 38 to 23. Bump misses openapi / spec quality, pricing understandable, request examples provided, response examples provided, errors and status codes documented, limits / constraints 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. Hanko leads 50 to 45. Bump misses self-service signup, no mandatory sales call, agent-compatible signup flow, programmatic credential creation, free trial or free allowance, fast time to first request; Hanko misses no mandatory sales call, agent-compatible signup flow, programmatic credential creation, cli available, mcp integration available.

Operate. Hanko leads 47 to 44. Bump misses structured, predictable output, machine-readable errors, 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

Bump does not publish a machine-readable starting price. Hanko starts at $29/month and has a free tier.

Signal by signal

Which to pick

Hanko clears more of the signals an agent needs, so it is the safer default for unattended use. Full profiles: Bump and Hanko. Alternatives to each: Bump, Hanko.

An agent can fetch this as data: POST /v1/compare {"slugs": ["bump", "hanko"]}