Bump vs GitBook
GitBook scores higher on the AgentReady, 96/100 against 52/100. They differ on 18 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.
GitBook. GitBook is the docs infrastructure that makes docs AI-ready and accurate.
Where GitBook is ahead
GitBook 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: openapi / spec quality, pricing understandable, request examples provided, response examples provided, errors and status codes documented and limits / constraints documented. Bump misses those.
And on adopt, self-service signup, agent-compatible signup flow, programmatic credential creation, free trial or free allowance and fast time to first request. Bump misses those.
Finally, on operate, structured, predictable output, machine-readable errors, rate-limit behavior predictable and agent compatibility verified. Bump misses those.
What neither does
Both fail no mandatory sales call, idempotency support. 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. GitBook leads 100 to 80. Bump misses clear canonical domain, llms.txt published, llms-full.txt / full agent docs; GitBook misses nothing.
Understand is whether an agent can read the docs and work out how the API behaves before calling it. GitBook leads 100 to 38. Bump misses openapi / spec quality, pricing understandable, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented; GitBook misses nothing.
Adopt. GitBook leads 90 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; GitBook misses no mandatory sales call.
Operate. GitBook leads 94 to 44. Bump misses structured, predictable output, machine-readable errors, idempotency support, rate-limit behavior predictable, agent compatibility verified; GitBook misses idempotency support.
Pricing
Bump does not publish a machine-readable starting price. GitBook does not publish one and has a free tier.
Signal by signal
| Signal | Bump | GitBook |
|---|---|---|
| AgentReady | 52 | 96 |
| Discovery | 80 | 100 |
| Understanding | 38 | 100 |
| Adoption | 45 | 90 |
| Operability | 44 | 94 |
| Public API | Yes | Yes |
| MCP server | Yes | Yes |
| OpenAPI spec | Yes | Yes |
| CLI | Yes | Yes |
| llms.txt | Unknown | Yes |
| Self-serve signup | No | Yes |
| Free tier | Unknown | Yes |
Which to pick
GitBook clears more of the signals an agent needs, so it is the safer default for unattended use. Full profiles: Bump and GitBook. Alternatives to each: Bump, GitBook.
An agent can fetch this as data: POST /v1/compare {"slugs": ["bump", "gitbook"]}