Anthropic shipped Claude Sonnet 5. On knowledge work it edges out Opus 4.8, its own flagship, at roughly half the price. The benchmark table isn't the story. The price column is.

I nearly skipped the release after reading the benchmark table. Then I reached the pricing. The mid-tier model matched the flagship on paid knowledge work at a fraction of the cost. For buyers, that column matters more than a narrow leaderboard win.

Read the price column, not the benchmark

Here are the numbers that matter. On GDPval-AA, the knowledge-work benchmark, Sonnet 5 scores 1618 against Opus 4.8's 1615. The mid-tier passed the flagship. On Humanity's Last Exam with tools, it is 57.4% versus 57.9%, a difference well inside rounding error. On the work that maps to what knowledge workers actually do, these two models are indistinguishable.

Sonnet 5 launches at $2 per million input tokens and $10 per million output at the introductory rate, settling to $3 and $15. Opus 4.8 is $5 and $25. The cheaper model is priced at roughly 40% of Opus for work where their measured results are close.

The moment a capability stops being scarce, the market reprices around delivery, not intelligence.

When the premium product and the mid-tier product do the same job, the premium is no longer buying capability. It is buying a slightly better result on the tail, for the cases where the last fraction of a percent matters. For the vast majority of knowledge work, that tail is irrelevant, and the market knows it. The price column is where that knowledge shows up first.

Compute did it. Storage did it. Bandwidth did it.

Compute, storage and bandwidth went through a similar repricing. Once the base capability became widely available, buyers paid for delivery, integration and reliability.

  • Compute. A cycle was once a rationed resource you scheduled time on. Now it is a commodity you rent by the second and never think about.
  • Storage. A megabyte was a budget line. Now storage is effectively free and the cost that matters is moving and querying the data.
  • Bandwidth. A bit over the wire was metered and precious. Now the pipe is assumed and the value moved to what flows through it.

In every case the capability did not disappear. It became the floor. And once it was the floor, the entire market repriced around the thing that was still scarce: delivery, integration, reliability, and cost at scale. Intelligence is now walking the same path. The capability to do frontier-grade agentic knowledge work is becoming the floor, not the ceiling.

Frontier-grade is now the default tier

The most telling signal is not in the benchmark or the price. It is in the distribution. Sonnet 5 is the model free and Pro users get by default. Frontier-grade agentic work is no longer the thing you pay up for. It is the thing you get when you don't pay attention. The premium tier and the default tier now overlap on capability.

Think about what that does to product strategy. If your entire pitch was "we have access to the best model," you no longer have a pitch, because the best-in-class-for-the-task model is the commodity default. The differentiation has to move somewhere else, and there are only a few places it can go: the data you feed the model, the harness you run it in, and the cost at which you can finish the job. I've argued the data point separately in models are commodities, clean data is not, and the harness point in route by task, not by vendor. When capability is uniform, routing to the cheapest sufficient model per task is not a nice-to-have. It is the architecture.

The question changed. Notice which one.

For two years the operative question was: can the model do the task? That question is now boring, because for most tasks the answer is yes, from the default tier, for a couple of dollars per million tokens. The interesting question is a different one entirely:

What does the task cost to finish, at scale, with nobody watching?

Every clause in that sentence is load-bearing. Cost to finish, not cost per call, because agentic work chains many calls and the total is what hits the invoice. At scale, because a workflow that pencils out at ten runs a day can bankrupt you at ten million. With nobody watching, because the economics only work if the agent completes autonomously, without a human babysitting each step and eating the real cost, which is salary, not tokens.

The selection problem is therefore concrete: engineer the cheapest reliable completion of a unit of work. Token price is one input alongside retries, tool calls, review and failure cost. The same economics sit behind my argument that the constraint is GPUs, not demand.

What operators should do about it

If capability is commoditizing and cost is the frontier, then the winning moves are unglamorous and entirely about execution:

  • Instrument cost per completed task, not per token. The token price is a red herring. Measure what it costs to finish a real unit of work end to end.
  • Default to the cheapest sufficient model and route up only on the tail. Reserve the flagship for the fraction of cases where the last percent actually pays.
  • Design for unattended completion. The moment a human has to watch, your cost model is dominated by labor and the token savings are noise.
  • Move differentiation to data, harness, and reliability. Capability is the floor now. Your edge lives in the layers the commodity model can't provide.

The leaderboard-watchers are optimizing the wrong variable. They are still asking whether the model is smart enough, a question the market has already answered and priced to the floor. The operators who win the next cycle are asking what it costs to finish the work when the intelligence is free and the only scarce thing left is disciplined, unattended, economical execution. Capability is commoditizing. Cost is the new frontier. For the wider thesis, the manifest and the Joule Wars lay out where the joules, and the margins, actually go.