AI keeps reading. Start charging.
ChatGPT, Claude, Perplexity and a long tail of agents lift your content every day and never pay you back. xpay turns every machine fetch into revenue — without blocking the bots that still send you readers, and without anything your human audience ever sees.
Per-query pricing · Weekly settlement · Edge gate, no CDN swap.ChatGPT-User
PerplexityBot
ClaudeBot
Googlebot
unknown-scraper-04
A pricing layer for machine traffic.
Revenue per machine fetch
Every legitimate agent request to your content gets a price. Quote, pay, fetch. Bots that won’t pay are politely declined — and the ones that send you readers still get through.
Drop-in, no CDN swap
A single edge handler in front of your site — or the WordPress plugin — adds the payment challenge. No theme migration, no paywall pop-up, nothing your human readers ever see.
You set the rules
Allow-list the bots that still drive referral traffic. Charge the ones that summarise. Block the ones that won’t identify. xpay is the layer; your policy is yours.
Charge the agents that don't cite you.
xpay segments machine traffic into three default lanes. Promote and demote bots between lanes any time — these are your defaults, not your jail.
Summarisation crawlers
ChatGPT, Claude, Perplexity, Gemini and the long tail of summarisation bots. They lift your content into an answer; the reader never clicks. This is where the money is.
Search-engine crawlers
Googlebot, Bingbot, classic crawlers that still send you click-through traffic. Default policy is allow — your call to flip it if your referral mix changes.
Unknown / unidentified
Bots that refuse to identify, refuse to pay, and don’t bring readers. Default policy is block. xpay surfaces fingerprints so you can graduate them into a tier if they earn it.
Four steps, one afternoon.
The gate goes in front of your site as an edge handler or via the WordPress plugin. Machine requests hit it; human page loads pass straight through.
Connect your site
Five-minute onboard at app.xpay.sh/onboard/publisher. We mint a site_id and discover which agents are already hitting you.
Set your price
Pick a per-fetch price (or per-1k-tokens). Different prices for different bots — premium tier for the ones that actually buy.
Install the gate
Add the edge handler (or the WordPress plugin). Machine requests get a payment challenge; human page loads are untouched.
Get paid per fetch
Compliant agents pay, fetch, cite. Live dashboard shows which agents paid for what content, settlement on a weekly cadence.
Start charging in five minutes.
Onboard mints your site_id, discovers which agents are hitting you, and proposes a starting price. Flip the gate on when you're ready.
# Cloudflare Worker / Vercel Edge
import { gateAgents } from '@xpay/edge-gate';
export default gateAgents({ siteId: '…' });Charging AI agents, in plain English
Quick answers for publishers whose content feeds the answer engines.
No. Googlebot, Bingbot and the classic search crawlers default to the allow lane — the same lane they’re in today. The charge lane targets summarisation and answer-engine crawlers that lift your content without sending the click. You can change the policy on any lane any time.
xpay sits in front of your site as an edge handler (or the WordPress plugin). Agents that announce themselves get matched against your policy. Agents that disguise themselves get fingerprinted (TLS, header order, request pattern) and routed to your default-unknown policy.
The compliant ones do — Anthropic, OpenAI and others have already shipped the buyer-side primitives needed to settle a 402 challenge. The long tail of agents pays via stablecoin rails. Non-compliant bots get declined; that loss to you is zero, because they weren’t paying you anyway.
Same shape, different defaults: xpay is publisher-first, not CDN-first. You don’t have to move your site behind a specific CDN, you set your own per-bot pricing, and the agentic-commerce rail (storefront) stacks on top from the same onboard.
Weekly settlement, fiat or stablecoin. The dashboard shows per-agent revenue, per-content-type revenue, and which articles are getting lifted most often. Connect Stripe / a bank account / a wallet at onboard.
Yes — that’s the point. One onboard, one dashboard, two rails. Charge AI agents for the crawl, and earn affiliate / first-party revenue when your readers convert on the recommendations. They don’t overlap.