Written by Meraky Consulting with AI assistance. Links to our own free tool and checklist are at the end.
Give an agent a wallet or a card and it will spend. That's the point. Paying per call for data, inference, search or compute is now a normal part of how agents work, whether through prepaid API credits, virtual cards, or stablecoin payments over protocols like x402.
The spending isn't the problem. The month-end is.
What finance actually sees
A single research agent can make thousands of small payments a month. On the wallet or card statement, each one is a line with an amount and a counterparty identifier. What it doesn't have:
- A vendor name you recognise. A wallet address or a processor descriptor, not "market data provider".
- What was bought. No invoice, no line items.
- Why. Which task, which job, which approval.
Multiply that by every agent in production and you get a ledger nobody can explain. That's the line your auditor circles.
The trend isn't slowing. Ramp reports that average monthly token spend by its customers has grown 13x since January 2025. And it isn't only bookkeeping: in research from the Cloud Security Alliance and Token Security, 65% of organisations had at least one security incident caused by AI agents in the past year, and 35% of those reporting incidents saw financial losses.
Two records that never meet
Most teams already have the data to explain agent spend. It just lives in two places that nobody joins:
- What the agent says it bought. Your agent, or the framework around it, knows the resource it called, the price it was quoted, and the task that triggered it.
- What actually left the account. The card statement, the provider invoice, or the on-chain transfer.
Reconciliation is matching the two. Once you do, every payment falls into one of five buckets:
| Status | Meaning | What to do |
|---|---|---|
| Matched | Log and payment agree | Book it |
| Mismatch | Both exist, but amount or payee differ | Usually a price change or a bug. Investigate |
| Unexplained | Money left, no record of why | This is the auditor's question. Find the cause before month-end |
| Unsettled | Agent thinks it paid, nothing moved | Keep it out of the books |
| Unknown | The paid call timed out, so the agent can't tell whether it paid | Count it as possibly spent until a transfer settles it |
If you only do one thing after reading this: make your agents write a payment log. One line per payment, with the transaction or receipt ID, the resource called, the amount, and the task. Everything else depends on it.
{"tx_hash": "0x…", "ts": "2026-10-01T12:00:00Z", "resource": "https://api.example.com/v1/data",
"pay_to": "0x…", "amount": "10000", "asset": "USDC", "decimals": 6,
"description": "Market data query", "category": "Data services"}
Five controls that prevent most of the pain
Reconciliation finds problems after the fact. These stop them happening:
- One payment instrument per agent. Its own virtual card, API key or wallet. Shared credentials make spend untraceable, and you can't stop one agent without stopping all of them.
- Limits at the provider, not in the prompt. An agent can't be trusted to enforce its own budget. Set per-transaction, daily and monthly caps at the card issuer, API provider or wallet.
- Approved vendors only. A payment to a new vendor or address needs a person first. This also blocks payment instructions injected through content the agent reads.
- Alerts on spikes, not just budgets. A budget alert at 100% tells you at month-end. A velocity alert (spend far above the normal hourly rate) tells you while the loop is still running.
- A kill switch you've tested. Pause the agent, freeze its card, revoke its keys, move its wallet balance. Write it down. Time it once a quarter.
Stablecoin payments: two extra things
If your agents pay in USDC or another stablecoin:
- Payments are usually irreversible. Size the wallet float as money you could lose.
- Tax may apply to every payment. In the US, for example, digital assets are generally treated as property, so spending them can be a taxable disposition even when the amount is twelve cents. Record the fair value in your reporting currency at the time of each payment, and ask your adviser how it applies to you.
Free tools to get started
We built two things while working through this ourselves:
- agent-ledger-export — a free, open-source command-line tool (Python, no dependencies). Give it your agent's payment log and a block-explorer CSV of the wallet's transfers, and it writes a reconciled ledger with the five statuses above, EUR and USD values, and a bank-statement file you can import into Xero.
- The 10-point agent spend checklist — one page, free, no sign-up. Tick what's true today; every unticked box is a way an agent can cost you money nobody notices.
We're also gauging interest in a hosted version that does the matching automatically and syncs to your accounting software. If that would help, join the waitlist.
Not accounting, tax or legal advice. Meraky Consulting builds software for finance operations. The tool and checklist are free; there's also a paid template kit on the same page.
Top comments (0)