# Binance API vs Deribit (slim)

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

- Full: https://www.anchorterminal.com/compare/binance-vs-deribit.md (~3,800 tokens) · this version ~1,730 tokens · JSON https://www.anchorterminal.com/compare/binance-vs-deribit.json · canonical https://www.anchorterminal.com/compare/binance-vs-deribit
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-04
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Binance API scores 63.2 (B) on agent readiness against Deribit's 59 (C), and leads in 4 of 7 scored categories. Both do exchange spot trading.

- Binance API: B 63.2, rank #473 of 1349 · https://www.anchorterminal.com/tools/binance.min.md
- Deribit: C 59, rank #646 of 1349 · https://www.anchorterminal.com/tools/deribit.min.md
- Binance API, 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 Security & auth, 72 against 62; Payments & pricing, 35 against 25; Maintenance & community, 81 against 65. Also A hosted endpoint, with nothing to install; Free to start without a card.
- Deribit, good for An agent trading crypto options, dated futures and perpetuals for an institutional or retail Deribit account, and anyone migrated from Coinbase International Exchange.

| Category | Binance API | Deribit |
| --- | --- | --- |
| Reliability (16%) | 45 | 45 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 86 | 88 |
| Agent ergonomics (13%) | 76 | 74 |
| Security & auth (14%) | 72 | 62 |
| Payments & pricing (10%) | 35 | 25 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 81 | 65 |
| Transparency & trust (7%) | 43 | 46 |

| Fact (where they differ) | Binance API | Deribit |
| --- | --- | --- |
| Vendor | Binance | Deribit FZE |
| Hosted endpoint | `https://agent.binance.com/mcp/agentic` | no (local only) |
| Transports | Streamable HTTP |  |
| Auth | OAuth or key | API key |
| 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 | Proprietary hosted exchange. The API is documented under the Deribit docs with an OpenAPI 3.0 file; no official client library is published |
| Tools exposed | none | 0 |
| Last release | 2026-10-30 | 2026-10-13 |
| Terms last updated | couldn't be read | 2026-08-13 |
| Privacy policy last updated | couldn't be read | no document linked |
| Customer content may train models | couldn't be read | not found in the text |
| Terms restrict automated access | couldn't be read | yes |
| Terms restrict benchmarking | couldn't be read | not found in the text |
| Terms or service can change without notice | couldn't be read | not found in the text |
| Arbitration or class-action waiver | couldn't be read | not found in the text |
| Popularity | 4.9k stars | none |

Why the edge:
- Maintenance & community, Binance API +16: 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.); Deribit 65 (Read as a closed service. The JSON-RPC changelog's latest production entry is 13 October 2026 and an entry dated 5 November 2026 describes the next release; Deribit's posts of 14 October and 2 November 2026 change fees (30). Entries of 18 August, 15 September and 13 October 2026, three in 90 days (20). A public changelog and a support site; whether support answers wasn't tested and the support site refused our reader (10 of 15). No official SDK and no MCP registry entry (0). The OpenAPI and AsyncAPI files are maintained with the docs (5 of 10). Total 65.)
- Security & auth, Binance API +10: 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.); Deribit 62 (Keys carry five scopes at read, read_write or none, `ip:ADDR` and `expires` limits, can be disabled, reset and removed by API, and self-generated Ed25519 or RSA keys keep the private half off Deribit. The HTTP `client_credentials` example passes `client_secret` in the query string, a documented option, so 10 off (20 of 30). `trade:read` and `wallet:none` give read-only and no-withdrawal keys and the 5 August 2025 release stopped `account:read` keys reading other keys' secrets; no per-order confirmation and the address allow-list article was unreadable (16 of 20). The API returns no untrusted content (10). `private/list_api_keys`, the transaction log and order history let an operator see what a key did, but no per-key call log was found (8 of 15). A HackerOne bug bounty per the support article title and HackerOne's customer story, neither page read first-hand (insights.deribit.com/bug-bounty answered 403), a VARA licence, and no security.txt on www.deribit.com (8 of 20). Total 62.)
- Payments & pricing, Binance API +10: 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.); Deribit 25 (No machine payment protocol (0). The fee schedule is on support.deribit.com, which answered 403; Deribit's own posts give VIP4 to VIP7 taker fees and the 0 bps linear options maker fee, so partial prices are public but the lowest tier is unchecked (5 of 20). Public market data needs no key and the test environment is free, with no card anywhere (20). A person signs up in a browser with identity checks before any key exists (0). Total 25.)