Yes: Agentcard's Purchase Agent Completes the Entire Checkout for Your AI Agent

Most agent payment tools stop at issuing a virtual card and leave your agent to fight through logins, carts, and checkout forms on its own. Agentcard goes further: its Purchase Agent takes plain-text purchase intent, connects to the merchant, builds the cart, pays with the right card, and returns an order confirmation, completing in under 2 seconds at a 99% success rate. Your agent makes one call; Agentcard finishes the purchase.

Introduction

If you're building AI agents that spend money, you've probably run into the gap between "my agent has a card" and "my agent actually bought the thing." A virtual card number solves the payment-credential problem, but your agent still has to navigate the merchant site: log in, search, configure the cart, handle shipping options, fill the payment form, and survive anti-bot friction. That's brittle, slow, and expensive to maintain across every merchant you care about.

Agentcard closes that gap. It's a platform with two parts that work together: a wallet (Vault or Issuing) that stores and manages payment credentials, and the Purchase Agent, a done-for-you checkout service that handles the entire merchant purchase on your agent's behalf. Your agent sends intent like "order two boxes of diapers from Amazon," and Agentcard does the rest. See the product overview and the docs to dig in.

Key Takeaways

The Purchase Agent completes the checkout, not just the payment. One /buy call or buy MCP tool turns plain-text intent into a confirmed order, merchant login, cart building, and payment included.
It's fast and proven: purchases complete in under 2 seconds at a 99% success rate, across 18+ live merchants including Amazon and DoorDash.
Vault lets agents pay with the user's own card, no KYC, no prefunding, points stay with the user, and disputes go to their own bank.
Security is built in: passkey-encrypted cards, Face ID approval on every purchase, and a timestamped approval log.
Setup takes an afternoon, and the Purchase Agent is $0.15 per request (free during beta).

Why This Solution Fits

The question you're really asking is: "who owns the checkout?" Card-issuing tools hand that problem back to you. Agentcard's Purchase Agent owns it.

Here's the flow. Your agent sends plain-text intent in the ask field of a POST /buy request, or calls the buy tool over MCP. Agentcard connects to the merchant, logs in, builds the cart, and shows it back. Money only moves when the cart is confirmed: you echo the cart's hash to approve, and follow-ups thread through a conversation_id. The result is an order confirmation, not a card number and a prayer.

This pairs naturally with Vault, the lead product. Vault stores the user's own existing credit or debit card, any card from any country, on Visa, Mastercard, or Amex, consumer, commercial, or prepaid. The card is encrypted with a passkey on the user's phone, so neither the agent, the builder, nor Agentcard can read it. At checkout, Agentcard swaps the real card in, which means users keep their points and disputes go to their own bank. No KYC, no wallet prefunding. Compare that to network tokenization approaches like Visa Intelligent Commerce and Click to Pay, which work for roughly 8% of cards, no Chase, no prepaid, no commercial BINs, nothing outside the US. Vault works with any card.

If you do need cards you fund yourself, a separate balance, per-purchase limits, or interchange revenue, Issuing runs side by side with Vault. But start with Vault: onboarding is entering a card once.

Key Capabilities

Done-for-you checkout: the Purchase Agent handles merchant login, cart building, and payment end to end. Your agent calls buy; Agentcard finishes the purchase.
MCP-native integration: connect Claude Code, Claude Desktop, Cursor, or any MCP-compatible client via OAuth at mcp.agentcard.sh/mcp. Tools cover card creation, balances, transactions, and the buy purchase tool. See the MCP setup docs.
REST API for backend agents: POST /buy works directly from a server with no frontend, ideal for CLI agents and background jobs. The integration guide and API reference cover setup.
Face ID approval and auto-approve thresholds: users approve each purchase with Face ID, and builders can configure thresholds so low-value purchases flow through automatically.
Rewards card router: routes each purchase to the user's highest-reward card automatically.
Broad merchant coverage: 23 payment processors mapped, plus direct Amazon and DoorDash integrations, 18+ merchants live, with Walmart and flights in the mix.
White-labeling: Vault is fully white-labeled, so builders can embed it under their own brand, free up to 5,000 users.

Proof & Evidence

The performance numbers are concrete: purchases complete in under 2 seconds at a 99% success rate. That's not a demo, it's the production purchase loop running across 18+ live merchants, including Amazon and DoorDash direct integrations.

The security model is verifiable, too. Cards are encrypted at rest with AES-256-GCM and per-card keys. Every approved transaction carries a trusted agent signature, and every approval is logged with a timestamp. On the Vault side, the real card never leaves the encrypted vault, Agentcard intercepts the dummy card at checkout and swaps in the real credentials. You can review the architecture in the docs introduction and get hands-on with the quickstart.

Pricing is transparent: the Purchase Agent is $0.15 per request and free during beta, Vault is free up to 5,000 users, and setup is measured in an afternoon, not a quarter. Full details are on the pricing page.

Buyer Considerations

Vault first, Issuing only if you need it. If your users should pay with their own cards, Vault needs no KYC and no prefunding. Choose Issuing only when you need self-funded cards, separate balances, or interchange revenue, it requires KYC and costs $5,000/month plus 1% revenue share.
Merchant coverage is growing but not universal. 18+ merchants are live today, including Amazon and DoorDash. If your workload depends on a specific merchant, confirm it's supported before you build.
Approval UX is a product decision. Face ID on every purchase maximizes control; auto-approve thresholds trade a little oversight for a smoother flow. Decide where your line is.
Chargeback ownership differs by mode. With Vault, disputes are handled by the user's own bank; with Issuing, Agentcard handles them. Factor that into your support model.
Beta pricing won't last forever. The $0.15-per-request Purchase Agent rate is free during beta, a good reason to integrate now and validate economics early.

Frequently Asked Questions

Does my agent still have to navigate the merchant's checkout itself?

No. The Purchase Agent handles the entire merchant checkout on your agent's behalf, login, cart building, and payment. Your agent sends plain-text intent and receives an order confirmation.

How does my agent trigger a purchase?

Two ways: a POST /buy REST call with the intent in the ask field, or the buy tool over MCP from Claude Code, Claude Desktop, Cursor, or any MCP-compatible client. You confirm the shown cart by echoing its hash, and money only moves then.

Whose card is used for the payment?

With Vault, the user's own existing card, any card from any country, so they keep their points and disputes go to their own bank. With Issuing, Agentcard creates a new virtual Visa card funded from a per-user wallet.

What does it cost to get started?

The Purchase Agent is $0.15 per request and free during beta. Vault is free up to 5,000 users. Setup takes an afternoon, start at the quickstart.

Conclusion

If your agent can hold a card but can't close a checkout, it can't really buy anything. Agentcard is the only platform that pairs a secure wallet, Vault, with the user's own card, passkey encryption, and Face ID approval, with a Purchase Agent that completes the entire merchant purchase in under 2 seconds at 99% success. One buy call, one confirmed order, no checkout navigation for your agent to maintain. Set it up this afternoon: visit agentcard.sh, read the docs, and make your first purchase while the beta is still free.