Your procurement team has a spreadsheet. Three columns: Google, Anthropic, OpenAI. Rows for price, features, SLA. One row is missing — the one that actually matters: "which department gets the invoice."

That invisible line will determine who controls your company's AI agents, and nobody in the meeting room realizes it yet.

You already know the pricing. Google bills agent compute to your cloud infrastructure line item. Anthropic bills session-hours plus tokens to your engineering API budget. OpenAI's SDK is free to download, but token costs scatter across individual developer accounts with no org-level billing. We've walked through those numbers. What we haven't walked through is the organizational wreckage that follows.

Budget ownership equals decision authority. When an autonomous agent starts doing real work — calling tools, writing emails, booking resources without a human clicking "approve" — someone has to pay for it. And whoever pays, controls. Controls rollout speed. Controls the kill switch. Controls whether the thing ships next week or sits in procurement review until Q4.

The infrastructure trap

Google's billing model hands governance to infrastructure teams. These are people who understand uptime, scaling, and cost optimization. They do not understand whether your customer-support agent is hallucinating refund policies.

They can tell you the agent consumed 847 vCPU-hours last month. They cannot tell you the agent promised a customer a full refund on a non-refundable ticket. Infra teams treat agent workloads like any other compute — right-size, auto-scale, cost-alert at 80% budget. The agent's behavior falls through the cracks because nobody on the infrastructure side has the domain expertise to evaluate what the agent actually does with those cycles.

The engineering trap

Anthropic's model puts engineering in charge. The people who built the agent own the bill. Logical, until you realize engineering doesn't control headcount budgets, doesn't own the customer relationship, and doesn't sit in the room when the VP of Operations asks why support costs tripled this quarter.

Engineers optimize for capability. They want the agent to do more, handle more edge cases, call more tools. That instinct directly conflicts with cost containment — and nobody gave engineering the authority to make that tradeoff for the whole organization. As Finout's April 12 cost analysis showed, a single hour-long coding session with a top-tier model can run about $0.70 before you count the engineering hours spent deciding whether to run it. Multiply that by a team of forty and suddenly you have a budget conversation that engineering never trained for.

The nobody trap

OpenAI's Agents SDK — open-sourced in March 2025 and updated on April 15, 2026 — costs nothing to run. But token costs scatter across individual developer API accounts. Nobody gets a centralized invoice. Which means nobody centrally controls the spend. Every developer is their own procurement department.

This is the worst outcome. Not because it's expensive — it might actually be cheaper — but because when the agent does something stupid at 3 AM, there's no single throat to choke.

As World Today News reported on April 19, these pricing architectures create fundamentally different organizational structures. The OpenAI structure is: none.

The question nobody's asking

As John Furrier wrote for SiliconANGLE on April 20: "The battle is shifting from models to platforms to control planes." He's right about the battle. He's wrong about who's fighting it. It's not vendor versus vendor. It's your infrastructure team versus your engineering team versus your product team, and none of them asked for this war.

Here's my take: the department holding the budget must also hold domain expertise to assess agent risk. Not compute risk. Not cost risk. Behavioral risk. Can this agent promise things you can't deliver? Can it access data it shouldn't? Can it take actions that require human judgment?

No vendor's pricing page answers those questions. And the org chart that results from each pricing model determines whether anyone in your company is even positioned to ask them. Right now, most companies default to whichever team already runs the cloud account — a selection criterion roughly as rational as choosing your surgeon based on who holds the hospital parking pass.

Before comparing features and benchmarks, trace where the agent invoice lands. Then ask: does that department understand what the agent does, not just what it costs?

You're not choosing a vendor. You're choosing which department owns the agent era. The pricing page already made that choice for you — you just haven't read it that way yet.