Claude Sonnet 4.6: Opus-Level Coding Performance at Sonnet Pricing

First Sonnet to Beat Previous Opus

Anthropic released Claude Sonnet 4.6 on February 17, 2026, at the same price as Sonnet 4.5 — but with performance that rivals the much more expensive Opus tier. For the first time ever, a Sonnet model is preferred over the previous generation's Opus in coding evaluations.

Benchmark Results

Benchmark	Sonnet 4.6	Sonnet 4.5	Opus 4.6
SWE-bench Verified	79.6%	77.2%	~80%
OSWorld (Computer Use)	72.5%	—	72.7%
ARC-AGI-2	58.3%	13.6%	—
Terminal-Bench 2.0	59.1%	—	—

The ARC-AGI-2 score represents a massive 4.3x improvement over Sonnet 4.5, jumping from 13.6% to 58.3%.

flowchart TD
    HUB(("First Sonnet to Beat<br/>Previous Opus"))
    HUB --> L0["Benchmark Results"]
    style L0 fill:#e0e7ff,stroke:#6366f1,color:#1e293b
    HUB --> L1["Developer Preference"]
    style L1 fill:#e0e7ff,stroke:#6366f1,color:#1e293b
    HUB --> L2["Pricing and Context"]
    style L2 fill:#e0e7ff,stroke:#6366f1,color:#1e293b
    style HUB fill:#4f46e5,stroke:#4338ca,color:#fff

flowchart LR
    subgraph BEFORE["Without an AI Voice Agent"]
        B1["Missed calls<br/>30 to 50 percent after hours"]
        B2["Receptionist payroll<br/>3,000 to 5,000 per month"]
        B3["Slow follow up<br/>lost leads"]
        B4["No call analytics"]
    end
    subgraph AFTER["With CallSphere"]
        A1["Zero missed calls<br/>24 by 7 coverage"]
        A2["Flat monthly fee<br/>199 to 1,499 per month"]
        A3["Instant follow up<br/>via CRM webhooks"]
        A4["Sentiment, intent,<br/>and lead score on every call"]
    end
    BEFORE -->|Switch| AFTER
    style BEFORE fill:#fee2e2,stroke:#dc2626,color:#7f1d1d
    style AFTER fill:#dcfce7,stroke:#059669,color:#064e3b

flowchart LR
    IN1["Monthly call volume"]
    IN2["Average deal value"]
    IN3["Current answer rate"]
    CALC["CallSphere captures<br/>missed calls 24 by 7"]
    OUT1["Recovered revenue per month"]
    OUT2["Receptionist cost saved"]
    OUT3["Net ROI"]
    IN1 --> CALC
    IN2 --> CALC
    IN3 --> CALC
    CALC --> OUT1
    CALC --> OUT2
    OUT1 --> OUT3
    OUT2 --> OUT3
    style CALC fill:#4f46e5,stroke:#4338ca,color:#fff
    style OUT3 fill:#059669,stroke:#047857,color:#fff

Developer Preference

In Claude Code testing, developers preferred Sonnet 4.6 over Sonnet 4.5 70% of the time and over the previous flagship Opus 4.5 59% of the time. This is unprecedented for a Sonnet-class model.

Pricing and Context

At $3/$15 per million tokens — five times cheaper than Opus — Sonnet 4.6 also introduces a 1 million token context window (beta), making it the first Sonnet-class model to support full codebase analysis in a single prompt.

The model is available across Claude.ai, the API, Amazon Bedrock, and Microsoft Foundry.

Source: CNBC | The New Stack | DataCamp | SitePoint

Claude Sonnet 4.6: Opus-Level Coding Performance at Sonnet Pricing — operator perspective

Behind Claude Sonnet 4.6: Opus-Level Coding Performance at Sonnet Pricing sits a smaller, more useful question: which production constraint just got cheaper to solve — first-token latency, language coverage, structured outputs, or tool-call reliability? The CallSphere stack treats announcements as input to an evals queue, not a product roadmap. Production agents stay pinned; new releases earn their slot only after a regression suite confirms cost, latency, and tool-call reliability move the right way.

What AI news actually moves the needle for SMB call automation

Most AI news is noise. A new benchmark score, a leaderboard reshuffle, a leaked memo — none of it changes whether your AI receptionist books appointments without dropping the call. The handful of things that do move production AI voice and chat are concrete: realtime API stability (does the WebSocket survive 5+ minutes without a stall?), language coverage (does it handle 57+ languages with usable accents, or is English the only first-class citizen?), tool-use reliability (does the model actually call the right function with the right argument types under load?), multi-agent handoffs (do specialist agents receive structured context, or just transcripts?), and latency under load (p95 first-token under 800ms when 200 concurrent calls hit the same endpoint?). The CallSphere rule on news is: if it doesn't move at least one of those five numbers in a measurable eval, it's a blog post, not a product change. What to track: provider changelogs for realtime endpoints, tool-call schema changes, language-add announcements, and any deprecation that pins your stack to a sunset date. What to ignore: leaderboard wins on tasks that don't map to your call flow, "agentic" benchmarks that don't measure tool latency, and demos that work because the prompt was hand-tuned for the demo. The teams that ship fastest treat AI news the same way ops teams treat CVE feeds — read everything, act on the small fraction that touches your runtime, archive the rest.

FAQs

Q: Is claude Sonnet 4.6 ready for the realtime call path, or only for analytics?

A: Most of the time it doesn't, and that's the right starting assumption. The relevant test is whether it improves at least one of: p95 first-token latency, tool-call argument accuracy on noisy inputs, multi-turn handoff stability, or per-session cost. Real Estate deployments run 10 specialist agents with 30 tools, including vision-on-photos for listing intake and follow-up.

Q: What's the cost story behind claude Sonnet 4.6 at SMB call volumes?

A: The eval gate is unsentimental — a regression suite that simulates real call traffic (noisy ASR, partial inputs, tool-call timeouts) measures four numbers, and a candidate has to win on three of four without losing badly on the fourth. Anything else is treated as a blog post, not a stack change.

Q: How does CallSphere decide whether to adopt claude Sonnet 4.6?

A: In a CallSphere deployment, new model and API capabilities land first in the post-call analytics pipeline (lower stakes, async, easy to roll back) and only later in the live realtime path. Today the verticals most likely to absorb new capability first are Salon and Sales, which already run the largest share of production traffic.

See it live

Want to see sales agents handle real traffic? Walk through https://callsphere.ai/demo or grab 30 minutes with the founder: https://callsphere.ai/book.