Skip to main content
AgentCard lets you create and manage prepaid virtual Visa cards that AI agents can use to make purchases on the web. Each card belongs to a cardholder, is funded by a hold on their payment method, and can be created, monitored, and closed programmatically.

Two products

AgentCard ships as two products on one backend. Pick the one that matches your use case — they use different packages, auth, and units, and mixing them up is the most common integration mistake.
Consumer (solo agent)Organizations (B2B / this guide)
ForAn individual giving their own agent a cardA platform issuing cards to its users
CLI / packageagent-cards (npm)agent-cards-admin (npm)
MCP@agent-cards/mcp (per-user OAuth)— (use the REST API)
AuthMagic-link sign-in → JWTAPI keys (sk_test_* / sk_live_*)
Amount unitsCLI --amount <dollars> (e.g. 25 = $25.00); MCP amount_centsREST amountCents (cents; 2500 = $25.00)
Payment-method commandagent-cards payment-method setup (singular)agent-cards-admin payment-methods setup (plural)
Max per cardPlan-scoped: 50Free/50 Free / 500 Basic$50 default (contact support for higher)
Docsagentcard.sh + agent.txtdocs.agentcard.sh (you are here)
This documentation covers the Organizations / REST API product. For the consumer agent-cards CLI and MCP server, see agentcard.sh and its agent.txt.

How it works

Card creation flow
  1. Create cardholders — Set up cardholders for each end-user or agent that needs cards
  2. Attach payment methods — Each cardholder saves a payment method via secure checkout
  3. Create cards — Issue virtual Visa cards with a specific spend limit, held on the cardholder’s payment method
  4. Give cards to agents — Your AI agents use the card number, expiry, and CVV to make purchases
  5. Monitor and close — Track balances in real time, close cards when done to release held funds

Access methods

REST API

Programmatic access with API keys. Create cards, manage cardholders, and attach payment methods.

CLI

Manage organizations, cards, and cardholders from your terminal with the agent-cards-admin CLI.

Key features

  • Prepaid cards — Cards are backed by payment method holds, so agents can never overspend
  • Per-card limits — Each card has a fixed spend limit (max $50.00 by default for API organizations; contact support to raise it)
  • Hold-based funding — Funds are held on the cardholder’s payment method and only captured on use
  • Real-time balances — Track remaining balance as transactions settle
  • Instant close — Revoke a card at any time, uncaptured holds are released
  • Audit trail — Every card creation, detail access, and close is logged