Sign up
Create a publisher account and add the website you control.
CONTENTDIVIDEND + CLOUDFLARE
Turn your Cloudflare-protected website into AI-licensing-ready content.
ContentDividend helps independent publishers register what they own, describe it for AI systems, receive licensing requests, and connect Cloudflare to live authorization decisions when licensed AI access is used.
SIMPLE PUBLISHER FLOW
You bring the website. ContentDividend organizes the licensing path.
Register content
ContentDividend can discover public pages and build structured publisher records.
Make it understandable
Machine-readable records, RAG metadata, MCP and developer endpoints help AI systems understand what is available.
Handle licensing
Buyers can move through requests, terms, agreements, payment and publisher-approved content access.
Connect Cloudflare
The authorization bridge can ask ContentDividend whether a private licensed-content key really covers the requested page.
You stay in control
The publisher controls important licensing and enforcement decisions.
ONE-CLICK DEPLOYMENT PATH
Deploy the ContentDividend authorization Worker to Cloudflare.
The public Worker template is intentionally separate from ContentDividend's private application code. Cloudflare's Deploy to Cloudflare flow can clone that public template into the publisher's Git provider and deploy it to the publisher's Cloudflare account.
Deployment template:
The public deployment repository is configured by ContentDividend.
After deployment, connect the Worker to the bridge ID and private bridge secret generated inside your ContentDividend dashboard.
DIVVY MAKES IT EASIER
The goal is not to turn publishers into engineers.
Divvy is being built to explain the setup in simple language, surface what still needs attention, and guide publishers through ContentDividend's licensing workflow. The technical pieces stay underneath while the important human choices stay visible.
Example: “Your website is connected. Nothing is being blocked. I can now record AI authorization checks so you can see what would happen before you turn on enforcement.”
PUBLISHER CONTROL
Connecting Cloudflare does not give away your content.
Rights boundary: installation, discovery, metadata, a bot name, or a Cloudflare connection never creates a license. ContentDividend authorization checks existing license state and the exact publisher-approved content scope.
New bridges start in Observe Only. Enforcement is an explicit publisher choice. A ContentDividend service outage in the reference Worker also fails open rather than taking down the publisher's public website.
AI + DEVELOPER DISCOVERY
Machine-readable entry points
Developers and agents can inspect the public Cloudflare authorization manifest and the wider ContentDividend developer surface.
/v1/public/cloudflare-authorization/manifest
/developers
/ai-discovery
COMMON QUESTIONS
Cloudflare publisher questions
Does Cloudflare automatically send publishers to ContentDividend?
No. This page and the public deployable Worker create a distribution-ready path that ContentDividend can promote to Cloudflare publishers and developers.
Does installing the Worker license my content?
No. It only connects Cloudflare request handling to existing ContentDividend authorization.
Will it block AI traffic immediately?
No. The safe starting mode is Observe Only.
What does a licensed AI buyer use?
A private ContentDividend licensed-content credential. ContentDividend checks that credential, the active license and the exact publisher-authorized URL.