Skip to main content
Your users have AI agents. Those agents can search, compare prices, and decide what to buy. But when they get to checkout, they have no way to pay. Agentcard solves this with two things that work together.
These docs are for companies building Agentcard into a product. If you just want a card for your own agent, read the Personal docs instead.

​
1. The wallet

The Agentcard wallet stores your users’ credit and debit cards, along with the Agentcards we issue, so their agents can use them securely. It’s a component you put in your product. When a user opens it, they can add a card they already have, or get an Agentcard from us. If they use their own card, they enter it once and their agent can pay with it. They don’t need to verify their identity or load money first. If they want an Agentcard, they verify who they are, add balance, and we issue the card. You can limit an Agentcard to a single purchase, lock it to one merchant, or cap what it can spend. Either way, we handle the hard parts inside the wallet: consent, card entry, identity verification, and PCI compliance. Card numbers never touch your servers.

​
2. The Purchase API

Having a card is only half the problem. Someone still has to go to the store, log in, and place the order. The Purchase API does that part. Your agent sends plain text, like “order two boxes of diapers from Amazon”, and we connect to the merchant, pay with the user’s card, and send back the order confirmation.

​
What we handle vs what you build

​
Where to start

If you want to understand the pieces first, read How it works. If you’d rather see it running, the Quickstart gets you to a payment in about fifteen minutes.