Agents Have Started Spending Money on Their Own, and No Control Layer Is Watching

The Problem

A rail that lets agents pay for themselves shipped again this week. The hard part is what comes next. Once a single agent spends money on every API call, every tool use, and every purchase it makes on your behalf, a finance team faces the equivalent of hundreds of employees each holding a corporate card. And what people get, agents do not. What is this month’s budget and who blew past it, is this charge off the usual pattern, does this amount need approval, which button stops everything when something goes wrong. A payment rail just moves the money. It does not control that money or show you where it went. One malfunction, one infinite loop, one prompt injection comes back as a bill.

Why Now

With Natural raising $30M and Stripe moving the same way, agents that pay for things are past the demo and into deployment. A control layer always follows a rail. When corporate cards spread, Ramp and Brex became large companies on spend management. When cloud bills exploded, observability and cost tooling became a category. Agent spend walks the same path, and the sequence has just started. The rail that moves the money is settling into place first, while the controls and observability a finance team would trust are still a blank. That blank does not stay open long.

How to Build It

Sit a control plane between the agent and the payment rail. When an agent requests a payment, that request does not go straight to the rail, it passes through this layer first: per-agent and per-team budgets and limits, merchant and category allowlists, anomaly detection that flags spend off the usual pattern, escalation to human approval above a threshold, and a full audit log of what went out, when, and why. A kill switch that stops everything at once sits up front.

flowchart LR
  A[AI Agent] -->|payment request| C[Spend Control Plane]
  C -->|budget and policy check| P[Budgets, Limits, Allowlists]
  C -->|anomaly and audit| M[Monitoring, Audit Log]
  C -->|approve or hold| R[Payment Rail]
  C -.->|flag large spend| H[Human Approval]

Enter narrow. Start as a drop-in dashboard on top of an agent payment API like Natural’s or Stripe’s, shipping budgets and limits, a real-time spend feed, and anomaly alerts first. Then wire into accounting and ERP to automate reconciliation. Then move audit and compliance reporting into a higher tier. Charge on the number of agents managed or the spend volume processed.

Success Criteria

First, do not get locked to one rail. Bolt onto a single payment infrastructure and you are done the moment that company ships the same feature. This has to be a neutral layer that rides on top of several rails. Second, balance the defaults. Too tight and the agent stalls, too loose and the control means nothing. A default policy that is safe without blocking real work is the product. Third, earn the finance team’s trust. You are not selling to developers, you are selling to the person accountable for the money. Whoever provides records that go straight into an audit, and the certainty of an instant stop when something breaks, takes this category.