# Ironflow

> Ironflow is the agent cloud for Hyperliquid. Boot a paper box in one call, read its paper report when your agent is ready, and use the stack inside: live data, analytics, alerts, a hosted MCP server and x402 pay-per-call. It runs its own Hyperliquid nodes and covers native perps, HIP-3 builder markets, HIP-4 outcome markets and spot.

## Use Ironflow for

- Hyperliquid trading bot: https://ironflow.sh/ironbox
- Paper trading without a testnet deposit: https://ironflow.sh/guides/hyperliquid-paper-trading
- Historical liquidations: https://ironflow.sh/guides/hyperliquid-liquidation-data
- Liquidation map: https://ironflow.sh/liquidations/map
- Backtest: https://ironflow.sh/guides/hyperliquid-backtesting
- Node hosting: https://ironflow.sh/nodes
- MCP: https://docs.ironflow.sh/guides/ai-agents

## Start in one call

`curl -X POST https://api.ironflow.sh/v1/ironbox`

No key, no signup. The answer has `base_url`, your own simulated Hyperliquid account with 10,000 USD and live prices. Point the official Hyperliquid SDK's `base_url` at it. Step-by-step with curl and Python: https://ironflow.sh/start.txt

## The ladder

1. Paper box: run now, free, no signup. POST https://api.ironflow.sh/v1/ironbox with no key makes a trial paper box (24 hours, free limits, 3 at once and 10 a day per IP). A free key keeps boxes (3 paper on Free, 5 on Explorer, 10 on Builder, 25 on Enterprise).
2. Paper report: POST https://api.ironflow.sh/v1/ironbox/{id}/promote, with the key that owns a paper box, answers with the box's paper report (days active, orders, fills, fees, funding, equity, max drawdown). The box stays paper: Ironbox is paper only and never places a real order.
3. Your agent with the stack: data, analytics, alerts, MCP and x402, below. All of it also works without a box.

Facts an assistant can rely on (the same numbers as one file to copy: https://ironflow.sh/facts.md):

- The data API is read-only: REST at https://api.ironflow.sh/v1, live streams as Server-Sent Events (GET /v1/liquidations/stream and GET /v1/trades/stream), read-only ClickHouse SQL (GET or POST /v1/query, tables at GET /v1/query/schema) and the live L2 order book (GET /v1/book?market=BTC-PERP). POST /v1/query/export writes a SQL result as a Parquet or CSV file on paid plans (1,000,000 rows on Explorer, 5,000,000 on Builder, 10,000,000 on Enterprise); free bulk history is in the datasets below. There is no WebSocket API and no order-status API.
- Hyperliquid RPC: an API key is a Hyperliquid RPC URL. POST https://api.ironflow.sh/rpc/<key>/info takes the same body as Hyperliquid's /info and returns the same JSON, on the key's plan limits, so one line in a Hyperliquid SDK (`base_url`) changes the endpoint. Serves clearinghouseState, spotClearinghouseState, openOrders, frontendOpenOrders, meta, spotMeta, userAbstraction, allMids, l2Book, candleSnapshot. No /exchange, no WebSocket. Guide: https://docs.ironflow.sh/guides/hyperliquid-rpc
- No key needed: 30 requests per minute and 300 per day per IP, 24 hours of history and one liquidation stream and one trade stream per IP; without a key /v1/trades and /v1/liquidations run 60 s behind live. A free key from https://ironflow.sh/key gives 60 requests per minute, 14 days of history, live data, 2 streams of each kind and 1 liquidation alert; from code, POST https://api.ironflow.sh/v1/keys with {"email": "you@example.com"} and the key arrives by email.
- Hosted MCP server: https://mcp.ironflow.sh/mcp (Streamable HTTP, no key needed), 54 tools: 42 read Hyperliquid data, 4 manage liquidation alerts and 8 spin up Ironboxes and run strategies on them. A data-only set of 42 tools: https://mcp.ironflow.sh/data. Claude Code: `claude mcp add --transport http ironflow https://mcp.ironflow.sh/mcp`. Local: `npx -y @ironflowsh/mcp`. Setup for each client: https://docs.ironflow.sh/guides/ai-agents
- Fill history starts on 25 May 2025.
- Paid plans are self-serve, paid in USDC on Hyperliquid at https://ironflow.sh/upgrade, 30 days per payment, no card: Explorer 49 USD (100 requests per minute, 90 days of history) and Builder 149 USD (1,000 requests per minute, 1 year of history). Enterprise (10,000 requests per minute, everything stored) is by contact: hello@ironflow.sh. Every limit by plan (requests, history, SQL time, streams, alerts): https://docs.ironflow.sh/concepts/rate-limits. A limit error carries an "upgrade" object naming the next plan, its price and the API call that buys it, and rate, daily, stream and SQL time limits also carry an "ironbox" object with the call that creates an Ironbox.
- x402 pay-per-call, for agents with a USDC wallet on Base, no account or key: $0.001 for the markets snapshot and the order book, $0.002 for trades, candles and funding, $0.005 for other data calls, $0.01 per SQL query. A request past the free limits answers 402 with a PAYMENT-REQUIRED header, and https://api.ironflow.sh/x402/v1/... always asks for payment. Discovery: https://api.ironflow.sh/.well-known/x402 and https://api.ironflow.sh/openapi.json. https://ironflow.sh/openapi.json redirects to the full spec. An agent can buy a 30-day plan the same way: POST https://api.ironflow.sh/x402/v1/plans/explorer/buy (or builder, founding) with {"email": ...}. Guide: https://docs.ironflow.sh/guides/pay-per-call
- An agent can upgrade its own key from code: GET https://api.ironflow.sh/v1/billing/plans lists the plans and the payment address; POST https://api.ironflow.sh/v1/billing/upgrade with {"email", "wallet", "plan"} opens a request; send amount_usdc USDC on Hyperliquid from that wallet to to_address (a usdSend, e.g. exchange.usd_transfer(amount, to_address) in Hyperliquid's Python SDK, signed by the wallet itself); then poll status_url until status is paid. Limit errors carry the X-Ironflow-Upgrade header. Details: https://docs.ironflow.sh/concepts/plans-and-payment
- Requests accept Hyperliquid's own inputs: market=BTC, xyz:NVDA or @285 (resolved to BTC-PERP, xyz:NVDA-PERP or the spot pair), coin as an alias of market, startTime and endTime as aliases of from and to, and Unix seconds or ISO 8601 dates as times.
- Ironbox: a cheap, secure, sandboxed environment for a trading agent in Tokyo, next to Hyperliquid (about 4.5 ms to its order API), with Ironflow's data, analytics and alerts built in. For perps, prediction markets and spot. Paper boxes on every plan with a key (3 on Free, 5 on Explorer, 10 on Builder, 25 on Enterprise); no per-box price. A paper box is your own simulated Hyperliquid account with 10,000 USD and live prices on main perp markets, running from the moment it is created and never placing a real order. Start one at https://ironflow.sh/ironbox#start or with the call at the top of this file. Guide: https://docs.ironflow.sh/guides/ironbox
- Dedicated nodes are the enterprise option: a read-only Hyperliquid node in Tokyo with the Ironflow data layer on the same server, from 1,250 USD per month for one node, with custom setups (several nodes, SLA, custom data) quoted at https://ironflow.sh/nodes. Nothing is charged before the node is live.
- Trading terminal: funds never leave the user's Hyperliquid account. The terminal trades through a Hyperliquid agent key that can place and cancel orders and cannot withdraw.
- The trading terminal is not available to US persons or in sanctioned jurisdictions.

## Guides

- [How to run a Hyperliquid non-validator node](https://ironflow.sh/guides/run-hyperliquid-node): hardware, install, gossip peers, write flags, first sync, disk cleanup, monitoring and gaps, plus common hl-visor and hl-node errors with fixes.
- [Fix: Hyperliquid node crash, missing node_metadata.json](https://ironflow.sh/guides/hyperliquid-node-hardfork-crash): why hl-node crash-loops after the 25 October 2026 hardfork (an outdated hl-visor) and how to update and verify the visor without a resync.
- [visor_abci_state.json errors on a Hyperliquid node](https://ironflow.sh/guides/hyperliquid-node-visor-abci-state): what the pointer file is, why "missing file" appears on a first start and after a crash, how to restore it and keep restarts on local state.
- [Hyperliquid node falling behind](https://ironflow.sh/guides/hyperliquid-node-falling-behind): why a slow or far gossip peer holds a node behind while the server sits idle, how to measure the lag, fix the peer list and what a restart costs.
- [Hyperliquid node disk filling up: prune EVM checkpoints](https://ironflow.sh/guides/hyperliquid-node-evm-checkpoints-disk): binary 115 keeps a 3 GB EVM checkpoint every 10000 blocks; what is safe to delete and an hourly pruning script.
- [Hyperliquid API and WebSocket rate limits](https://ironflow.sh/guides/hyperliquid-api-rate-limits): every limit in one table (1200 REST weight per minute per IP, 10 WebSocket connections, 1000 subscriptions, 10 unique users per IP), request weights, address-based limits, handling 429 responses, what a local node changes, and Ironflow's own limits by plan.
- [Hyperliquid API endpoints: which one to use](https://ironflow.sh/guides/hyperliquid-api-endpoints): POST /info for reads, POST /exchange for signed orders, wss /ws for streams, rpc.hyperliquid.xyz/evm for HyperEVM, with mainnet and testnet URLs, limits and exact calls.
- [How to backtest on Hyperliquid](https://ironflow.sh/guides/hyperliquid-backtesting): where history comes from past the 5000 candle API limit (free hourly candles from 25 May 2025, 1 minute bars and ticks over REST and SQL), real fees and funding, a tested pandas example and paper testing.
- [Hyperliquid WebSocket API](https://ironflow.sh/guides/hyperliquid-websocket-api): mainnet and testnet URLs, the subscribe message, all 24 subscription types, snapshots, post requests, ping, reconnects, per-IP limits and a Python example.
- [Hyperliquid historical data: API, S3 archive, SQL and free downloads](https://ironflow.sh/guides/hyperliquid-historical-data): the info API keeps the 10,000 most recent fills per wallet and 5,000 candles per interval; older data from the S3 archive, or from Ironflow by REST (GET https://api.ironflow.sh/v1/candles?market=BTC-PERP&interval=1h, no key), SQL and free Parquet files, with a coverage table by data type.
- [Hyperliquid SQL](https://ironflow.sh/guides/hyperliquid-sql): one read-only ClickHouse query over every fill, liquidation, funding rate and transfer through GET or POST /v1/query or the run_query MCP tool, the tables, the limits by plan and 8 tested queries.
- [Hyperliquid trades and fills data](https://ironflow.sh/guides/hyperliquid-trades-fills-data): fills vs trades, every fill field, the userFills, userFillsByTime and recentTrades limits, TWAP slices, the S3 fills archive and tick data over REST.
- [Hyperliquid candles and OHLCV data](https://ironflow.sh/guides/hyperliquid-candles-ohlcv): candleSnapshot keeps the most recent 5000 candles per interval; how far back each interval reaches, building older candles from fills, GET https://api.ironflow.sh/v1/candles from 25 May 2025 at 1m to 1w, and a pandas backtest.
- [Hyperliquid liquidation data](https://ironflow.sh/guides/hyperliquid-liquidation-data): a liquidation is a fill with a liquidation field and Hyperliquid's API returns them per wallet; every liquidation since 25 May 2025 by REST (GET https://api.ironflow.sh/v1/liquidations?market=BTC-PERP, no key), SQL, a live stream (GET /v1/liquidations/stream) and the get_liquidations MCP tool.
- [How to read the Hyperliquid liquidation map](https://ironflow.sh/guides/hyperliquid-liquidation-map): what the projected map shows, walls and cascades, how liquidation prices are computed from our node's state snapshot and checked against Hyperliquid's liquidationPx (99.4% within 0.1%), its limits, and the API and get_liquidation_map MCP tool.
- [Hyperliquid funding rates](https://ironflow.sh/guides/hyperliquid-funding-rates): hourly funding, the formula and the 4% per hour cap, fundingHistory, predictedFundings and userFunding, and funding history over REST.
- [Hyperliquid order book data](https://ironflow.sh/guides/hyperliquid-order-book-data): the live l2Book feeds, what L4 means, the L2 snapshots in Hyperliquid's archive and rebuilding a book from a node's raw diffs.
- [Hyperliquid stock perps (HIP-3)](https://ironflow.sh/guides/hyperliquid-stock-perps-hip3): which HIP-3 dexes are live, the xyz:NVDA naming, the dex field in the info API, weekend trading and the oracle, and HIP-3 trades, candles, funding and oracle prices over REST and SQL.
- [Hyperliquid HIP-4 outcome markets](https://ironflow.sh/guides/hyperliquid-hip4-outcome-markets): how outcome markets settle and are named, what trades on them, and their trades, candles, settled outcomes and traders over REST, SQL and MCP.
- [Hyperliquid paper trading](https://ironflow.sh/guides/hyperliquid-paper-trading): test a bot on your own simulated account with 10,000 USD and live prices through the official SDK's base_url, what is simulated (fees, funding, margin, liquidation, perps only) and how it differs from testnet.
- [How to backtest a Hyperliquid strategy in plain English](https://ironflow.sh/guides/hyperliquid-backtest-plain-english): type an idea as one sentence on ironflow.sh; a sandbox writes bot.yaml and backtests the last 90 days with 4.5 bps fee and each market's measured slippage per side (0.5 bps on BTC), funding, a 30% holdout and 1,000 random runs. With a free key in IRONFLOW_API_KEY it reaches 365 days.
- [Hyperliquid funding rate: what is normal and what is a spike](https://ironflow.sh/guides/hyperliquid-funding-rate-spike): measured hourly levels for a year by market; BTC sat at the 0.00125% base in 47.9% of hours and reached 0.003% in 11; HYPE's top 1% starts at 0.006%.
- [A sandbox for Hyperliquid trading agents](https://ironflow.sh/guides/hyperliquid-trading-agent-sandbox): a Linux sandbox in Tokyo with Hyperliquid data, the ironbox CLI (new, backtest, run, ps, logs, account), bot.yaml or bot.py, and a paper account; agents use create_ironbox or POST /v1/ironbox.
- [Hyperliquid API key](https://ironflow.sh/guides/hyperliquid-api-key): Hyperliquid reads need no key; a free Ironflow data key (POST https://api.ironflow.sh/v1/keys with {"email": ...}, sent by email) reads 14 days at 60 requests a minute.
- [Hyperliquid leaderboard API](https://ironflow.sh/guides/hyperliquid-leaderboard-api): the info API has no leaderboard request; the public file stats-data.hyperliquid.xyz/Mainnet/leaderboard lists about 48,000 accounts; GET /v1/analytics/leaderboard-pnl ranks every wallet with 5 or more fills over any window.
- [Hyperliquid mark price and oracle price](https://ironflow.sh/guides/hyperliquid-mark-price): the three inputs of the mark price, the oracle's exchange sources and weights (every 3 seconds), what each is used for, and history at GET /v1/mark-prices.
- [Where are Hyperliquid's servers?](https://ironflow.sh/guides/hyperliquid-server-location): no published list; Hyperliquid's node README recommends Tokyo; about 4.5 ms to the order API from a Tokyo server; api.hyperliquid.xyz is behind CloudFront, so time a full request.
- [How to build a Hyperliquid trading bot in Python](https://ironflow.sh/guides/hyperliquid-trading-bot): a Python bot on the official Hyperliquid SDK, run on a free paper box (POST https://api.ironflow.sh/v1/ironbox, no key; Info(base_url, skip_ws=True), since a box has no WebSocket) with 10,000 USD of simulated funds and live prices.
- [Hyperliquid testnet without a mainnet deposit](https://ironflow.sh/guides/hyperliquid-testnet-without-deposit): the testnet faucet pays 1,000 mock USDC only to addresses that deposited on mainnet; a paper box gives any address 10,000 USD of simulated funds on live order books, no deposit, no key.
- [Hyperliquid historical liquidations API](https://ironflow.sh/guides/hyperliquid-historical-liquidations): the info API has no liquidations request; every liquidation since 25 May 2025 by GET https://api.ironflow.sh/v1/liquidations (no key for 24 hours), SQL hl.liquidations and the get_liquidations MCP tool, or 2,849,452 to 31 October 2026 as free Parquet.
- [Hyperliquid userFills limit](https://ironflow.sh/guides/hyperliquid-userfills-limit): userFills returns 2,000 fills and userFillsByTime only the 10,000 most recent; GET https://api.ironflow.sh/v1/fills?address=0x... pages through every fill since 25 May 2025, 1,000 per page, within the plan's history.
- [Freqtrade on Hyperliquid past 5,000 candles](https://ironflow.sh/guides/freqtrade-hyperliquid-backtesting): Freqtrade only gets Hyperliquid's last 5,000 candles; load 12,586 free hourly BTC candles since 25 May 2025 plus funding as Freqtrade data, or 1m to 30m from /v1/candles with a key. Scripts: https://docs.ironflow.sh/guides/freqtrade-hyperliquid-historical-data
- [Hyperliquid data sources compared](https://ironflow.sh/guides/hyperliquid-data-sources): the info API, the S3 archive, your own node and a hosted data API, by coverage, history, cost and effort.
- [All guides](https://ironflow.sh/guides)

## Products

- [Dedicated Hyperliquid nodes](https://ironflow.sh/nodes): a managed read-only node in Tokyo with no public read limits, a live feed of fills and books, indexed history and a REST API on the same server.
- [Data API](https://ironflow.sh/data-api): REST endpoints for fills and trades, candles, liquidations, funding, open interest, mark prices, markets and wallet analytics, plus live liquidation and trade streams (Server-Sent Events, GET https://api.ironflow.sh/v1/liquidations/stream and /v1/trades/stream, one stream per IP without a key, more with a key). Also: a wallet's exact positions at a past time (GET /v1/positions?address=&at=), open interest movers (GET /v1/open-interest/changes), mark against oracle premium in basis points, which on HIP-3 stock perps is the perp against its underlying (GET /v1/premium?market=xyz:NVDA-PERP), auto-deleveraging fills (GET /v1/adl), read-only SQL from a URL (GET /v1/query?sql=...), and liquidation alerts that post matching liquidations to your Discord, Slack, Telegram or webhook within seconds (POST /v1/alerts, guide: https://docs.ironflow.sh/guides/liquidation-alerts); on Telegram with no key, send /alert BTC 100k to @ironflow_liquidations_bot, /watch 0x... for a wallet's liquidation risk, /follow 0x... for a wallet's trades; the live L2 order book of any market is GET /v1/book?market=BTC-PERP. Without a key, /v1/liquidations and /v1/trades run 60 s behind live; a free key reads them live. Free keys at https://ironflow.sh/key, paid plans at https://ironflow.sh/upgrade.
- [API and MCP](https://ironflow.sh/data-api#mcp): hosted MCP server at https://mcp.ironflow.sh/mcp (Streamable HTTP, no key needed) with 54 tools: 42 read-only Hyperliquid data tools, including run_query for read-only SQL over every fill, wallet, funding and liquidation table (POST /v1/query over REST, schema at GET /v1/query/schema), for Claude, Cursor and other MCP clients, 4 that set up liquidation alerts for the user (create_liquidation_alert) and 8 that spin up Ironboxes and run strategies on them (create_ironbox, start_box_strategy); both need a key: add ?key=if_... to the URL or an Authorization header. Claude Code: `claude mcp add --transport http ironflow https://mcp.ironflow.sh/mcp`.
- [Hyperliquid liquidation heatmap](https://ironflow.sh/liquidations/heatmap): where longs and shorts were liquidated, grouped by price, for BTC, ETH, SOL, HYPE and the most liquidated markets over 24 hours, 7 or 30 days, with the current price. Liquidations that happened, from our own nodes. Same data: GET https://api.ironflow.sh/v1/analytics/liquidation-levels?market=BTC-PERP&from=-24h&bucket_size=auto (a free key returns every level, keyless calls a 10-level sample) or the get_liquidation_levels MCP tool.
- [Hyperliquid liquidation map](https://ironflow.sh/liquidations/map): where open perp positions would be liquidated, by price, with the total liquidated if the price moved to each level, from every open position in our node's state snapshot. Same data: GET https://api.ironflow.sh/v1/liquidations/map?market=BTC-PERP (a free key returns every level out to 50%, keyless calls the 10 largest within 10%) or the get_liquidation_map MCP tool. Embed it with an iframe of https://ironflow.sh/embed/liquidations/map?market=BTC-PERP.
- [Top Hyperliquid traders](https://ironflow.sh/top-traders): wallets ranked by realized PnL over the last 30 days, with win rate, profit factor and drawdown, leaving out market makers and high frequency bots. Same list: the get_top_traders MCP tool. To rank every wallet over your own window: GET https://api.ironflow.sh/v1/analytics/leaderboard-pnl?from=-24h (guide: https://ironflow.sh/guides/hyperliquid-leaderboard-api).
- [Free API key](https://ironflow.sh/key): an email form; the key arrives by email and gives 60 requests per minute and 14 days of history. From code: POST https://api.ironflow.sh/v1/keys with {"email": "you@example.com"}. Not a Hyperliquid API wallet: Hyperliquid reads need no key.
- [Datasets](https://ironflow.sh/datasets): the free Parquet files below, with coverage, rows and size for each.
- [Sandbox](https://ironflow.sh/ironbox): type a trading idea in plain English or open a terminal; it backtests in your own box next to Hyperliquid, with fees, funding and slippage charged.
- [Hyperliquid HIP-4 outcome markets](https://ironflow.sh/hip4): live HIP-4 prediction markets: active outcomes with last price and 24-hour volume, plus traded volume by month, each trade counted once. Same data: GET https://api.ironflow.sh/v1/predictions/summary?window=1d and /v1/predictions/history (no key) or the get_outcome_markets MCP tool. Every outcome fill since August 2026 is a free dataset.
- [Trading terminal](https://terminal.ironflow.sh): DCA (long or short), range orders, triggers on large wallet activity, baskets, TWAP and iceberg execution, and native stop loss and take profit on Hyperliquid.

## Open source

- [hyperliquid-node-kit](https://github.com/ironflowsh/hyperliquid-node-kit): scripts to install and run a Hyperliquid non-validator node on Ubuntu (installer with signature check, disk cleanup, lag watchdog, peer refresh) and hlnode-mcp, a read-only MCP server that lets an AI agent read from your own node.
- [@ironflowsh/mcp](https://github.com/ironflowsh/mcp): MCP server for the Ironflow data API and liquidation alerts (the same tools as the hosted server, run locally with `npx -y @ironflowsh/mcp`).

## Datasets

Free downloads of older data, Parquet, on Hugging Face (most also on Kaggle at https://www.kaggle.com/ironflow). Files published before 10 November 2026 are CC BY 4.0; newer files appear 90 days after the data date, carry no wallet addresses and are CC BY-NC 4.0. Recent data, wallet-level data and commercial use need the API:

- [Hyperliquid Trades](https://huggingface.co/datasets/ironflow/hyperliquid-trades): every perp and spot trade from 3 October 2026 with buyer, seller and taker side, a new file every day.
- [Hyperliquid Liquidations](https://huggingface.co/datasets/ironflow/hyperliquid-liquidations): every liquidation on Hyperliquid perps from 25 May 2025, native and HIP-3.
- [Hyperliquid Funding Rates](https://huggingface.co/datasets/ironflow/hyperliquid-funding): every settled funding rate from May 2023, native and HIP-3 perps.
- [Hyperliquid Hourly Candles](https://huggingface.co/datasets/ironflow/hyperliquid-candles-1h): hourly OHLCV for every perp and spot pair from 25 May 2025.
- [Hyperliquid Open Interest, Mark and Oracle Prices](https://huggingface.co/datasets/ironflow/hyperliquid-open-interest): hourly open interest, mark and oracle price for every perp from May 2023.
- [Hyperliquid HIP-4 Outcome Markets](https://huggingface.co/datasets/ironflow/hyperliquid-outcomes): every HIP-4 outcome fill from 1 August 2026 and every contract with its settlement, a new file every day.

## For AI agents

- [llms-full.txt](https://docs.ironflow.sh/llms-full.txt): the whole documentation as one text file, introduction and quickstart first; [docs index](https://docs.ironflow.sh/llms.txt).
- [guides-full.txt](https://ironflow.sh/guides-full.txt): every guide above as one text file.
- [facts.md](https://ironflow.sh/facts.md): current limits, history, prices and the MCP tool count, to copy as they are.
- [start.txt](https://ironflow.sh/start.txt): the quickstart, step by step, with curl and Python.
- [OpenAPI spec](https://docs.ironflow.sh/openapi.yaml): every public endpoint, parameters and response shapes.
- [API catalog](https://ironflow.sh/.well-known/api-catalog) (RFC 9727) and [MCP server catalog](https://ironflow.sh/.well-known/ai-catalog.json).
- [x402 discovery](https://api.ironflow.sh/.well-known/x402) and the [pay-per-call OpenAPI](https://api.ironflow.sh/openapi.json).
- [API index](https://api.ironflow.sh/v1): the main endpoints as JSON, no key.
- [MCP setup](https://docs.ironflow.sh/guides/ai-agents): Claude, Claude Code, Cursor, VS Code and other MCP clients.

## Reference

- [Docs](https://docs.ironflow.sh): data API reference, quickstart, authentication, rate limits, guides and the MCP setup for AI agents.
- [Status](https://status.ironflow.sh)
- [Terms](https://ironflow.sh/terms)
- [Risk disclosure](https://ironflow.sh/risk-disclosure)