# Binance API vs Bybit

> Binance scores 63.2 (B) to Bybit's 57.3 (C) for exchange spot trading. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/binance-vs-bybit
- Markdown: https://www.anchorterminal.com/compare/binance-vs-bybit.md (~4,700 tokens)
- 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-03

Binance API scores 63.2 (B) on agent readiness against Bybit's 57.3 (C), and leads in 4 of 7 scored categories. Bybit leads on payments & pricing and transparency & trust. Both do exchange spot trading.

- Binance API: grade B, 63.2/100, rank #448 of 1349. Markdown https://www.anchorterminal.com/tools/binance.md · JSON https://www.anchorterminal.com/api/v1/tools/binance.json
- Bybit: grade C, 57.3/100, rank #745 of 1349. Markdown https://www.anchorterminal.com/tools/bybit.md · JSON https://www.anchorterminal.com/api/v1/tools/bybit.json
- Best crypto exchange APIs and MCP servers for AI agents: https://www.anchorterminal.com/best/crypto-exchanges/index.md
- All 210 exchanges comparisons: https://www.anchorterminal.com/compare/crypto-exchanges/index.md

## Which one, for what

### Binance API (B)

Good for: An agent trading a funded Binance account outside the prohibited countries, with the deepest set of markets in this group and a free testnet.

Ahead on:
- Schema & documentation, 86 against 73
- Agent ergonomics, 76 against 66
- Security & auth, 72 against 60
- Maintenance & community, 81 against 66

Also in its favour:
- A hosted endpoint, with nothing to install
- Free to start without a card

Watch for: No status page or incident history found on binance.com or in the API docs

### Bybit (C)

Good for: An agent trading spot, perpetuals, futures and options in a person's Bybit account outside the excluded jurisdictions, with a demo environment to rehearse on.

Ahead on:
- Payments & pricing, 40 against 35
- Transparency & trust, 51 against 43

Also in its favour:
- Runs on your own machine

Watch for: No status page, incident history or SLA was found; the terms say the API is not guaranteed to be available


## Why the edge

### Maintenance & community: Binance API +15

- Binance API (81): Read as a closed service. The spot changelog's newest entry is 30 October 2026, the MCP docs are dated 30 October and binance-cli v2.2.0 shipped on 20 October (30). Changelog entries on 2 September, 18 September, 27 October and 30 October (20). A public changelog, connectors pushed in October and a Skills Hub merging pull requests weekly; issue replies not read (10 of 15). Official connectors in nine languages current as of October 2026; the MCP server is not in the official registry (15). Connector CI not read; the CLI publishes release installers (6 of 10). 30 + 20 + 10 + 15 + 6 = 81.
- Bybit (66): Read as a hosted service with an open-source MCP server. The MCP package shipped 2.1.26 on 30 October 2026 and the V5 changelog's latest entry is 29 October (30). 31 npm versions since 16 April 2026, 11 of them in the last 90 days, and 24 changelog entries in the same window (20). The trading-mcp repository has 4 open issues and 18 forks; whether issues get answers was not checked, and the API has no public forum we could read (10 of 25). Not in the official MCP registry (0). The package has four dependencies, no install scripts, a publish workflow and no test workflow (6 of 10). 66.

### Schema & documentation: Binance API +13

- Binance API (86): The docs are Markdown in a public repository with a Postman collection and a Swagger spec, but the spec was last pushed in October 2024 (20 of 25). llms.txt and llms-full.txt on developers.binance.com (10). Each endpoint states its weight, parameters and notes on behaviour, with less on when not to use one (15 of 20). Enums for order types, time in force and symbol filters, required columns in the parameter tables (12 of 15). Request and response examples throughout and an error code list with messages (14 of 15). A dated changelog since 2018 with retirements announced months ahead, such as the 2 September 2026 field removal notified on 2 December 2025 (15). 20 + 10 + 15 + 12 + 14 + 15 = 86.
- Bybit (73): No OpenAPI or other machine-readable contract for the REST API; the MCP server's 398 tools have zod schemas turned into JSON Schema, so the contract exists for the MCP surface only (12 of 25). No llms.txt; the docs are a public Docusaurus repository (bybit-exchange/docs) whose MDX source an agent can read (5 of 10). The MCP tool descriptions state purpose, rules and an agent hint per tool, and the API reference gives one page per endpoint (15 of 20). Parameters are typed with enums such as category and orderType and required flags (12 of 15). Request and response examples on each endpoint page and an error code page of about 750 codes with text (14 of 15). A dated changelog with 24 entries in the last 90 days, versioned V3 to V5 (15). 73.

### Security & auth: Binance API +12

- Binance API (72): API keys with HMAC, RSA or Ed25519 signatures, permissions for reading, trading, futures and withdrawals, an IP restriction, revocation in API Management, and OAuth with four scopes on the MCP server; no key expiry found (28 of 30). Read-only keys, sub-accounts, withdrawals only with an IP restriction, and the MCP server's isolated Agentic sub-account with no withdrawal scope and confirmation before writes (18 of 20). The API returns no untrusted content (10). Keys are listed in API Management and used weight is returned per call, but no per-call log for the operator was found (6 of 15). security.txt with a contact and no expiry, a Bugcrowd programme named in the proof-of-solvency repository, no certification read (10 of 20). 28 + 18 + 10 + 6 + 10 = 72.
- Bybit (60): API keys scoped by product group with a readOnly flag, a separate Withdraw value, IP binding, a 90-day expiry for unbound keys, HMAC or RSA signing, and revocation on the management page; no OAuth (24 of 30). A read-only key and a withdrawal-free key are first-class, but the MCP server has no read-only mode and relies on the client's approval prompt for writes (14 of 20). Tools return the exchange's own data, not third-party text (10). The API key info endpoint shows permissions, IPs and expiry, and an IP change log exists for institutional accounts, but no per-call audit log was found (7 of 15). No security.txt on bybit.com or the docs host, no disclosure policy or bug bounty found on a page we could read, proof-of-reserves articles in the help centre (5 of 20). 60.

### Agent ergonomics: Binance API +10

- Binance API (76): limit on depth, trades and klines, a symbols filter on exchangeInfo and tickers, and SBE encoding, though fields cannot be selected (16 of 25). fromId, startTime, endTime and limit on history endpoints (16 of 20). Error codes with messages an agent can branch on, such as the rate limit and timestamp errors (17 of 20). newClientOrderId on orders, a cancel-replace endpoint and the 5xx unknown-status rule, but no idempotency key on other writes (12 of 20). Connectors in nine languages, a CLI with testnet and demo profiles, and a timestamped HMAC or Ed25519 signature on every private call (15). 16 + 16 + 17 + 12 + 15 = 76.
- Bybit (66): Read for the API with the MCP server beside it. The MCP server has 398 tools in one list with no toolset, module or read-only switch (5 of 25, nothing added back). V5 reads take limit and cursor and category filters (15 of 20). retCode and retMsg on every response with a code list an agent can branch on, though create-order answers before the order is final and the docs say to confirm over WebSocket (14 of 20). orderLinkId makes order retries safe and every MCP tool carries readOnlyHint and destructiveHint (17 of 20). Five required fields on an order, official SDKs in Python, Go, Java and .NET (15). 66.

### Transparency & trust: Bybit +8

- Binance API (43): The editorial half. A closed service whose Terms of Use couldn't be read; the docs, connectors, CLI and skills are MIT on GitHub (10 of 30). The privacy notice couldn't be read, so no retention or subprocessor statement was checked; the prohibited-countries list is public and dated (5 of 30). The changelog gives retirement dates for SBE schemas and FIX fields months ahead (16 of 20). No subprocessor or data-location statement read (0 of 20). 10 + 5 + 16 + 0 = 31.
- Bybit (51): The editorial half. A closed hosted service. The terms read are the UAE entity's PDF served from bybit.com, clear on API use and availability, but the global terms page renders by script and was not read; the MCP server is MIT (12 of 30). The privacy policy was not read, so data handling is unscored (5 of 30). The changelog dates removals and response changes but gives no notice period or deprecation policy (10 of 20). No subprocessor list or data location statement was read (0 of 20). 27.

### Payments & pricing: Bybit +5

- Binance API (35): No machine payment protocol (0). A 0.1 per cent standard spot fee is stated in the fee FAQ; the maker and taker table and futures fees load by script and weren't read (15 of 20). Public market data needs no key and the testnet is free with a GitHub login (20). A person signs up, passes Verified Plus verification, deposits and mints a key (0). 0 + 15 + 20 + 0 = 35.
- Bybit (40): No machine payment protocol (0). The fee schedule is public without login, with VIP 0 maker and taker rates per product and the tier criteria (20). Reading market data needs no key and the demo environment costs nothing, no card is asked for at sign-up (20). A person must register, pass identity verification and mint the key in a browser (0). 40.

## Score by category

| Category | Weight | Binance API | Bybit | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 45 | 45 | even |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 86 | 73 | Binance API +13 |
| Agent ergonomics | 13% (16.2 this run) | 76 | 66 | Binance API +10 |
| Security & auth | 14% (17.5 this run) | 72 | 60 | Binance API +12 |
| Payments & pricing | 10% (12.5 this run) | 35 | 40 | Bybit +5 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 81 | 66 | Binance API +15 |
| Transparency & trust | 7% (8.8 this run) | 43 | 51 | Bybit +8 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **63.2 · B** | **57.3 · C** | |

## Facts side by side

| Fact | Binance API | Bybit |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Binance | Bybit |
| Hosted endpoint | `https://agent.binance.com/mcp/agentic` | no (local only) |
| Transports | Streamable HTTP | stdio |
| Auth | OAuth or key | API key |
| Pricing | Pay per use | Pay per use |
| x402 | no | no |
| Licence | Proprietary hosted service under Binance's Terms of Use, which load by script and weren't read. The API docs, connectors, CLI and Skills Hub are open on GitHub under MIT | none |
| Tools exposed | none | 398 |
| Read-only variant documented | no | yes |
| llms.txt | yes | no |
| Last release | 2026-10-30 | 2026-10-30 |
| Terms last updated | couldn't be read | couldn't be read |
| Privacy policy last updated | couldn't be read | couldn't be read |
| Customer content may train models | couldn't be read | couldn't be read |
| Terms restrict automated access | couldn't be read | couldn't be read |
| Terms restrict benchmarking | couldn't be read | couldn't be read |
| Terms or service can change without notice | couldn't be read | couldn't be read |
| Arbitration or class-action waiver | couldn't be read | couldn't be read |
| Popularity | 4.9k stars | 43 stars |

## Verdicts

**Binance API.** Binance publishes numeric rate limits, a free testnet with FIX, connectors in eight languages and, since late October 2026, a remote MCP server that trades only in a dedicated sub-account with no withdrawal scope. There is no status page, the terms and privacy notice could not be read, and the MCP tool list is not published.

**Bybit.** Bybit publishes per-endpoint rate limits, a demo environment, scoped keys with a read-only flag and IP binding, and an official stdio MCP server whose 398 tools carry read-only and destructive annotations. There is no status page, no OpenAPI file, no SLA, the MCP server has no toolsets, and the global terms and privacy pages are drawn by script.

## Before you call either

### Binance API

1. Read the X-MBX-USED-WEIGHT and X-MBX-ORDER-COUNT headers and stop on 429 for the Retry-After seconds; a 418 ban runs 2 minutes to 3 days
2. Treat a 5xx on an order as unknown, not failed, and query the order by origClientOrderId before retrying
3. Use an Ed25519 key with an IP restriction and only the reading and trading permissions; never enable withdrawals for an agent key
4. Develop on testnet.binance.vision with BINANCE_API_ENV=testnet; it resets about monthly without notice
5. For the MCP route, the person must fund the Agentic sub-account from the web UI first; the agent cannot move funds in from the main account

### Bybit

1. Create a key with only the permission groups the task needs, set readOnly for research keys, leave Withdraw off and bind an IP, or the key expires after 90 days
2. Send a unique orderLinkId on every order and reuse it when amending or cancelling, since create-order is asynchronous and confirmed over WebSocket
3. Read X-Bapi-Limit-Status before bursts and wait until X-Bapi-Limit-Reset-Timestamp on retCode 10006; on HTTP 403 stop all sessions for at least 10 minutes
4. Test on api-demo.bybit.com with a demo key from the production account, not on testnet demo mode, which the docs call meaningless
5. Run the MCP server with BYBIT_TESTNET=true first, and only in a client that shows a per-call approval, because the server has no read-only mode of its own

## Questions

### Which is better for AI agents, Binance API or Bybit?

Binance API scores 63.2 (B) on agent readiness against Bybit's 57.3 (C), and leads in 4 of 7 scored categories. Bybit leads on payments & pricing and transparency & trust.

### Do Binance API and Bybit need an API key?

Binance API takes an API key or an OAuth sign-in. Bybit needs an API key.

### Can an agent call Binance API and Bybit without installing anything?

Binance API has a hosted endpoint at https://agent.binance.com/mcp/agentic. Bybit runs on your own machine, with no hosted endpoint listed.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/binance-vs-bybit.json, and with the fewest tokens: https://www.anchorterminal.com/compare/binance-vs-bybit.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "binance", "b": "bybit"}`. From a terminal: `anchor compare binance bybit`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/binance.json and https://www.anchorterminal.com/api/v1/tools/bybit.json

## Other comparisons with Binance API or Bybit

- [Bitfinex API vs Bybit](https://www.anchorterminal.com/compare/bitfinex-vs-bybit.md)
- [Bitget vs Bybit](https://www.anchorterminal.com/compare/bitget-vs-bybit.md)
- [Bithumb Open API vs Bybit](https://www.anchorterminal.com/compare/bithumb-vs-bybit.md)
- [Bitstamp API vs Bybit](https://www.anchorterminal.com/compare/bitstamp-vs-bybit.md)
- [Bybit vs Coinbase Advanced Trade API](https://www.anchorterminal.com/compare/bybit-vs-coinbase-advanced-trade.md)
- [Bybit vs Coinbase MCP server (Coinbase for Agents)](https://www.anchorterminal.com/compare/bybit-vs-coinbase-mcp.md)
- [Bybit vs Crypto.com Exchange API](https://www.anchorterminal.com/compare/bybit-vs-crypto-com-exchange.md)
- [Bybit vs Deribit](https://www.anchorterminal.com/compare/bybit-vs-deribit.md)
- [Bybit vs dYdX](https://www.anchorterminal.com/compare/bybit-vs-dydx.md)
- [Bybit vs Gate](https://www.anchorterminal.com/compare/bybit-vs-gate-io.md)
- [Bybit vs Gemini Exchange API](https://www.anchorterminal.com/compare/bybit-vs-gemini-exchange.md)
- [Bybit vs HTX trading API](https://www.anchorterminal.com/compare/bybit-vs-htx.md)
- [Bybit vs Hyperliquid](https://www.anchorterminal.com/compare/bybit-vs-hyperliquid.md)
- [Bybit vs Kraken API](https://www.anchorterminal.com/compare/bybit-vs-kraken.md)
- [Bybit vs KuCoin](https://www.anchorterminal.com/compare/bybit-vs-kucoin.md)
- [Bybit vs MEXC API](https://www.anchorterminal.com/compare/bybit-vs-mexc.md)
- [Bybit vs OKX API](https://www.anchorterminal.com/compare/bybit-vs-okx.md)
- [Bybit vs Uniswap Trading API](https://www.anchorterminal.com/compare/bybit-vs-uniswap.md)
- [Bybit vs Upbit Open API](https://www.anchorterminal.com/compare/bybit-vs-upbit.md)
- [Binance API vs Bitfinex API](https://www.anchorterminal.com/compare/binance-vs-bitfinex.md)
- [Binance API vs Bitget](https://www.anchorterminal.com/compare/binance-vs-bitget.md)
- [Binance API vs Bithumb Open API](https://www.anchorterminal.com/compare/binance-vs-bithumb.md)
- [Binance API vs Bitstamp API](https://www.anchorterminal.com/compare/binance-vs-bitstamp.md)
- [Binance API vs Coinbase Advanced Trade API](https://www.anchorterminal.com/compare/binance-vs-coinbase-advanced-trade.md)
- [Binance API vs Coinbase MCP server (Coinbase for Agents)](https://www.anchorterminal.com/compare/binance-vs-coinbase-mcp.md)
- [Binance API vs Crypto.com Exchange API](https://www.anchorterminal.com/compare/binance-vs-crypto-com-exchange.md)
- [Binance API vs Deribit](https://www.anchorterminal.com/compare/binance-vs-deribit.md)
- [Binance API vs Gate](https://www.anchorterminal.com/compare/binance-vs-gate-io.md)
- [Binance API vs Gemini Exchange API](https://www.anchorterminal.com/compare/binance-vs-gemini-exchange.md)
- [Binance API vs HTX trading API](https://www.anchorterminal.com/compare/binance-vs-htx.md)
- [Binance API vs Hyperliquid](https://www.anchorterminal.com/compare/binance-vs-hyperliquid.md)
- [Binance API vs Kraken API](https://www.anchorterminal.com/compare/binance-vs-kraken.md)
- [Binance API vs KuCoin](https://www.anchorterminal.com/compare/binance-vs-kucoin.md)
- [Binance API vs MEXC API](https://www.anchorterminal.com/compare/binance-vs-mexc.md)
- [Binance API vs OKX API](https://www.anchorterminal.com/compare/binance-vs-okx.md)
- [Binance API vs Uniswap Trading API](https://www.anchorterminal.com/compare/binance-vs-uniswap.md)
- [Binance API vs Upbit Open API](https://www.anchorterminal.com/compare/binance-vs-upbit.md)
- [Binance API vs dYdX](https://www.anchorterminal.com/compare/binance-vs-dydx.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp