Give your agents a wallet. Keep control of the spend.
Scoped cards, hard limits, a double-entry ledger, and a written reason for every decision, including the declines.
One card, one job, one set of bounds.
Issue a virtual card scoped to one agent, one task, or one purchase. Set the total, the per-transaction ceiling, the velocity window, the merchant categories and the approval threshold.
One prompt, anything on this list.
Search, order, pay, track. You just approve.
Overspend isn't caught after the fact. It can't happen.
Every unit of money lives in a real double-entry ledger. Every movement is a balanced transaction: debits equal credits, in the same currency.
HOLD → RELEASE → AVAILABLE
There is no privileged caller.
Every authorization runs the same path, in the same order, for every client. Your agent is checked exactly as hard as your dashboard.
Each failure returns a reason code, not a shrug. Your agent can respond intelligently to a decline because the decline says something.
One approval. One purchase.
Set an approval threshold. Anything at or above it is declined as pending, and opens a review. Approve from the dashboard, or from Slack.
CONSUMED ON RETRY · THEN SPENT
Agents don't need a phone number. They need a structured answer.
An agent searching the open web finds a phone number, a 2019 price list and a CAPTCHA. A-MERCHANT gives it a structured answer: who has it, at what price, how far away, how many are in stock, and when they can deliver.
The tools are a surface, not a shortcut.
Connect Claude, your own agents, or any MCP-compatible client with one config block. Every capability is also a documented REST endpoint.
We never guess where your money is.
Underneath the card sits AFP, the Agentic Financial Protocol. You describe the payment, not the plumbing. AFP scores every eligible rail on cost, speed and finality, and routes down the one that fits.
Gated means built, tested and switched off. Rails that move value outside the card network carry Travel Rule messaging and counterparty wallet screening, wired in before the rail can be enabled. We turn a rail on when it's real, not when it demos.
A database dump yields nothing usable.
Currency is a field, not a fork.
Cards are issued by a licensed issuing partner under licence from the card networks, operating under a sponsoring institution in each market. a·card is not a bank.
Priced in USD. No card required to build.
Free to start. Upgrade when your agent gets busy.
The per-card cap is a hard platform ceiling on what any single card may carry. It sits above, and independently of, the limits you set yourself. Interchange and rail fees are passed through at cost and disclosed before a payment executes.
The agents are already here. Give them a budget.
5 min setup. Works with Claude Desktop and any MCP client.