How to Give Your AI Agent a Card (Step-by-Step)

Why your agent needs its own card

The moment your agent can make a purchase, it graduates from assistant to operator. The difference is enormous.

Without a card, your agent is a research intern. It finds the best AWS pricing, writes the comparison, and hands you a recommendation. You then go to AWS, enter your card, click through 4 pages of checkout, and complete the purchase yourself. The agent did 90% of the work but you're still the bottleneck at checkout.

With a card, your agent is an autonomous operator. It finds the best AWS pricing, creates a single-use virtual card scoped to $50, purchases the compute instance, and sends you the receipt. You approved the $50 limit upfront. The agent handled everything else.

This isn't theoretical. Developers using Claude Code are already buying API credits, renewing domains, and scaling cloud infrastructure — all through agent cards. The infrastructure exists today.

What an agent card actually is

An agent card is a virtual Visa (or Mastercard) issued specifically for an AI agent to use. It works exactly like a normal card at checkout — same card number, expiry, CVV format — but with three critical differences:

Scoped spending

Every card has a hard balance limit. You load $25, the agent can spend up to $25. Not $25.01. The limit is enforced at the network level, not by software that can be overridden.

Isolated credentials

Each card has its own unique number. If one card is compromised, you revoke it without affecting any other card. Your personal card is never exposed.

Machine-readable

The card details are accessible via API or MCP tools. The agent can programmatically request the card number, use it at checkout, and report the result — no human copy-pasting.

The combination of these three properties is what turns a regular virtual card into an agent card. Your agent gets spending power with hard guardrails.

Step-by-step: issue a card for your agent

Step 1: Create a Plu account

Download the Plu app or sign up at app.getplu.com. Identity verification takes about 2 minutes — passport or national ID. You'll have an account before your coffee gets cold.

Step 2: Fund your balance

Three options:

• USDT/USDC: Send stablecoins from any wallet on Tron (TRC20) or Ethereum (ERC20). Balance updates in 10–30 seconds on Tron, 1–3 minutes on Ethereum. Network fees under $1 on Tron. Fastest and cheapest for crypto-native users.
• Bank transfer: Send USD, NGN, GHS, KES, XOF, or other local currencies from your bank. Converted at market rate with zero markup spread.
• Mobile Money: In supported markets (Nigeria, Ghana, Kenya, Côte d'Ivoire), fund directly from M-Pesa, Wave, Orange Money, or MTN MoMo.

Step 3: Create a virtual card

In the Plu app, tap "Create Card." Set the spending limit — the maximum the agent can spend on this card. Choose single-use (auto-cancels after one payment) or multi-use (recurring with a monthly cap).

The card generates instantly: card number, expiry date, CVV. These credentials are encrypted at rest and only decrypted when requested through authenticated MCP or API calls.

Step 4: Connect to your AI agent via MCP (beta)

Add Plu's MCP server to your agent:

# Claude Code
claude mcp add --transport http plu-cards https://mcp.getplu.com/agent

# Cursor / Windsurf / Cline — add to MCP config:
{
 "mcpServers": {
 "plu-cards": {
 "url": "https://mcp.getplu.com/agent"
 }
 }
}

Restart your agent session. The agent now has access to tools: create_card, get_card_details, check_balance, list_cards, fund_card, revoke_card, and get_transactions.

Step 5: Let the agent spend

Tell your agent what to buy. It creates a card (or uses an existing one), retrieves the credentials, enters them at checkout, and completes the purchase. You get a notification for approval. Approve, and the transaction clears.

MCP setup for Claude Code and Cursor

MCP (Model Context Protocol) is the standard way AI agents interact with external tools. Instead of building a custom integration, your agent calls standardized tools through an MCP server — the same way it calls web search or file system tools.

Plu's MCP server exposes seven tools:

Example interaction in Claude Code

You: "Buy me a .com domain on Namecheap for under $15."

Agent: I'll create a $15 single-use card for this purchase.
 [calls create_card with limit=$15, single_use=true]

Agent: Card created. Checking Namecheap pricing...
 example.com is available for $10.28.
 [calls get_card_details to retrieve PAN/CVV]

Agent: Completing checkout on Namecheap...
 Purchase complete. Domain registered: example.com
 Card balance remaining: $4.72 (card will auto-cancel)
 Receipt: [transaction details]

The agent never sees your personal card. The $15 card can't be used for anything else. If the domain costs more than $15, the transaction fails — hard limit.

Funding options: USDT, USDC, and fiat

Most agent card platforms only accept USD from US bank accounts. That works if you're a developer in San Francisco. It doesn't work if you're a developer in Lagos, Nairobi, Accra, Abidjan, Manila, or São Paulo.

Plu accepts USDT and USDC. This is the single biggest differentiator. If you hold stablecoins — from freelancing, crypto trading, DeFi yields, or simply as a savings vehicle — you can fund agent cards without touching the traditional banking system.

The flow: wallet → Plu → agent card → Visa transaction. One step from crypto to purchasing power.

Why this matters for global developers

A developer in Nigeria holding USDT on Binance can fund an agent card in 30 seconds, for under $1 in network fees. The same developer trying to use AgentCard or Privacy.com can't — those platforms only accept USD from US accounts.

A developer in Côte d'Ivoire with USDT on Tron can fund an agent card and have their Claude Code agent purchase a Vercel Pro subscription. There is no other agent card platform that makes this possible.

Fiat funding is also available in multiple currencies: USD, NGN, GHS, KES, XOF, and more. Mobile money funding (M-Pesa, Wave, Orange Money) is supported in applicable markets. zero markup spread on all conversions.

Security: why this is safer than sharing your card

The default behavior for most people is: copy your credit card number into the agent's context, hope for the best. This is dangerous for several reasons.

Your card has no per-transaction limit in the agent's context. If the agent hallucinates and sends 10 purchase requests, each one clears. Your card number is now in the conversation history — stored in logs, potentially accessible in future sessions. If the agent interacts with a malicious website, your full card details are exposed.

Agent cards fix every one of these problems:

• Hard spending cap — the card physically cannot exceed its loaded balance. A $25 card stops at $25. Enforced by Visa's network, not by the agent's code.
• Isolated credentials — each card is a unique number. Compromising one card doesn't expose any other card or your personal payment methods.
• Single-use option — card auto-cancels after one payment. Even if the credentials leak post-transaction, they're useless.
• Human-in-the-loop — every card creation and payment triggers an approval notification. You see the merchant, amount, and purpose before approving. Disable for trusted recurring tasks.
• Encrypted at rest — AES-256-GCM encryption on all card credentials. Decrypted only on authenticated, explicit request through MCP or API.
• Instant revocation — one API call or one tap in the app kills the card immediately. No waiting for the bank to process a cancellation.

What agents actually buy

Based on real agent card usage patterns across the industry:

• API credits and compute — agents monitoring their own API usage and topping up when credits run low. OpenAI, Anthropic, xAI, Replicate.
• Cloud infrastructure — agents that auto-scale. When traffic spikes, the agent provisions more compute on AWS, GCP, or DigitalOcean. When traffic drops, it scales down.
• Domains and hosting — time-sensitive purchases. An agent monitoring domain expiration dates renews them before they lapse.
• SaaS subscriptions — preventing service interruption. GitHub Pro, Figma, Notion, Slack, Zoom.
• Digital advertising — budget management. An agent that adds budget when ROAS is positive and pauses when it's not.
• Research and data — procurement agents buying datasets, premium API access, or research reports.
• E-commerce — personal assistant agents ordering groceries, booking restaurants, purchasing gifts.

Agent card platforms compared

The space is moving fast. Here's how the major platforms compare today:

If you're in the US with a US bank account, you have plenty of options. AgentCard and Privacy.com are both solid for single-use cards with MCP support.

If you're anywhere else — or if you hold USDT — Plu is the only platform that works. 143 countries, stablecoin funding, local currency support, and zero fees. The global developer who needs an agent card has one real choice.

Frequently asked questions

Is it safe to give an AI agent a card?

Yes — when the card is properly scoped. An agent card with a $25 hard limit, single-use, and human approval enabled is safer than sharing your personal card. The worst case is the agent spends $25 on the wrong thing. Your personal card exposure is zero.

Which AI agents support MCP?

Claude Code, Claude Desktop, Cursor, Windsurf, Cline, OpenAI Codex, and any agent built on an MCP-compatible framework. ChatGPT support via HTTP bridge is coming. Custom agents can use the REST API directly.

Can I fund agent cards with crypto?

Yes. Plu supports USDT and USDC on Tron (TRC20) and Ethereum (ERC20). No other major agent card platform supports stablecoin funding.

What happens if my agent overspends?

It can't. Agent cards have hard spending limits enforced at the Visa network level. A $50 card cannot process a $50.01 transaction. This is the fundamental difference between an agent card and sharing your credit card number.

Can I use this outside the US?

Yes. Plu works in 143 countries. Fund with local currency, USDT, or USDC. The Visa card is accepted at any merchant worldwide.

Is there a free tier?

Yes. Create up to 10 cards per month with a $500 per-card limit. No monthly fees. You pay only when the agent spends.

Your agent is already smarter than your intern. Give it a budget to match.

Ready to go global?

Learn more about Plu in your region.