Every Models & LLM APIs comparison and buyer's guide for building AI agents — 20 pieces and counting. Each is a head-to-head or a “best X for Y” roundup with a sources-backed verdict.
Moonshot's new coding model cuts reasoning tokens ~30% while nudging its own benchmarks up — a wager that per-step cost, not raw smarts, now decides agentic coding.
The new model isn't worse. Your prompt was quietly overfit to the old one's defaults — so the swap changes your agent's behavior even when you change nothing. Freeze the baseline before you switch, not after.
OpenAI's new three-tier lineup is priced for a router, not a pick. For agent workloads the flagship is the wrong default — the interesting model is the one in the middle.
Google shipped a Flash model that beat its own Pro on SWE-bench Verified. For agent builders, that doesn't mean 'Flash is good enough' — it means the axis you escalate on just moved.
Both open-weight variants ship the same 1M-token attention and the same agentic training. For an agent, the choice isn't a smartness tier — it's a per-turn cost knob.
Qwen3-4B, Phi-4-mini, Gemma, Nemotron 3 Nano: the pick forks on a question no leaderboard prints — are you short on memory or short on tokens-per-dollar? And the score that decides an agent isn't MMLU.
Sonnet 5 lands at 40% below Opus and beats it on terminal work — but a new tokenizer quietly inflates every token count by ~30%, so the rate card is not the price. Do the cost math in your own units.
GPT-5.5 and Claude Opus 4.8 are tied on SWE-bench Verified at ~88.6%. That means the leaderboard number stopped being the answer — and your agent's scaffolding started being it.
An open-weight model is now within a point of Claude Opus on long-horizon coding benchmarks. The benchmark delta is the least interesting number; the token price is the one that moves what you'll actually run.
Both vendors shipped an official agent SDK, so the choice looks like a feature bake-off. It isn't. They sit at different layers and bet on different hard parts — and their defaults decide which one your problem is one line of code away from.
Anthropic tried to give programmatic Claude usage its own bill, then reversed it on the day it was due. The retreat doesn't fix the problem it exposed.
Four open-weight MoE models now run real agents. The headline parameter counts are nearly decorative — pick by active params and post-training, not by the leaderboard screenshot.
The best open VLM for an agent isn't the one that scores highest on MMMU. It's the one that can hand back an accurate click coordinate — and those are not the same models.
OpenAI now ships three ways to call its models — but one of them has a death date. Here is how to choose, and the one reason reasoning models behave better on the newest surface.
Agents don't run on chatbot leaderboards. The model that wins your tool loop is decided by function-calling reliability, agentic benchmarks, and an "agent tax" the headline price hides.
Three clouds rent you the same frontier models. The thing that actually locks you in is the agent runtime wrapped around them, and most teams pick it by accident.
A frontier model on every node is the default, not the optimum. Most agent calls are narrow, repetitive, and format-constrained — exactly the shape a small model was built for.
The benchmark you compare on today expires in three weeks. The license you build on doesn't. Pick an open-weight family the way it will still matter next quarter — by what you're allowed to do with it, and what it costs to serve.
An MoE model computes like a small model and remembers like a giant one. That split is great for a token factory and a trap for a single self-hosted agent.
The open-versus-closed debate in agents is framed as a fight over frameworks — but the real leverage moved to a layer where the distinction barely applies.