# Attach a stop loss or take profit the exchange enforces

> Attach a stop loss or take profit the exchange enforces: 8 companies fully do it, 9 with a limit, 20 carry the tag. Every listing in Crypto exchanges with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/crypto-exchanges.protective-orders/
- Markdown: https://www.anchorterminal.com/niches/crypto-exchanges.protective-orders/index.md (~1,700 tokens)
- Slim: https://www.anchorterminal.com/niches/crypto-exchanges.protective-orders/index.min.md (~380 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/crypto-exchanges.protective-orders/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 |
| --- | --- | --- | --- | --- |
| 8 | 9 | 20 | 8 | 7 |

## What counts as done

A trigger order visible in the open orders read-back with its trigger flag and trigger price set, reduce-only where supported, that does not execute until the trigger price is reached. Verified by reading it back, not by the placement response alone.

How agents ask for it: set a stop loss 3% below my entry; add a take profit at 70,000; make the stop reduce-only so it cannot open a new position; bracket this order

## Does the job

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

- **Binance API (Binance)**: STOP_LOSS, STOP_LOSS_LIMIT, TAKE_PROFIT and TAKE_PROFIT_LIMIT with stopPrice or trailingDelta; stopPrice and type appear in the order read-back; OCO order lists bracket an entry. Reduce-only is a futures field.
- **Bitfinex API (iFinex Inc.)**: STOP, STOP LIMIT and TRAILING STOP types (EXCHANGE prefix for spot), Reduce Only flag 1024 and OCO flag 16384; the order array carries ORDER_TYPE, PRICE_AUX_LIMIT and FLAGS on read-back.
- **Bitget (BTG Technology Holdings Limited)**: Strategy orders of type tpsl, trigger, oco and trailing_stop with reduceOnly and trigger price type; place-order also takes preset takeProfit and stopLoss; strategy detail endpoints read them back.
- **Bybit (Bybit Virtual Asset Platform Operator L.L.C. S.P.C)**: triggerPrice turns an order conditional, takeProfit and stopLoss attach to entries, reduceOnly and closeOnTrigger exist; open orders with orderFilter=StopOrder return stopOrderType and triggerPrice.
- **Coinbase Advanced Trade API (Coinbase, Inc.)**: order_configuration has stop_limit_stop_limit_gtc and gtd and trigger_bracket_gtc and gtd; historical order reads return the configuration and trigger status.
- **Deribit (Deribit FZE)**: stop_market, stop_limit, take_market, take_limit and trailing_stop with trigger_price and reduce_only; open orders by label include trigger orders.
- **Kraken API (Payward, Inc.)**: stop-loss, take-profit, trailing-stop and their limit forms with a trigger of last or index, reduce_only, and close[ordertype] conditional closes on the primary order.
- **OKX API (Aux Cayes FinTech Co. Ltd.)**: attachAlgoOrds with tpTriggerPx and slTriggerPx, algo orders, and closeOrderAlgo in the position read-back with trigger prices and types.

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

- **Bitstamp API (Bitstamp Ltd.)**: stop_price, trigger (last, index or mark) and reduce_only exist for derivatives markets only, with errors 400.047 to 400.060 naming stop fields; spot orders have no stop type.
- **Crypto.com Exchange API (Foris DAX Limited)**: OCO, OTO and OTOCO brackets through the advanced group; a plain stop-loss order type is not visible in the readable material and the API docs are unreadable.
- **dYdX (dYdX Trading Inc.)**: Stop and take-profit conditional orders exist (flag 32), but the Python client placed a stop market as a limit that filled at once, open since February 2025 (acc-19).
- **Gate (Gate)**: Price-triggered order tools for spot, futures and delivery plus trail orders, with list and get tools; field detail is unverified because the docs host answered 403.
- **Gemini Exchange API (Gemini Trust Company, LLC)**: exchange stop limit orders with stop_price are the only trigger type; status returns stop_price; no stop-market or reduce-only for spot.
- **HTX trading API (HTX)**: buy-stop-limit and sell-stop-limit with stop-price and operator, read back with those fields; spot only, no stop-market and no reduce-only.
- **Hyperliquid (Hyperliquid Labs)**: trigger orders with triggerPx, isMarket and tpsl plus normalTpsl grouping and reduceOnly; openOrders omits isTrigger, frontendOpenOrders shows it (acc-23), and the SDK's order() has no TP/SL parameters (acc-06).
- **KuCoin (KuCoin)**: The spot stop order model has stop_price but no stop type, and acc-34 saw stop-loss orders execute at once; futures orders take stop up or down with reduce_only and close_order.
- **MEXC API (MEXC (Comoros) Ltd)**: Spot order types are LIMIT, MARKET, LIMIT_MAKER, IOC and FOK with no stop; futures trigger orders with stopLossPrice exist but the reference marks order endpoints Under maintenance.

## Couldn't check

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

- **Coinbase MCP server (Coinbase for Agents) (Coinbase, Inc.)**: The tool table lists create, edit, cancel and close position; whether a stop or bracket configuration is accepted is not documented.

- not this job: Bithumb Open API (Bithumb Co., Ltd.): Order types are limit, price (market buy), market (market sell) and best; no stop, trigger or conditional type exists.
- not this job: Uniswap Trading API (Uniswap Labs): No stop or trigger orders; swaps execute at once or not at all.
- not this job: Upbit Open API (Dunamu Inc.): Order types are limit, price, market and best; no stop or trigger order exists.

## What stops agents finishing

- SDK has no stop or take-profit parameter and raw trigger fields return 422
- stop type cannot be chosen in the client, so the stop fills immediately
- open-orders read does not return the trigger flag, so a wrong stop looks right

## Around it

Before: crypto-exchanges.place-order. After: crypto-exchanges.read-back-state, crypto-exchanges.stream-updates.

## Where this comes from

Weight 8 of 100 in Crypto exchanges: 7 of 40 accounts; in four of them (acc-06, acc-23, acc-34, acc-19) the stop was placed as a plain order or executed at once

As data: https://www.anchorterminal.com/api/v1/use-cases/crypto-exchanges.protective-orders.json, or the MCP tool get_use_case with id crypto-exchanges.protective-orders. 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
