Same loop every time — the agent asks, you approve, it pays with a single-use card. Here’s where that turns out to be genuinely useful.
Let an agent order food, groceries, or a last-minute gift — without leaving a card sitting in yet another app.
“Order me a pizza.” → one tap approves $24.50 at Gino’s, paid with a card good for exactly that.
Running something that could be prompt-injected, jailbroken, or just buggy? Hand it a leash, not your card number.
Even a compromised agent can only spend what you approved — one merchant, one amount. There’s no standing card for it to drain.
Have an agent sign you up for a service as a capped, merchant-locked mandate — not a card on file you’ll fight to cancel later.
Cancel from your dashboard and the merchant can never charge you again.
“Book the 8am flight under $300.” The agent assembles it; you approve the exact total before anything is charged.
Every booking is scoped to the amount and merchant you saw — no open-ended card.
Household staples, pet food, printer ink — recurring purchases an agent can handle within limits you set once.
Monthly caps per agent keep “restock” from ever becoming a surprise.
Building something that needs to pay for API credits, tools, or data? Give it a token instead of a card, and cap what it can spend.
See For developers for the integration.
See the loop behind all of these on How it works · or the guarantees