Xenarch — X402 Mcp Server For Ai Agent Payments

Name: Xenarch — X402 Mcp Server For Ai Agent Payments
Author: xenarch-ai

@xenarch-ai

Xenarch — X402 Mcp Server For Ai Agent Payments について

x402 MCP server for AI agent payments. Gasless USDC micropayments on Base L2. Claude, Cursor, LangChain, CrewAI, AutoGen, LangGraph resolve HTTP 402 with no API keys. Non-custodial, settlement-provider-agnostic, 0% fee.

#mcp #mcp-server #x402 #http-402 #ai-agent-payments #claude #cursor #langchain #crewai #usdc #base-l2 #non-custodial #pay-per-crawl #micropayments #pay-json #xenarch

基本情報

カテゴリ

AI とエージェント

ライセンス

MIT

ランタイム

node

トランスポート

stdio

公開者

xenarch-ai

投稿者

Em de Vries

設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "xenarch": {
      "command": "npx",
      "args": [
        "-y",
        "@xenarch/agent-mcp"
      ]
    }
  }
}

ツール

ツールは検出されませんでした

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is Xenarch — X402 Mcp Server For Ai Agent Payments?

Xenarch is a non-custodial x402 MCP server that enables AI agents (Claude, Cursor, LangChain, CrewAI) to pay for HTTP 402-gated APIs and content with USDC micropayments on Base L2. It requires no API keys, no subscriptions, and no credit card on file. The agent wallet never needs ETH; USDC is the only token it holds. Payments settle on-chain directly from the agent wallet to the publisher wallet with 0% Xenarch fee.

How to use Xenarch — X402 Mcp Server For Ai Agent Payments?

Configure your wallet by placing a private key in ~/.xenarch/wallet.json, then add the server to any MCP client (e.g., claude mcp add xenarch -- npx @xenarch/agent-mcp). Fund the wallet with USDC on Base — no ETH or other tokens needed. Optionally set the XENARCH_API_TOKEN environment variable to enforce managed caps and scope, and run xenarch agent login once to enable control-plane and merchant tools.

Key features of Xenarch — X402 Mcp Server For Ai Agent Payments

Non-custodial USDC micropayments on Base L2
Works on any host, not platform-locked
Agent needs only USDC — no ETH or gas coin
0% Xenarch fee, no contract in money flow
29 MCP tools for discovery, payments, control, and merchant operations
Open standard: x402 protocol plus pay.json

Use cases of Xenarch — X402 Mcp Server For Ai Agent Payments

AI agents paying for gated content per request
API monetization without subscriptions or API keys
Publishers charging per-request for their APIs
Agents from Claude, Cursor, LangChain, and CrewAI paying for HTTP 402–gated services
Machine-to-machine micropayments on Base L2

FAQ from Xenarch — X402 Mcp Server For Ai Agent Payments

What is the x402 protocol?

x402 is an open protocol for HTTP 402 Payment Required: a server returns HTTP 402 with a signed price and payment details, the client signs a USDC micropayment on Base L2, then retries the request with proof of payment. Xenarch automates both halves for AI agents.

Does the agent need ETH to pay?

No. The agent wallet only ever needs USDC on Base L2 — no ETH, no gas coin of any kind.

How are spending caps and scope enforced?

Set the XENARCH_API_TOKEN environment variable to an xa_live_ agent key. The MCP server then refuses to pay without the token (fail‑closed), enforcing per‑tx, daily, and monthly caps, plus allow/deny scope rules. Caps can be managed via the dashboard at dash.xenarch.dev.

Is Xenarch custodial?

No. Xenarch never holds funds and there is no Xenarch contract between the agent and the publisher. Payments are direct USDC transfers (EIP‑3009) from the agent wallet to the publisher wallet.

What transports and auth methods does the server support?

The server uses a private key for wallet operations (set via XENARCH_PRIVATE_KEY), an optional API token for caps/scope control, and a SIWE session (via xenarch agent login) for control‑plane and merchant tools. All payment communication uses the x402 HTTP handshake.