Products
Payments
Pay links for checkout, subscriptions, invoices and donations, paid in USDC at a hosted checkout on pay.xenarch.com.
Gating
Charge AI agents and bots for pages and APIs with HTTP 402. People reach your pages as before.
Agents
Let an AI agent pay x402 gates and pay links from its own wallet, within spend caps you set.
How a payment moves
- The seller’s wallet is the payee. In every x402 payment requirement Xenarch issues,
payTois the seller’s own wallet. - The payer signs an EIP-3009
transferWithAuthorizationfor USDC. Paying is a signature, not a transaction, so the payer needs USDC and no ETH. - A third-party x402 facilitator submits the transfer on Base and pays the gas. The default stack is PayAI, xpay, Mogami, Heurist and Daydreams.
- Xenarch reads the transaction receipt from Base, finds the USDC
Transferto the seller’s wallet, checks the amount, and records the payment.
Gating in one paragraph
A bot requests a gated page. Your integration (WordPress, Joomla, a Cloudflare Worker or FastAPI middleware) asks Xenarch for a gate and answers402 Payment Required with an x402 version 1 body. The agent pays through a facilitator and requests the page again with the X-Xenarch-Gate-Id and X-Xenarch-Tx-Hash headers. Your integration confirms that pair with Xenarch and serves the page. No access token is issued. How it works shows each step and the exact 402 body.
Key properties
Next steps
Agent quickstart
Pay for gated content from an agent.
Publisher quickstart
Charge AI agents for your pages.
Payments
Create pay links and take USDC at a hosted checkout.
API reference
Endpoints, authentication and rate limits.