Reach the long tailyour bilateral deals don't cover.
The long-tail publishers your AI tools actually need — trade press, niche sites, regional outlets — block your bots and aren't covered by your bilateral deals with Westlaw, Bloomberg, or FactSet. xpay✦ is the layer that reaches them: one MSA, one invoice, one audit trail, 1,000+ publishers.
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.
Bilateral licensing doesn't cover the long tail.
You signed Westlaw and Bloomberg. The trade press, niche industry blogs, and regional outlets your AI tools actually need? Still scraped, still blocked, still gray-zone — and growing larger every quarter.
Every AI initiative re-litigates content sourcing.
Marketing wants Jasper. Legal wants Harvey. Research wants Hebbia. Each vendor has its own sourcing story. Your CISO has the same conversation five times.
Procurement hates per-vendor billing.
Five AI tools, five sourcing contracts, five invoice flows. Finance asks why. AP asks again next quarter.
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.
One MSA reaches the long tail.
Your existing bilateral deals continue. xpay covers the 1,000+ publishers you can't reasonably negotiate with directly — including the ones blocking your bots today.
Audit logs your CISO will sign off on.
Per-query attribution, content hashes, settlement receipts. Pipe to your SIEM (Splunk, Datadog, S3 + Athena). Compliance-ready by default.
Single invoice, project-level chargeback.
Tag spend by project, business unit, or AI tool. One xpay invoice, clean chargeback to internal cost centers.
Three lines. Ship Tuesday.
Native SDKs across the agent stack. Drop in xpay where you already retrieve.
import { EnterpriseClient } from '@xpay/enterprise';
const client = new EnterpriseClient({
orgId: 'acme-corp',
ssoToken,
auditLogSink: 'splunk://acme-siem',
costCenter: 'marketing-ai',
});
// Same SDK across every internal AI tool.
const docs = await client.retrieve({ query, maxCost: 1.00 });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
Internal AI assistants
F500 marketing, legal, research, commsAI platform vendors
Glean, Sana, Writer Enterprise, Microsoft Copilot extensionsConsulting & advisory AI
McKinsey/BCG-style internal research agentsStop 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 catalogEnterprise AI — FAQ
Common questions from agent builders evaluating xpay
Trade press, niche industry blogs, regional outlets, mid-tier ad-monetized publishers across every vertical your internal AI tools actually touch. Most of them block AI bots elsewhere and aren't covered by Westlaw, Bloomberg, FactSet, or your other bilateral programs. xpay is the single MSA that reaches all of them.
They are independent. Continue Westlaw, Bloomberg, FactSet, Reuters as-is for the marquee names. Use xpay for the long-tail publishers your AI tools actually touch but you don't have — and won't reasonably get — direct deals with.
Yes. Enterprise plans typically start at $10K/month commit with volume discounts and dedicated support. Custom MSA available.
SAML / OIDC SSO. SCIM provisioning. Role-based access (admin, builder, viewer). Per-user spend caps.
Stream to your SIEM (Splunk, Datadog, S3 + Athena, custom HTTPS sink). Per-query metadata: timestamp, publisher, content hash, amount, requesting project. Content payloads not stored by xpay.
Typical: 2-4 weeks. Security review, MSA red-line, SSO setup, audit-log integration. Sales can provide SOC2 report, DPIA template, and standard MSA.
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.