# Create or manage an exchange-side grid or DCA bot

> Create or manage an exchange-side grid or DCA bot: 2 companies fully do it, 3 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.exchange-bots/
- Markdown: https://www.anchorterminal.com/niches/crypto-exchanges.exchange-bots/index.md (~1,150 tokens)
- Slim: https://www.anchorterminal.com/niches/crypto-exchanges.exchange-bots/index.min.md (~230 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/crypto-exchanges.exchange-bots/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

Two or three companies' docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 2 | 3 | 20 | 2 | 2 |

## What counts as done

The bot is created and visible in a list call with its parameters, and the create call either succeeds or returns an error naming the wrong field.

Measured, for our own tests: the bot is created in one create call.

How agents ask for it: set up a grid bot on SUI perp between 3 and 4 dollars; list my running grid bots; amend the DCA bot's amount

## Does the job

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

- **Bitget (BTG Technology Holdings Limited)**: Grid section has validate, create, modify, add investment, close and detail endpoints for grid and neutral grid bots; validate checks parameters without creating.
- **Crypto.com Exchange API (Foris DAX Limited)**: cdcx bot create, list, pause, resume, update and terminate for DCA and GRID bots, in the mutate tier with terminate as dangerous.

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

- **Bybit (Bybit Virtual Asset Platform Operator L.L.C. S.P.C)**: Futures grid bot endpoints exist, but creating one through the MCP skill failed with 400006 naming no field and the correct schema was only in the TypeScript source (acc-17).
- **Gate (Gate)**: AI hub tools create spot, margin, infinite and futures grid and martingale bots, list running ones and stop them; there is no amend tool and no first-hand success.
- **OKX API (Aux Cayes FinTech Co. Ltd.)**: Grid and DCA endpoints and 18 bot tools exist, but creating a contract grid bot was refused with 51000 for an instrument the list and amend endpoints accept (acc-14); DCA amend is missing (acc-39).

- not this job: Binance API (Binance): No grid or DCA bot endpoints in the spot API reference or the MCP scopes.
- not this job: Bitfinex API (iFinex Inc.): No grid or DCA bot endpoints in the reference.
- not this job: Bithumb Open API (Bithumb Co., Ltd.): No bot endpoints; TWAP split orders are the only server-side strategy.
- not this job: Bitstamp API (Bitstamp Ltd.): No bot endpoints in the API reference.
- not this job: Coinbase Advanced Trade API (Coinbase, Inc.): No bot endpoints in the spec.
- not this job: Coinbase MCP server (Coinbase for Agents) (Coinbase, Inc.): No bot tools.
- not this job: Deribit (Deribit FZE): No grid or DCA bot methods.
- not this job: dYdX (dYdX Trading Inc.): No server-side bots.
- not this job: Gemini Exchange API (Gemini Trust Company, LLC): No bot endpoints.
- not this job: HTX trading API (HTX): Grid orders are listed as not supported by API.
- not this job: Hyperliquid (Hyperliquid Labs): No server-side grid or DCA bots; TWAP and trailing stop are order types.
- not this job: Kraken API (Payward, Inc.): Grid and DCA skills run in the agent, not on the exchange.
- not this job: KuCoin (KuCoin): No bot endpoints in the reference navigation.
- not this job: MEXC API (MEXC (Comoros) Ltd): No bot endpoints.
- not this job: Uniswap Trading API (Uniswap Labs): No server-side bots.
- not this job: Upbit Open API (Dunamu Inc.): No bot endpoints.

## What stops agents finishing

- create refused for an instrument the list and amend endpoints accept
- documented parameter names and types differ from the API's

## Around it

Before: crypto-exchanges.mcp-from-assistant, crypto-exchanges.market-data-read. After: crypto-exchanges.read-back-state.

## Where this comes from

Weight 2 of 100 in Crypto exchanges: 2 of 40 accounts, both failures on create (Bybit 400006, OKX 51000)

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