xpay

• Name: xpay
• URL: https://www.xpay.sh/
• Category: agentic-commerce marketplace / MCP tool-and-content monetization layer / x402 spending-controls control plane
• Tags: ethereum-ecosystem
• Summary: xpay is a marketplace-and-controls wrapper around agent payments. The real product is one account, one proxy layer, and one spend-governance surface across paid content, tools, and existing MCP/API endpoints. The x402 facilitator matters, but mainly as one settlement module under a broader operating stack.
• What it does:
  • Runs AgentFeed, a publisher marketplace where agents can license content from 5,000+ publishers through MCP-native query endpoints
  • Runs xpay Tools, a marketplace exposing 1,000+ pay-per-use API tools 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 receive Base-USDC payouts through xpay proxy URLs
  • Operates an x402 facilitator on Base while presenting 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 open-source x402 ecosystem projects
• Key claims:
  • The official site calls xpay a “two-sided MCP-native marketplace and payment layer,” which is a better fit than treating it as just an x402 helper or MCP directory
  • The docs llms.txt call it an “AI Agent Payment Control Platform” and place non-custodial spend controls, API monetization, tools, and facilitator endpoints inside one product surface
  • The Smart Proxy docs make runaway-spend prevention, hard budgets, anomaly alerts, and multi-agent management first-class features rather than dashboard garnish
  • The MCP Monetization docs say existing MCP servers can be wrapped with “zero code changes,” which is the clearest evidence that proxy monetization is core to the stack
  • The Tools docs show xpay packaging discovery and execution routing for agents, not merely collecting payments after the fact
• 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

• Stronger reads: x402, machine-payments-protocol, and agent-payments-protocol.

Control surface

• The leverage sits in account issuance, proxy routing, tool admission, spend ceilings, and which settlement paths xpay exposes behind one developer-facing endpoint.

• That makes xpay a real operating layer for agent commerce, but still not the protocol baseline.

• Last reviewed: 2026-06-04 UTC