Cost Optimization Just Got a Second Author

A model rewrote its own GPU serving code, cut OpenAI’s inference cost, and got itself a price cut in the field — while nobody prompted it to think about money.

That’s not a caching trick. That’s not a router sending easy questions to a cheaper tier. That’s the thing traditionally done to a model — the entire FinOps-for-AI playbook — being done by one, autonomously, at the infrastructure layer. And it landed in the same week I was already forwarding myself an open-source tool that does the mirror-image job on AWS: scan the account, find the waste, hand you a ranked list with a dollar figure attached, no ticket, no Slack thread, no waiting on next quarter’s audit. Cost optimization didn’t get better tooling. It got a second author, on both sides of the meter, in the same seven days.

Your agent lost you money last week, rated the experience five stars, and you agreed with it. That is not a bug in the agent. That is the entire shape of the market we just walked into. When a machine negotiates on your behalf and comes back with a worse deal than a better machine would have gotten, it does not return an error. It returns a plausible, satisfying, worse outcome — and then it tells you the deal was fair. And here is the cruelest part: you have no way to know it was wrong, because you never see the deal you didn’t get.

The best deal in software just ended, and the replacement bill is non-deterministic.

For two years, flat-rate coding-agent pricing was the deal of the decade. Twenty bucks a month, point an agent at your codebase, let it churn. You were almost certainly consuming more value than you paid for. That wasn’t generosity. It was customer acquisition, financed by venture money, priced below cost on purpose. And in a two-week window this spring, three different vendors quietly clawed it back.