# Bybit vs Deribit (slim)

> Deribit scores 59 (C) to Bybit's 57.3 (C) for exchange market data. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/bybit-vs-deribit.md (~4,100 tokens) · this version ~2,030 tokens · JSON https://www.anchorterminal.com/compare/bybit-vs-deribit.json · canonical https://www.anchorterminal.com/compare/bybit-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)

Deribit scores 59 (C) on agent readiness against Bybit's 57.3 (C), and leads in 3 of 7 scored categories. Bybit leads on payments & pricing and transparency & trust. Both do exchange market data.

- Bybit: C 57.3, rank #712 of 1349 · https://www.anchorterminal.com/tools/bybit.min.md
- Deribit: C 59, rank #646 of 1349 · https://www.anchorterminal.com/tools/deribit.min.md
- Bybit, 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 25; Transparency & trust, 51 against 46. Also Runs on your own machine.
- 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. Ahead on Schema & documentation, 88 against 73; Agent ergonomics, 74 against 66.

| Category | Bybit | Deribit |
| --- | --- | --- |
| Reliability (16%) | 45 | 45 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 73 | 88 |
| Agent ergonomics (13%) | 66 | 74 |
| Security & auth (14%) | 60 | 62 |
| Payments & pricing (10%) | 40 | 25 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 66 | 65 |
| Transparency & trust (7%) | 51 | 46 |

| Fact (where they differ) | Bybit | Deribit |
| --- | --- | --- |
| Vendor | Bybit | Deribit FZE |
| Transports | stdio |  |
| Licence | none | 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 | 398 | 0 |
| Read-only variant documented | yes | no |
| llms.txt | no | yes |
| 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 | 43 stars | none |

Why the edge:
- Schema & documentation, Deribit +15: 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.); Deribit 88 (OpenAPI 3.0.0 for the whole JSON-RPC surface (Deribit API 2.1.1, about 1.4 million characters) plus AsyncAPI files for the WebSocket side (25). llms.txt with production and upcoming indexes, and a Markdown twin of every page (10). Each operation has a description such as "Places a buy order for an instrument." with parameter notes, and the articles say when to use WebSocket subscriptions over polling, but the reference seldom says when not to use a method (13 of 20). Parameters are typed with enums (order `type` has eight values, `time_in_force` four) and required flags, with `amount` or `contracts` as a documented either-or (13 of 15). Every reference page carries an example request and response, and the errors page lists about 159 codes with retry guidance, though most operations document only a 200 response and the smaller error tables disagree with the full one on two codes (12 of 15). A versioned path (/api/v2), a production and an upcoming docs branch, and a dated changelog of 64 entries since 21 January 2020 (15). Total 88.)
- Payments & pricing, Bybit +15: 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.); 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.)
- Agent ergonomics, Deribit +8: 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.); Deribit 74 (An API, read for response sizing. `public/get_order_book` takes `depth`, `get_instruments` filters by currency and kind, and history methods take `count` and `offset`, though `get_instruments` returns every instrument for a currency and costs 10,000 credits (18 of 25). Count and offset pagination, time ranges on trade and transaction logs, and WebSocket channels with interval and depth options (16 of 20). Numeric error codes with short names, a `wait` value on some errors, and sample code that branches on them (18 of 20). A `nonce` on orders since May 2026 returns the existing order on retry, a `label` lets an agent find its own orders, and 10040 marks the calls safe to retry; no MCP annotations apply (16 of 20). Few required parameters and sensible defaults (limit and good_til_cancelled), but no official SDK in any language, so every caller signs and frames JSON-RPC itself (6 of 15). Total 74.)
- Transparency & trust, Bybit +5: 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.); Deribit 46 (The editorial half. A closed service whose terms (Deribit FZE membership terms and DRB Panama Inc. terms) sit on a support site that answered 403, with the entity confirmed on VARA's register (12 of 30). The privacy policy was not read, and nothing in the docs states retention (0 of 30). The changelog marks deprecations and the upcoming docs branch previews the next release, but removals such as `public/get_index` on 25 November 2025 carry no notice period (10 of 20). No subprocessor or data-location statement found (0 of 20). Total 22.)