About Xenarch
Xenarch is a USDC payment rail on Base built on x402. Sellers use it for payment links, publishers and developers use it to charge for sites and APIs, and AI agents use it to pay. Payments go wallet to wallet with a 0% Xenarch fee.
Payments, gating and agents
Xenarch offers USDC payment links and x402 payment gating. Its MCP server is the npm package @xenarch/agent-mcp. Sellers can create checkout, subscription, invoice and donation links in the dashboard at dash.xenarch.dev. Hosted links use pay.xenarch.com/l/<link id>. Gating integrations include a WordPress plugin, a Joomla package, a Cloudflare Worker and Python FastAPI middleware with a require_payment decorator. Install the MCP server with npx @xenarch/agent-mcp.
Payments settle directly to the seller’s wallet
In every x402 payment requirement Xenarch issues, payTo is the seller’s own wallet. USDC moves from the payer to the seller with no Xenarch contract in between. Xenarch never holds the funds.
Xenarch forwards the payer’s signed authorization to a third-party x402 facilitator. The facilitator broadcasts the transaction and pays the gas. Xenarch never sends an on-chain transaction itself.
Xenarch then reads the transaction receipt from Base RPC and checks for a USDC Transfer to the seller. A facilitator cannot fake a settlement.
Xenarch picked PayAI, xpay, Mogami, Heurist and Daydreams in its May 10, 2026 audit because each was live on Base mainnet, was free and needed no API key. Xenarch advertises this default facilitator stack to agents and uses it for hosted checkout.
Xenarch supports only Base mainnet and native USDC. Native USDC uses contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base mainnet and has 6 decimals.
Public code, pay.json and the MCP Registry
Xenarch publishes code in its GitHub organization, xenarch-ai. Its public repositories include pay-json, xenarch-mcp, xenarch-sdks, xenarch-plugins, xenarch-examples and x402-agent.
The SDKs, MCP server and most plugins use the MIT license. The WordPress plugin uses GPL-2.0 or later. The platform, web and docs repositories are not public.
Xenarch also publishes the pay.json standard, which includes an ordered list of facilitators. The specification is at v1.2, with pay-json version 1.2.0 on npm and pay.json version 1.2.0 on PyPI.
The MCP server is published on npm as @xenarch/agent-mcp, version 1.3.1, exposing 103 tools. Its official MCP Registry listing is io.github.xenarch-ai/xenarch-mcp at version 1.3.1.
Xenarch Inc. and company contact
The legal entity named in the terms is Xenarch Inc., incorporated in Wyoming, United States. The terms are governed by Wyoming law, with disputes heard in Laramie County courts.
The company’s postal address is 1021 E Lincolnway #8183, Cheyenne, WY 82001, United States.
Xenarch’s contact mailbox is [email protected]. The company’s terms, privacy policy and security.txt name this mailbox as the contact.
Questions
Xenarch is a product of Xenarch Inc., Wyoming, United States.
No. The seller’s wallet is the payment destination, and a third-party facilitator broadcasts the payer’s signed authorization.
Xenarch charges a 0% fee. Payments settle in USDC on Base.
Parts of Xenarch are open source. The SDKs, MCP server, plugins, examples and pay.json are public in the xenarch-ai GitHub organization. The platform, web and docs repositories are not public.