I Put 76 APIs Behind x402-over-MCP — and an Agent Paid for One
说明与用途
ExchangeRebel 通过 x402 协议将 76 个 API 操作集成到单一 MCP 服务器,实现按调用付费。代理先发起未付费请求,收到支付挑战,签署支付后重试,服务器确认支付并返回数据及收据。首笔成功付费记录于 2026‑10‑14。存在的缺口包括 MCP 上缺少直接 SOL/USDC 支付通道以及客户端对支付挑战的支持有限。
问题
Agents cannot handle traditional checkout flows such as subscriptions, API keys, or prepaid balances, making per‑call payment difficult.
结果
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.
工作流
- 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"].
证据
Agents can't fill in a pricing page, can't manage a subscription, and shouldn't be holding your API keys.
The MCP server lives at https://exchangerebel.com/mcp — one stateless Streamable HTTP endpoint on the same worker as the rest of the fleet.
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.
- 记录日期: 2026-10-14T19:41:22.784Z