Agentcard
virtual cards for AI agents, now with DoorDash checkout
Last verified:
What is Agentcard?
AgentCard issues single-use virtual Visa cards and programmatic card controls so AI agents, scripts, and agent-first platforms can make online purchases on behalf of users or services. The product is provided as a developer-friendly CLI, REST API, and admin CLI for organizations, enabling quick card issuance, cardholder and organization management, and integration with Stripe for billing and payment-method setup. Key features include one-command card creation with card PAN/CVV/expiry printed to the terminal, per-card spend limits and expiry windows (cards live for a short, defined period), and real-time tracking of card activity and balances for auditing agent spend. AgentCard is aimed at developer teams building autonomous agents, platforms issuing cards to agent instances, and startups that need programmatic, ephemeral payment instruments for AI-driven workflows.
Agentcard pricing
Pricing model: Freemium
AgentCard requires creating an organization and attaching a payment method via Stripe; the site describes saving a card on file in Stripe during setup with no initial charge. The product offers pay-as-you-go card issuance tied to your organization and Stripe billing; during beta there is a per-card amount cap (e.g., whole-dollar amounts up to the stated beta limit). Specific plan tiers, monthly subscription pricing, or per-card fees are not listed on the public docs pages and are managed through your organization and Stripe billing integration.
Agentcard pros
- Single-command card issuance from the terminal
- CLI prints full card details immediately for programmatic use
- Supports single-use virtual Visa cards for online merchants
- Cards have configurable whole-dollar amounts up to the beta cap
- Cards automatically expire after a short live window for security
- Admin CLI for organizations, API keys, and billing management
- REST API for programmatic card creation and retrieval
- Stripe Checkout integration to attach payment methods securely
- Ability to create and manage cardholders via API
- Re-fetch card details while the card remains live
- Session tokens stored locally for headless or scripted flows
- Passwordless magic-link authentication for fast onboarding
- CLI supports non-interactive flags for automated agent setup
- Organization-scoped API keys for multi-tenant billing and control
- Real-time transaction and balance endpoints for monitoring
Agentcard cons
- Per-card dollar cap during beta limits high-value purchases
- Cards are short-lived (7-day live window) which may not suit long-term subscriptions
- Requires Node.js 18+ to install the primary CLI
- Initial setup requires a browser-based Stripe Checkout step
- Some workflows require an admin CLI and separate tooling
- Beta limitations may change pricing or feature availability
- Dependence on Stripe for payment-method storage and billing
- No native physical card option; Visa virtual cards only
Frequently asked questions about Agentcard
How do I create my first card from the terminal?
Install the agentcard CLI (npm install -g agentcard), sign up with passwordless magic-link authentication (agentcard signup --email [email protected]), complete the one-time setup which opens a Stripe Checkout session to save a payment method, then request a card with agentcard request new --amount <dollars>; the CLI prints PAN, CVV, expiry, cardholder name, and billing address immediately.
What authentication methods does AgentCard use?
For developer and operator flows AgentCard uses passwordless email magic-link authentication for the user-facing CLI and API keys for programmatic/admin access (the admin CLI issues API keys scoped to organizations); session tokens are stored locally for CLI sessions and API keys are used in Authorization headers for HTTP requests.
How long is a virtual card valid for?
Virtual cards issued by AgentCard are short-lived; card details are live for a limited window (commonly seven days in beta) and can be re-fetched with the request get command while the card remains live.
What is the maximum amount I can load on a single card?
During the beta the CLI and docs state you may request whole-dollar amounts up to the per-card cap (the documentation specifies a $150 cap during beta), and cards are created for whole-dollar amounts when requested from the CLI or API.
Can I programmatically issue cards for multiple agents or users?
Yes — AgentCard exposes a REST API and an admin CLI that let you create organizations, create cardholders, generate API keys, and then create cards programmatically on behalf of those cardholders so platforms can issue cards at scale to multiple agents or end users.
How do I attach a payment method to an organization or cardholder?
The setup flow opens a Stripe Checkout session where you save a payment method on file; the admin API and cardholder endpoints include routes to create a payment-method setup link (checkoutUrl) which you open in a browser to attach a Stripe payment method to the cardholder or organization.
What card networks and merchant support exist?
AgentCard issues virtual Visa cards intended for use at online merchants that accept Visa; the docs and API reference describe these as virtual Visa cards suitable for typical online checkout flows.
Can I retrieve card details after creation?
Yes — while a card remains within its live window you can re-fetch its details via the CLI command agentcard request get <id> or the API GET cards endpoint to retrieve PAN, expiry, CVV, and other metadata.
Is there an organization or multi-tenant model?
AgentCard provides an organization model used as the billing and administrative unit; you create an organization with the admin CLI, manage members, and issue API keys scoped to that organization for multi-tenant control and billing.
What developer environments are supported and what are requirements?
The primary developer tooling is distributed via npm and requires Node.js 18 or later for the agentcard CLI and the admin CLI; the setup flow requires opening a browser for Stripe Checkout but the CLI supports non-interactive flags for scripted or automated setups.