Get paid every time AI uses your content.
Setting up is easy and fast, with full auditable control of all site configurations and licensing preferences at every stage. OpenRSL lets you call the shots in stopping misuse and turning your website’s AI-driven traffic into recurring usage revenue.
Drop an OpenRSL library into your stack, set your terms, and let crawlers pay for what they take. No invoices, no chasing, no contracts to sign one by one.
Or, use the PDS PropertyRightsRSL™ plugin toolkit, a commercial implementation of OpenRSL that uses PDS and Stripe for licensing and settlement. Publishers can install the turnkey plugins instantly on compatible sites:
OpenRSL gates your content behind the licensing requirements you stipulate for each asset. Make money for every retrieval, training usage, citation, and user engagement events where AI tool workflows need access to your website.
You publish terms
OpenRSL generates your rsl.xml and points robots.txt at it — your prices and allowed uses, on the public record.
A crawler discovers
An AI crawler reads robots.txt, finds your rsl.xml, and sees exactly what it may use and at what price.
License & pay
It accepts your terms; the OLP server issues a signed license ticket and holds payment for the intended use.
You get paid
Your content is served against the ticket, funds settle to you, and a signed receipt lands in your audit log.
Three steps.
The plugin generates your rsl.xml, points robots.txt at it, and connects payouts. From there, every license is recorded automatically.
1. Install
Drop in the OpenRSL library for your stack (PHP, Python, or TypeScript) and it scaffolds your license file at /rsl.xml.
2. Set terms
Choose which AI uses you allow: train, summarize, cite, or inference. Set a price per request, per token, or per article.
3. Connect payouts
A pluggable payments layer handles the money. Stripe is supported out of the box, and you can wire in any provider you run.
Your content stays where it is. Your URLs stay where they are. OpenRSL adds a license, a record, and a settlement path. That is all.
A signed receipt for every use. An auditable log you can hand to a lawyer or a regulator. A revenue line that did not exist last year.
You set the price.
Use flexible OpenRSL tools to declare your terms in rsl.xml (public and machine-readable), then crawlers pay what you declared.
Aligned with training use, where the volume of text consumed is the relevant unit.
For crawling and inference use, where each query is a discrete event regardless of response length.
A flat fee per article accessed under a given license type. Simplifies pricing for archives and single-piece licensing.
Common questions.
How does payout work?
The payment layer is pluggable. Settlement runs through whichever provider you configure: Stripe ships built in, or implement the provider interface for your own backend.
Do I need to change my existing site structure?
No. rsl.xml sits at a known path. Your URLs, CMS, and publishing workflow stay the same.
Is the standard open?
Yes. RSL is an open standard. OpenRSL is the open-source reference implementation. Anyone can implement it independently.
