Mercury agent cards: give your AI a real spending limit

Your agent does not need a credit card. It needs a card that says no. Mercury launched Mercury Spend on August 11 with agent cards — virtual cards an AI agent can transact on, inside limits a human set and the agent cannot change. The product is for Mercury's banking customers. The control pattern is for everyone running agents that touch money.

What actually happened

Mercury's announcement describes Spend as budgets plus cards built into the banking dashboard, for employees and for agents. The mechanics, as reported by CFOtech and Fast Company:

• Budgets are scoped to a purpose — travel, software, procurement — and cards are issued against them
• Transactions over the limit are declined at the point of sale, not flagged in a report next month
• Merchants can be restricted by name or merchant category code
• Only a human can create an agent card. The agent spends within the limits and cannot alter them
• Cards are trackable, auditable, and cancellable
• Cards auto-freeze when a receipt, memo, or category is missing, and stay frozen until someone supplies it

Mercury's release puts its base at more than 300,000 entrepreneurs, and ties Spend into Command, its natural-language assistant. CEO Immad Akhund framed the pitch around founders needing "a scalable and programmatic way to manage spending."

Why agent spend controls matter for your business

We have watched this arrive in pieces: agents getting bank accounts, agents opening Stripe accounts, agent identity vendors consolidating. Mercury's version is the clearest statement of the right shape so far, and you can steal it without switching banks.

The shape is this: the limit is enforced by a system the agent cannot reach. That is the whole idea. An agent instructed to stay under $200 will stay under $200 until a prompt injection, a hallucinated price, or a retry loop says otherwise. A card that declines at $200 does not care what the agent believes. One is a suggestion; the other is a control. We made the same argument about keeping approval gates out of agents' reach, and it holds here with money attached.

Three things worth doing this month, whatever you bank with:

Give every agent its own payment instrument. Not a shared company card. A virtual card per agent, per purpose, with its own ceiling. When something goes sideways you kill one card, and you know exactly which workflow it was.

Set the merchant allowlist, not just the amount. A ceiling stops runaway spend. An MCC restriction stops the category of spend you never authorized. Most virtual card issuers — Ramp, Brex, Stripe Issuing, plenty of banks — support both today.

Keep the human in the create step, not the approve step. Approving every transaction defeats the automation. Approving the card — its budget, its merchants, its expiry — gives you the control without the babysitting.

The bank you use is a preference. Making the limit un-negotiable is the requirement.

Sources: Mercury via BusinessWire, Fast Company, CFOtech.