agentcard

name	agentcard
description	Pay for things with Agentcard, virtual debit cards for AI agents. Fund a wallet, mint single-use or subscription cards, reveal credentials to fill a checkout, track transactions, and shop at supported merchants through the agent-cards CLI. Use when the user asks you to buy something, pay for an API or SaaS signup, subscribe to a service, issue a card, or manage agent spending.
license	MIT
requiredCapabilities	["egress:api.agentcard.sh","egress:registry.npmjs.org"]
metadata	{"homepage":"https://agentcard.sh","docs":"https://docs.agentcard.sh"}

Agentcard: cards you can pay with

Agentcard gives you a real payment method without ever holding the user's own card. The user funds a wallet; you mint a virtual debit card sized to one purchase, pay, and the card closes itself after the first approved charge. Subscriptions use multi-use cards with a hard total limit. Every money move needs the user's explicit go-ahead.

VOCABULARY: the user's WALLET is their cards; their BALANCE is their cash. Cards are funded from the balance.

Setup (once per computer)

Install the CLI on your computer; it stays installed:

npm install -g agent-cards   # or: npx -y agent-cards@latest <command>
agent-cards whoami           # signed in? shows the account. Otherwise: sign in below

Sign in (once per person)

Each person connects their own Agentcard account. Never sign one person's agent into another person's account.

1. agent-cards login --email <their email> sends a one-time code to that email.
2. Ask them to read the code back to you in chat (if they have connected their inbox to you and ask you to, you may fetch it yourself).
3. agent-cards login --email <their email> --code <code> completes sign-in. The session persists in your $HOME across turns.

Headless alternative: if $AGENT_CARDS_JWT is set in your environment (for example vended through the keychain), the CLI uses it directly; no login needed. New users can create an account at https://agentcard.sh, or login walks them through it by email.

Driving it

The CLI is an agent-first tool catalog (the same catalog as the Agentcard MCP server). Load the canonical guide into context once per session, then follow it:

agent-cards api --agent-help          # read this fully, once per session
agent-cards api search <regex>        # find tools (balance, create_card, buy, ...)
agent-cards api describe <tool>       # schema before first use; never guess
agent-cards api call <tool> '<json>'  # invoke; JSON result on stdout

Tools that move money refuse to run without --confirm. That flag is your attestation that the user confirmed the exact action in chat, so ask first, every time: amount, merchant, and what it is for.

Common moves, all via api call: get_balance, add_funds (returns a single-use Apple Pay / Google Pay link; relay it to the user verbatim, never shortened or paraphrased), create_card with amount_cents (single-use by default; type: "multi_use" for subscriptions), get_card_details (PAN/CVV, only when actually filling a checkout), list_transactions, close_card. Shopping at supported merchants (DoorDash and others) goes through the conversational buy tool: call get_instructions first and keep passing the same conversation_id.

First-time accounts hit gating statuses in a fixed ladder; each error names the next step (user_info_required then kyc_required then wallet_funding_required). Identity verification is conversational (ID photo, confirm fields, short browser face scan) and happens once.

Rules

• Confirm before money moves. create_card, add_funds, withdraw, any checkout: state amount + merchant, get a yes in chat, then pass --confirm.
• Never post card credentials in a shared channel. Reveal PAN/CVV only in the card owner's 1:1, only when needed to complete a payment, and prefer pasting them straight into the payment form over showing them at all.
• Non-interactive shells only. Use api call and flag-complete commands. Never run the CLI's interactive prompts (cards create, signup, support, bare fund) from your shell; they hang without a TTY.
• Right-size cards. Mint for the purchase amount plus tax/tip headroom, not the whole balance. Single-use unless the merchant charges repeatedly.
• Format money as dollars. $12.50, not 1250 cents (amounts are in cents).
• Payment links are single-use. If one expires or gets consumed, mint a fresh one; never ask the user to pay twice for the same thing.

Org deployments (advanced)

If your admin has vended a shared Agentcard org credential to this conversation (see your "Shared org credentials" list), that is the org's B2B API key for api.agentcard.sh: call it by proxy through the credential broker instead of signing in personally. The B2B surface (org cards, spend policies, webhooks) is documented at https://docs.agentcard.sh.