How AI agents pay, and how to cap their spending
AI agent costs commonly take two routes. The first is model API credits: OpenAI, Anthropic and OpenRouter all sell credits up front and can buy more automatically when the balance runs low. The second is an agent buying from merchants for you, which Visa and Mastercard are piloting. RDVCC has no agent-specific card and is not part of these pilots. What you can do is use a dedicated prepaid virtual credit card for API auto top-ups. With RDVCC card auto top-up off, the card balance is essentially the limit on what that card can be charged.
Where AI agent payments come from
| Payment route | How it charges | Status | What you control |
|---|---|---|---|
| Model API credits | You buy credits and usage draws them down. With auto top-up, the card is charged when the balance falls below a threshold | In wide use | The threshold and amount on the platform, and the card balance |
| An agent buying for you | Tokenized credentials, under rules you approve in advance | Pilots and gradual rollout by card networks and platforms | The permission rules offered by the platform and issuer |
| Giving a browser agent your card number | The agent fills in the card on a web page like a person | Technically possible, at your own risk | The card balance and card status |
Auto top-up rules at three API providers
| Provider | Auto top-up | When credits run out | Expiry and refunds |
|---|---|---|---|
| OpenAI API | Prepaid credits from $5. Auto recharge buys more when the balance falls below your threshold, with an optional monthly limit on automatic recharges only | API requests return a billing error. The cutoff can lag, so the balance can go negative and is deducted from your next purchase | Expire 1 year after purchase; non-refundable unless required by law or contract |
| Anthropic API | Auto-reload: set the trigger balance and the balance to reload to on the Billing page. If you are already below the trigger, you are charged as soon as you turn it on | You can no longer call the API or use the playground | Expire after 1 year, cannot be extended, and are non-refundable |
| OpenRouter | Top up manually, or set auto top-up below a threshold | Not stated in its FAQ | OpenRouter reserves the right to expire unused credits one year after purchase. Unused credits can be refunded within 24 hours of purchase, excluding platform fees and crypto payments |
API charges in our ledger
The window is 2026-08-11 to 11-08 and covers the API merchants of these three providers on RDVCC cards, excluding Claude and ChatGPT subscriptions. Unless noted, figures are per person with an authorization.
| Measure | OpenAI API | Anthropic API | OpenRouter |
|---|---|---|---|
| People with a successful charge | About 45% | About 30% | About 79% |
| People with a decline | About 14% | About 9% | About 21% |
| Of those declined, at least one balance or limit decline | About 82% | About 79% | About 75% |
| Charge size (median per person) | $20 | $20 | $15.39 |
| Of those charged, same amount 3+ times | About 9% | About 9% | About 9% |
| Of those charged, 3+ charges in a day | About 9% | About 4% | About 2% |
| Authorizations with a 3D Secure fee | None | None | None |
People with neither a successful charge nor a decline had only verifications, reversed authorizations or unsettled authorizations, which does not mean a charge failed. The 3D Secure row depends on the mix of BINs and does not mean these providers never ask for it.
Limits: the sample is small, especially for Anthropic and OpenRouter, and the top three people make up about 58% of transactions at these providers. The ledger cannot tell which charges an agent started, or separate manual from automatic top-ups. A repeated amount only looks like an auto top-up.
Most people pay only a few times. Among those charged, about 9% paid the same amount three or more times. Three or more charges in a day apply to about 9% at OpenAI and 2% to 4% at the other two. We suggest those accounts set a limit up front. If a charge is declined, check the card balance first, since that is the most common cause.
How to cap what an agent can spend
- Open a separate card for one API account. Keeping it apart from subscriptions and ads makes statements easier to reconcile.
- Keep only this period’s budget on the card. A prepaid card must be topped up before it can spend. With RDVCC card auto top-up off, the card balance is essentially the limit on what it can be charged, though a settled amount can occasionally exceed the authorization. With it on, the limit becomes your account balance and the monthly auto top-up cap you set. Per-transaction fees come from your account balance if the card is short.
- Set the auto top-up threshold and amount on the platform. Keep each top-up, plus any tax, below the card balance so it isn’t declined. OpenAI also lets you set a monthly limit.
- Check your transaction history regularly. If you see a charge you don’t recognize, freeze the card to stop further spending. A frozen card can’t be withdrawn from: unfreeze it and wait 30 minutes after its last transaction first. If you won’t use it again, close it and the balance returns to your account after settlement.
Agents buying for you: card networks and OpenAI
| Date | Who | What happened |
|---|---|---|
| 2025-04 | Visa | Launched Visa Intelligent Commerce so AI can find and buy for users |
| 2025-04-29 | Mastercard | Launched Agent Pay and Agentic Tokens, built on existing tokenization |
| 2025-09 | OpenAI, Stripe | Released the Agentic Commerce Protocol and Instant Checkout in ChatGPT. OpenAI’s developer docs say Instant Checkout is for approved partners; from March 2026 media reported that OpenAI scaled it back, so check OpenAI for the current status |
| 2025-12-18 | Visa | Completed hundreds of controlled, real-world agent transactions with partners |
| 2026-06-10 | Visa, OpenAI | Announced a collaboration. Transactions run within user-set permissions such as spending limits, merchant categories or required approvals, using tokenized credentials |
| 2026-10-20 | Visa, BILL, Billtrust | Launched a pilot in which authorized agents complete approved invoice payments through supplier portals |
These approaches share tokenized credentials and payments under rules the user sets in advance. They require platforms and merchants to take part, and some also need issuer support. RDVCC cards are not part of them today.
Should you give an agent your card number?
We suggest avoiding it where you can (our advice, not a platform rule). Once a card number, expiry and CVC are in a prompt or a log, they may be stored. If you must do it, use a separate card, keep only enough for that purchase on it (cards have a minimum top-up, shown on the card opening page), and close it afterwards, or freeze it first, in which case the money stays on the card. If 3D Secure is required, a person has to read the code.
FAQ
Can I pay for the OpenAI API with a virtual card?
What happens if an agent spends too much?
Does RDVCC offer an agent-specific card?
Can I get a refund for unused API credits?
Can I get unused money back from the card?
What if an API auto top-up is declined?
Official sources
- Claude Help Center: How do I pay for my Claude API usage? ↗
- OpenAI Help Center: Prepaid billing ↗
- OpenRouter FAQ: Credit and billing systems ↗
- OpenAI Developers: Agentic Commerce key concepts ↗
- Stripe: Stripe powers Instant Checkout in ChatGPT ↗
- Retail Gazette: OpenAI pivots ChatGPT shopping strategy (2026-03) ↗
- Mastercard: Mastercard unveils Agent Pay (2025-04-29) ↗
- Visa: Find and Buy with AI (Visa Intelligent Commerce) ↗
- Visa: Visa and Partners Complete Secure AI Transactions (2025-12-18) ↗
- Visa: Visa Partners with OpenAI (2026-06-10) ↗
- Visa: Visa, BILL and Billtrust live pilot (2026-10-20) ↗
Related reading
Last updated 2026-11-09 · Facts checked 2026-11-09 · RDVCC Payments Research
Need a card that works?
Prepaid Visa and Mastercard from $1 · 7×24 support