Your agent just got past the paywall —legally.
When your browser-agent hits a 402, xpay✦ settles the payment and the session resumes. No CAPTCHA workarounds. No proxy fleets. No "give up and try a different site." One account, 1,000+ publishers, every paywall handled.
The publishers you want are blocking you.
A growing share of quality publishers now block AI bots at the gateway. Scraping harder doesn't fix it. Bilateral licensing doesn't scale. Common Crawl is months stale.
Paywalls kill your task completion rate
Your agent navigates to a research page and hits a "subscribe to read" wall. Task fails. User complains. Your evals tank.
Cloudflare 403s on every other request
Anti-bot detection treats your headless Chrome as a scraper. You spend more time on stealth plugins than on agent logic.
The good content lives behind gateways.
High-quality publishers gate their content for a reason — to be paid. Your agent's task completion rate drops every time it hits one. Bilateral licensing isn't an option at startup scale. Scraping harder doesn't fix the gate.
xpay✦ is the legitimate way in.
Publishers in our network actively chose to be paid via xpay — including ones that block every other AI agent at the gateway. You pay what content's worth. You get the content. Everybody wins.
402 → settle → resume, automatically
When the agent hits HTTP 402 on any xpay-enabled site, the SDK settles the micropayment and the page loads. No code branches, no manual retry.
One wallet, every publisher
Stop maintaining 50 scraping account credentials. One xpay wallet pays any publisher in the network. Spend caps and per-domain limits built in.
Whitelisted at the WAF.
Publishers in our network whitelist xpay traffic at the gateway. No CAPTCHA. No anti-bot retries. Your agent walks straight in — and every settlement produces a receipt your lawyers will love anyway.
Three lines. Ship Tuesday.
Native SDKs across the agent stack. Drop in xpay where you already retrieve.
import { Stagehand } from '@browserbasehq/stagehand';
import { withXpay } from '@xpay/browser';
const stagehand = withXpay(new Stagehand(), {
wallet,
maxCostPerSession: 5.00,
});
await stagehand.page.goto('https://wsj.com/article/...');
// If the page returns 402, xpay handles the settlement.
// stagehand.page now sees the unlocked content.Live in five minutes.
01
Get an API key
Sign up at app.xpay.sh, fund a wallet (USDC on Base), get your API key. New accounts ship with $50 in free credits.
02
Drop in the retriever
Three lines of code. Native SDKs for LangChain, LlamaIndex, CrewAI, Stagehand, Playwright. Or hit the REST API directly with x402 headers.
03
Get licensed content + receipts
Each query returns the document, publisher attribution, and a settlement receipt. Pay only for what you actually retrieve. Cap spend per project, per user, per domain.
Built for agents like these
Browser-use frameworks
Browser Use, Stagehand, SkyvernBrowser-as-a-service
Browserbase, Hyperbrowser, Steel.dev, Anchor BrowserComputer-use agents
Claude computer-use, Multion, Adept-styleStop scraping.Start accessing.
Pay-per-query access to 1,000+ publishers — including the mid-tier sites blocking every other AI agent. One API key. Receipts by default.
Self-serve · $50 free credits · No BD calls · No MSA requiredOr browse the publisher catalogBrowser Agents — FAQ
Common questions from agent builders evaluating xpay
Most of the mid-tier ad-monetized publishers in our network actively gate their content (paywalls, WAF blocks, robots.txt). They joined xpay specifically to be paid for AI access — and they whitelist xpay traffic at the gateway. You reach them; you cannot reach them with stealth plugins, residential proxies, or browser farms.
Our SDK attaches a request interceptor. When a response comes back with HTTP 402 and an x402 challenge, the SDK signs a payment, replays the request, and returns the unlocked content to the page. The agent never sees the paywall.
Today, only xpay-network publishers (1,000+ and growing). For non-network sites, the SDK is a no-op. We're actively recruiting publishers to expand coverage — request specific domains and we'll prioritize.
No. Publishers in our network whitelist xpay traffic at the WAF layer — a paid 402 settlement is a first-party authorized request. No CAPTCHA. No anti-bot retries. No proxy farms.
Per-session, per-domain, and per-wallet caps. Hit the cap and the next 402 fails open (you choose: skip the page or surface the error to the user).
Yes. Native wrappers for Stagehand, Browserbase Sessions, Browser Use, and raw Playwright. Drop-in replacements with three extra lines.
Other use cases
Explore xpay for other agent flavors.
Browse the publisher catalog
Browse 4,930+ publishers by vertical, language, country, or AI-bot blocking status.