No scheme's public documents offer the points below.
The scorecard in the article FORA resources
Based on the scorecard rows "Who counts", "Is the split rule published?" and the statements under #adds-statements, across the eight schemes.
In the six schemes that say how use is counted, the AI company reports its own use, the operator or the licensee counts it, or no one counts per use; CCC and CLA haven't said for AI.
The AI System sends the ILC Platform the licensing payment and a usage reporting file that includes its aggregated use of the publisher’s licensed content.
Publisher Onboarding Guide Internet Licensing Collective "How ILC licensing works"
Basis: the scorecard row "Who counts the use your share rests on?" (#sc-counts-ilc to #sc-counts-ndp). ILC: the AI company. ProRata and DPCMO: ProRata's engine. Perplexity: its own traffic. NDP: TNO, the licensee. Kopinor: a lump sum.
On FORA, every fetch is a transaction for one URL; the operator's Exchange signs the offer, and the AI company signs its acceptance.
The agent's detached acceptance signature over this item's `offer`.
Protocol reference: FORA v1 FORA documentation TransactionItem.agent_acceptance
The Exchange's signature covers the entire offer (Offer.signature, #journey-counted-fora).
The schemes' public terms offer at most an audit or a dispute right.
Partner may request to have an independent third party confidentially inspect the Records if it reasonably disputes Revenue Share paid under this Agreement.
ProRata Online Master Services Agreement (MSA) ProRata.ai §6
ProRata allows an inspection in a dispute; ILC says it "supports auditing of license compliance" (publishers page); CLA's general method includes "usage audits". No scheme describes checking each report against a record it didn't get from the payer.
On FORA, the operator reconciles each AI company's report with the fetch records before it splits the pool.
The agent reports what it consumed, not what it estimated: an Exchange MUST NOT refuse a report because this differs from the estimate, in either direction.
Protocol reference: FORA v1 FORA documentation UsageReport.consumed_quantity
The protocol binds each report to its transaction; the reconciliation is the operator's job in the article's design.
Seven of the eight don't publish enough to redo the sum.
Detailed calculations and technical implementation procedures are established in the Allocation Rules and are not publicly disclosed.
ILC Royalty Distribution Policy, shown in ILC's publisher portal Internet Licensing Collective §1 no public URL
Basis: the scorecard row "Is the split rule published?" (#sc-split-ilc to #sc-split-ndp).
GPT-NL publishes its rule; its public documents don't say whether a contributor gets the token counts and quality scores the sum needs.
The share that a Content Contributor can expect is proportionate to the Data Value of the individual dataset as a relative percentage of the Data Value of the Prepared Dataset.
Annex 6: Revenue Sharing Mechanism TNO, GPT-NL §2.1
The rule is published (#sc-split-ndp). Absence: no contributor statement or report of token counts and scores was found; the agreement itself is confidential (template §11).
On FORA, your statement gives your weight, the total weight, the pool, the operator's cut and the version of the rule.
FORA project statement FORA project no public URL
The article's design for the operator's statement.
ProRata sends monthly statements down to the article; ILC sends periodic ones and makes them confidential; none promises data per fetch.
ProRata will deliver to Partner (including by making available to partner a web-based access to the information) a statement of Partner Revenue Share for the preceding month
ProRata Online Master Services Agreement (MSA) ProRata.ai §6, "Reporting"
ProRata's statement goes to "Partner-level", publication and article detail. ILC: "ILC shall provide Publisher with periodic royalty statements through the Platform" (§4.1), and statements are "confidential information of ILC" (§7.5). "None promises data per fetch" is an absence across the eight.
On FORA, you see each of your transactions, and the report filed against it, as it arrives.
REQUIRED. Hex-encoded detached Ed25519 signature over the canonical serialization of the ENTIRE Offer — every field, including `pricing`, `terms` (the full licensing payload), `expires_at`, and `exchange`.
Protocol reference: FORA v1 FORA documentation Offer.signature
The protocol creates a record per transaction; showing it to the publisher as it arrives is the operator's dashboard in the article's design.
Your own priced terms beside the pool's: join the pool with one term for everything, or a term per section and per use; terms you price yourself run next to it, and the same fetch records back both.
A resource carries zero or more `LicenseTerm` entries, at most 32. Each term is a complete, self-contained access arrangement, and a resource with several terms is the normal case.
Licensing terms FORA documentation "Overview"
A record proves the fetch; what a model did with the page afterward comes from the AI company's report, and an audit checks it.
REQUIRED. Hex-encoded detached Ed25519 signature over the canonical serialization of the ENTIRE Offer — every field, including `pricing`, `terms` (the full licensing payload), `expires_at`, and `exchange`.
Protocol reference: FORA v1 FORA documentation Offer.signature
The signatures cover what was offered and accepted for one fetch. Use inside the model leaves no record outside the AI company.