The Model Stopped Being the Product This Week

Five "unrelated" stories, one repricing: the value in AI has moved to everything around the model, if you're paying attention. You read this newsletter; obviously you are.

The most important thing that happened in AI this week is that nothing particularly important happened to a model. Instead, a coding agent got caught exfiltrating repositories. A lab shipped a flagship that costs more, yet holds less context than its predecessor. Apple sued OpenAI over hardware engineers. Anthropic moved a migration deadline for the third time. OpenAI repriced prompt caching. The coverage has largely treated these as five stories, but I disagree. I think they’re one story, and it’s not about any of the companies involved.

Here’s my thesis: model capability is commoditizing rapidly, and the actual competition is now around the inputs around the model. Training data, training environments, distribution endpoints, inference capacity, memory bandwidth. Each of this week’s events is the market getting ahead of that via pricing.

Remember, I spent a decade watching this exact transition happen in cloud, where the story stopped being “whose compute is better” years before the marketing did. The prices were the leading indicator there, too. Welcome to Cloud Economics, refactored for the AI era.

Prices, Prices Everywhere

Development sessions got a price, and it turns out you’ve been paying it. The Grok Build incident is being covered as a security failure, which it absolutely is. It’s also a financial disclosure. A vendor doesn’t wire full-repository upload into a coding tool because it’s careless; that stuff is wildly expensive to move around at scale. (Do not talk to me about “free ingress,” at this scale it is oh so very far from free.) A vendor does this because authentic development sessions on real codebases are the scarce input for training coding models, and there is no synthetic substitute. I posit that this single fact neatly explains a set of economics the industry treats as separate mysteries: why coding agents are priced below cost, why vendors tolerate flat-rate plans that lose gobs of money on heavy users, why the Grok 4.5 launch post presents “trained alongside Cursor” as a selling point. The “subsidy” is in fact them shrewdly making a purchase. “Your session data” is what they’re getting here, and it’s wildly valuable to them. Your coding agent is cheap for the same reason the casino comps your room: the house is not confused about who's paying. This week the price became accidentally visible, and once a price is visible, a market forms around it: expect increased disclosure, with actual-training-excluded tiers at an explicit premium, and understand that that premium is the market rate for your data. Enterprises are currently selling that asset for zero. Most of them haven’t noticed they’re the seller.

“But my vendor already says they don’t train on my data.” Sure. Read what those statements actually govern. There are three separate planes here: what gets collected off your machine, what gets retained, and what gets trained on. “We don’t train on your data” speaks to exactly one of the three, and is entirely compatible with collecting and retaining everything for “debugging,” “abuse monitoring,” or the ever-popular “service improvement.” The Grok toggle was this distinction rendered as UI: it governed training consent while the repos kept flowing. And these are attestations; you can’t verify any of them from outside the vendor’s infrastructure, which is why the “what’s on the wire” test mattered. An attestation is a pinky promise with a legal department, backed in this case by the full faith and credit of... Elon Musk. Meanwhile, notice that ZDR is something you upgrade to. Vendors already sell zero-retention tiers at enterprise pricing, which means the training-excluded premium I’m predicting isn’t a prediction at all, because it already exists. It’s just been filed under “compliance” instead of “the price of your data,” and nobody’s done the subtraction.

Training environments became the closed layer. The same launch post contained the week’s second disclosure, because why wouldn’t it. A model trained alongside a specific tool is no longer separable from that tool; its benchmark performance is model-in-harness performance, and some fraction of the capability stays behind when you migrate harnesses. (It misses you.) This matters because it inverts the commoditization story at exactly the layer where buyers feel it. Weights leak, distill, and converge; that layer is commoditizing and will continue to do so. The RL environment and the interaction data do not leak (y’know, ideally). So the defensible asset has moved from the model to the environment the model was shaped in, and switching costs, which everyone believes are falling, are instead reconstituting themselves as capability that evaporates on migration. This is the next generation’s lock-in story. Nobody even has to sign an “all-in” agreement about it this time.

Distribution endpoints became existential—in both directions. Apple’s suit against OpenAI reads like big tech poaching drama until you notice what it’s actually about: batteries, logic boards, hardware engineers. OpenAI is building a device. Apple is defending the device layer as the crown jewels at the same moment it’s swapping Siri’s intelligence over to Google. Apple’s institutional bet is that hardware is the moat and intelligence is a commodity input you re-source annually. OpenAI’s bet is the inverse: intelligence is the moat and hardware is the escape route from platform tollbooths. Exactly one of those bets can be right, and at least one of them is currently suing like it knows it. The Gemini swap is evidence for both positions simultaneously. It proves that frontier models are now swappable components at the platform layer, and it proves that platform owners will commoditize any lab that doesn’t control an endpoint. Which yields the prediction the on-device conversation keeps missing: local inference isn’t a threat arriving at the labs, it’s a necessity arriving from inside them. You cannot ship a performant device whose intelligence round-trips to a datacenter at datacenter prices and datacenter latency. The most committed future buyers of efficient small-model inference are the frontier labs themselves.

Inference capacity got a shiny new rationing mechanism; no it is not the deadline. Anthropic extended included Fable 5 access a third time in five weeks. The consensus read is capacity strain plus indecision, with a dash of “GPT-5.6 scared the everloving poop out of them.” That… doesn’t explain the behavior. A capacity-constrained vendor enforces a cutoff; a revenue-seeking one prices it. They’re not doing either of these. Either they’re idiots without a plan, which, sorry, I do not accept, or there’s something else going on here. Extending repeatedly, with the metered structure pre-announced and the date held loose, is a measurement. Each cliff-and-extension cycle produces production data on migration behavior and price elasticity before the credits pricing is committed. This isn’t about generosity or suddenly finding capacity; it’s market research on user behavior. You aren't getting a reprieve; you've been enrolled in a study. Compensation is not being offered. This is the template for how the industry exits flat-rate pricing generally: softly, instrumented to high heaven to get behavioral measurements out of it, with no pre-announcement, and the deadline drama that everyone’s focused on? Well that, gentle reader, is simply where the unsightly seam shows up. Underneath it sits the allocation logic. If inference margins are anywhere near the healthier published estimates, every subsidized subscription token carries an opportunity cost in API revenue, which makes consumer flat-rate plans permanent loss leaders held for data and mindshare purposes. The deadline keeps moving because holding to it was never the objective.

Memory bandwidth got a price tag. GPT-5.6 reached general availability with sticker prices flat across generations and one structural change: cache writes now bill at 1.25x the uncached input rate. Two things follow, and neither is “sneaky stealth price hike they’re hoping you won’t spot.” First, except for AWS’s Managed NAT Gateway data processing (itself a study in bastardry), a vendor meters what constrains it. A surcharge on cache writes is OpenAI stating, in a place that kinda sucks at spin, that memory bandwidth is its binding scarcity. As billing dimensions multiply across providers, each price sheet in turn becomes an increasingly understandable map of that provider’s infrastructure economics; if I can be slightly dismissive, the discipline of reading them is worth more than most of the analyst coverage it will eventually replace. Second, and further out: this pricing taxes statefulness precisely as long-running, memory-heavy agents become the industry’s designated growth product. The invoice-optimal agent under this structure compresses its context and recomputes at inference time rather than remembers. We have built a computer that forgets things on purpose to save money, which is the most relatable technology has been in years. Billing design is now (or will be soon) shaping agent architecture, the technically optimal system and the economically optimal system are diverging, and the discipline that bridges that gap doesn’t have a name yet. Cloud economics didn’t really have a name in 2016 either. I ended up making a career out of it anyway.

What this predicts

Follow those five repricings forward and they converge on a small number of claims I’m comfortable committing to.

The capability conversation isn’t going to be a meaningful purchasing input. Within a couple of years, “which model is best” will sound the way “which cloud has better VMs” sounds now: a question that was settled by convergence and replaced by questions about everything surrounding the commodity. The buyers who adapt early will evaluate harness compatibility, data terms, egress behavior, and billing structure while their competitors are still reading leaderboards. You weren’t buying EC2 instances by comparing them to VMs past the first few years either.

Verification displaces attestation. The Grok incident demonstrated that wire-level auditing is cheap, public, and career-making for whoever runs it. Vendor responses will bifurcate: some will sell provable boundaries, most will move execution server-side where the question “what left my machine” cannot be asked, because “all of it” is the obvious answer. Auditability itself becomes a product attribute, and the locally-executing agent, currently treated as the legacy form factor, becomes the compliance-preferred one in regulated industries just as vendors finish abandoning it.

Pricing becomes the primary disclosure channel. Deadline behavior, regional availability gaps, cache surcharges, credit structures: commercial behavior is now leaking more true information about lab economics and capacity than any filing or keynote I’ve ever seen. The analytical edge shifts to whoever reads those signals systematically. Price sheets are the new S-1s, except they update monthly and nobody audits them.

And the composite prediction, the one this whole week of news drama leads me to: the labs finish becoming cloud-shaped. Consumption-driving products, vertical solutions, owned endpoints, loss-leader tiers, capacity rationing, billing complexity. Every incentive documented above pushes the same direction. You'll know it's complete when one of them throws a 60,000-person conference about it. I've already got the name picked out: re:Inference. The invoice is in the mail. The interesting question for the next two years isn’t “which lab has the best model.” It’s which lab builds the best business around the fact that the model no longer matters most, and which vendors in the surrounding ecosystem get absorbed the way the early AWS ecosystem was.

So no, I'm not going to rank this week's news. I'm going to keep reading pricing pages, because they're the one place a vendor's marketing department doesn't get a vote. You should probably do the same.

— C