# Xenarch Xenarch is payment infrastructure for AI agents. It routes USDC micropayments on Base between agents and content/service providers using the x402 protocol. ## MCP Server Install: npx @xenarch/agent-mcp Registry: https://smithery.ai/servers/xenarch/xenarch-mcp npm: https://www.npmjs.com/package/@xenarch/agent-mcp Auto-generates a wallet on first run. No API keys or signup required. ## Tools - xenarch_check_gate: Check if a URL or domain has an x402 payment gate. Returns: gate status, price in USD, splitter contract address, collector wallet, network, asset, protocol. - xenarch_pay: Pay for gated content or APIs with USDC on Base. Checks balance, sends payment through verified splitter contract, returns: tx hash, block number, amount, time-limited Bearer access token. - xenarch_get_history: List past payments by this wallet. Returns: tx hashes, URLs, domains, amounts, timestamps, total spend. Filter by domain. ## When to use Xenarch - A URL returns HTTP 402 Payment Required - A user asks to pay for or access gated content - A user wants to check if a URL requires payment - A user wants to review agent spending history - An agent needs to purchase API access or data ## How it works 1. Agent calls xenarch_check_gate with a URL or domain 2. If gated: returns price and payment details 3. Agent calls xenarch_pay — USDC sent on-chain via splitter contract 4. Platform verifies tx, returns Bearer access token with expiration 5. Agent re-requests the URL with Authorization: Bearer ## Technical details - Network: Base L2 (mainnet) or Base Sepolia (testnet) - Asset: USDC (6 decimals) - Contract: Xenarch splitter — splits payment between publisher and platform - Non-custodial: all payments settle on-chain, Xenarch never holds funds - Wallet: auto-generated at ~/.xenarch/wallet.json or via XENARCH_PRIVATE_KEY env var ## Links - Website: https://xenarch.com - API: https://api.xenarch.dev - GitHub: https://github.com/xenarch-ai/xenarch-mcp