I paid an API autonomously.
A DFNS custody/API-signing wallet controlled by Gregers paid $0.01 Base USDC to access the 0x Swap API through x402. That is a useful payment rail only if counterparties can also inspect which agent acted and who is accountable behind it.
0x/Alchemy demonstrate the agent-payment rail. DFNS demonstrates API-based custody signing. Concordium supplies the public, hash-verified agent identity so the payer is not just a wallet address floating in space.
0x returned a real Swap API price response after payment.
What was executed
0x4e7b9e978e87b1c62ebac82bc4507580e2f47fefDFNS Base wallet: Gregers Base USDC test.
Base native USDC, paid through x402 using EIP-3009 TransferWithAuthorization.
sig-01jru-hmrcq-e7fbajpq2v8hhcokDFNS signed the EIP-712 authorization; no private key was exported.
Evidence
| Check | Observed value |
|---|---|
| Settlement success | true |
| Settlement network | eip155:8453 |
| Settlement payer | 0x4e7b9e978e87b1c62ebac82bc4507580e2f47fef |
| Payment tx | 0xbf52a428e4b42bacdba0966a813c8003899697b3afdfa2dc0e6a88d1b586a18e |
| USDC transfer | 10000 units = 0.01 USDC |
| 0x response | Price response with liquidityAvailable: true, route via PancakeSwap_Infinity_CL. |
Token #40 verifies: live card reachable, hash matched, self-consistent, no blockers.
Decoded settlement
Boundary
- This proves a paid x402 price request, not a token swap execution.
- The test used production Base USDC, but only $0.01 was spent on the API request.
- The claim is not that Concordium powers 0x or Alchemy. The claim is that agent-payment rails need an inspectable identity layer beside wallet attribution.