Reach the brand-name publishersyour scraper can't.
The trusted, ad-monetized, brand-name publishers your enterprise customers want sourced — the ones that make outputs feel "researched, not generated" — block AI bots by default. xpay✦ is the drop-in retriever that reaches them: pay-per-query, full attribution, receipts as evidence.
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.
Brand-name sources are blocked.
The Tier-1 publishers your enterprise customer wants you to cite — Reuters, WSJ, Bloomberg-tier — block AI bots by default. Without paid access, your output reads like the rest of the AI slop.
Plagiarism risk on every output.
Your model paraphrases scraped content. Customer publishes. Original publisher's lawyer sends a letter. Your contract has indemnification clauses.
Stale training data = stale outputs.
Customers want copy that references this week's news, this quarter's earnings, today's product launches. Your model knows 2024.
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.
Reach Tier-1 publishers.
xpay✦ unlocks publishers your scraper literally cannot fetch — the ones whose name on a citation actually means something to your enterprise customer.
Drop-in retriever, three lines.
Add xpay✦ as a retrieval source in your existing chain — Anthropic, OpenAI, your own model. No infra rebuild.
Brand-safety filters per customer.
Allow-list publishers per workspace. Enterprise customer wants only Tier-1 sources? Configure it. No code changes per tenant.
Three lines. Ship Tuesday.
Native SDKs across the agent stack. Drop in xpay where you already retrieve.
import { XpayRetriever } from '@xpay/sdk';
const retriever = new XpayRetriever({
wallet,
allowList: ['reuters.com', 'wsj.com', 'bloomberg.com'],
maxCostPerGeneration: 0.50,
});
const sources = await retriever.fetch(brief);
const draft = await llm.complete({
prompt: buildPrompt(brief, sources),
});
// draft.citations are real, paid, traceable URLs.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
AI writing platforms
Jasper, Copy.ai, Writer.com, AnywordMarketing content tools
Brand-safe content generation at scaleInternal enterprise content
F500 marketing/comms AI assistantsStop 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 catalogAI Writing Tools — FAQ
Common questions from agent builders evaluating xpay
Most of the brand-name, ad-monetized, professionally-edited publishers your enterprise customer wants cited block AI bots by default. They joined xpay specifically to be paid for AI access — and they whitelist xpay traffic at the WAF. You reach them through xpay; you cannot reach them by scraping.
Outputs grounded in licensed, retrieved sources have citations. Citations create a paper trail — your customer can show "this draft was informed by these paid sources" rather than "the model invented it." Insurers and legal teams treat the two very differently.
Yes. Per-workspace configuration. Tier-1-only for the bank, broad allow for the media agency. Same code path.
Up to you. Most platforms absorb at $0.05-$0.15 per generation as part of their margin; some surface it as an "enterprise sourcing" upsell. We provide per-query receipts so you can pass-through cleanly if you choose.
Yes. xpay is the retrieval layer, not the generation layer. Compose with OpenAI, Anthropic, your own fine-tuned model — the source documents flow into your prompt as you already do RAG.
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.