Its own card
One card is created for one purchase, locked to it, and destroyed when it completes. Your real number is never shared.
Its own card with a limit you set. The bank's security check cleared for it. A checkout it finishes in its own browser. Zero taps from you.
See how a purchase runsOne card is created for one purchase, locked to it, and destroyed when it completes. Your real number is never shared.
Bank challenges on AgentPay cards are answered automatically. No code sent to your phone, at any hour.
Sign in to a store once. Your agent keeps the session, saves its card to the account, and checks out alone.
Asks you first, or buys on its own, never past a card's limit. Every charge in one activity feed.
Any model, any framework. Install the skill as a plain file, or wire the SDK or MCP. Your assistant pays from its next run, with a card it creates itself, inside the limit you set.
Every endpoint is callable by the agent itself. It creates its card, checks its budget, starts a checkout, connects a store, registers a webhook. No human in the loop unless you put one there.
POST /v1/cardscreates its own cardGET /v1/spendreads what it may still spendPOST /v1/checkoutbuys, in its own browserPOST /v1/connectionskeeps a store signed inPOST /v1/webhookshears back when money movesPick the door your agent already uses. Click one and watch it type. Then sign up free to add money and get a key.
npx skills add Kato-Official/agentpay-skillsA plain Markdown skill: your agent reads it and knows how to pay.
Two modes. In Asks you first, every purchase waits for your yes, however small. In Buys on its own, the agent never goes past the limit you set.
How it worksLink AgentPay to WhatsApp or Telegram, or talk to it by voice. The agent asks there, you answer there. A purchase waits for your yes and nothing else.
Your store logins live in the vault on our servers, never in the agent's prompt. You approve with your passkey one time on the merchant's own page. The agent's browser keeps the session from then on.
At the payment page the agent types the card it created a second ago: number, expiry, CVC. The bank's check is answered for it. Zero human steps from search to receipt.
Fund one prepaid wallet by card, bank transfer or stablecoin. Every agent, every card and every purchase draws from it.
One multi-use card per tool, each with its own monthly limit. Pause the card and the subscription stops.
Every agent purchase is fenced, logged and tied to its run:
Your assistant books the flight, orders the dinner, renews the subscription. Each purchase on a card made for it, capped at what the person approved, never on their real number.
An ops agent that pays invoices, tops up API credits and buys the supplies. Multi-use cards per vendor with monthly limits, one wallet, every charge tied to the run that made it.
Coding agents that buy a domain, a server or a dataset mid-task. Install the skill, and the agent pays from its next run with zero human steps.
Every card, every check, every checkout. No plan to pick, nothing to upgrade to.
No card details. Live in two minutes.
For a company buying at size, with a contract, invoicing and a name to call.
A 20 minute call, then you are set up.
Everything you need to know about AgentPay.
It is payments for AI agents. A business funds one prepaid wallet. The agent creates its own cards from it, single use for one purchase or multi use for a subscription, with the limit you set. The bank's security check (3D Secure) is cleared for it, and it checks out in its own browser that stays signed in to the store.
No. The agent pays with a Visa or Mastercard that works anywhere cards are accepted, in the store's normal checkout. The store sees a card, not an agent.
Both. A consumer assistant buys for its users on cards made per purchase. A company agent runs purchases from one wallet with per-vendor limits. The same API, the same console.
A linked card is your real card in the agent's hands: the bank's code lands on your phone, every charge blends into one statement, and one leak exposes the whole account. An AgentPay card is created for one purchase, capped, answered for at the bank, tied to the agent and its run, and destroyed when done.
You do, with two modes. Asks you first: every purchase waits for your yes, however small, on the web, WhatsApp, Telegram or by voice. Buys on its own: the agent never goes past a card's limit. Either way every charge lands in one activity feed.
Bank challenges on AgentPay cards are answered programmatically, on our side. No code is sent to your phone and nobody waits, at any hour.
Any. The skill is a plain Markdown file any agent can read; the MCP server, the TypeScript and Python SDKs and the REST API cover the rest. Claude, GPT, Gemini, Grok, Llama and Mistral agents run on it today.
By card, by bank transfer, or with stablecoins through our payment partner with no custody on our side. Money in the wallet is spendable by every agent you connect, inside the limits you give each card.
Free: unlimited cards, unlimited 3D Secure, up to $30,000 on one card, unlimited agents and store logins. Enterprise terms, invoicing and higher limits on request.
Cards work at every store today; that is why we start there. As stores adopt agent payment protocols, the same wallet and the same limits apply to them.
Agents have started to buy: flights, servers, domains, tools, lunch for the team. They need a way to pay that was built for them, not a card number copied out of a drawer.
At Joomjoo we have been building the payment layer for AI agents: one prepaid wallet, cards the agent creates itself, the bank's security check cleared on its own, and a browser that stays signed in. AgentPay is that platform, open to anyone, free to start.
AgentPay is how agents pay.