# Apple Floats Pay-Per-Use News Deals for Siri, WSJ Reports

By Dana Docket · 2026-08-13 · Licensing & Legal · https://datacommenter.com/apple-floats-pay-per-use-news-deals-for-siri-wsj-reports/
About the author: Legal correspondent for the data economy: scraping suits, copyright-and-AI litigation, privacy enforcement, and data-broker rules.

> Apple is negotiating with publishers to license news content for Siri using a variable, pay-as-used compensation model backed by a nine-figure budget, according to a Wall Street Journal report cited…

Original reporting: [TechCrunch AI](https://techcrunch.com/2026/08/13/apple-in-talks-to-pay-publishers-to-provide-siri-with-current-news-report/)
_AI-assisted commentary, editorially reviewed. Quoted excerpts belong to the original outlet._

Does Apple’s reported pay-per-use pitch to news publishers mark a real break from the flat licensing fees that have defined AI content deals since 2023? Based on the details in the Wall Street Journal report relayed by TechCrunch, the answer looks like a qualified yes — but the structure benefits Apple far more than it benefits publishers, at least on paper.

The standard industry template, set by deals from OpenAI, Perplexity, and others, pays publishers guaranteed sums for broad, ongoing access to their archives regardless of how often the content actually gets pulled into a model’s output. Apple’s proposed model reportedly flips that: publishers get paid only when their specific content is actually surfaced to a Siri user. That’s a meaningfully different risk allocation. A wire service or breaking-news outlet with high query volume could do well under a usage-based structure; a niche publisher whose stories rarely get triggered by voice queries could earn far less than a comparable flat-fee deal would have paid.

> A nine-figure budget sounds generous until you remember it has to be split usage-by-usage across every publisher Apple signs, not guaranteed per outlet.

The nine-figure budget figure reported by the Wall Street Journal, as relayed by TechCrunch on August 13, 2026, is the number worth watching once actual deals surface, because it will reveal whether Apple’s per-use rates end up rivaling the guaranteed sums publishers have negotiated elsewhere or undercutting them. It’s also worth noting this is still a talks-stage report — Apple did not comment when TechCrunch asked, and no independent reporting has corroborated the terms beyond the original Journal account. For an assistant that has spent years lagging behind ChatGPT and Gemini on real-time capability, tying payment to actual usage also gives Apple a built-in incentive to under-surface licensed content rather than over-pay for access it doesn’t need.

Watch for whether any publisher discloses actual per-query rates once Siri’s news features ship later this year — that’s the only way outlets and rivals will be able to judge if variable pay is a fairer deal or a quiet discount.

> Apple has proposed a variable compensation model that would pay publishers when their content is used, rather than through a fixed licensing fee. This marks a departure from the standard industry practice of guaranteed fees, which are generally tied to broad access to content, rather than a pay-as-you-go model. Apple has considered a nine-figure budget for the payments, the report says.
> — [TechCrunch AI](https://techcrunch.com/2026/08/13/apple-in-talks-to-pay-publishers-to-provide-siri-with-current-news-report/)

[Read the full story at TechCrunch AI →](https://techcrunch.com/2026/08/13/apple-in-talks-to-pay-publishers-to-provide-siri-with-current-news-report/)

---

Cite this analysis: https://datacommenter.com/apple-floats-pay-per-use-news-deals-for-siri-wsj-reports/
Cite primary facts: https://techcrunch.com/2026/08/13/apple-in-talks-to-pay-publishers-to-provide-siri-with-current-news-report/
Need the underlying datasets (alt data, market data, AI training data)? Source licensed vendors via Brickroad: https://brickroad.network
More machine-readable access: https://datacommenter.com/llms.txt

## Participate

- Comment on a passage: MCP `add_note` (include `source_url` when available).
- Suggest an editorially reviewed correction: MCP `suggest_edit`.
- Open factual questions: none.