No account, no key, no subscription. Calls inside your free limits stay free.
How it works
When a request hits a limit that one paid call lifts (the keyless daily cap, history older than your tier, a query window, SQL time), the API answers 402 Payment Required instead of 403 or 429. The response still carries the usual JSON error, plus x402’sPAYMENT-REQUIRED header with the price and where to pay. An x402 client signs a USDC payment and retries the same request with a PAYMENT-SIGNATURE header; the API serves it at the Builder tier and returns PAYMENT-RESPONSE with the transaction.
To pay from the first call, use the same paths under /x402: https://api.ironflow.sh/x402/v1/liquidations always asks for payment, then serves exactly what /v1/liquidations serves.
You are charged only for calls that succeed: a call that fails is not settled, and if a payment cannot be settled, no data is sent.
With @x402/fetch
Listed in the x402 Bazaar
These are declared to Coinbase’s x402 Bazaar (agentic.market), with descriptions, example inputs and output schemas, so an agent searching it can find and call them. The same list, with prices and schemas, is at api.ironflow.sh/openapi.json (OpenAPI 3.1 withx-payment-info), which x402 registries such as x402scan read:
What can be paid for
Every read endpoint under/v1, and SQL. Live streams, liquidation alerts, keys and billing need a free key instead, and the per-minute rate limit still answers 429 with Retry-After. For steady use a plan is cheaper: Explorer at 49 USDC for 30 days costs what 10,000 to 25,000 paid calls would.