# Move funds between wallets, portfolios or sub-accounts

> Move funds between wallets, portfolios or sub-accounts: 2 companies fully do it, 7 with a limit, 19 carry the tag. Every listing in Crypto exchanges with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/crypto-exchanges.transfers/
- Markdown: https://www.anchorterminal.com/niches/crypto-exchanges.transfers/index.md (~1,350 tokens)
- Slim: https://www.anchorterminal.com/niches/crypto-exchanges.transfers/index.min.md (~380 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/crypto-exchanges.transfers/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 | 7 | 19 | 2 | 0 |

## What counts as done

Balances on both sides change by the amount and the transfer appears in the account's bills or ledger with an id.

Measured, for our own tests: the balances change within 10 seconds.

How agents ask for it: move 100 USDC from spot to futures; fund the agent portfolio from my main one; transfer to the sub-account

## Does the job

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

- **Hyperliquid (Hyperliquid Labs)**: usdClassTransfer moves USDC between spot and perp, with a subaccount form, and usdSend moves to another address; all are signed actions, so an agent wallet needs care.
- **OKX API (Aux Cayes FinTech Co. Ltd.)**: POST /api/v5/asset/transfer moves funds between funding and trading accounts and to sub-accounts with a key that need not withdraw.

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

- **Binance API (Binance)**: The MCP Transfer scope moves funds between wallets inside the Agentic sub-account only; the first deposit from the main account is a manual step the agent cannot do.
- **Bitget (BTG Technology Holdings Limited)**: The MCP read-only flag names transfer among the writes it blocks, so a transfer verb exists; the API transfer endpoints were not opened.
- **Coinbase Advanced Trade API (Coinbase, Inc.)**: The transfer permission allows moves between the account's portfolios and not external withdrawals; the move-funds call was not read in detail.
- **Coinbase MCP server (Coinbase for Agents) (Coinbase, Inc.)**: The CLI key's Transfer permission moves funds between the person's portfolios only; no MCP transfer tool is listed.
- **Crypto.com Exchange API (Foris DAX Limited)**: The funding group covers wallet deposit and withdrawal endpoints; a sub-account transfer command is not shown in the readable material.
- **Deribit (Deribit FZE)**: Subaccount transfer methods exist, but they sit under the wallet scope which also enables withdrawals.
- **KuCoin (KuCoin)**: Flex Transfer and transfer quota endpoints appear in the reference navigation; their fields were not read.
- **MEXC API (MEXC (Comoros) Ltd)**: User universal transfer endpoints exist; their field detail was not read.

## Couldn't check

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

- **Bitfinex API (iFinex Inc.)**: A wallet transfer endpoint exists in the reference index but was not opened in this pass.
- **Bitstamp API (Bitstamp Ltd.)**: Sub-account transfer endpoints were not located in the page text in this pass.
- **Bybit (Bybit Virtual Asset Platform Operator L.L.C. S.P.C)**: Asset tools list transfer queries; the inter-account transfer endpoint itself was not opened.
- **dYdX (dYdX Trading Inc.)**: Subaccount transfers are chain messages not covered on the pages read.
- **Gate (Gate)**: A wallet module exists in the local server; its transfer tools were not read.
- **Gemini Exchange API (Gemini Trust Company, LLC)**: Account transfer endpoints for Fund Manager keys were not read.
- **HTX trading API (HTX)**: Spot to futures transfer endpoints were not read in this pass.
- **Kraken API (Payward, Inc.)**: Spot to futures wallet transfers were not read in this pass.
- **Upbit Open API (Dunamu Inc.)**: Pocket (sub-account) transfer endpoints were not read in this pass.

- not this job: Bithumb Open API (Bithumb Co., Ltd.): Deposits and withdrawals only; no internal wallet or sub-account transfer endpoint in the index.
- not this job: Uniswap Trading API (Uniswap Labs): No wallets or portfolios to move between.

## What stops agents finishing

- agent sub-account starts empty and only the human can fund it (Binance)
- transfers between portfolios need a separate Transfer permission (Coinbase)
- withdrawals are dangerous-tier and gated behind a flag the agent should not hold

## Around it

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

## Where this comes from

Weight 2 of 100 in Crypto exchanges: No first-hand account; rests on the Binance, Coinbase, Kraken and Bitget vendor pages that each scope transfers inside the account and keep withdrawals off, and on the equal-weight floor

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