Kernel vs Scrapybara
Kernel scores higher on the AgentReady, 89/100 against 76/100. They differ on 9 of the 41 signals. Which ones decides whether an agent can adopt them without a person watching.
What each one is
Kernel. Kernel provides crazy fast, open source browser infrastructure for AI agents to access the internet.
Scrapybara. Scrapybara provides powerful virtual desktop infrastructure for computer use agents.
Where Kernel is ahead
Kernel passes pricing understandable and limits / constraints documented, and Scrapybara 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: self-service signup and free trial or free allowance. Scrapybara misses those.
And on operate, retry behavior documented, rate-limit behavior predictable and observable execution. Scrapybara misses those.
Where Scrapybara is ahead
Scrapybara 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: copyable quickstart. Kernel misses it.
What neither does
Both fail no mandatory sales call, agent-compatible signup flow, fast time to first request, 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. Kernel leads 92 to 85. Kernel misses authentication documented; Scrapybara misses pricing understandable, limits / constraints documented.
Adopt. Kernel leads 71 to 55. Kernel misses no mandatory sales call, agent-compatible signup flow, fast time to first request, copyable quickstart; Scrapybara misses self-service signup, no mandatory sales call, agent-compatible signup flow, free trial or free allowance, fast time to first request.
Operate is whether an agent can run against it in production and recover when a call fails. Kernel leads 94 to 65. Kernel misses idempotency support; Scrapybara misses retry behavior documented, idempotency support, rate-limit behavior predictable, observable execution.
Pricing
Kernel starts at $0/mo and has a free tier. Scrapybara does not publish one.
| Kernel plans | Scrapybara plans |
|---|---|
| Free $0/mo | - |
| Hobbyist $30/mo | - |
| Start-up $200/mo | - |
| Enterprise Custom | - |
Signal by signal
| Signal | Kernel | Scrapybara |
|---|---|---|
| AgentReady | 89 | 76 |
| Discovery | 100 | 100 |
| Understanding | 92 | 85 |
| Adoption | 71 | 55 |
| Operability | 94 | 65 |
| Public API | Yes | Yes |
| MCP server | Yes | Yes |
| OpenAPI spec | Yes | Yes |
| CLI | Yes | Yes |
| llms.txt | Yes | Yes |
| Self-serve signup | Yes | Unknown |
| Free tier | Yes | Unknown |
Which to pick
Kernel clears more of the signals an agent needs, so it is the safer default for unattended use. Full profiles: Kernel and Scrapybara. Alternatives to each: Kernel, Scrapybara.
An agent can fetch this as data: POST /v1/compare {"slugs": ["kernel", "scrapybara"]}