xpay primary sources — 2026-05-03

Project status in this pass

• No canonical standalone xpay whitepaper or litepaper surfaced.
• The clearest current source of truth is the official xpay site, the docs llms.txt, the product docs, and the developer-resources pages.
• xpay is best understood as an agentic-commerce marketplace and payment-control layer spanning content licensing, tool access, spend governance, and monetization.

Primary-source snapshots

1) Official site / core positioning

• URL: https://www.xpay.sh/
• Key excerpt:
  • The official site describes xpay as a “two-sided MCP-native marketplace and payment layer.”
  • It says publishers can license content to AI agents through AgentFeed, while agent builders get pay-per-use access to 5,000+ publishers and 1,000+ API tools through one account.
  • It also says Smart Proxy adds spending controls so autonomous agents “never overspend,” and frames xpay as protocol-agnostic across MCP, MPP, x402, cards, stablecoins, and REST.

2) Docs llms.txt / platform map

• URL: https://docs.xpay.sh/llms.txt
• Key excerpt:
  • The docs file calls xpay an “AI Agent Payment Control Platform” and explicitly says it provides non-custodial spending controls and API monetization via x402.
  • It lists xpay Tools, Smart Proxy, Paywall-as-a-Service, MCP Monetization, and the xpay facilitator as connected products in one stack.
  • It also states the technical base layer is USDC on Base and points to the public facilitator endpoints.

3) xpay Tools / aggregated MCP access

• URL: https://docs.xpay.sh/en/tools
• Key excerpt:
  • The Tools docs say xpay offers “1000+ pay-per-use AI tools” with “one API key, any MCP client.”
  • They describe three access patterns: a master server with meta-tools for search and execution, collection servers for curated subsets, and provider servers for direct provider-specific tools.
  • This is a useful clue that xpay is packaging discovery and execution orchestration, not just payment collection.

4) Smart Proxy / spend governance layer

• URL: https://docs.xpay.sh/en/products/smart-proxy
• Key excerpt:
  • The Smart Proxy docs say the product sits between agents and x402-powered APIs to prevent runaway spending.
  • The page lists hard spending limits, daily and monthly budgets, per-agent controls, anomaly detection, alerting, emergency shutoffs, and allowlist/routing configuration.
  • This is a strong sign that governance and budget enforcement are core product layers rather than ancillary dashboard features.

5) MCP Monetization / zero-code proxy wrapping

• URL: https://docs.xpay.sh/en/products/mcp-monetization
• Key excerpt:
  • The MCP Monetization docs say users can wrap any MCP server with an xpay proxy “with zero code changes.”
  • They describe per-tool pricing, Base-USDC payouts, xpay-issued proxy URLs, API-key-based buyer authentication, and billing metadata returned alongside tool responses.
  • This shows xpay is trying to monetize existing tool surfaces without requiring operators to rebuild their servers around a new payment system.

6) Developer resources / SDK and ecosystem footprint

• URL: https://docs.xpay.sh/en/developer-resources
• Key excerpt:
  • The developer-resources page lists @xpaysh/agent-kit, CLI tooling, analytics/debug tools, and several open-source x402 ecosystem projects including awesome-x402, x402-agent-kit, x402-local, and x402-sdk.
  • Example code covers both protected agent fetch flows and seller-side paywall middleware.
  • This broad tooling surface reinforces that xpay is acting as an operating layer around machine-paid access, not merely a hosted marketplace page.

Working conclusion

xpay is best cataloged as an agentic-commerce marketplace and payment-control plane. The deciding evidence in this pass was the repeated combination of publisher licensing, tool aggregation, one-key MCP access, proxy-based monetization, per-agent spending controls, and protocol-agnostic routing across several payment and integration rails.