Nobody Approved the Spend. It Came Four Cents at a Time.

A founder I work with at an $11M company set his AP approval threshold at $2,500. Anything above it needed his sign-off, and that rule had held for years. Then his card statement showed $31,000 to a single AI vendor for the quarter. He was sure he'd never approved it, and he was right. The charge was 14,000 separate API calls, not one of them over a few dollars. Every call slid under his threshold. His control was the threshold, and the spend was shaped to walk right past it.

Thresholds assume transactions are big and rare

An approval policy is a dollar line. It assumes money leaves the company in discrete, reviewable chunks: a vendor invoice, a signed contract, a card swipe at a real merchant. Catch the outlier above the line, ignore the noise below it. That worked when a purchase was an event you could point to.

Agentic tools break the assumption. They bill by action. A research agent runs 400 times before lunch at a few cents a run. No single charge is worth a human's attention. The total is a real number anyway, and nothing inside it ever asks to be reviewed.

The protocol data shows where this heads. More than 167 million agent-to-agent transactions have already settled in 2026 on X402, an open payments rail built for stablecoin micropayments too small for card interchange. Your version is smaller and already on your statement: the metered AI line on a SaaS invoice, the per-run charge on a tool someone in product wired up last month.

What you were actually controlling

An approval threshold doesn't govern spend. It governs the size of a transaction. When money stops arriving in large pieces, the threshold stops seeing it.

What you wanted to control was simpler than a dollar line. Did someone decide this was worth buying. You proxied that decision with an amount because size and significance used to move together. A $10,000 charge mattered. A $4 charge didn't. Agent spend cuts the two apart. A $4 charge that fires 8,000 times matters more than the $10,000 invoice you stop to read.

This bites a growing company harder than a big one. You don't have a procurement team tracking aggregate vendor spend in real time. You have a threshold and a monthly statement. By the time the statement lands, the quarter is already the quarter.

What to control instead

Move the control off the single transaction and onto the vendor. Set a monthly ceiling for every tool that bills by action, and have it pause or alert when cumulative spend crosses the line, no matter how many charges it took to get there. A per-charge threshold can't do that. A per-vendor cap can.

Tag the metered and agentic vendors so you read their run-rate weekly instead of meeting it at close. The number that matters is dollars per vendor this month against the cap you set, not the size of any one charge.

Then put a name on each agent. A tool that spends money on its own needs an owner whose budget it draws from. Your old question was whether a transaction was big enough to check. The real one now is who turned the thing on and what its limit is.

Your threshold still works. It's just guarding a door the money stopped using.