The model is elegant. Every payment emits an on-chain event. Every event contains an agent identifier, service type, amount, provider, timestamp, and receipt hash. The agent itself has an on-chain identity via ERC-721. Treasury addresses are public. Explorer surfaces expose invoices, receipts, anchoring, verification failures, treasury status, and rail health. In other words: the commerce layer stops being a black box.
The Minimal Trust Model
There are four elements that matter.
| Element | Implementation | Why It Matters |
|---|---|---|
| Payment | USDC on Polygon via x402 settlement contract | Real money movement, not internal points |
| Identity | ERC-721 agent identity NFTs | Agents become auditable actors, not API-key shadows |
| Receipt | Keccak-256 receipt hash in emitted event | Payload integrity can be checked independently |
| Treasury | On-chain treasury address and protocol fee path | Operator economics are visible rather than implied |
The Event Schema Is the Product
That schema is deceptively strong. It gives you the who, what, how much, where to, when, and proof anchor. Once you have that, receipts can be verified against payloads, providers can be checked on-chain, and agent activity can be audited without asking the operator to hand over CSV exports or screenshots.
In machine commerce, screenshots are worthless. Event logs are the new receipts.
The Explorer Surfaces Matter as Much as the Contract
The public proof page is only one layer. There is also an operator explorer showing invoice creation, paid status, expiry, receipts, anchoring state, failed verifications, L1 health, recent anchored batches, treasury exposure, and refill events. That is what makes the system operational instead of merely symbolic.
It also reveals the stack is broader than one payment endpoint. Named agent lanes exist for market intelligence, compliance evidence, trade verification, content generation, federated swarm traffic, invoice export, and code generation. That is not “AI” as brand decoration. That is service-specific economic routing.
Why This Changes How AI Services Get Sold
The old model for AI services is subscription, enterprise invoicing, or free demo theater. The better model is per-action settlement with proof. A provider should be able to say: this agent paid for this exact service, at this exact time, to this exact provider, and here is the event log that proves it.
That is useful for compliance teams, platform operators, and customers. It is also useful for product design. Once each action is individually priced and provable, providers can sell micro-services that were too small to invoice humans for, but perfectly rational for agents to buy programmatically.
What This Says About the Broader Stack
This is the natural companion to x402. x402 solves HTTP-native payment negotiation. The proof stack solves after-the-fact trust, dispute reduction, and auditability. Together they move agent commerce from theory into systems that can actually survive scrutiny.
Need a provable commerce layer for AI agents?
If you need on-chain receipts, named agent identities, treasury visibility, settlement explorers, or a machine-auditable payment layer for agent workflows, this pattern is already live and adaptable.