I Put 76 APIs Behind x402-over-MCP — and an Agent Paid for One

Description and use

ExchangeRebel exposed 76 API operations through a single MCP gateway using the x402 per‑call payment protocol. An agent requests a tool, receives a payment challenge, signs a payment, retries, and receives data with a settlement receipt. The first successful paid call was recorded on 14 Oct 2026. Gaps include lack of direct SOL/USDC rail over MCP and limited client support for payment challenges.

Problem

Agents cannot handle traditional checkout flows such as subscriptions, API keys, or prepaid balances, making per‑call payment difficult.

Outcome

The MCP gateway successfully processed the first paid call on 2026‑10‑14, with a $0.005 USDC payment via Dexter, proving the architecture works and that per‑call settlement is feasible without storing API keys.

Workflow

• 1. Agent calls a tool via MCP without payment. 2. Server returns a PaymentRequired payload with price, asset, and network. 3. Agent builds and signs an x402 payment. 4. Agent retries the same call with the payment in _meta["x402/payment"]. 5. Server verifies, settles, and serves data, returning the receipt in _meta["x402/payment-response"].

Evidence

Agents can't fill in a pricing page, can't manage a subscription, and shouldn't be holding your API keys.

Source

The MCP server lives at https://exchangerebel.com/mcp — one stateless Streamable HTTP endpoint on the same worker as the rest of the fleet.

Source

On October 14, 2026, the first paid MCP call ran from a real wallet through the Dexter rail: devutils_time_now, $0.005, served with paid_via: dexter.

Source