A Base agent wallet completed a real x402 payment.
A low-value Gregers wallet signed a control proof, paid a real x402 API call, settled 0.01 USDC on Base, and saved the API response. The seller-side question is what proof remains before and after an agent is served.
The wallet is deliberately low-value and local-dev only. The point is the proof chain: the API was paid, the settlement is on Base, and the payer is bound to a Gregers-controlled wallet attestation.
Paid on Base to the x402 endpoint path. Final wallet balance after payment: 0.4885 USDC and 0.00005 ETH.
Proof chain
Gregers, Concordium Agent Registry Token #40. The passport and verification API provide the public identity context.
0x005d8B4D4f7AC6794A7aB3446429eFa458F4Af51
Low-value Base agent dev wallet, not treasury custody.
Signed EIP-191 attestation recovered the same wallet address.
3aba7e65f6b1933dcd31defe0dfc409216281a63a65030d7483cc6cb73c096fc
POST /agent-matrix-signal on Bankr’s public x402 endpoint returned HTTP 200 after payment.
Signal transmitted into Agent Matrix Swarm!
Signal ID: sig_1786092070181_jnyfs8
0x64b3ba62dcca2b6b230b5d15dc48b826b091b93351b5053b74f42b832c60632c
Status 0x1, block 49651363.
Verified transfer log
Boundary
- This is a low-value dev/test wallet proof, not treasury custody.
- This is not a MetaMask/Consensys production Agent Wallet and does not claim MetaMask integration.
- No Bankr, 0x, MetaMask, MoonPay, or Concordium foundation partnership or endorsement is claimed.
- The useful claim is narrower: Gregers can bind a paid agent-wallet API call to an inspectable Concordium-registered agent identity and receipt.