{ "gated": true, "gate_id": "7f3a1b2c-9d4e-4a8b-b6f1-2c3d4e5f6a7b", "accepts": [ { "scheme": "exact", "network": "base", "maxAmountRequired": "3000", "resource": "https://example.com/article", "payTo": "0xabc123...publisher_wallet", "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913", "maxTimeoutSeconds": 60 } ], "facilitators": [ { "name": "PayAI", "url": "https://facilitator.payai.network", "priority": 1, "spec_version": "v1" }, { "name": "xpay", "url": "https://facilitator.xpay.dev", "priority": 2, "spec_version": "v2" } ], "seller_wallet": "0xabc123...publisher_wallet", "network": "base", "asset": "USDC" } ```

xenarch_pay

```json { "success": true, "gate_id": "7f3a1b2c-9d4e-4a8b-b6f1-2c3d4e5f6a7b", "tx_hash": "0xdef456...abc789", "facilitator": "PayAI", "seller_wallet": "0xabc123...publisher_wallet", "url": "https://example.com/article", "wallet": "0x123...your_wallet", "content": "...gated content here..." } ```

xenarch_get_history

```json { "payments": [ { "domain": "example.com", "amount_usd": "0.003", "tx_hash": "0xdef456...abc789", "paid_at": "2026-04-10T14:35:00Z" } ], "total_spent_usd": "0.003000", "count": 1, "wallet": "0x123...your_wallet" } ```

## HTTP 402 — the unused status code that x402 finally activates HTTP 402 Payment Required is a status code reserved in the HTTP spec since 1997 for machine-to-machine payment. It went unused for decades because there was no open protocol for how a client should pay a 402 response. x402 is that protocol: a server returns HTTP 402 with a signed price and payment details, the client signs a USDC micropayment on Base L2, and retries the request with proof of payment. Xenarch's MCP server automates both halves for AI agents — it reads the 402 challenge, signs the payment via `x402-fetch`, and replays the request, returning the on-chain tx hash plus the gated content. Learn more: the [x402 spec](https://www.x402.org/) defines the payment handshake; [pay.json](https://xenarch.com) (authored by Xenarch) is the companion open standard for machine-readable pricing served at `/.well-known/pay.json` — think robots.txt for payments. ## API monetization with HTTP 402 Xenarch is an API monetization primitive built on the HTTP 402 spec. Unlike API gateway monetization platforms (Apigee, Kong, AWS API Gateway) that require subscriptions, dashboards, and API keys, Xenarch lets any API charge per request with no account creation and no key provisioning — the caller pays USDC on Base L2, the API verifies the on-chain transaction, access is granted. For publishers, this means: - No integration with Stripe/card processors - No subscription plans, pricing tiers, or quota dashboards - No custodial balance held by a platform - Per-request pricing that works for human users, bots, and AI agents uniformly - API monetization that settles on-chain in real time The Python SDK includes a one-decorator FastAPI middleware; see `xenarch-sdks/python` for publisher integration. ## Setup 1. Configure your wallet: ```bash mkdir -p ~/.xenarch cat > ~/.xenarch/wallet.json << 'EOF' { "privateKey": "0xYOUR_PRIVATE_KEY" } EOF chmod 600 ~/.xenarch/wallet.json ``` 2. Add to Claude Code: ```bash claude mcp add xenarch -- npx @xenarch/agent-mcp ``` Or add to Claude Desktop / Cursor / any MCP client: ```json { "mcpServers": { "xenarch": { "command": "npx", "args": ["@xenarch/agent-mcp"], "env": { "XENARCH_PRIVATE_KEY": "0xYOUR_PRIVATE_KEY" } } } }

Xenarch Agent MCP

Installation