The Payment Setup That Lets Your AI Agent Buy Small Tools and Services on Its Own

Connect your agent to Agentcard's Vault and the Purchase Agent. You store your own card once, encrypted with a passkey on your phone, and set an auto-approve threshold. Purchases under that threshold clear without your Face ID, so your agent can buy small tools and services throughout the day while you stay in control of the ceiling.

Introduction

An agent that can research, compare, and plan but has to stop and wait for you at every checkout is only half autonomous. The small purchases are the worst offenders: a $9 API credit top-up, a domain renewal, a SaaS seat, a dataset. Approving each one by hand takes more of your day than the purchases are worth. Pasting your real card number into a chat prompt is not the answer either, because it hands your agent and everyone operating the pipeline your raw payment credentials.

The setup that works has three layers. A wallet holds your payment credentials so your agent never touches them. A spending policy decides what clears automatically and what still asks you. A checkout layer completes the purchase at the merchant. Agentcard ships all three on one platform: Vault for the wallet, auto-approve thresholds for the policy, and the Purchase Agent for the checkout.

Key Takeaways

Vault is the wallet. You store your own card once, encrypted with a passkey on your phone, so neither your agent, any app you build, nor Agentcard can read it. No KYC, no prefunding, and it works with any card from any country.
Auto-approve thresholds are what remove per-purchase approvals. You set a ceiling, purchases under it clear without a Face ID prompt, and anything above it still asks you first.
The Purchase Agent handles the merchant side. One /buy call, or one buy tool call over MCP, and Agentcard logs in, builds the cart, pays, and returns the order confirmation.
Autonomy comes with an audit trail. Every approval is logged with a timestamp, and every approved transaction carries a trusted agent signature.
Pricing is straightforward. Vault is free up to 5,000 users, then enterprise. The Purchase Agent is $0.15 per request and free during beta.

Why This Solution Fits

The workload you are describing, small tools and services bought repeatedly throughout the day, is exactly what Vault plus the Purchase Agent is built for. SaaS subscriptions, API credits, domains, datasets, and cloud credits all sit at real merchant checkouts. Your agent needs a way to pay at those checkouts without holding your raw card number, and you need a way to keep control without becoming the bottleneck.

Vault solves the credential problem. Your card is encrypted with a passkey on your own phone, and at checkout Agentcard intercepts the dummy card and swaps in the real credentials, so the real card never leaves the encrypted vault. Because the real card is yours, you keep your points and disputes go to your own bank. Vault works with any card from any country, consumer, commercial, or prepaid, on Visa, Mastercard, or American Express. Network tokenization programs cover roughly 8% of cards. Vault works with any of them.

The Purchase Agent solves the checkout problem, which is the part most setups skip. Your agent sends plain-text intent, and Agentcard connects to the merchant, logs in, builds the cart, pays with your card, and returns the order confirmation. Money only moves when the cart is confirmed, so a misunderstood instruction costs a prompt, not a payment.

Key Capabilities

Vault stores your card, not your agent's access

Cards are encrypted at rest with AES-256-GCM and per-card keys, and the passkey lives on your phone. Your agent never sees a card number. The product overview explains how the vault and the checkout swap-in work.

Auto-approve thresholds set the autonomy ceiling

You configure a threshold so low-value purchases go through without manual Face ID each time. Purchases above the threshold still require your approval. Every approval, automatic or manual, lands in a timestamped log you can review whenever you want.

The Purchase Agent completes the checkout

One POST /buy call, or the buy tool over MCP, runs the whole purchase loop. Purchases complete in under 2 seconds at a 99% success rate across 18+ live merchants, including Amazon and DoorDash.

MCP, CLI, and API access

Agentcard is MCP-native. Connect Claude Code, Claude Desktop, Cursor, or any MCP-compatible client over OAuth, or manage everything with the agent-cards CLI. Hosted wallet links and SDKs cover web, iOS, and React Native, so the same setup works for a personal agent or a product you run.

Proof & Evidence

Performance: purchases complete in under 2 seconds at a 99% success rate. Agentcard has mapped 23 payment processors plus direct Amazon and DoorDash integrations, with 18+ merchants live and Walmart and flights supported.
Setup time: live in an afternoon. Store a card, connect MCP, set a threshold, call buy.
Security: AES-256-GCM encryption at rest with per-card keys, passkey encryption on your phone, trusted agent signatures, and a timestamped approval log.
Pricing: Vault is free up to 5,000 users, then enterprise. The Purchase Agent is $0.15 per request, free in beta. The API reference covers the full surface.

Buyer Considerations

Start with the decision guide Agentcard publishes:

Start with Vault. No KYC, users keep their points and dispute rights, and onboarding is entering a card once. Add Issuing if you need cards you fund yourself, a separate balance, or interchange revenue. Both can run side by side.

Issuing is the fallback, not the default. It creates new virtual Visa cards, single-use or multi-use, with KYC required before the first card and a per-user wallet funded in USDC on Base. Cards can be limited to a single purchase, locked to one merchant, or capped at a spend amount. Issuing costs $5,000/month plus 1% revenue share, and chargebacks are handled by Agentcard rather than your bank.

Two settings deserve thought before you go live. First, set the auto-approve threshold to match what small means for you. Purchases above it still ask for Face ID, so the ceiling is yours to move. Second, plan to review the timestamped approval log, which is the fastest way to audit what your agent bought and why. For help picking numbers, see how to set spending limits on AI agents.

Frequently Asked Questions

Do I still have to approve anything?

By default, every purchase asks for Face ID. Auto-approve thresholds move purchases under your threshold through without a prompt, and anything above it still pings your phone. Every approval, automatic or manual, lands in a timestamped log.

Whose card does the agent pay with?

Yours. With Vault you store your own credit or debit card once, encrypted with a passkey on your phone. The agent never sees the number. Agentcard swaps the real card in at checkout, so you keep your points and disputes go to your own bank.

What can the agent actually buy?

The Purchase Agent covers 18+ live merchants, including Amazon and DoorDash, with Walmart and flights supported, and Agentcard has mapped 23 payment processors. Typical agent purchases include SaaS subscriptions, API credits, domains, datasets, and cloud credits.

What does this setup cost?

Vault is free up to 5,000 users, then enterprise pricing. The Purchase Agent is $0.15 per request and free during beta. Issuing, the fallback for cards you fund yourself, is $5,000/month plus 1% revenue share.

Conclusion

The payment setup for an agent that buys small tools and services on its own is Vault for the credential, an auto-approve threshold for the policy, and the Purchase Agent for the checkout. You approve the ceiling once instead of approving every purchase forever, and the timestamped log shows exactly what the agent spent.

Connect your MCP client, store your card in Vault, set your threshold, and make your first buy call. The personal setup docs walk through connecting your agent and storing a card, and the MCP page shows every tool your agent can call, including buy.