{"name":"x402-facilitator-celo","title":"x402 facilitator (Celo)","version":"0.1.0","protocol":"mcp","protocolVersion":"2025-11-25","supportedProtocolVersions":["2025-11-25","2025-06-18"],"transport":"streamable-http","endpoint":"https://api.x402.celo.org/mcp","usage":"POST JSON-RPC 2.0 (initialize, tools/list, tools/call) with Accept: application/json, text/event-stream","tools":[{"name":"get_supported","description":"The (x402Version, scheme, network) kinds and extensions this facilitator verifies and settles. Same answer as GET /supported."},{"name":"get_config","description":"Every settleable asset with its address, decimals, transfer method and EIP-712 domain values, plus the pricing model (gas at cost, plus a fee in basis points on the payment value when the asset has a USD price), the gas fallback and the free-credit allowances. Same answer as GET /api/config."},{"name":"get_health","description":"Whether the facilitator behind this host is answering. Same answer as GET /health."},{"name":"verify_payment","description":"Check a signed x402 payment against its requirements: signature, amount, balance and simulation. Moves no funds. Same answer as POST /verify, and it spends the same per-IP allowance."},{"name":"payment_status","description":"Whether a signed payment authorization has been used on chain, for a client whose settle reply was lost. Answers unspent, consumed or expired from the chain (EIP-3009 authorizationState, or the Permit2 nonce bitmap). unspent is not final: the authorization can still be used until validBefore, and a settlement already in flight reads as unspent here. Only consumed and expired are final; expired is only reported 5 s after validBefore, so a payment still in flight is not called final. The settled and pending states need the owning API key and are only served over HTTP. Same answer as GET /settle/status, and it spends the same per-IP allowance."}]}