KernelCode Request Access
<p>06</p>Kernel Agent

Verificationagents can buy.

An MCP server and x402-enabled API through which AI agents discover verification tools, purchase individual checks, retrieve findings and consume results programmatically.

See all six toolsRequest Access
<p>01</p> How a call works

Discover. Pay. Verify. Act.

The x402 specification includes an MCP payment flow, so agents can pay directly when they call an individual tool — no subscription required.

  1. <p>01</p>Discover

    The agent connects to the Kernel MCP server and lists the verification tools.

  2. <p>02</p>Pay

    Paid tools answer with an x402 payment request. The agent pays per call in USDC.

  3. <p>03</p>Verify

    Kernel runs the check in an isolated worker and returns structured JSON.

  4. <p>04</p>Act

    The agent blocks the deploy, proposes a fix, or requests a deeper check.

<p>02</p> Example

An agent verifying code before deployment.

The agent asks, Kernel checks, the agent fixes — and the updated report and commit hash are recorded.

agent sessionillustrative
Coding agent

“Verify my contract before deploying to Robinhood Chain.”

Kernel MCP · scan_contract

Paid via x402

Review required

1 high-severity finding

{
  "tool": "scan_contract",
  "status": "review_required",
  "findings": [{
    "severity": "high",
    "issue": "privileged withdraw lacks access check"
  }]
}
Agent

Proposes a fix and reruns verification.

Kernel

Records the updated report and commit hash.

mcp configillustrative
{
  "mcpServers": {
    "kernel": {
      "url": "https://mcp.kernelcode.io"
    }
  }
}

Illustrative — the endpoint opens with early access.