# Trade perpetuals with leverage, funding and liquidation in view

> 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.

- Canonical: https://www.anchorterminal.com/niches/crypto-exchanges.perps-trading/
- Markdown: https://www.anchorterminal.com/niches/crypto-exchanges.perps-trading/index.md (~1,500 tokens)
- Slim: https://www.anchorterminal.com/niches/crypto-exchanges.perps-trading/index.min.md (~380 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/crypto-exchanges.perps-trading/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

Four or more companies' docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 4 | 12 | 19 | 10 | 9 |

## What counts as done

Position opened with the requested leverage, visible with entry, size, funding and liquidation price in the position read-back, and closable reduce-only.

Measured, for our own tests: the reduce-only close takes one call.

How 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

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **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.
- **Deribit (Deribit FZE)**: Perpetuals, futures and options with reduce_only orders and position methods in the reference; acc-40 wrote options bots against it.
- **Hyperliquid (Hyperliquid Labs)**: updateLeverage action, clearinghouseState with leverage and liquidationPx, reduceOnly close; acc-23 and acc-31 ran small live accounts.
- **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.

## Does the job, with a limit

It 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.

- **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.
- **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.
- **Bitget (BTG Technology Holdings Limited)**: USDT-FUTURES orders take posSide, reduceOnly and marginMode; the position endpoint fields (liquidation price, funding) were not opened.
- **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.
- **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).
- **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.
- **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.
- **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).
- **Gate (Gate)**: Futures tools cover orders, positions, leverage and price-triggered orders; liquidation and funding fields are unverified without the docs.
- **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.
- **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.
- **KuCoin (KuCoin)**: Futures add order takes leverage, stop, reduce_only and close_order; the position read-back was not read.
- **MEXC API (MEXC (Comoros) Ltd)**: Positions return liquidatePrice and leverage, but the contract reference marks order and trigger endpoints Under maintenance.

## Couldn't check

The docs were closed to us, or silent. These carry no mark either way.

- **HTX trading API (HTX)**: The USDT-margined swap reference is a separate page not opened in this pass.

- not this job: Bithumb Open API (Bithumb Co., Ltd.): Spot KRW and BTC markets only; no derivatives.
- not this job: Uniswap Trading API (Uniswap Labs): Spot swaps only.
- not this job: Upbit Open API (Dunamu Inc.): Spot only.

## What stops agents finishing

- perps portfolio read answers 403 with view and trade permissions (Coinbase)
- perps served to a country list the agent cannot read because the terms load by script
- chain venue has no market order, only a limit with slippage, and the client reports it as limit

## Around it

Before: crypto-exchanges.market-data-read, crypto-exchanges.rehearse-no-money. After: crypto-exchanges.protective-orders, crypto-exchanges.read-back-state.

## Where this comes from

Weight 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

As 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.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
