Payments & Infra · Machine-to-machine payments · 2026Casper testnet
AgentPay
An on-chain service registry and x402 micropayments for pay-per-call API access on Casper.
- Contracts
- 3 on Casper
- Verification
- < 500 ms
01 The problem
Paying for an API per call is still a human workflow: sign-ups, keys, invoices. Automated clients need to discover a service, pay for one call and move on.
Providers list their APIs in an on-chain registry and add one middleware. Clients find providers through an MCP server, attach a signed x402 payment header, and settlement and reputation updates happen on Casper.
02 How it works
Hover or tap a step
03 What I built
- 01Registry, Payment and Reputation contracts in Rust on Casper testnet.
- 02A TypeScript MCP server with search, call, balance and history tools.
- 03Provider middleware and a facilitator that verify signature, nonce, balance and limit in under 500 ms.