by Agentcard Corporation

AgentCard review, pricing and verdict

Let your AI agent pay online with a card it never sees, from the user's Vault or newly issued

Best for
Indie developer building a Claude Code agent
Not for
Compliance officer at a regulated financial institution
  • App connectors
  • Automation

Should you use AgentCard?

Agentcard lets AI agents pay online without seeing a real card number. Vault stores a user's own card and asks for passkey approval, while Issuing creates new cards from a USDC balance. Vault has a free plan, and the changelog shows near-daily releases into October 2026.

Native MCP server with 20+ tools covering the full card lifecycle, so agents can issue and spend Visa cards without a single line of custom HTTP code.

Early-mover advantage as one of the few MCP-native virtual card providers. Network effects grow as 40+ agent clients, including ChatGPT's app store, ship native AgentCard config examples.

Also for

  • Startup CTO prototyping an autonomous purchasing workflow
  • Independent developers building Claude Code or Cursor agents that automate SaaS purchases, API credit top-ups, or software license procurement
Show 3 more
  • Startup teams who want their AI agents to autonomously buy cloud resources or domain names without sharing company card details inside an agent's context
  • Builders testing multi-step agentic pipelines that include a real checkout step and need a safe, capped payment method for end-to-end integration tests
  • Companies on the Companies tier who are building agentic products that need to issue per-user virtual cards with controlled spending budgets at scale

Also not for

  • Engineer needing sub-$1 micro-payment volume at high frequency

Main trade-off

Free tier's low per-card and per-month card caps, plus mandatory human approval before every card creation, limit fully autonomous, high-frequency agent spending workflows. Every card now also requires a one-time identity check, adding friction for anonymous or highly automated use cases.

AgentCard pricing

Vault: free for up to 5,000 users, with an Enterprise plan for unlimited users on a talk-to-sales basis. Since 13 September 2026 every company starts on a free plan with live production access, and a paid plan only lifts the 5,000-cardholder limit. Issuing: the company earns a 1% revenue share each time a card is used and can add its own markup; user funds are added in USD and held as USDC on Base. Personal accounts: the agent-cards CLI lists Basic at $15 a month and Pro at $100 a month, while the public pricing page does not show personal plans, so check the CLI before relying on either figure. Compare options in the personal agent cost guide.

Billing model
Freemium

Install AgentCard

npx agent-cards setup-mcp

Before you start

  • Node.js 18 or later installed (npm comes with Node)
  • Run agent-cards login to authenticate via magic-link email and generate your AGENT_CARDS_JWT
  • Add a payment method via the setup_payment_method MCP tool or Stripe Checkout before creating any cards
  • Add the MCP server to your agent config: URL https://mcp.agentcard.sh/mcp, transport HTTP, Authorization: Bearer <AGENT_CARDS_JWT>

How to invoke it

Exposed as 20+ MCP tools (create_card, list_cards, check_balance, get_card_details, buy, and more) called by any MCP-compatible agent after registering the HTTP server at https://mcp.agentcard.sh/mcp with JWT Bearer auth.

Works with

  • Claude Code
  • Claude Desktop
  • Cursor
  • Cline
  • Windsurf
  • OpenClaw
  • ChatGPT (via app store)
  • Any MCP HTTP client

Required runtime

  • Node.js >= 18 (for agent-cards CLI)
  • Stripe-connected payment method (for card funding)

Where it runs

  • Web
  • Desktop
  • CLI
  • API

Data it can reach

  • virtual card credentials
  • transaction history
  • payment methods
  • plan and usage data
  • identity verification data (KYC via Stripe Identity)

The permissions this connector asks for, as its own documentation states them.

What AgentCard can do

14 actions an agent can call. Open one for its parameters and an example.

Create CardIssues a new virtual card with a fixed spend limit, funded from the account balance.

Example call

create_card(amount_cents=2500)

Parameters

ParameterTypeNeededDescription
amount_centsnumberRequiredThe card's spend limit in US cents. For example, 2500 = $25.00. Per-card caps depend on the account's plan; call get_plan to read maxCardAmountDollars.

Returns

FieldTypeDescription
card_idstringUnique identifier for the newly created card.
last_fourstringLast four digits of the card number.
expirystringCard expiry in MM/YY format.
statusstringCard status: pending_approval, active, or closed.
List CardsReturns all virtual cards on the account with their IDs, last four digits, expiry dates, balances, and statuses.

Example call

{
  "name": "list_cards",
  "arguments": {}
}

Returns

FieldTypeDescription
cardsarrayArray of card objects, each containing card_id, last_four, expiry, balance_cents, and status.
Check BalanceRetrieves the current balance of a specific card without exposing the full card credentials.

Example call

check_balance(card_id="card_7f3k2m")

Parameters

ParameterTypeNeededDescription
card_idstringRequiredWhich card to read the remaining balance from; use an id returned by create_card or list_cards.

Returns

FieldTypeDescription
balance_centsnumberRemaining balance on the card in US cents.
statusstringCurrent card status (active, closed, pending_approval).
Get Card DetailsDecrypts and returns the full card number (PAN), CVV, and expiry date needed to complete a payment. May require human approval before returning credentials.

Example call

get_card_details(card_id="card_p9x1qa")

Parameters

ParameterTypeNeededDescription
card_idstringRequiredCard to reveal credentials for (number, CVV, expiry), taken from earlier card results.

Returns

FieldTypeDescription
panstringFull 16-digit card number (PAN), AES-256-GCM decrypted.
cvvstring3-digit card security code.
expirystringCard expiry in MM/YY format.
Close CardPermanently closes a virtual card. This action is irreversible and any remaining balance is released back to the payment method hold.

Example call

close_card(card_id="card_b5t8zc")

Parameters

ParameterTypeNeededDescription
card_idstringRequiredThe card to shut down so it can take no further charges.

Returns

FieldTypeDescription
successbooleanTrue if the card was closed successfully.
closed_atstringISO 8601 timestamp of when the card was closed.
List TransactionsRetrieves the full transaction history for a specific card, showing merchant name, amount, status, and timestamps.

Example call

list_transactions(card_id="card_w2n6dv")

Parameters

ParameterTypeNeededDescription
card_idstringRequiredCard to pull charge history for.

Returns

FieldTypeDescription
transactionsarrayArray of transaction objects, each with merchant_name, amount_cents, status, and created_at.
Setup Payment MethodOpens a Stripe Checkout session to save a new payment method (credit or debit card) to the account, which is used to fund future virtual cards.

Example call

{
  "name": "setup_payment_method",
  "arguments": {}
}

Returns

FieldTypeDescription
checkout_urlstringStripe Checkout URL the user must visit to complete the payment method setup.
List Payment MethodsReturns all saved payment methods on the account with their brand, last four digits, expiry, and which one is set as the default.

Example call

{
  "name": "list_payment_methods",
  "arguments": {}
}

Returns

FieldTypeDescription
payment_methodsarrayArray of payment method objects with id, brand, last_four, expiry, and is_default.
Show all 14 actions
Get PlanDisplays the current plan (Free or Basic), the per-card spending cap, monthly card usage count, and available upgrade options.

Example call

{
  "name": "get_plan",
  "arguments": {}
}

Returns

FieldTypeDescription
plan_namestringName of the current plan: Free or Basic.
per_card_cap_centsnumberMaximum amount in cents that can be loaded onto a single card (5000 on Free, 50000 on Basic).
monthly_cards_usednumberNumber of cards issued in the current calendar month.
BuyConversational purchase tool that accepts a natural-language description of what to buy and handles merchant lookup, cart building, and checkout end-to-end.

Example call

{
  "name": "buy",
  "arguments": {
    "description": "Buy a 1-month ChatGPT Plus subscription for $20"
  }
}

Parameters

ParameterTypeNeededDescription
descriptionstringRequiredPlain-English description of the purchase to complete, including the item, quantity, and optionally the target merchant.

Returns

FieldTypeDescription
order_summaryobjectObject with merchant_name, items_purchased, total_charged_cents, card_id, and order_id where available.
Pay CheckoutCreates a new virtual card and immediately fills it into an active browser checkout form in a single atomic operation, minimising the window in which credentials are exposed.

Example call

{
  "name": "pay_checkout",
  "arguments": {
    "amount_cents": 4999
  }
}

Parameters

ParameterTypeNeededDescription
amount_centsnumberRequiredThe exact amount in cents to load onto the card and charge at the checkout form currently open in the browser.

Returns

FieldTypeDescription
card_idstringID of the card that was created and used.
checkout_statusstringResult of the checkout attempt: success, failed, or requires_action.
Get InstructionsReturns the current usage guide for AgentCard MCP tools. Call this at the start of any agent session to ensure the agent uses the most up-to-date workflow.

Example call

{
  "name": "get_instructions",
  "arguments": {}
}

Returns

FieldTypeDescription
instructionsstringFull usage guide text including workflow order, safety rules, and tool reference summary.
Get Funding StatusPolls the status of a card creation after the Stripe Checkout payment step, confirming when the card is funded and ready to use.

Example call

get_funding_status(card_id="card_h4j0re")

Parameters

ParameterTypeNeededDescription
card_idstringRequiredCard to inspect the funding hold on, as listed by the account.

Returns

FieldTypeDescription
statusstringCurrent funding status: pending, funded, or failed.
card_activebooleanTrue when the card is funded and ready to use for purchases.
x402 FetchPerforms an HTTP request and automatically handles HTTP 402 Payment Required responses by issuing a virtual card and paying the requested micropayment amount without human intervention.

Example call

{
  "name": "x402_fetch",
  "arguments": {
    "url": "https://api.example.com/premium-endpoint",
    "method": "GET"
  }
}

Parameters

ParameterTypeNeededDescription
urlstringRequiredThe URL to fetch. If the server returns HTTP 402, AgentCard automatically pays and retries.
methodstringdefault GETOptionalHTTP method: GET, POST, PUT, DELETE. Defaults to GET.
bodystringOptionalRequest body for POST/PUT requests, as a JSON string.
headersobjectOptionalAdditional HTTP headers to include in the request.

Returns

FieldTypeDescription
statusnumberHTTP status code of the final response after any payment was handled.
bodystringResponse body from the target URL.
payment_madebooleanTrue if a 402 was encountered and a micropayment was automatically issued to proceed.

What AgentCard is for

Agentcard is a payments layer for AI agents from Y Combinator-backed Agentcard Corporation. Its Vault keeps a user's saved card behind passkey approval, and Issuing mints cards an agent can spend once or repeatedly. Agents connect through MCP, a CLI or browser integrations, and the company says insurance covers up to $250.

  • Vault for the user's own cards

    A person saves any card once and approves each agent purchase with a passkey or master password, or allows auto-approval within limits they set.

  • Issuing for new agent cards

    One-time or multi-use cards created for an agent, funded from a USDC wallet that users top up with Apple Pay or Google Pay, with instant settlement.

  • Placeholder card at checkout

    The agent submits a stand-in card, the user approves, and the real card pays, so the agent never sees the number.

  • Purchase API and shopping agent

    A company can let its agent search stores, build a cart and place an order for each shopper, with webhooks for approvals and order updates.

Show all 7 features
  • Browser and messaging integrations

    Works with Kernel, Browserbase, Browser Use, Anchor, your own browser, and iMessage providers Linq and Blooio.

  • Insurance for agent mistakes

    The vendor says Vault carries a cover for the agent's mistakes, on top of the dispute rights a bank gives any cardholder.

  • MCP server and CLI

    Coding agents register the MCP server at mcp.agentcard.sh and use the agent-cards CLI to log in, check plans and manage cards.

What people use it for

  • Automated SaaS subscription renewal

    An agent monitors a subscription expiry date, calls create_card with the exact renewal price, then fills the card at the merchant checkout so the developer never shares their real payment credentials.

  • API credit replenishment

    A coding agent tracks its own remaining API credits, issues a $20 card when the balance drops below a threshold, and tops up its provider account without any human touchpoint beyond the initial approval.

  • Natural-language e-commerce checkout

    A shopping agent calls the buy MCP tool with a plain-English description such as 'buy a 6-month gym membership', browses linked merchants, builds a cart, and completes checkout with a freshly issued card scoped to the exact cart total.

  • One-off software license procurement

    A developer agent identifies a missing dependency or tool, purchases a $10 license, and installs it in one terminal session without the developer ever entering payment details manually.

Strengths and limits

Strengths

  • Two clear products: Vault pays with the user's own card after a passkey approval, Issuing creates new cards for an agent, so a team picks by use case rather than by workaround.
  • The approval sits with the human by default, and agents receive a placeholder card rather than the real number, which limits what a leaked prompt or log can expose.
  • Vault accepts consumer, commercial and prepaid cards from any country, and bank-statement disputes work as they do for any other charge.
  • Easy to try: Vault has a free plan and every company gets live production access without paying for a subscription.
  • Ships fast: the changelog shows entries nearly every day into mid-October 2026, including webhooks, a purchase package and shopping-only app connections.

Limits

  • The public pricing page lists only company Vault plans, so personal-plan prices appear only in CLI help and a developer cannot confirm limits on the website.
  • Issuing needs an ID and face check for every user, which blocks fully anonymous or batch-created agent accounts.
  • Funds for Issuing are held as USDC on Base, an extra rail that finance teams may need to approve.
  • Several checkout types are still refused according to the changelog, such as merchants that take the card on their own server, so some stores will not work yet.
  • The product has changed shape twice this year, so older MCP-only setup guides online may no longer match the current docs.

AgentCard alternatives

The nearest AI agent skills on Hokai for the same job.

SkillWorks withConnects byChecked
AgentCard This pageClaude · ChatGPT · Cursor · WindsurfMCP25 Oct
Easy MCP AITurns a WordPress site into an MCP server that Claude and ChatGPT can run.Claude · ChatGPT · Codex · Cursor +2MCP22 Nov
OMNIGATEx402 gateway for agents: find paid APIs, vet a spend, run budgeted scripts--MCP17 Nov
Personal Agent ProtocolOpen standard for how personal AI agents sign in and act for customers.--Skill file27 Oct

AgentCard facts

Protocol
MCP
Authentication
Token
Latency class
Fast
Open source
Yes
Maintainer founded
2025
Headquarters
San Francisco, CA
Total funding
Backed by Y Combinator

What changed

  • New feature Real-time authorization webhook and buy tool added source
  • Release AgentCard launches publicly with MCP server and CLI (v1.0) source
  • New feature Hold-based card funding replaces wallet model source

Questions about AgentCard

What does Agentcard do for an AI agent?

Agentcard lets an AI agent pay online without holding a real card number. Its Vault product stores a person's own card and asks them to approve each purchase with a passkey, while its Issuing product creates new one-time or multi-use cards from a USDC balance. Agentcard Corporation is backed by Y Combinator, and its docs recommend most teams start with Vault.

How do I connect Agentcard to my agent?

For coding agents, run npx agent-cards setup-mcp or add the HTTP MCP server at mcp.agentcard.sh/mcp with your token, then sign in with the agent-cards CLI. Companies building a product start from the Vault quickstart or the agent-cards integrate command, which writes sandbox credentials and wires the Vault, Issuing or Purchase API into a branch for review. Issuing users complete an ID and face check before the first card.

Is Agentcard free, and what do the paid plans cost?

Vault is free for up to 5,000 users, and Vault Enterprise lifts the cap through sales. Every company now starts free with live production access. Issuing pays the company a revenue share on card use. For personal accounts, the CLI lists Basic at $15 and Pro at $100 a month, though the public pricing page omits them.

What can I use instead of Agentcard?

On Hokai, the nearest neighbours are Stripe's Link wallet skill, built by a payments company, and a messaging-standard route through Personal Agent Protocol. Agentcard differs by offering both a stored-card Vault and card issuing, and by working with browser agents such as Kernel and Browserbase. Teams already deep in Stripe may find a Stripe-native wallet simpler.

Who should use Agentcard and who should skip it?

It fits companies building personal assistants or shopping agents that need user approval on each purchase, and developers who want a coding agent to buy credits or licences. It is a weaker fit for anonymous, high-volume micro-payments, because Issuing requires an ID check and every purchase passes an approval step unless the user sets auto-approval limits.

About AgentCard

Agentcard is a payments layer that lets an AI agent pay for things online without ever holding a raw card number. It began as an MCP server that issued prepaid virtual cards to coding agents, and Y Combinator-backed Agentcard Corporation has since split the product in two: Vault, which stores a person's own cards and asks them to approve each agent purchase, and Issuing, which creates new one-time or multi-use cards for an agent from a USDC balance.

Read the full background

Vault is the default starting point in the vendor's own docs. A user saves a card once, any network and any country, and the agent submits a placeholder card at checkout. The user approves with a passkey or master password, or sets auto-approval within limits they choose. Disputes run through the cardholder's bank like any other charge, and the vendor says it insures up to $250 against agent mistakes. It works with agent browsers such as Kernel and Browserbase, and with iMessage and web front ends.

Issuing suits teams that need a fresh card per job. Users complete an ID and face check, fund a wallet through Apple Pay or Google Pay, and the agent spends from it. A company building on Issuing earns a 1% revenue share on card use and can add its own markup. Pally is one of the listed customers.

The older MCP server still exists. Coding agents such as Claude Code, Cursor and Windsurf can register it and call card tools, and the changelog shows new tooling shipping almost daily through 14 October 2026, including a purchase package so a company can sell through its own agent.

Where it falls short: the public pricing page now describes only the company-facing Vault plans, so a solo developer has to read the CLI docs to find personal plan prices. Every Issuing card needs identity verification, and approvals add friction by design. Teams that want a wallet inside a payments company they already use may prefer the Stripe Link agent wallet, and the Personal Agent Protocol covers a neighbouring problem. For how approval gates fit a personal agent, see the approval gates guide, and for the wider field the best personal AI agents roundup.

Sources and guides

More Agent Skills on Hokai

  • Link Agent WalletOne-time-use cards from your Link wallet for agents, approved by you
  • NVIDIA BioNeMo Agent ToolkitAgent-callable skills for protein folding, docking, and genomics on NVIDIA NIM
  • find-skillSearch and install skills from the Orthogonal library for agents.
  • DiditIdentity verification, KYB, AML and transaction monitoring an agent can configure and run over a hosted MCP server.
  • ComposioOne MCP endpoint that lets an agent act in 1,500+ apps with managed auth.
  • Pipedrive MCP ServerConnect Claude, ChatGPT and Cursor to your Pipedrive CRM with no code