Place, amend or cancel a spot or perp order and confirm it
Four or more companies' docs show a full fit.
What counts as done
An order id and status from the exchange, the order readable back by the client order id the agent sent, and the agent able to cancel it. A rejected order carries a reason that names the bad field.
Measured, for our own tests: the order id and status arrive within 5 seconds, and the cancel takes one further call. No docs we read state these figures, so they don't count against a listing here.
How agents ask for it: buy 0.01 BTC at 60,000 limit
, market sell half my ETH
, cancel that order
, place this order with my client id and tell me when it fills
Does the job 5
The docs show it meets the test above, and nothing we read says otherwise.
| Listing | Why |
|---|---|
| Binance API B Binance | POST /api/v3/order takes newClientOrderId, unique among open orders with duplicates rejected; GET and DELETE accept origClientOrderId; rejections read Filter failure: MIN_NOTIONAL, LOT_SIZE or PRICE_FILTER. source |
| Bybit C Bybit Virtual Asset Platform Operator L.L.C. S.P.C | orderLinkId is always unique for spot, perps and futures and required for options; open-order queries by orderLinkId; errors such as 170136 and 110017 name the quantity or price rule. Create is asynchronous. source |
| Deribit C Deribit FZE | private/buy and sell with label, post_only, reduce_only and trigger fields; cancel and edit by label; errors carry a code and name such as invalid_arguments. acc-02 calls Deribit the reliable exception. source |
| Kraken API BB Payward, Inc. | AddOrder with cl_ord_id that uniquely identifies an open order, validate=true to check without trading, and cancel or query by cl_ord_id; the CLI maps these to --cl-ord-id and --validate. source |
| Upbit Open API C Dunamu Inc. | Orders with ord_type limit, price, market or best and an identifier that must be unique across the account and is never reusable; lookup by uuid or identifier; orders/test validates first. source |
Does the job, with a limit 16
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.
| Listing | Why |
|---|---|
| Bitfinex API C iFinex Inc. | Submit order takes a cid and returns a notification array; orders are fetched by cid only together with cid_date, and the docs show no rejection text naming the bad field. source |
| Bitget C BTG Technology Holdings Limited | POST /api/v3/trade/place-order with clientOid (1 to 32 chars, orderId wins if both sent) and lookup by clientOid; the error list gives codes with generic text, so a rejection may not name the field. acc-33 hit a 5 dollar minimum. source |
| Bithumb Open API D Bithumb Co., Ltd. | POST /v2/orders with limit, price, market or best types and an optional client_order_id of 1 to 36 chars, readable back by it; the error code page was not opened, and keys need a verified Korean account. source |
| Bitstamp API D Bitstamp Ltd. | Order endpoints take client_order_id and errors name the field (400.008 malformed client_order_id, 400.020 below minimum); duplicate client_order_ids are allowed since November 2023, so a retry can execute twice. source |
| Coinbase Advanced Trade API B Coinbase, Inc. | client_order_id must be unique and a repeat returns the existing order; a preview endpoint and enumerated failure reasons exist; but 40 to 55 per cent of signed requests got bare 401s from one HTTP client (acc-20). source |
| Coinbase MCP server (Coinbase for Agents) C Coinbase, Inc. | orders_preview then orders_create with a portfolio named; Claude asks for confirmation; the docs warn that high-reasoning modes stop short of executing and lower-tier models pick the wrong product. source |
| Crypto.com Exchange API D Foris DAX Limited | cdcx_trade_order with acknowledged: true, --dry-run preview and order detail by client_oid; the Exchange API docs host answers 403, so rejection texts and min-size rules are unverified. source |
| dYdX BB dYdX Trading Inc. | Orders are signed chain transactions with a unique 32-bit clientId; the indexer fetches an order by its own id, and market orders are limits with slippage that the client reports as limit (acc-19). source |
| Gate C Gate | cex_spot_create_spot_order exists locally and hosted; on the hosted server the text client id is overwritten with remote_mcp (acc-11); the API v4 docs on gate.com answered 403 here. source |
| Gemini Exchange API BB Gemini Trust Company, LLC | /v1/order/new takes client_order_id and /v1/order/cancel by order_id; order status is fetched by order_id only and the spec does not say duplicates are rejected. source |
| HTX trading API E HTX | client-order-id up to 64 chars is no longer checked for uniqueness, so the latest order wins on lookup; errors name the rule (order-value-min-error: Order total cannot be lower than 5 USDT). source |
| Hyperliquid D Hyperliquid Labs | order action with cloid, reduceOnly and per-order statuses; unrounded prices give Px is invalid and BTC prices above 100,000 must be whole numbers (acc-07, acc-32); errors are strings without codes. source |
| KuCoin C KuCoin | clientOid up to 40 chars with lookup and cancel by clientOid and an order test endpoint; the SDK says not to reuse a clientOid but not what happens if you do; docs pages render by script. source |
| MEXC API C MEXC (Comoros) Ltd | newClientOrderId with lookup and cancel by origClientOrderId, POST /api/v3/order/test, and errors that name the rule (minimum transaction volume cannot be less than 0.5 USDT); uniqueness of the client id is not stated. source |
| OKX API B Aux Cayes FinTech Co. Ltd. | clOrdId unique among live orders and reusable after terminal state, used to query, cancel and amend; instruments publish tickSz, lotSz and minSz; but 51000 is a generic Parameter error. source |
| Uniswap Trading API B Uniswap Labs | /quote then /swap builds a transaction the agent signs and broadcasts; there is no order id, status or cancel, and quotes expire in 30 seconds. source |
What stops agents finishing
- minimum notional rejects risk-sized orders silently, so half the signals never trade
- price above a threshold must be a whole number and the error does not say so
- duplicate client order ids accepted, so a retry after a timeout executes twice
Around it
Before: crypto-exchanges.market-data-read, crypto-exchanges.rehearse-no-money, decision-models.size-position. After: crypto-exchanges.protective-orders, crypto-exchanges.read-back-state, notifications.telegram-alert.
Where this comes from
Weight 14 of 100 in Crypto exchanges: 12 of 40 accounts place orders; the repeated failures are price and size formatting (acc-07, acc-25, acc-32, acc-33) and order type reported wrongly (acc-19)
The same as data: /api/v1/use-cases/crypto-exchanges.place-order.json, or the MCP tool get_use_case with id crypto-exchanges.place-order. Other jobs in this category: /api/v1/niches?category=crypto-exchanges.
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.