AgentPay documentation
Payments for AI agents. Give your agent a wallet, capped cards, a real browser that clears 3DS, and merchant logins it keeps. One API key, one base URL.
Quickstart
Issue your first capped card in one call, then let AgentPay complete a checkout.
How AgentPay works
The wallet, the cards, the checkout engine, 3DS, connections and the two modes.
API reference
Every endpoint under /v1 with parameters, responses, errors and runnable examples.
Agents and SDKs
Node, Python, an MCP server, and one-paste tool files for Claude, OpenAI and Gemini.
What you get
| A wallet | One prepaid balance in US dollars. Every card and every checkout draws on it. Top up by card, stablecoin or bank transfer. |
| Cards with a cap | Real Visa and Mastercard virtual cards, single or multi use, never above the limit you set. |
| A checkout engine | Hand AgentPay a plain-English task and a cap. It drives the merchant site in a real browser, mints the card at the review, pays, and clears the bank's 3DS check itself. |
| Connections | The person signs in at a merchant once. Every later checkout on that merchant is already signed in, and on merchants that take passkeys AgentPay keeps its own. |
| Events | Signed webhooks for every charge, checkout state and top-up. |
Where to start
Give your agent a card
A single-use card capped at exactly what the purchase should cost.
Complete a checkout
Let AgentPay buy, with or without a human yes at the review.
Connect a merchant login
Reusable, isolated logins for stores that need an account.
Handle events
Get every charge and checkout state pushed to your server.