Crawlbase vs Kernel
Kernel scores higher on the AgentReady, 89/100 against 68/100. They differ on 14 of the 41 signals. Which ones decides whether an agent can adopt them without a person watching.
What each one is
Crawlbase. Crawlbase provides web crawling, scraping, and parsing APIs at scale.
Kernel. Kernel provides crazy fast, open source browser infrastructure for AI agents to access the internet.
Where Crawlbase is ahead
Crawlbase passes authentication documented, and Kernel 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: agent-compatible signup flow, fast time to first request and copyable quickstart. Kernel misses those.
Where Kernel is ahead
Kernel passes structured api reference, openapi / spec quality, request examples provided, response examples provided and errors and status codes documented, and Crawlbase 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: programmatic credential creation. Crawlbase misses it.
And on operate, structured, predictable output, machine-readable errors, retry behavior documented and rate-limit behavior predictable. Crawlbase 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.
Understand is whether an agent can read the docs and work out how the API behaves before calling it. Kernel leads 92 to 38. Crawlbase misses structured api reference, openapi / spec quality, request examples provided, response examples provided, errors and status codes documented; Kernel misses authentication documented.
Adopt. Crawlbase leads 81 to 71. Crawlbase misses no mandatory sales call, programmatic credential creation; Kernel misses no mandatory sales call, agent-compatible signup flow, fast time to first request, copyable quickstart.
Operate. Kernel leads 94 to 53. Crawlbase misses structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable; Kernel misses idempotency support.
Pricing
Crawlbase does not publish a machine-readable starting price and has a free tier. Kernel starts at $0/mo and has a free tier.
| Crawlbase plans | Kernel plans |
|---|---|
| - | Free $0/mo |
| - | Hobbyist $30/mo |
| - | Start-up $200/mo |
| - | Enterprise Custom |
Signal by signal
| Signal | Crawlbase | Kernel |
|---|---|---|
| AgentReady | 68 | 89 |
| Discovery | 100 | 100 |
| Understanding | 38 | 92 |
| Adoption | 81 | 71 |
| Operability | 53 | 94 |
| Public API | Yes | Yes |
| MCP server | Yes | Yes |
| OpenAPI spec | Unknown | Yes |
| CLI | Yes | Yes |
| llms.txt | Yes | Yes |
| Self-serve signup | Yes | Yes |
| Free tier | Yes | Yes |
Which to pick
Kernel clears more of the signals an agent needs, so it is the safer default for unattended use. Full profiles: Crawlbase and Kernel. Alternatives to each: Crawlbase, Kernel.
An agent can fetch this as data: POST /v1/compare {"slugs": ["crawlbase", "kernel"]}