{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/crypto-exchanges.perps-trading/",
    "json": "https://www.anchorterminal.com/niches/crypto-exchanges.perps-trading/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/crypto-exchanges.perps-trading/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/crypto-exchanges.perps-trading/index.min.md"
  },
  "markdown": "Four or more companies' docs show a full fit.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 4 | 12 | 19 | 10 | 9 |\n\n## What counts as done\n\nPosition opened with the requested leverage, visible with entry, size, funding and liquidation price in the position read-back, and closable reduce-only.\n\nMeasured, for our own tests: the reduce-only close takes one call.\n\nHow agents ask for it: go long ETH perp at 3x; what is my liquidation price; close the position; cap leverage at 3x and daily loss at 30 dollars\n\n## Does the job\n\nThe docs show it meets the test above, and nothing we read says otherwise.\n\n- **Bybit (Bybit Virtual Asset Platform Operator L.L.C. S.P.C)**: Linear perps with reduceOnly, closeOnTrigger and qty=0 close-up-to-max; position tools cover leverage, trading stop and closed PnL.\n- **Deribit (Deribit FZE)**: Perpetuals, futures and options with reduce_only orders and position methods in the reference; acc-40 wrote options bots against it.\n- **Hyperliquid (Hyperliquid Labs)**: updateLeverage action, clearinghouseState with leverage and liquidationPx, reduceOnly close; acc-23 and acc-31 ran small live accounts.\n- **OKX API (Aux Cayes FinTech Co. Ltd.)**: SWAP orders with tdMode, reduceOnly and leverage; positions carry liquidation and funding fields and attached TP/SL algos.\n\n## Does the job, with a limit\n\nIt does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.\n\n- **Binance API (Binance)**: The MCP page lists futures trading in the sub-account and acc-28 traded USDT-M futures with bracket orders; the futures REST reference pages load by script, so leverage and liquidation fields were not read.\n- **Bitfinex API (iFinex Inc.)**: Derivatives orders take leverage in META $F33 and Reduce Only is a flag; the positions read-back and liquidation fields were not opened.\n- **Bitget (BTG Technology Holdings Limited)**: USDT-FUTURES orders take posSide, reduceOnly and marginMode; the position endpoint fields (liquidation price, funding) were not opened.\n- **Bitstamp API (Bitstamp Ltd.)**: Derivatives orders take leverage, margin_mode, reduce_only and stop fields; the position read-back and liquidation fields were not confirmed in the page text.\n- **Coinbase Advanced Trade API (Coinbase, Inc.)**: Perpetuals run on a Deribit-based gateway with user.trades channels; the perps portfolio summary answered 403 for a key holding view and trade (acc-21).\n- **Coinbase MCP server (Coinbase for Agents) (Coinbase, Inc.)**: US dated futures only, in the default portfolio, with base_size in contracts and predicted_liquidation_price in the preview; no perpetuals.\n- **Crypto.com Exchange API (Foris DAX Limited)**: Perpetual positions, close-position and margin commands exist; liquidation and funding fields could not be read because the API docs answer 403.\n- **dYdX (dYdX Trading Inc.)**: Perps-only venue with reduce-only orders; the protocol has no market order type, so fills come from slippage limits (acc-19).\n- **Gate (Gate)**: Futures tools cover orders, positions, leverage and price-triggered orders; liquidation and funding fields are unverified without the docs.\n- **Gemini Exchange API (Gemini Trust Company, LLC)**: Perpetuals order status is enabled for perps accounts; service is for US customers after UK, EEA and Australian accounts closed.\n- **Kraken API (Payward, Inc.)**: Futures service with 39 tools and futures paper trading; futures orders have no --validate and the position read-back fields were not opened.\n- **KuCoin (KuCoin)**: Futures add order takes leverage, stop, reduce_only and close_order; the position read-back was not read.\n- **MEXC API (MEXC (Comoros) Ltd)**: Positions return liquidatePrice and leverage, but the contract reference marks order and trigger endpoints Under maintenance.\n\n## Couldn't check\n\nThe docs were closed to us, or silent. These carry no mark either way.\n\n- **HTX trading API (HTX)**: The USDT-margined swap reference is a separate page not opened in this pass.\n\n- not this job: Bithumb Open API (Bithumb Co., Ltd.): Spot KRW and BTC markets only; no derivatives.\n- not this job: Uniswap Trading API (Uniswap Labs): Spot swaps only.\n- not this job: Upbit Open API (Dunamu Inc.): Spot only.\n\n## What stops agents finishing\n\n- perps portfolio read answers 403 with view and trade permissions (Coinbase)\n- perps served to a country list the agent cannot read because the terms load by script\n- chain venue has no market order, only a limit with slippage, and the client reports it as limit\n\n## Around it\n\nBefore: crypto-exchanges.market-data-read, crypto-exchanges.rehearse-no-money. After: crypto-exchanges.protective-orders, crypto-exchanges.read-back-state.\n\n## Where this comes from\n\nWeight 10 of 100 in Crypto exchanges: 9 of 40 accounts trade or build for perps, 6 of them on Hyperliquid; the builders who went live did so with 100 to 300 dollars\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/crypto-exchanges.perps-trading.json, or the MCP tool get_use_case with id crypto-exchanges.perps-trading. Draft, read 2026-11-12 from public docs and first-hand accounts, not yet reviewed by a person.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Trade perpetuals with leverage, funding and liquidation in view",
        "url": ""
      }
    ],
    "description": "Trade perpetuals with leverage, funding and liquidation in view: 4 companies fully do it, 12 with a limit, 19 carry the tag. Every listing in Crypto exchanges with the reason and a source.",
    "facts": null,
    "h1": "Trade perpetuals with leverage, funding and liquidation in view",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/crypto-exchanges.perps-trading/",
    "published": "",
    "section": "agents",
    "title": "Trade perpetuals with leverage, funding and liquidation in view |…",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/crypto-exchanges.perps-trading/"
  },
  "tokens": {
    "markdown": 1500,
    "slim": 380
  },
  "version": 1
}
