Keep going
Every workflow on Rundown University, free for 7 days
Members get all guides, courses, live sessions, and $1,000+ in partner perks.
published jun 26, 2026
Members get every guide, course, and $1,000+ in partner perks.
In this guide, you will learn how to give an AI agent a real payment method without handing over your main credit card. The workflow uses AgentCard to create prepaid or single-use virtual cards, then lets an agent such as Codex attempt a supervised checkout.
You will build a controlled agent purchasing workflow: install AgentCard, sign in, attach a low-risk funding source, issue a small card, and give the agent a checkout task with strict spend and approval rules.
The safe version is not fully autonomous. The agent can help navigate checkout, but you should keep the spending limit small, watch the browser, and require a human approval before the order is placed.
Agent commerce is still early. Some stores have anti-bot flows, confusing checkout forms, 3DS checks, or payment widgets that agents handle poorly. Start on a simple, low-stakes purchase before trying a merchant with queues, limited inventory, or complex shipping rules.
AgentCard also publishes an MCP server and experimental agentic checkout commands. Those are useful when you want the agent to request card details through tools instead of relying on copied text, but you should still keep approval and spend limits in place.
Start with a prepaid, single-use, low-limit card and keep a human approval step before the agent places the order.
Before you install anything, decide what the agent is allowed to do. The card details are real payment credentials, so treat them like secrets.
Use a prepaid or tightly limited card for testing. The point is to make the agent useful without giving it access to your real financial blast radius.
Open a terminal in a scratch folder. Keeping this in a playground directory makes it easier to clean up if you are just experimenting.
mkdir agent-card-playground
cd agent-card-playground
npm install -g agentcardConfirm the CLI is available:
agentcard --helpThe current CLI uses the package name agentcard and exposes commands such as signup, setup, request, details, balance, and agentic.
Sign in with your email address. AgentCard sends a magic link, so keep your email open.
agentcard signup --email you@example.comAfter you click the magic link, run setup. This is where you add your profile, phone number, payment method, and any required verification.
agentcard setupIf AgentCard asks for identity verification, complete it through the provider flow. The video showed Stripe-hosted payment and identity screens, but you should still do your own review before submitting personal information.
Once setup is finished, request a small card amount for your test purchase. The current CLI uses request new for single-use virtual cards.
agentcard request new --amount 50If you need to re-fetch the card details later, use:
agentcard request get <request-id>Only reveal card details in the moment you need them. If you paste them into an agent chat, assume they are now part of that conversation history.
Give the agent a specific, low-risk task. Separate billing information from shipping information, and make the approval rule explicit.
Try buying this item with AgentCard: <product URL>
Budget: $50 maximum, including shipping and taxes.
Payment: use the AgentCard virtual card only.
Shipping: use the shipping address I provide in this chat.
Rules:
- do not buy substitutions
- do not save payment details to the store account
- stop at the final review screen
- ask me before clicking Place Order
- if a page asks for login, a queue, 3DS, or identity verification, stop and ask meWatch the browser while the agent works. In the video, Codex eventually completed an NBA Store checkout, but it struggled with form controls and payment-method dropdowns before the order went through.
Agents can still get stuck on checkout pages. Anti-bot protection, limited inventory, payment widgets, and browser handoffs can all confuse them.
After the order, check AgentCard and the merchant confirmation to make sure the charge amount, merchant, and shipping details are correct.
Once the basic CLI flow works, you can expose AgentCard through MCP so compatible agents can request setup instructions or create cards through tools.
{
"mcpServers": {
"agentcard": {
"command": "npx",
"args": ["-y", "agentcard-mcp"]
}
}
}AgentCard also exposes experimental agentic checkout commands. Use these only after you understand the basic card request flow and have a clear approval process.
agentcard agentic connect
agentcard agentic buy --merchant "Example" --url https://example.com --item "Test item" --amount 10 --checkoutKeep going
Members get all guides, courses, live sessions, and $1,000+ in partner perks.