by Agentcard Corporation
Let your AI agent pay online with a card it never sees, from the user's Vault or newly issued
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.
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.
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.
npx agent-cards setup-mcp
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.
The permissions this connector asks for, as its own documentation states them.
14 actions an agent can call. Open one for its parameters and an example.
Example call
create_card(amount_cents=2500)
Parameters
| Parameter | Type | Needed | Description |
|---|---|---|---|
| amount_cents | number | Required | The 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
| Field | Type | Description |
|---|---|---|
| card_id | string | Unique identifier for the newly created card. |
| last_four | string | Last four digits of the card number. |
| expiry | string | Card expiry in MM/YY format. |
| status | string | Card status: pending_approval, active, or closed. |
Example call
{
"name": "list_cards",
"arguments": {}
}Returns
| Field | Type | Description |
|---|---|---|
| cards | array | Array of card objects, each containing card_id, last_four, expiry, balance_cents, and status. |
Example call
check_balance(card_id="card_7f3k2m")
Parameters
| Parameter | Type | Needed | Description |
|---|---|---|---|
| card_id | string | Required | Which card to read the remaining balance from; use an id returned by create_card or list_cards. |
Returns
| Field | Type | Description |
|---|---|---|
| balance_cents | number | Remaining balance on the card in US cents. |
| status | string | Current card status (active, closed, pending_approval). |
Example call
get_card_details(card_id="card_p9x1qa")
Parameters
| Parameter | Type | Needed | Description |
|---|---|---|---|
| card_id | string | Required | Card to reveal credentials for (number, CVV, expiry), taken from earlier card results. |
Returns
| Field | Type | Description |
|---|---|---|
| pan | string | Full 16-digit card number (PAN), AES-256-GCM decrypted. |
| cvv | string | 3-digit card security code. |
| expiry | string | Card expiry in MM/YY format. |
Example call
close_card(card_id="card_b5t8zc")
Parameters
| Parameter | Type | Needed | Description |
|---|---|---|---|
| card_id | string | Required | The card to shut down so it can take no further charges. |
Returns
| Field | Type | Description |
|---|---|---|
| success | boolean | True if the card was closed successfully. |
| closed_at | string | ISO 8601 timestamp of when the card was closed. |
Example call
list_transactions(card_id="card_w2n6dv")
Parameters
| Parameter | Type | Needed | Description |
|---|---|---|---|
| card_id | string | Required | Card to pull charge history for. |
Returns
| Field | Type | Description |
|---|---|---|
| transactions | array | Array of transaction objects, each with merchant_name, amount_cents, status, and created_at. |
Example call
{
"name": "setup_payment_method",
"arguments": {}
}Returns
| Field | Type | Description |
|---|---|---|
| checkout_url | string | Stripe Checkout URL the user must visit to complete the payment method setup. |
Example call
{
"name": "list_payment_methods",
"arguments": {}
}Returns
| Field | Type | Description |
|---|---|---|
| payment_methods | array | Array of payment method objects with id, brand, last_four, expiry, and is_default. |
Example call
{
"name": "get_plan",
"arguments": {}
}Returns
| Field | Type | Description |
|---|---|---|
| plan_name | string | Name of the current plan: Free or Basic. |
| per_card_cap_cents | number | Maximum amount in cents that can be loaded onto a single card (5000 on Free, 50000 on Basic). |
| monthly_cards_used | number | Number of cards issued in the current calendar month. |
Example call
{
"name": "buy",
"arguments": {
"description": "Buy a 1-month ChatGPT Plus subscription for $20"
}
}Parameters
| Parameter | Type | Needed | Description |
|---|---|---|---|
| description | string | Required | Plain-English description of the purchase to complete, including the item, quantity, and optionally the target merchant. |
Returns
| Field | Type | Description |
|---|---|---|
| order_summary | object | Object with merchant_name, items_purchased, total_charged_cents, card_id, and order_id where available. |
Example call
{
"name": "pay_checkout",
"arguments": {
"amount_cents": 4999
}
}Parameters
| Parameter | Type | Needed | Description |
|---|---|---|---|
| amount_cents | number | Required | The exact amount in cents to load onto the card and charge at the checkout form currently open in the browser. |
Returns
| Field | Type | Description |
|---|---|---|
| card_id | string | ID of the card that was created and used. |
| checkout_status | string | Result of the checkout attempt: success, failed, or requires_action. |
Example call
{
"name": "get_instructions",
"arguments": {}
}Returns
| Field | Type | Description |
|---|---|---|
| instructions | string | Full usage guide text including workflow order, safety rules, and tool reference summary. |
Example call
get_funding_status(card_id="card_h4j0re")
Parameters
| Parameter | Type | Needed | Description |
|---|---|---|---|
| card_id | string | Required | Card to inspect the funding hold on, as listed by the account. |
Returns
| Field | Type | Description |
|---|---|---|
| status | string | Current funding status: pending, funded, or failed. |
| card_active | boolean | True when the card is funded and ready to use for purchases. |
Example call
{
"name": "x402_fetch",
"arguments": {
"url": "https://api.example.com/premium-endpoint",
"method": "GET"
}
}Parameters
| Parameter | Type | Needed | Description |
|---|---|---|---|
| url | string | Required | The URL to fetch. If the server returns HTTP 402, AgentCard automatically pays and retries. |
| method | stringdefault GET | Optional | HTTP method: GET, POST, PUT, DELETE. Defaults to GET. |
| body | string | Optional | Request body for POST/PUT requests, as a JSON string. |
| headers | object | Optional | Additional HTTP headers to include in the request. |
Returns
| Field | Type | Description |
|---|---|---|
| status | number | HTTP status code of the final response after any payment was handled. |
| body | string | Response body from the target URL. |
| payment_made | boolean | True if a 402 was encountered and a micropayment was automatically issued to proceed. |
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.
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.
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.
The nearest AI agent skills on Hokai for the same job.
| Skill | Works with | Connects by | Checked |
|---|---|---|---|
| Claude · ChatGPT · Cursor · Windsurf | MCP | 25 Oct | |
| Claude · ChatGPT · Codex · Cursor +2 | MCP | 22 Nov | |
| -- | MCP | 17 Nov | |
| -- | Skill file | 27 Oct |
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.
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.
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.
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.
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.
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.
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.
Protocol, authentication, permissions and the call contracts on this page are read from Agentcard Corporation's own documentation. The verdict is Hokai's reading of them, not the maintainer's claim.