Skip to content

Proof402

Before an AI agent spends your money, it has to buy proof.

My role
Builder · Hack-Nation 2026 (Spiral challenge)
When
2026
Status
Hack-Nation 2026
Stack
Next.js 15, TypeScript, Tailwind CSS

01

Where it started

As AI agents get wallets and call paid APIs, the hard problem isn't payment but permission. An agent that can pay can also burn a budget on a scam API or a fake grant.

02

What I owned

Builder · Hack-Nation 2026 (Spiral challenge)

03

How I built it

  • Designed a policy gate that intercepts every risky agent action and answers with a real HTTP 402 Payment Required, ready for L402 clients.
  • Issued machine-readable proof receipts (verdict, confidence, evidence, risk flags) for 3–6 sat Lightning-style micropayments behind a swappable payment adapter.
  • Built a configurable spend policy (caps, confidence thresholds, blocked terms) and a live dashboard of allowed, denied and manual-review actions.

04

What changed

Every agent spend leaves an auditable reason (allowed, denied or sent to manual review), using a 402 and receipt schema ready to plug into real Lightning rails.

Next.js 15TypeScriptTailwind CSSHTTP 402 / L402Lightning