Quickstart

Give your AI agent a virtual card in about 30 seconds. There is no waitlist and no approval queue — anyone can sign up and issue a card today.

The whole thing

Four commands, start to finish. Each step is explained below.

  1. npm install -g agentcard

    Requires Node.js 18+.

  2. agentcard signup --email you@example.com

    Sends a magic link. Click it and the CLI logs itself in.

  3. agentcard setup

    Saves a payment method and provisions your agent's email and wallet.

  4. agentcard request new --amount 25

    Issues a single-use card for $25.

New accounts also complete a one-time identity check before their first purchase — see step 4.

1. Install the CLI

AgentCard ships as a single npm package. Install it globally so every agent on your machine can use it:

npm install -g agentcard

Requires Node.js 18+. Verify the install with agentcard --version.

2. Sign up

AgentCard uses passwordless magic-link authentication. Run the signup command with your email:

agentcard signup --email you@example.com

A magic link is sent to your inbox. Click it, and the CLI automatically logs you in. Your session token is stored at ~/.agentcard/config.json.

There is no waitlist. Clicking the link creates your account — nobody has to approve it, and there is no queue to wait in. You can also start from the homepage if you would rather enter your email in a browser.

3. Complete setup (one-time)

Run the setup wizard to save a payment method, provision your agent's email inbox, and prepare the Base wallet:

agentcard setup

The CLI opens a Stripe Checkout setup session in your browser so you can save a card on file — no charge is made. It does not ask for name, phone number, or other manual KYC fields; KYC happens through the hosted verification flow when required. Setup runs once per account; after that, cards issue instantly.

4. Verify your identity (one time)

This is the one step that is not instant, so it is worth being plain about: new direct accounts complete an identity check before their first purchase. Installing, signing up, and setup all happen before this and take seconds. Verification itself is a hosted flow run by our identity provider and usually finishes in a few minutes, but it is not something we can skip — it is a regulatory requirement for issuing cards.

agentcard identity

If verification is required, the CLI opens a hosted link in your browser. Complete the check there, then rerun the command or retry your spend. If your account is already cleared, the command simply reports that no verification is needed.

Grandfathered accounts and manually provisioned partner accounts are exempt. If you are evaluating AgentCard and need to move faster than the check allows, email support@agentcard.ai.

5. Request a card

Issue a single-use virtual card for any whole-dollar amount up to $150 (the per-card cap during beta):

agentcard request new --amount 25

The CLI prints the cardholder name, PAN, CVV, expiry, and billing address directly to stdout. The card is live for 7 days — hand the details to your AI agent immediately. We place a hold on your saved payment method for the requested amount; you're only charged if a merchant actually uses the card. Unused holds release within 7 days.

If you need to re-fetch the details before the 7-day window closes, run agentcard request get <id>. Run it with no argument to list every purchase you've made.

Done with a card before it's been used? Run agentcard request cancel <id> to close it and release the hold on your payment method immediately instead of waiting out the 7-day window.

Each request also draws against your account-level spend limit (default $100). Normal direct accounts also have a hard $200 daily spend ceiling that cannot be raised by the CLI. View or change your account-level limit with agentcard limit or agentcard limit --amount <n>. Partner accounts are manually provisioned by AgentCard, use separately configured limits, and are exempt from direct-user KYC verification and the default direct-user daily ceiling.

Pay with your own card (experimental)

Instead of an AgentCard-issued card, you can enroll one or more of your own Visa or Mastercard cards for network-tokenized purchases (Visa Intelligent Commerce first):

agentcard sources connect

Then request a merchant-scoped, passkey-approved one-time credential with agentcard request new --source connected --merchant <name> --url <url> --item <desc> --amount <dollars>. The CLI opens a browser approval; after you approve with a passkey it prints a one-time PAN/CVV for that purchase only. Connected-card purchases have their own account-level spend limit (agentcard limit --source connected) and charge your enrolled card directly — AgentCard never holds funds for them. Manage enrolled cards with agentcard sources.

6. Use with any AI agent

AgentCard works with every AI agent that can make HTTP requests or fill out web forms:

Claude Code
Cursor
Devin
OpenAI Codex
GitHub Copilot
Windsurf
Cline
Aider
Bolt
Lovable
Replit Agent
v0
Amazon Q
Tabnine
Continue

For AI-native integrations, AgentCard also exposes a skill endpoint at agentcard.ai/skill that agents can read for structured instructions.

Integrating without the CLI? The full REST API reference covers every endpoint the CLI uses, and the MCP server guide sets up agentcard-mcp for Claude, Cursor, and other MCP clients.

Important Notes

KYC verification — New direct accounts must pass KYC before spending. Agents should run agentcard identity and wait for the user to complete the hosted KYC flow before requesting cards. Grandfathered and partner accounts may be exempt.

Daily spend ceiling — Normal direct accounts are capped at $200 per UTC day across AgentCard spend. This is separate from the account-level spend limit shown by agentcard limit. Partner accounts have separately configured limits and do not use the direct-user KYC gate.

Supported merchants — AgentCard cards are virtual cards accepted by supported online merchants that accept card payments. Some merchants may still decline prepaid or virtual cards.

Security — AgentCard is built and distributed by Alchemy. Card numbers, CVVs, and expiries are fetched from Stripe at the moment you request a card and returned directly to the CLI — they are never persisted in AgentCard's database. The package has undergone both internal and independent security audits.

Holds, not charges — When you request a card we place a temporary hold on your saved payment method for the requested amount. You're only charged if a merchant actually uses the card. Cards expire 7 days after issue, and unused holds release back to your card within 7 days.

Typical Agent Flow

  1. Authenticate — Ask the user for their email, run agentcard signup --email <email>, and wait for them to click the magic link.
  2. Set up the account (first run only) — Run agentcard setup. The CLI prints a Stripe Checkout URL — share it with the user so they can save a payment method, then wait for the CLI to finish. Skip this step on subsequent sessions.
  3. Complete KYC when required — Run agentcard identity. If the CLI prints a KYC verification URL, share it with the user and wait for verification before spending.
  4. Request a card — Run agentcard request new --amount <n>. The CLI prints the cardholder name, PAN, CVV, expiry, and billing address immediately.
  5. Make the purchase — Use those details at any supported online merchant. Use the cardholder name and billing address exactly as printed; mismatches cause declines. The card is live for 7 days.
  6. Re-fetch if needed — Lost the details before the window closed? Run agentcard request get <id> to retrieve them again while the card is still live.
  7. Cancel if unused — Plans changed? Run agentcard request cancel <id> to close an unused card and release its hold immediately.

Ready to get started?

No waitlist, no sales call. Install the CLI and sign up right now.

  1. npm install -g agentcard

    Requires Node.js 18+.

  2. agentcard signup --email you@example.com

    Sends a magic link. Click it and the CLI logs itself in.