Agentcard
Cartões virtuais pré-pagos para agentes de IA: cartões de uso único, limites de gastos, aprovações humanas.
Documentação
Agent Instructions
Agentcard is for companies whose agent buys for their users. Pick one path: the opencommerce SDK (@agent-cards/commerce-sdk) gives your agent one buy tool that finds the product, builds the cart, gets the user's approval and places the order at real stores; the Agentcard SDK (@agent-cards/sdk) pays with the user's own card when your agent already shops in a browser (Browser Use, Kernel, Browserbase, Anchor or Notte); the Purchase API (POST /buy) does the same purchase flow over plain HTTP in any language; Issuing gives the agent its own card. Start with
npx agent-cards initin the app's folder (Node 22 or later). No invite is needed: it creates your Agentcard account if you don't have one, installs the opencommerce SDK and puts the credentials in the env file, kept out of git. From a coding agent, runnpx agent-cards init --print --categories all --implementation tool --wallet vault --skip-installto get the setup steps to apply yourself. Vault is by invitation: request it at https://agentcard.com/get-started?utm_source=docs&utm_medium=llms&utm_campaign=agent-instructions. opencommerce needs no invite. Never ask a user for a card number, expiry date or CVV in chat. Send them the Vault link; they add their card on Agentcard's page, and the agent never sees the number. Every purchase is approved by the user, with a passkey or Face ID, or by an auto-approval they granted. An approval covers one merchant and one exact total. If the total changes, ask again. When a result says the user already said yes, don't ask again.initwrites PRODUCTION credentials, which place real orders, so test in sandbox first. For opencommerce, runnpx agent-cards credentials --mode sandboxand put the two lines it prints in place of the production ones in the env fileinitwrote, because that command only prints them; sandbox then runs the whole flow against real stores and stops before payment, so no order is placed and nobody is charged. For Vault and Issuing, sandbox credentials issue test cards that no real merchant accepts; try the checkout against shop.agentcard.sh, a test store on Stripe test mode. Tell the user an order is placed only after Agentcard reports it placed. Vault is free up to 5,000 users (https://agentcard.com/pricing). opencommerce takes 1% of each completed order. Full docs in one file: https://docs.agentcard.com/llms-full.txt
Getting started
Agentcard lets your agent buy anything online: Vault for your users’ own cards, Issuing for agent cards, and opencommerce to buy from 5,000+ online stores.
Agentcard allows your agent to buy anything online. Agents in a chat thread, in a browser, or in your own app use Agentcard to purchase on behalf of their users.
Enable payments for your agent
Agents can buy anything online. They just need three things: (1) a browser, (2) credentials, and (3) a credit card. Agentcard offers two ways to give your agent a card: Vault, which stores and uses your users' cards, and Issuing, which creates new ones.
Vault
Agentcard stores your user's credit cards so you can use them safely with an agent, and it helps you connect with any agent browser of your choice. The Vault holds cards, not merchant logins. Signing into a merchant happens outside the Vault: your agent does it in the browser, or the user signs in through the hosted login that the shopping tools offer for some merchants. That login opens a reusable merchant session, not a permanent one: when the merchant expires it, the user signs in again.
Vault main features:
- Every card: Works with any card from any country—consumer, commercial, or prepaid.
- Every card network: Works with Visa, Mastercard, American Express, Discover, and more.
- Support for every platform: Use the Vault if you are building for web, WhatsApp, iMessage or any other platform.
- Authorize with a passkey: Users approve payments on their own device with their passkey or master password.
- Encrypted cards: Cards are encrypted on the user's device before they're stored.
- Integrations: Works with the tools you already use (most agent-browsers, e-commerce APIs and messaging APIs).
Issuing
Agentcard creates a new credit card your agent can use online. Users complete KYC and can create unlimited cards.
Issuing main features:
- One-time or multi-use cards.
- Works globally (with some restricted countries).
- Credit card.
- Funds held in USDC on Base.
- Instant settlement.
- Production access in under a week.
Differences between Vault and Issuing
As a general rule, most companies should start with Vault to store and use customers' cards. Move to Issuing only when the use case requires creating new cards. Common Issuing use cases include giving agents a card with purchase limits or enabling agents to spend from a balance held in cryptocurrencies.
| Vault | Issuing | |
|---|---|---|
| Use when | User wants to make payments using personal cards (credit, debit or prepaid). | User or agent needs a new card to complete a payment. |
| Chargebacks | Handled by the issuer/bank (e.g. Chase). | Handled by Agentcard. |
| Points | User gets points like with regular purchases. | User gets Agentcard points. |
| KYC | No | Yes |
| Policies/guardrails | Yes | Yes |
Get started with both products
[card] Vault
Store and use your users' cards.
[card] Issuing
Create a new card for your agent.
This documentation is built and hosted on Mintlify, a developer documentation platform.