X402 Services

What x402-services does

The x402-services MCP server gives agent frameworks access to a 147-tool suite centered on Robinhood Chain, identified in the README as chain ID 4663. Its Robinhood Chain coverage includes block and transaction data, native and token balances, ERC-20 transfers, event logs, gas estimates, contract inspection, read-only contract calls, account nonces, address activity, tokenized-stock registry data, USDG statistics, and transfer webhooks.

The same service also exposes broader crypto and trading-intelligence functions. These include token prices and metadata, honeypot and rug checks, new-token signals, perpetuals and options data, prediction-market information, catalysts, execution and MEV signals, sanctions screening, transaction simulation, portfolio and PnL data, DeFi lending metrics, Solana safety checks, escrow primitives, and agent infrastructure such as memory, queues, locks, counters, and webhook scheduling.

How it works

Connect an MCP client to https://x402-services-production.up.railway.app/mcp. Calling tools/list returns the available tools and their JSON schemas. The catalog at /api/catalog provides the machine-readable list of tools and prices.

Requests use x402 payment terms. An unpaid request first receives HTTP 402 details; an x402 client settles the required amount and retries with an X-PAYMENT header. The README lists USDC settlement on Base, Polygon, Arbitrum, or Solana, as well as USDG on Robinhood Chain. Prices vary by operation: examples include $0.001 for a latest-block query, $0.005 for a transaction lookup, and $0.01 to register an address-transfer watcher.

The HTTP API is also usable without MCP. Its base path is https://x402-services-production.up.railway.app/api, and requests use JSON POST bodies. The Robinhood Chain watcher accepts an address and HTTPS callback URL, then posts transfer events to that URL when new ERC-20 transfers are detected.

Setup and configuration

No account, API key, signup, or subscription is described as required. Supply an x402-capable payment wrapper around fetch, provide a signer through that client, and point the MCP configuration at the /mcp endpoint. For direct HTTP use, send JSON to the relevant /api route and let the x402 client handle payment and retry behavior.

The README does not document environment variables, local installation steps, or a self-hosted deployment procedure. Payment assets and networks must match the options accepted by the service.

Tools and capabilities

The x402-services MCP server groups its tools into these documented areas:

• Robinhood Chain RPC and trading intelligence
• Crypto, token, sniping, derivatives, options, and prediction-market data
• Compliance, transaction safety, portfolio, and PnL analysis
• Agent-to-agent escrow and DeFi lending
• Solana safety and onchain analytics
• AI chat, model listing, and inference health checks
• Durable agent primitives, including storage, queues, locks, pub/sub, rate limits, and idempotency

The AI routes include fast and frontier chat endpoints, a model-listing endpoint, and a free health check. AI inference is described as payable in USDG on Robinhood Chain.

Limitations and notes

The service is pay-per-call, so agents need a compatible x402 payment flow and supported settlement asset. The README does not identify specific MCP clients or provide client-specific configuration examples. It also states that the service is not financial, legal, or tax advice. Tool availability and pricing should be checked through /api/catalog, which the README describes as the current machine-readable catalog.