{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/crypto-exchanges.place-order/",
    "json": "https://www.anchorterminal.com/niches/crypto-exchanges.place-order/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/crypto-exchanges.place-order/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/crypto-exchanges.place-order/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| 5 | 15 | 20 | 14 | 12 |\n\n## What counts as done\n\nAn 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.\n\nMeasured, for our own tests: the order id and status arrive within 5 seconds, and the cancel takes one further call.\n\nHow 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\n\n## Does the job\n\nThe docs show it meets the test above, and nothing we read says otherwise.\n\n- **Binance API (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.\n- **Bybit (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.\n- **Deribit (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.\n- **Kraken API (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.\n- **Upbit Open API (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.\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- **Bitfinex API (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.\n- **Bitget (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.\n- **Bithumb Open API (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.\n- **Bitstamp API (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.\n- **Coinbase Advanced Trade API (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).\n- **Coinbase MCP server (Coinbase for Agents) (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.\n- **Crypto.com Exchange API (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.\n- **dYdX (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).\n- **Gate (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.\n- **Gemini Exchange API (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.\n- **HTX trading API (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).\n- **Hyperliquid (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.\n- **KuCoin (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.\n- **MEXC API (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.\n- **OKX API (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.\n- **Uniswap Trading API (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.\n\n## What stops agents finishing\n\n- minimum notional rejects risk-sized orders silently, so half the signals never trade\n- price above a threshold must be a whole number and the error does not say so\n- duplicate client order ids accepted, so a retry after a timeout executes twice\n\n## Around it\n\nBefore: 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.\n\n## Where this comes from\n\nWeight 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)\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/crypto-exchanges.place-order.json, or the MCP tool get_use_case with id crypto-exchanges.place-order. 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": "Place, amend or cancel a spot or perp order and confirm it",
        "url": ""
      }
    ],
    "description": "Place, amend or cancel a spot or perp order and confirm it: 5 companies fully do it, 15 with a limit, 20 carry the tag. Every listing in Crypto exchanges with the reason and a source.",
    "facts": null,
    "h1": "Place, amend or cancel a spot or perp order and confirm it",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/crypto-exchanges.place-order/",
    "published": "",
    "section": "agents",
    "title": "Place, amend or cancel a spot or perp order and confirm it | Anchor…",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/crypto-exchanges.place-order/"
  },
  "tokens": {
    "markdown": 1900,
    "slim": 380
  },
  "version": 1
}
