ContentDividend
ContentDividend Developers & AI Rights Adapters
Have more than 100 pages? Upgrade to Pro for only $9.99/mo for unlimited pages.
Upgrade to Pro →
← Developer Portal
Phase F · Step 5

One publisher policy, multiple interoperable rights surfaces.

The Unified Rights Adapter Layer converts explicit publisher choices and existing ContentDividend records into machine-readable outputs without replacing RSL, URVP, Cloudflare controls, licensing agreements, or publisher ownership.

Conservative by design: ContentDividend does not infer Content Signals from edge blocking. Search, AI-input and AI-training signals must be explicitly selected by the publisher.

Rights Passport

The F4 passport stays the canonical discovery identity. F5 points external adapters back to it.

RSL / OLP

Published RSL remains authoritative. F5 advertises it but does not rewrite or silently republish publisher RSL.

CoMP v1

Publishers can expose a CoMP-aligned package metadata adapter that points to licensing terms and protected retrieval. ContentDividend does not claim IAB certification and the adapter does not create commercial terms.

Cloudflare Content Signals

Generate explicit search, ai-input and ai-train directives plus the optional content-use value where selected. Technical blocking remains separate from commercial permission.

robots.txt & llms.txt

Generate copy-ready snippets that advertise the Rights Passport, licensing manifest, URVP and RSL where available.

WordPress

The generic WordPress adapter can publish rights discovery links and append the publisher's current ContentDividend robots snippet without storing ContentDividend buyer credentials.

Machine discovery

GET /.well-known/contentdividend-rights-adapters.json GET /v1/public/sites/{site_id}/rights-adapters.json GET /v1/public/sites/{site_id}/adapters/comp.json GET /v1/public/sites/{site_id}/adapters/robots.txt GET /v1/public/sites/{site_id}/adapters/llms.txt

External-service boundary

F5 generates interoperable profiles and installation artifacts. It does not silently change a publisher's Cloudflare account and it does not claim a direct TollBit API synchronization that has not been configured through a supported partner interface.