One engine.Four layers.
Kernel Scan, Prove, Attest and Agent share one verification engine — one job system, one report format, many interfaces.
Pick the depth of evidence you need.
Start with an automated scan, go deeper with formal verification, then publish the result so anyone can check it later.
Kernel Scan
Static analysis, dependency checks and dangerous-permission detection for repositories and contracts.
<p>02</p>Kernel Prove
Formal verification with Aristotle for supported code and properties.
<p>03</p>Kernel Attest
Tamper-evident verification records on Robinhood Chain.
<p>04</p>Kernel Agent
An MCP server and x402 API so agents can buy individual checks.
One unified job and reporting system.
Every interface submits jobs to the same engine. Workers do the checking, reports land in structured storage, and attestations are anchored onchain.
Untrusted code never runs next to the money.
The most important engineering rule at Kernel: repository code is never executed inside a normal Cloudflare Worker.
Isolated runners
Scans run in isolated scanning runners, never in the request path.
No ambient access
Runners get restricted network access and no access to secrets.
Payments kept apart
Payment handling is separated from verification execution, so a hostile repository can’t reach the payment path.