Niches · Crypto exchanges

Trade perpetuals with leverage, funding and liquidation in view

Four or more companies' docs show a full fit.

4companies, full fit
12companies, fit with a limit
19companies carry the tag
10share of the category's work
9first-hand accounts

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. No docs we read state these figures, so they don't count against a listing here.

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 4

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

ListingWhy
Bybit C
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. source
Deribit C
Deribit FZE
Perpetuals, futures and options with reduce_only orders and position methods in the reference; acc-40 wrote options bots against it. source
Hyperliquid D
Hyperliquid Labs
updateLeverage action, clearinghouseState with leverage and liquidationPx, reduceOnly close; acc-23 and acc-31 ran small live accounts. source
OKX API B
Aux Cayes FinTech Co. Ltd.
SWAP orders with tdMode, reduceOnly and leverage; positions carry liquidation and funding fields and attached TP/SL algos. source

Does the job, with a limit 13

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.

ListingWhy
Binance API B
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. source
Bitfinex API C
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. source
Bitget C
BTG Technology Holdings Limited
USDT-FUTURES orders take posSide, reduceOnly and marginMode; the position endpoint fields (liquidation price, funding) were not opened. source
Bitstamp API D
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. source
Coinbase Advanced Trade API B
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). source
Coinbase MCP server (Coinbase for Agents) C
Coinbase, Inc.
US dated futures only, in the default portfolio, with base_size in contracts and predicted_liquidation_price in the preview; no perpetuals. source
Crypto.com Exchange API D
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. source
dYdX BB
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). source
Gate C
Gate
Futures tools cover orders, positions, leverage and price-triggered orders; liquidation and funding fields are unverified without the docs. source
Gemini Exchange API BB
Gemini Trust Company, LLC
Perpetuals order status is enabled for perps accounts; service is for US customers after UK, EEA and Australian accounts closed. source
Kraken API BB
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. source
KuCoin C
KuCoin
Futures add order takes leverage, stop, reduce_only and close_order; the position read-back was not read. source
MEXC API C
MEXC (Comoros) Ltd
Positions return liquidatePrice and leverage, but the contract reference marks order and trigger endpoints Under maintenance. source

Couldn't check 1

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

ListingWhy
HTX trading API E
HTX
The USDT-margined swap reference is a separate page not opened in this pass.

Doesn't do this job 3

Listings in the category that do something else, with the reason.

ListingWhy
Bithumb Open API D
Bithumb Co., Ltd.
Spot KRW and BTC markets only; no derivatives. source
Uniswap Trading API B
Uniswap Labs
Spot swaps only. source
Upbit Open API C
Dunamu Inc.
Spot only. source

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

The same as data: /api/v1/use-cases/crypto-exchanges.perps-trading.json, or the MCP tool get_use_case with id crypto-exchanges.perps-trading. Other jobs in this category: /api/v1/niches?category=crypto-exchanges.

Draft, read 2026-11-12 from public docs and first-hand accounts, not yet reviewed by a person. A mark says what the docs show, not what a run measured.

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.