Anthropic launches Claude Sonnet 5

The number everyone quoted at launch was the price - $2 per million input tokens and $10 per million output, dropping to $3 and $15 after August 31. But per-token price is only half of what an agent actually costs. Cost per task is price multiplied by how many tokens the model burns to finish the job, and this is where Sonnet 5 gets counterintuitive. Independent testing placed it at 53 on the Artificial Analysis Intelligence Index ^[3], yet MarkTechPost's cost-performance analysis found that at high effort levels Sonnet 5 can cost more than Opus 4.8 to reach comparable quality, because it generates substantially more tokens per task ^[2].

The practical implication is that a buyer who compares only the sticker prices will misjudge their agent bill. The savings are real, but they concentrate at low and medium effort, on simpler and repetitive workloads where the token overhead stays contained ^[2]. That subtlety is exactly what the loudest skeptics in developer communities seized on, framing the release as a lateral move rather than a genuine step up - a reading that the promotional pricing conveniently softens until it expires.

This launch reads as a business decision as much as a model release. Large enterprises including Meta, Amazon, and Uber have begun restricting AI token usage as inference bills climb, a reversal of the earlier era of unconstrained consumption ^[4]. Anthropic priced Sonnet 5 below Opus 4.8, GPT-5.5, and Gemini 3.1 Pro to capture that cost-sensitive demand ^[5].

Timing sharpens the picture. The company filed confidential IPO paperwork weeks before the launch ^[4], and a cheaper mid-tier model that widens agent deployment is precisely the growth narrative a public offering rewards ^[5]. The strategic bet is cost-per-task economics over benchmark bragging rights: Anthropic is wagering that the next wave of revenue comes from agents running millions of inexpensive steps, not from a single headline-grabbing flagship. Whether the token-bloat problem undercuts that thesis is the open question the pricing debate keeps circling back to.

On raw capability, Sonnet 5 lands between its predecessor and the flagship. It scores 63.2% on SWE-bench Pro versus 58.1% for Sonnet 4.6 and 69.2% for Opus 4.8, and it closes most of the reasoning gap on Humanity's Last Exam ^[2]. On at least one axis it slips past the flagship: on the GDPval knowledge-work benchmark, Sonnet 5 narrowly edges Opus 4.8 - unusual for a model positioned a tier below ^[2].

The agentic upgrade is the real story. Anthropic positions Sonnet 5 as its most agentic Sonnet yet, built to make plans, use tools like browsers and terminals, and run autonomously on work that used to require a larger, more expensive model ^[1]. The gains show up most in the tool-use benchmarks: Sonnet 5 jumps to 80.4% on Terminal-Bench 2.1 from Sonnet 4.6's 67.0%, and to 81.2% on OSWorld-Verified computer-use tasks from 78.5% ^[2]. The New Stack framed the release the same way the numbers do - closing the gap with Opus while staying cheap until August ^[6]. The takeaway is that Sonnet 5's edge is less about topping any single leaderboard and more about finishing long, tool-heavy jobs reliably at a lower headline rate.

Reception split cleanly along one fault line. Developer YouTube and early adopters ran Sonnet 5 through live coding gauntlets within hours of release, and some reported it fixed backend bugs that the flagship had been stuck on for days, praising its speed. The dominant note in the busiest community threads, though, was skeptical: the highest-engagement discussions asked bluntly what the point was, pointing to the same cost paradox and to a version number that looked like marketing meant to match a rival's 5.

What emerged from defenders and critics together was a usable rule rather than a verdict: match the effort level to the task. Reach for Sonnet 5 at low or medium effort, where its speed and token savings compound on high-volume, routine agent steps, and keep a flagship model for architecture-heavy reasoning ^[2]. Early enterprise testers were more measured than either camp, valuing the model's judgment in refusing risky requests as much as its raw build speed ^[7].