Health, pricing, decoder, scans, and paid routes are responding.
LIVE SERVICE STATUS
All published systems operational.
This page describes service readiness, not transaction volume. Revenue is counted only after a successful on-chain Base USDC settlement.
Exact USDC payments on Base mainnet through the published facilitator.
Current production contract and discovery metadata version.
CAIP-2 identifier for Base mainnet.
MONITORING CONTRACT
Use the JSON endpoints for automation.
GET /api/health— lightweight liveness response.GET /api/status— version, product routes, x402 state, and timestamp.- HTTP 402 on a paid route is healthy and expected when no payment is attached.
- HTTP 429 or 503 may be retried with backoff. Other 4xx responses require correcting the request.