Industries · publishers & content sites
The bots you block would pay to read. Let them in, and show them who they are paying.
Machine readers are traffic that earns nothing today. Paid access turns them into revenue the way human readers turn into advertising, and verification is what keeps them coming back.
The bind
Crawlers and agents already read your content. Blocking them protects nothing you can sell; letting them in for free gives it away. Per-request payment is the third option, and it is arriving on rails that already exist.
A machine decides what to pay by policy, not by a reputation it has read about. An endpoint nobody can vouch for gets throttled, deprioritised or skipped, and you never see the sale you lost.
What changes
- A verified status any bot can check for free before paying: an accountable, verified operator stands behind this endpoint, with a guarantee deposit behind it.
- No custody of personal data and no signup for the reader. The attestation ties your payTo address and resource URLs to your issuer's signature.
- Nothing new in your paywall. The middleware decorates the 402 responses you already send, and a reader that cannot check the verdict simply proceeds as before.
The trust perimeter
Attested vendors invite their agents. Every 402 you send can carry it: an accountable operator stands behind this endpoint, verified for free at any time, and agents can join the perimeter too once agent attestation opens with v1. Reading who is inside is free to everyone.
Selling over x402? Let's find out if we fit.
We are onboarding our first partners: API sellers, publishers, marketplaces and regulated platforms.