Use case
Publishers or site operators, upon detecting AI crawlers bulk-fetching original pages, must decide whether to allow or block and turn crawl volume into per-page USDC billing records chargeable to the crawler.
robots.txt, paywalls, anti-bot services such as Cloudflare, and manual licensing contracts.
The old approach is blanket robots.txt rules or manual licensing talks; crawl volume cannot be metered per page, so content owners neither get paid nor can quantify usage.
xOcto's call
Demand is evidenced
Trend: a settlement layer between model crawlers and content owners is being carved out as its own product. Entry: start with news media and vertical content sites that hold copyrighted material and are already negotiating licensing terms with model vendors, selling per-page billing plus auditable statements rather than another anti-crawl plugin; pricing is undisclosed and not invented.
Reason to use it
Why users would choose it
Inference: versus blanket blocking or manual negotiation, it records each crawl directly as a per-page USDC charge, removing the post-hoc counting and reconciliation step, so content owners already negotiating with model vendors would try it first.
Where the easy answer breaks down
The tension worth following
An English validation note will follow from the public evidence.
If this is your job
Worth trying. Inference: versus blanket blocking or manual negotiation, it records each crawl directly as a per-page USDC charge, removing the post-hoc counting and reconciliation step, so content owners already negotiating with model vendors would try it first.
Entry and what to borrow
Trend: a settlement layer between model crawlers and content owners is being carved out as its own product. Entry: start with news media and vertical content sites that hold copyrighted material and are already negotiating licensing terms with model vendors, selling per-page billing plus auditable statements rather than another anti-crawl plugin; pricing is undisclosed and not invented.