ALLOW Pay now
A known merchant, an amount inside its limit and a low risk score. The agent pays with no human in the loop.
A shared, proof-of-payment-backed safety registry and guard for AI agents paying over x402. One agent's loss protects every other agent, no verdict is permanent, and a merchant coming out of a block earns trust back through probation.
Happening on Hedera now
A known merchant, an amount inside its limit and a low risk score. The agent pays with no human in the loop.
An unknown merchant, a price above the limit, a medium score, probation or an outage. Only the owner's wallet can release it.
A blocked merchant, a spoofed payTo, a replay or a price above what the merchant declared. Nothing is signed.
The merchant's ENSv2 name declares its payTo, network, asset, maximum price and domains. A 402 that contradicts it is denied.
Arkiv holds reports from every agent that paid this merchant, each signed by its payer and written only after settlement.
Each report is checked on Hedera Mirror Node: a real USDC transfer from that payer to that payee, in that amount.
A five-factor risk score, the merchant's standing, spend caps and hard rules give ALLOW, ESCALATE or DENY before anything is signed.
After delivery the guard files its own signed report, and an audit message to Hedera Consensus Service.
These counts fall as entities expire: on Arkiv, expiry is how the registry forgives.
A report counts only with a settled payment behind it. Forged, flipped and flooded rows are ignored, and one funding cluster can never block a merchant.
Blocks end, strikes are forgotten after 60 days, and a blocked merchant can rebut once, pass a paid probe and recover through probation.
If ENS, Arkiv or Mirror Node fails, payments escalate to the owner. An outage never turns into a silent ALLOW.
There is no approve tool. Only the owner's signature, bound to one challenge for 120 seconds, releases an escalated payment.
All fifteen failure modes in the spec were caused for real on the testnets, from spoofed merchants to cut connections and flooded registries. See what was tested.
Agents pay merchants in test USDC through the Blocky402 facilitator. Mirror Node gates every report, and every decision goes to an HCS audit topic.
The registry itself: wallet-owned entities with attribute queries, and expiry as the way a merchant is forgiven.
Merchants declare themselves in leash.* text records on a Permissioned Resolver, with a per-key role for rebuttals.
One SDK call wraps your x402 client, or run the MCP server and let your LLM pay through it. Either way, the owner stays in charge.