HTTP 402 payments with policy limits, request-bound receipts, escrow, and audit trails. All visible through Casper.
An autonomous AI agent requests premium data from a protected resource.
The server responds with a PaymentRequirement — amount, merchant, requestHash, and expiry.
The agent checks its spending policy (merchant allowlist, per-payment max, total budget) and authorizes exactly one request-bound payment.
Casper records the payment. The receipt is bound to the exact HTTP request. The API verifies it and releases premium data.
mock-* hashes. No real Casper funds are moved.pnpm demo:mock