xpay

• Name: xpay
• URL: https://www.xpay.sh/
• Category: agent-commerce proxy / marketplace wrapper / spend-governance middleware
• Tags: ethereum-ecosystem
• Summary: xpay is proxy policy and marketplace packaging around paid agent tools. Smart Proxy is the real note: budgets, route rewrites, tool admission, and payout interception under one operator. Useful glue, not a payment rail.
• What it does:
  • Runs AgentFeed, a publisher marketplace where agents can license content through MCP-native query endpoints
  • Runs xpay Tools, a paid tool shelf exposed through master, collection, and provider-specific MCP endpoints
  • Inserts Smart Proxy between agents and paid APIs to enforce per-request, daily, monthly, per-agent, and allowlist-based spending rules
  • Wraps existing APIs or MCP servers with Paywall-as-a-Service and MCP Monetization so operators can price tools and route payouts through xpay proxy URLs
  • Operates an x402 facilitator on Base while marketing the broader stack as protocol-agnostic across MCP, MPP, x402, cards, stablecoins, and REST fallbacks
  • Ships developer tooling such as @xpaysh/agent-kit, CLI flows, local x402 tools, and related open-source projects
• Key claims:
  • xpay is mostly a proxy-policy note. The marketplace shelf matters, but Smart Proxy is the choke point.
  • The leverage sits in budgets, allowlists, route rewrites, tool admission, anomaly handling, and payout routing behind the proxy.
  • The zero-code MCP monetization pitch matters because xpay wants to sit in front of other people’s tools, not merely sell its own endpoints.
  • The protocol-agnostic language still outruns the clearest live surface; today this is mainly Base/x402-era operator packaging with marketplace gloss.
• Whitepaper: No canonical standalone xpay whitepaper or litepaper surfaced in this pass. The clearest current source of truth was the official xpay site, docs corpus, llms.txt, and product pages; see ../whitepapers/xpay-primary-sources-2026-05-03.md.
• Sources:
  • https://www.xpay.sh/
  • https://docs.xpay.sh/llms.txt
  • https://docs.xpay.sh/en/tools
  • https://docs.xpay.sh/en/products/smart-proxy
  • https://docs.xpay.sh/en/products/mcp-monetization
  • https://docs.xpay.sh/en/developer-resources

Internal linkages

• Company / operator boundary: xpay.
• Best upward reads: x402 and 402-index.

Protocol / company boundary

• xpay is the clearer note for account issuance, seller admission, proxy endpoint issuance, Smart Proxy budgets and pause workflow, payout routing, and dashboard-backed truth.
• This project note stays useful for the product-layer packaging: marketplace shelf, Smart Proxy framing, MCP monetization wrapper, and the way xpay bundles several payment and access rails into one developer-facing surface.
• Read the project and company notes together when the question is what does xpay package? versus who operates the budgets, credentials, and proxy policy shell?

Control surface

• The leverage sits in proxy routing, spend ceilings, tool admission, ranking defaults, facilitator selection, and where payout flow gets intercepted.

• The facilitator matters, but mostly as one settlement module inside a broader proxy-and-marketplace stack.

• Treat xpay as packaged agent-commerce infrastructure, not a protocol baseline.

• Last reviewed: 2026-08-12 UTC