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) | |
|---|---|---|
| For | An individual giving their own agent a card | A platform issuing cards to its users |
| CLI / package | agent-cards (npm) | agent-cards-admin (npm) |
| MCP | @agent-cards/mcp (per-user OAuth) | Same MCP server, authenticated with a user’s OAuth credentials — not API keys |
| Auth | Magic-link sign-in → JWT | API keys (sk_test_* / sk_live_*) for the REST API |
| Amount units | CLI --amount <dollars> (e.g. 25 = $25.00); MCP amount_cents | REST amountCents (cents; 2500 = $25.00) |
| Payment-method command | agent-cards payment-method setup (singular) | agent-cards-admin payment-methods setup (plural) |
| Max per card | Plan-scoped: 500 Basic | $50 default (contact support for higher) |
| Docs | Personal | Companies (you are here) |
This is the Companies documentation — issuing cards to your users via the REST API, admin CLI, and webhooks. If you’re an individual who wants to give your own agent a card, see the Personal docs instead.
How it works
- Create cardholders — Set up cardholders for each end-user or agent that needs cards
- Attach payment methods — Each cardholder saves a payment method via secure checkout
- Create cards — Issue virtual Visa cards with a specific spend limit, held on the cardholder’s payment method
- Give cards to agents — Your AI agents use the card number, expiry, and CVV to make purchases
- 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