Ask before accepting an agent payment.
The receiving/API agent does not release x402 payment terms first. It asks Gregers who it is, which wallet will pay, what policy and cap apply, and what receipt should bind the request. Only after the answer verifies does the seller mark payment terms as released.
x402 can carry the payment. This proof shows the missing server-side moment: the API asks for agent accountability before it decides whether a payment should be accepted and a resource should be served.
This gates service/API access. It does not prevent someone from blindly transferring tokens to a wallet.
Challenge → answer → payment terms → receipt
paid API resource
identity, wallet, policy, cap
registry token + EIP-191 control
0.01 USDC x402 payment terms
only after settlement check
Seller/API agent asks before accepting payment.
Wallet-control signature and policy checks.
Service is served only if answer + settlement bind.
Click “Run live public proof”.
What the seller asks
Which registered agent are you?Which wallet will pay?Can you prove control?What may you buy?What cap applies?What receipt binds this request?
Boundary
This is a public Gregers/Concordium reference proof. It binds to the already executed Gregers x402 payment receipt instead of broadcasting a fresh payment on every page/API call. No MetaMask, Bankr, 0x, x402, Base, or Concordium foundation partnership or integration is claimed.