{ "data": { "a": { "slug": "deribit", "name": "Deribit", "vendor": "Deribit FZE", "vendorUrl": "https://www.deribit.com", "kind": "http-api", "category": "crypto-exchanges", "summary": "Deribit is a crypto options, futures and perpetuals exchange owned by Coinbase, with a JSON-RPC API over WebSocket and HTTP, a FIX API and a test environment at test.deribit.com.", "url": "https://www.anchorterminal.com/tools/deribit", "markdownUrl": "https://www.anchorterminal.com/tools/deribit.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/deribit.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/deribit.json", "dns": "deribit.grade.anchorterminal.com", "license": "Proprietary hosted exchange. The API is documented under the Deribit docs with an OpenAPI 3.0 file; no official client library is published", "transports": [], "packages": [], "auth": "api-key", "authNotes": "API keys are made in the account settings or with `private/create_api_key`, each with scopes `account`, `trade`, `wallet`, `block_trade` and `block_rfq` at `read`, `read_write` or `none`, plus `ip:ADDR` and `expires` limits. Tokens come from `public/auth` by `client_credentials` (key and secret), `client_signature` (HMAC-SHA256 over timestamp, nonce and data, so the secret never travels) or `refresh_token`. Self-generated Ed25519 or RSA keys let Deribit hold only the public half. The HTTP example passes `client_secret` in the query string (https://docs.deribit.com/articles/authentication, https://docs.deribit.com/articles/access-scope, checked 2026-11-03).", "pricing": "usage", "pricingNotes": "The API has no charge of its own; trades pay maker and taker fees per instrument. The fee schedule is on support.deribit.com, which answered our reader with 403, so the lowest-tier rates are unchecked. Deribit's own posts of 14 October and 2 November 2026 give VIP4 to VIP7 taker fees of 1.75 to 1.40 bps on perpetuals and futures from 19 October 2026, and 0 bps maker fees on USDC-settled linear daily options from 5 November 2026 (https://insights.deribit.com/exchange-updates/new-fee-tier-on-perpetuals-and-futures/, checked 2026-11-03).", "priceSummary": "0.02% fee", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the API docs, the OpenAPI file or the articles index (checked 2026-11-03). Accounts are funded by crypto deposit after a browser signup.", "endpoints": [] }, "toolCount": 0, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://docs.deribit.com/", "llmsTxt": "https://docs.deribit.com/llms.txt", "openapi": "https://docs.deribit.com/specifications/deribit_openapi.json", "capabilities": [ "exchange.derivatives", "exchange.market-data", "exchange.spot-trading", "exchange.balances", "exchange.transfers", "market.crypto" ], "tags": [ "official", "hosted", "closed-source", "openapi", "llms-txt", "api-key", "sandbox", "usage-priced", "no-status-page", "bug-bounty", "rest" ], "lastRelease": "2026-10-13", "graded": true, "anchor": { "graded": true, "score": 59, "grade": "C", "agentReady": false, "rank": 646, "ranked": true, "rankOf": 1349, "categoryRank": 9, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 74, "maintenance": 65, "payments": 25, "reliability": 45, "schema": 88, "security": 62, "transparency": 46 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "low", "date": "2026-11-03" }, "negative": 0, "verdict": "Deribit's JSON-RPC API has scoped keys with IP and expiry limits, asymmetric signing, an OpenAPI file, numeric rate limits and a 64-entry changelog. There is no official MCP server or client library, the fee schedule, terms and privacy policy sit on a support site that refused our reader, and the status page did not resolve.", "bestFor": "An agent trading crypto options, dated futures and perpetuals for an institutional or retail Deribit account, and anyone migrated from Coinbase International Exchange.", "strengths": [ "Keys carry `account`, `trade`, `wallet`, `block_trade` and `block_rfq` scopes at read, read_write or none, with `ip:ADDR` and `expires` limits, and Ed25519 or RSA keys keep the private half off Deribit", "OpenAPI 3.0 and AsyncAPI files, llms.txt indexes and Markdown twins for every reference page", "Credit-based rate limits with numbers, per sub-account, and an errors page of about 159 codes with retry guidance (10028 back off, 10040 retry, 13009 refresh)", "A separate test environment at test.deribit.com with the same API and its own accounts and keys", "A dated JSON-RPC changelog since 2020 and an upcoming docs branch that previews the next release" ], "weaknesses": [ "No official MCP server, and the GitHub organisation has no public repositories, so no official SDK in any language", "The fee schedule, terms of service, privacy policy and restricted-jurisdictions list are on support.deribit.com, which answered 403, so the lowest-tier maker and taker fees are unchecked", "status.deribit.com did not resolve for our reader and Coinbase's status page has no Deribit component we could find, so the incident record is unchecked", "The HTTP authentication example sends `client_secret` in the query string", "Breaking changes such as the 15 September 2026 change to `user.changes` carry no notice period in the changelog" ], "agentNotes": [ "Create the key with `trade:read_write` and `wallet:none`, an `ip:` limit and an `expires` value; keep `account:read` unless the task edits subaccounts", "Authenticate with `client_signature` or an Ed25519 key over WebSocket rather than `client_credentials` over HTTP, which puts the secret in the URL", "Watch the `limits` field of `private/get_account_summary` and back off on error 10028; a session that runs out of credits is closed and must reconnect", "Send a `nonce` with orders so a retry after a timeout does not place a second order, and treat `order_not_found` on cancel as a possible fill", "Develop against https://test.deribit.com/api/v2 first; production and test need separate accounts and keys" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "low", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 59 } ], "editorialScores": { "ergonomics": 74, "maintenance": 65, "payments": 25, "reliability": 45, "schema": 88, "security": 62, "transparency": 22 }, "provenanceScore": 69, "checked": { "categories": { "ergonomics": "2026-11-03", "maintenance": "2026-11-03", "payments": "2026-11-03", "reliability": "2026-11-03", "schema": "2026-11-03", "security": "2026-11-03", "transparency": "2026-11-03" }, "last": "2026-11-03", "oldest": "2026-11-03", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl 'https://test.deribit.com/api/v2/public/get_order_book?instrument_name=BTC-PERPETUAL\u0026depth=5'" }, "letme": { "capability": "https://letme.dev/exchange.derivatives", "tool": "https://letme.dev/deribit" }, "area": "payments", "unitPrices": [ { "item": "Perpetual and futures taker fee, VIP4 tier", "unit": "pct", "usd": 0.0175, "note": "1.75 bps from 19 October 2026 per Deribit's post of 14 October 2026. Base-tier fees unchecked" } ], "provenance": { "legalEntity": "Deribit FZE", "domain": "deribit.com", "domainRegistered": "2014-01-15", "endpointOnVendorDomain": true, "terms": "https://support.deribit.com/hc/en-us/articles/25944532191645-Deribit-Exchange-Membership-Terms-Deribit-FZE", "privacy": "", "statusPage": "", "changelog": "https://docs.deribit.com/changelogs/jsonrpc", "securityTxt": "unknown", "checked": "2026-11-03", "notes": [ "Deribit FZE is on VARA's public register, licence VL/23/12/002, active, issued 1 November 2024. Deribit's own post of 29 November 2024 says institutional and qualified investors contract with Deribit FZE and retail clients with DRB Panama, a broker member.", "The terms URL comes from a search result title (Deribit Exchange Membership Terms, Deribit FZE, version 26 January 2026); support.deribit.com answered 403 to our reader, so the terms, the privacy policy and the fee and restricted-jurisdictions articles were not read.", "RDAP gives deribit.com a registration date of 15 January 2014, registrar MarkMonitor.", "status.deribit.com did not resolve on 3 November 2026 and Coinbase's status page showed no Deribit component or incident, so no status page is recorded.", "https://www.deribit.com/.well-known/security.txt answered an HTML page with only the site title, so security.txt is unknown. Deribit's bug bounty runs on HackerOne per the support article title and HackerOne's customer story; insights.deribit.com/bug-bounty answered 403.", "docs.deribit.com/robots.txt allows everything but /cdn-cgi/ and /_next/, with Content-Signal ai-input=yes. support.deribit.com's robots.txt allows article pages; the 403 is the site's answer, not a robots rule." ], "score": 69 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/deribit.json", "live": { "slug": "deribit", "securityTxt": { "url": "https://deribit.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-04T15:54:13.971728133Z" }, "updatedAt": "2026-11-04T15:54:13.971728133Z" } }, "answer": "Deribit scores 59 (C) on agent readiness against HTX trading API's 43.3 (E), and leads in every scored category.", "b": { "slug": "htx", "name": "HTX trading API", "vendor": "HTX", "vendorUrl": "https://www.htx.com", "kind": "http-api", "category": "crypto-exchanges", "summary": "HTX, the exchange formerly Huobi, runs REST and WebSocket APIs for spot and derivatives trading, balances, transfers and withdrawals, authenticated with HMAC-signed API keys that carry read, trade and withdraw permissions.", "url": "https://www.anchorterminal.com/tools/htx", "markdownUrl": "https://www.anchorterminal.com/tools/htx.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/htx.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/htx.json", "dns": "htx.grade.anchorterminal.com", "repo": "https://github.com/HuobiRDCenter", "transports": [], "packages": [], "auth": "api-key", "authNotes": "API keys made in the account's API Management page after a browser sign-up and identity check. Requests are signed with HMAC SHA256 (SignatureVersion 2) over the query string, with AccessKeyId, Timestamp and the Signature sent as query parameters; the secret never travels. A main account key carries Read, Trade and Withdraw permissions, a sub-user key Read and Trade only. A key can be bound to up to 20 IP addresses, and the docs say a key without IP binding expires after 90 days (https://huobiapi.github.io/docs/spot/v1/en/, checked 2026-11-03).", "pricing": "usage", "pricingNotes": "Trading fees per order. The fee schedule at htx.com/fee is drawn by script and answered our reader with no text, so no rate is recorded; third-party guides give 0.2 per cent maker and taker at the base tier, which is a lead and not a source. Public market data needs no key and no account (https://www.htx.com/fee/, checked 2026-11-03).", "priceSummary": "Pay per use", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the API docs or on the pages that loaded (checked 2026-11-03). Trading fees are taken from each fill.", "endpoints": [] }, "toolCount": 0, "popularity": { "githubStars": 684, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://huobiapi.github.io/docs/spot/v1/en/", "capabilities": [ "exchange.market-data", "exchange.spot-trading", "exchange.derivatives", "exchange.balances", "exchange.transfers", "market.crypto" ], "tags": [ "hosted", "api-key", "closed-source", "usage-priced", "python", "java", "go", "no-status-page" ], "lastRelease": "2026-10-21", "graded": true, "anchor": { "graded": true, "score": 43.3, "grade": "E", "agentReady": false, "rank": 1156, "ranked": true, "rankOf": 1349, "categoryRank": 21, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 69, "maintenance": 57, "payments": 15, "reliability": 38, "schema": 40, "security": 51, "transparency": 25 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "low", "date": "2026-11-03" }, "negative": 0, "verdict": "HTX's API has per-endpoint rate limits, read, trade and withdraw key permissions with IP binding, and SDKs in five languages. No official MCP server exists, the testnet is closed, the public reference is still Huobi's with a 2022 changelog, and the fee schedule, terms and restricted countries are on script-drawn pages we couldn't read.", "bestFor": "Spot and USDT-margined derivatives for agents that can hold an HTX key, with no MCP server and no testnet.", "strengths": [ "Key permissions split into Read, Trade and Withdraw, sub-user keys without Withdraw, and up to 20 bound IP addresses per key", "Rate limits published per endpoint with numbers, and remaining-quota headers on every response", "A client-order-id unique within 8 hours on orders and idempotent on withdrawals, so a retry doesn't double an order", "Official SDKs in Python, Java, C++, C# and Go, the contract ones pushed on 21 October 2026" ], "weaknesses": [ "No official MCP server; the only one in the MCP registry is a third party's read-only ticker server", "The testnet is shut down, so order logic can only be tried with real funds", "The public API reference is still branded Huobi with a last changelog entry of June 2022, and HTX's newer docs are drawn by script", "No status page, no SLA and no documented 429 or Retry-After behaviour", "The fee schedule, user agreement, privacy policy and restricted-country list couldn't be read, so none is recorded first-hand" ], "agentNotes": [ "Ask the operator for a key with Read and Trade only and bound to your IP addresses; a key without IP binding expires after 90 days", "Send a fresh client-order-id of up to 64 characters with every order and reuse it only on retry; a repeat within 8 hours answers invalid.client.order.id", "Watch X-HB-RateLimit-Requests-Remain and pace at under 100 order calls per 2 seconds per UID; limits are shared by every key on the account", "There is no testnet; try order logic with the smallest size the market allows", "Confirm the person's country is served before trading; the restricted list in the user agreement couldn't be read here" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "low", "grade": "E", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 43.3 } ], "editorialScores": { "ergonomics": 69, "maintenance": 57, "payments": 15, "reliability": 38, "schema": 40, "security": 51, "transparency": 15 }, "provenanceScore": 34, "checked": { "categories": { "ergonomics": "2026-11-03", "maintenance": "2026-11-03", "payments": "2026-11-03", "reliability": "2026-11-03", "schema": "2026-11-03", "security": "2026-11-03", "transparency": "2026-11-03" }, "last": "2026-11-03", "oldest": "2026-11-03", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl https://api.huobi.pro/market/tickers" }, "letme": { "capability": "https://letme.dev/exchange.market-data", "tool": "https://letme.dev/htx" }, "area": "payments", "provenance": { "legalEntity": "", "domain": "htx.com", "domainRegistered": "1995-12-13", "endpointOnVendorDomain": false, "terms": "https://www.htx.com/en-in/support/360000298561/", "privacy": "", "statusPage": "", "changelog": "https://huobiapi.github.io/docs/spot/v1/en/", "securityTxt": "none", "checked": "2026-11-03", "notes": [ "The legal entity is unread. The HTX Platform User Agreement and every other page on www.htx.com answered our reader with no text on 3 November 2026 (the pages are drawn by script), so the terms, privacy policy, fee schedule and about page were not read. Terms URL recorded from a search result's title.", "RDAP gives htx.com a registration date of 13 December 1995, long before the exchange took the name in 2023; the domain was acquired, not registered, by the exchange.", "The API endpoint api.huobi.pro is on the old huobi.pro domain, not htx.com.", "www.htx.com/robots.txt allows / and disallows account paths (finance/account, user-center/security and the like). www.huobi.com/robots.txt disallows everything and was not read further. huobiapi.github.io has no robots.txt.", "https://www.htx.com/.well-known/security.txt answered no text; recorded as none. status.htx.com does not resolve." ], "score": 34 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/htx.json", "live": { "slug": "htx", "securityTxt": { "url": "https://htx.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-04T15:54:20.226147452Z" }, "updatedAt": "2026-11-04T15:54:20.226147452Z" } }, "edges": [ { "by": 48, "category": "schema", "leads": "deribit", "name": "Schema \u0026 documentation", "reasons": { "a": "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.", "b": "No OpenAPI or other machine-readable contract found in the docs or the GitHub accounts (0). No llms.txt on htx.com, and the readable reference is a static page (0). Each endpoint states its purpose and parameters, without when-to-use guidance (12 of 20). Parameter tables carry types, required flags and enums for order types and states (10 of 15). Request and response examples throughout and error-code tables with messages (11 of 15). Versions v1 and v2 are mixed in one reference whose last changelog entry is 24 June 2022, while HTX's newer docs on htx.com couldn't be read (7 of 15). 0 + 0 + 12 + 10 + 11 + 7 = 40." }, "scores": { "a": 88, "b": 40 } }, { "by": 21, "category": "transparency", "leads": "deribit", "name": "Transparency \u0026 trust", "reasons": { "a": "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.", "b": "The editorial half. A closed service whose user agreement exists but couldn't be read (script-drawn pages), so the licence clarity is unknown rather than unclear (10 of 30). The privacy policy was not read (0 of 30, unchecked). The testnet shutdown and the 2022 changelog entries are dated, with no deprecation policy (5 of 20). No subprocessor or data-location statement read (0 of 20). 10 + 0 + 5 + 0 = 15." }, "scores": { "a": 46, "b": 25 } }, { "by": 11, "category": "security", "leads": "deribit", "name": "Security \u0026 auth", "reasons": { "a": "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.", "b": "HMAC-signed keys with Read, Trade and Withdraw permissions, sub-user keys without Withdraw, up to 20 bound IPs, revocation in the account and a 90-day expiry without IP binding. The AccessKeyId and the HMAC signature travel as query parameters; the secret does not, so no deduction for a secret in the URL (24 of 30). Read-only keys and withdraw-free keys exist; no server-side confirmation for orders or withdrawals (14 of 20). The API returns the exchange's own data, no untrusted content (10). No per-call log or key-use history found for the operator (3 of 15). No security.txt, disclosure policy or certification found on the pages that loaded (0 of 20). 24 + 14 + 10 + 3 + 0 = 51." }, "scores": { "a": 62, "b": 51 } }, { "by": 10, "category": "payments", "leads": "deribit", "name": "Payments \u0026 pricing", "reasons": { "a": "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.", "b": "No machine payment protocol (0). The fee schedule at htx.com/fee is drawn by script and answered no text, so no price is recorded first-hand (0 of 20, unchecked). Public market data needs no key, card or account; trading needs a verified and funded account. Judgement call (15 of 20). A person must sign up in a browser and pass identity checks (0). 0 + 0 + 15 + 0 = 15." }, "scores": { "a": 25, "b": 15 } }, { "by": 8, "category": "maintenance", "leads": "deribit", "name": "Maintenance \u0026 community", "reasons": { "a": "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.", "b": "Read as a closed service. The readable changelog ends on 24 June 2022, but the official contract SDKs were pushed on 21 October 2026 and the spot SDKs in April and July 2026, so the API surface is still being maintained; judgement call (20 of 30). SDK pushes on 30 July, 23 August and 21 October 2026 are commits, not releases (10 of 20). A Telegram group for API support and a support centre, neither tested; GitHub issues not read (8 of 15). Official SDKs in five languages (15). No CI seen, dependencies not checked (4 of 10). 20 + 10 + 8 + 15 + 4 = 57." }, "scores": { "a": 65, "b": 57 } }, { "by": 7, "category": "reliability", "leads": "deribit", "name": "Reliability", "reasons": { "a": "Read with the hosted lines on the JSON-RPC API. status.deribit.com did not resolve for our reader on 3 November 2026 and Coinbase's status page showed no Deribit component, so no status page is scored, with the unchecked line below (0). No readable history (5). Rate limits are documented with numbers, 50,000 credits per sub-account refilled at 10,000 a second, and matching-engine tiers of 5 to 30 requests a second by 7-day volume (15). Error 10028 ends the session and the errors page says to back off exponentially; 10040 means retry; the 6 May 2026 release added a `nonce` for idempotent orders (15). No SLA found (0). The API is generally available; only Starbase is limited to selected clients (10). 0 + 5 + 15 + 15 + 0 + 10 = 45.", "b": "Read with the hosted lines. No status page found; status.htx.com does not resolve and nothing on htx.com was readable (0). No readable incident history (5). Rate limits documented per endpoint with numbers, 100 order calls per 2 seconds per UID and so on, with remaining-quota headers (15). No 429 or Retry-After behaviour is documented and the only limit error named is 1006 for conditional orders; a client-order-id unique within 8 hours and an idempotent withdrawal id give safe retries on writes (8 of 15). No SLA found (0). The spot and swap APIs are generally available (10). 0 + 5 + 15 + 8 + 0 + 10 = 38." }, "scores": { "a": 45, "b": 38 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Deribit FZE", "b": "HTX", "name": "Vendor" }, { "a": "no (local only)", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "", "b": "", "name": "Transports" }, { "a": "API key", "b": "API key", "name": "Auth" }, { "a": "Pay per use", "b": "Pay per use", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary hosted exchange. The API is documented under the Deribit docs with an OpenAPI 3.0 file; no official client library is published", "b": "none", "name": "Licence" }, { "a": "0", "b": "0", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "no", "name": "llms.txt" }, { "a": "2026-10-13", "b": "2026-10-21", "name": "Last release" }, { "a": "2026-08-13", "b": "no date given", "name": "Terms last updated" }, { "a": "no document linked", "b": "no document linked", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "684 stars", "name": "Popularity" } ], "faq": [ { "answer": "Deribit scores 59 (C) on agent readiness against HTX trading API's 43.3 (E), and leads in every scored category.", "question": "Which is better for AI agents, Deribit or HTX trading API?" }, { "answer": "Both need an API key.", "question": "Do Deribit and HTX trading API need an API key?" }, { "answer": "No hosted endpoint is listed for Deribit. No hosted endpoint is listed for HTX trading API.", "question": "Can an agent call Deribit and HTX trading API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 45 against 38", "Schema \u0026 documentation, 88 against 40", "Agent ergonomics, 74 against 69", "Security \u0026 auth, 62 against 51", "Payments \u0026 pricing, 25 against 15", "Maintenance \u0026 community, 65 against 57", "Transparency \u0026 trust, 46 against 25" ], "also": null, "goodFor": "An agent trading crypto options, dated futures and perpetuals for an institutional or retail Deribit account, and anyone migrated from Coinbase International Exchange.", "slug": "deribit", "watchFor": "No official MCP server, and the GitHub organisation has no public repositories, so no official SDK in any language" }, { "aheadOn": null, "also": null, "goodFor": "Spot and USDT-margined derivatives for agents that can hold an HTX key, with no MCP server and no testnet.", "slug": "htx", "watchFor": "No official MCP server; the only one in the MCP registry is a third party's read-only ticker server" } ], "history": null, "job": { "capability": "exchange.derivatives", "name": "Exchange derivatives" }, "others": [ { "json": "https://www.anchorterminal.com/compare/bitfinex-vs-deribit.json", "title": "Bitfinex API vs Deribit", "url": "https://www.anchorterminal.com/compare/bitfinex-vs-deribit" }, { "json": "https://www.anchorterminal.com/compare/bitfinex-vs-htx.json", "title": "Bitfinex API vs HTX trading API", "url": "https://www.anchorterminal.com/compare/bitfinex-vs-htx" }, { "json": "https://www.anchorterminal.com/compare/bitget-vs-deribit.json", "title": "Bitget vs Deribit", "url": "https://www.anchorterminal.com/compare/bitget-vs-deribit" }, { "json": "https://www.anchorterminal.com/compare/bitget-vs-htx.json", "title": "Bitget vs HTX trading API", "url": "https://www.anchorterminal.com/compare/bitget-vs-htx" }, { "json": "https://www.anchorterminal.com/compare/bithumb-vs-deribit.json", "title": "Bithumb Open API vs Deribit", "url": "https://www.anchorterminal.com/compare/bithumb-vs-deribit" }, { "json": "https://www.anchorterminal.com/compare/bithumb-vs-htx.json", "title": "Bithumb Open API vs HTX trading API", "url": "https://www.anchorterminal.com/compare/bithumb-vs-htx" }, { "json": "https://www.anchorterminal.com/compare/bitstamp-vs-deribit.json", "title": "Bitstamp API vs Deribit", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-deribit" }, { "json": "https://www.anchorterminal.com/compare/bitstamp-vs-htx.json", "title": "Bitstamp API vs HTX trading API", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-htx" }, { "json": "https://www.anchorterminal.com/compare/bybit-vs-deribit.json", "title": "Bybit vs Deribit", "url": "https://www.anchorterminal.com/compare/bybit-vs-deribit" }, { "json": "https://www.anchorterminal.com/compare/bybit-vs-htx.json", "title": "Bybit vs HTX trading API", "url": "https://www.anchorterminal.com/compare/bybit-vs-htx" }, { "json": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-deribit.json", "title": "Crypto.com Exchange API vs Deribit", "url": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-deribit" }, { "json": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-htx.json", "title": "Crypto.com Exchange API vs HTX trading API", "url": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-htx" }, { "json": "https://www.anchorterminal.com/compare/deribit-vs-upbit.json", "title": "Deribit vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/deribit-vs-upbit" }, { "json": "https://www.anchorterminal.com/compare/gate-io-vs-htx.json", "title": "Gate vs HTX trading API", "url": "https://www.anchorterminal.com/compare/gate-io-vs-htx" }, { "json": "https://www.anchorterminal.com/compare/gemini-exchange-vs-htx.json", "title": "Gemini Exchange API vs HTX trading API", "url": "https://www.anchorterminal.com/compare/gemini-exchange-vs-htx" }, { "json": "https://www.anchorterminal.com/compare/htx-vs-hyperliquid.json", "title": "HTX trading API vs Hyperliquid", "url": "https://www.anchorterminal.com/compare/htx-vs-hyperliquid" }, { "json": "https://www.anchorterminal.com/compare/htx-vs-kraken.json", "title": "HTX trading API vs Kraken API", "url": "https://www.anchorterminal.com/compare/htx-vs-kraken" }, { "json": "https://www.anchorterminal.com/compare/htx-vs-kucoin.json", "title": "HTX trading API vs KuCoin", "url": "https://www.anchorterminal.com/compare/htx-vs-kucoin" }, { "json": "https://www.anchorterminal.com/compare/htx-vs-mexc.json", "title": "HTX trading API vs MEXC API", "url": "https://www.anchorterminal.com/compare/htx-vs-mexc" }, { "json": "https://www.anchorterminal.com/compare/htx-vs-okx.json", "title": "HTX trading API vs OKX API", "url": "https://www.anchorterminal.com/compare/htx-vs-okx" }, { "json": "https://www.anchorterminal.com/compare/htx-vs-uniswap.json", "title": "HTX trading API vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/htx-vs-uniswap" }, { "json": "https://www.anchorterminal.com/compare/htx-vs-upbit.json", "title": "HTX trading API vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/htx-vs-upbit" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-deribit.json", "title": "Binance API vs Deribit", "url": "https://www.anchorterminal.com/compare/binance-vs-deribit" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-htx.json", "title": "Binance API vs HTX trading API", "url": "https://www.anchorterminal.com/compare/binance-vs-htx" }, { "json": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-deribit.json", "title": "Coinbase Advanced Trade API vs Deribit", "url": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-deribit" }, { "json": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-htx.json", "title": "Coinbase Advanced Trade API vs HTX trading API", "url": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-htx" }, { "json": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-deribit.json", "title": "Coinbase MCP server (Coinbase for Agents) vs Deribit", "url": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-deribit" }, { "json": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-htx.json", "title": "Coinbase MCP server (Coinbase for Agents) vs HTX trading API", "url": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-htx" }, { "json": "https://www.anchorterminal.com/compare/deribit-vs-uniswap.json", "title": "Deribit vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/deribit-vs-uniswap" }, { "json": "https://www.anchorterminal.com/compare/deribit-vs-dydx.json", "title": "Deribit vs dYdX", "url": "https://www.anchorterminal.com/compare/deribit-vs-dydx" }, { "json": "https://www.anchorterminal.com/compare/deribit-vs-gate-io.json", "title": "Deribit vs Gate", "url": "https://www.anchorterminal.com/compare/deribit-vs-gate-io" }, { "json": "https://www.anchorterminal.com/compare/deribit-vs-gemini-exchange.json", "title": "Deribit vs Gemini Exchange API", "url": "https://www.anchorterminal.com/compare/deribit-vs-gemini-exchange" }, { "json": "https://www.anchorterminal.com/compare/deribit-vs-hyperliquid.json", "title": "Deribit vs Hyperliquid", "url": "https://www.anchorterminal.com/compare/deribit-vs-hyperliquid" }, { "json": "https://www.anchorterminal.com/compare/deribit-vs-kraken.json", "title": "Deribit vs Kraken API", "url": "https://www.anchorterminal.com/compare/deribit-vs-kraken" }, { "json": "https://www.anchorterminal.com/compare/deribit-vs-kucoin.json", "title": "Deribit vs KuCoin", "url": "https://www.anchorterminal.com/compare/deribit-vs-kucoin" }, { "json": "https://www.anchorterminal.com/compare/deribit-vs-mexc.json", "title": "Deribit vs MEXC API", "url": "https://www.anchorterminal.com/compare/deribit-vs-mexc" }, { "json": "https://www.anchorterminal.com/compare/deribit-vs-okx.json", "title": "Deribit vs OKX API", "url": "https://www.anchorterminal.com/compare/deribit-vs-okx" }, { "json": "https://www.anchorterminal.com/compare/dydx-vs-htx.json", "title": "dYdX vs HTX trading API", "url": "https://www.anchorterminal.com/compare/dydx-vs-htx" } ], "panel": null, "scores": [ { "by": 7, "deribit": 45, "edge": "deribit", "htx": 38, "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 48, "deribit": 88, "edge": "deribit", "htx": 40, "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 5, "deribit": 74, "edge": "deribit", "htx": 69, "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "by": 11, "deribit": 62, "edge": "deribit", "htx": 51, "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "by": 10, "deribit": 25, "edge": "deribit", "htx": 15, "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 8, "deribit": 65, "edge": "deribit", "htx": 57, "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 21, "deribit": 46, "edge": "deribit", "htx": 25, "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Deribit scores 59 (C) on agent readiness against HTX trading API's 43.3 (E), and leads in every scored category. Both do exchange derivatives.", "tasks": null, "tutorials": [], "verdicts": { "deribit": "Deribit's JSON-RPC API has scoped keys with IP and expiry limits, asymmetric signing, an OpenAPI file, numeric rate limits and a 64-entry changelog. There is no official MCP server or client library, the fee schedule, terms and privacy policy sit on a support site that refused our reader, and the status page did not resolve.", "htx": "HTX's API has per-endpoint rate limits, read, trade and withdraw key permissions with IP binding, and SDKs in five languages. No official MCP server exists, the testnet is closed, the public reference is still Huobi's with a 2022 changelog, and the fee schedule, terms and restricted countries are on script-drawn pages we couldn't read." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/deribit-vs-htx", "json": "https://www.anchorterminal.com/compare/deribit-vs-htx.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/deribit-vs-htx.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/deribit-vs-htx.min.md" }, "markdown": "Deribit scores 59 (C) on agent readiness against HTX trading API's 43.3 (E), and leads in every scored category. Both do exchange derivatives.\n\n- Deribit: grade C, 59/100, rank #646 of 1349. Markdown https://www.anchorterminal.com/tools/deribit.md · JSON https://www.anchorterminal.com/api/v1/tools/deribit.json\n- HTX trading API: grade E, 43.3/100, rank #1156 of 1349. Markdown https://www.anchorterminal.com/tools/htx.md · JSON https://www.anchorterminal.com/api/v1/tools/htx.json\n- Best crypto exchange APIs and MCP servers for AI agents: https://www.anchorterminal.com/best/crypto-exchanges/index.md\n- All 210 exchanges comparisons: https://www.anchorterminal.com/compare/crypto-exchanges/index.md\n\n## Which one, for what\n\n### Deribit (C)\n\nGood for: An agent trading crypto options, dated futures and perpetuals for an institutional or retail Deribit account, and anyone migrated from Coinbase International Exchange.\n\nAhead on:\n- Reliability, 45 against 38\n- Schema \u0026 documentation, 88 against 40\n- Agent ergonomics, 74 against 69\n- Security \u0026 auth, 62 against 51\n- Payments \u0026 pricing, 25 against 15\n- Maintenance \u0026 community, 65 against 57\n- Transparency \u0026 trust, 46 against 25\n\nWatch for: No official MCP server, and the GitHub organisation has no public repositories, so no official SDK in any language\n\n### HTX trading API (E)\n\nGood for: Spot and USDT-margined derivatives for agents that can hold an HTX key, with no MCP server and no testnet.\n\nWatch for: No official MCP server; the only one in the MCP registry is a third party's read-only ticker server\n\n\n## Why the edge\n\n### Schema \u0026 documentation: Deribit +48\n\n- 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.\n- HTX trading API (40): No OpenAPI or other machine-readable contract found in the docs or the GitHub accounts (0). No llms.txt on htx.com, and the readable reference is a static page (0). Each endpoint states its purpose and parameters, without when-to-use guidance (12 of 20). Parameter tables carry types, required flags and enums for order types and states (10 of 15). Request and response examples throughout and error-code tables with messages (11 of 15). Versions v1 and v2 are mixed in one reference whose last changelog entry is 24 June 2022, while HTX's newer docs on htx.com couldn't be read (7 of 15). 0 + 0 + 12 + 10 + 11 + 7 = 40.\n\n### Transparency \u0026 trust: Deribit +21\n\n- 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.\n- HTX trading API (25): The editorial half. A closed service whose user agreement exists but couldn't be read (script-drawn pages), so the licence clarity is unknown rather than unclear (10 of 30). The privacy policy was not read (0 of 30, unchecked). The testnet shutdown and the 2022 changelog entries are dated, with no deprecation policy (5 of 20). No subprocessor or data-location statement read (0 of 20). 10 + 0 + 5 + 0 = 15.\n\n### Security \u0026 auth: Deribit +11\n\n- 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.\n- HTX trading API (51): HMAC-signed keys with Read, Trade and Withdraw permissions, sub-user keys without Withdraw, up to 20 bound IPs, revocation in the account and a 90-day expiry without IP binding. The AccessKeyId and the HMAC signature travel as query parameters; the secret does not, so no deduction for a secret in the URL (24 of 30). Read-only keys and withdraw-free keys exist; no server-side confirmation for orders or withdrawals (14 of 20). The API returns the exchange's own data, no untrusted content (10). No per-call log or key-use history found for the operator (3 of 15). No security.txt, disclosure policy or certification found on the pages that loaded (0 of 20). 24 + 14 + 10 + 3 + 0 = 51.\n\n### Payments \u0026 pricing: Deribit +10\n\n- 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.\n- HTX trading API (15): No machine payment protocol (0). The fee schedule at htx.com/fee is drawn by script and answered no text, so no price is recorded first-hand (0 of 20, unchecked). Public market data needs no key, card or account; trading needs a verified and funded account. Judgement call (15 of 20). A person must sign up in a browser and pass identity checks (0). 0 + 0 + 15 + 0 = 15.\n\n### Maintenance \u0026 community: Deribit +8\n\n- 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.\n- HTX trading API (57): Read as a closed service. The readable changelog ends on 24 June 2022, but the official contract SDKs were pushed on 21 October 2026 and the spot SDKs in April and July 2026, so the API surface is still being maintained; judgement call (20 of 30). SDK pushes on 30 July, 23 August and 21 October 2026 are commits, not releases (10 of 20). A Telegram group for API support and a support centre, neither tested; GitHub issues not read (8 of 15). Official SDKs in five languages (15). No CI seen, dependencies not checked (4 of 10). 20 + 10 + 8 + 15 + 4 = 57.\n\n### Reliability: Deribit +7\n\n- Deribit (45): Read with the hosted lines on the JSON-RPC API. status.deribit.com did not resolve for our reader on 3 November 2026 and Coinbase's status page showed no Deribit component, so no status page is scored, with the unchecked line below (0). No readable history (5). Rate limits are documented with numbers, 50,000 credits per sub-account refilled at 10,000 a second, and matching-engine tiers of 5 to 30 requests a second by 7-day volume (15). Error 10028 ends the session and the errors page says to back off exponentially; 10040 means retry; the 6 May 2026 release added a `nonce` for idempotent orders (15). No SLA found (0). The API is generally available; only Starbase is limited to selected clients (10). 0 + 5 + 15 + 15 + 0 + 10 = 45.\n- HTX trading API (38): Read with the hosted lines. No status page found; status.htx.com does not resolve and nothing on htx.com was readable (0). No readable incident history (5). Rate limits documented per endpoint with numbers, 100 order calls per 2 seconds per UID and so on, with remaining-quota headers (15). No 429 or Retry-After behaviour is documented and the only limit error named is 1006 for conditional orders; a client-order-id unique within 8 hours and an idempotent withdrawal id give safe retries on writes (8 of 15). No SLA found (0). The spot and swap APIs are generally available (10). 0 + 5 + 15 + 8 + 0 + 10 = 38.\n\n## Score by category\n\n| Category | Weight | Deribit | HTX trading API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 45 | 38 | Deribit +7 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 88 | 40 | Deribit +48 |\n| Agent ergonomics | 13% (16.2 this run) | 74 | 69 | Deribit +5 |\n| Security \u0026 auth | 14% (17.5 this run) | 62 | 51 | Deribit +11 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 25 | 15 | Deribit +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 65 | 57 | Deribit +8 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 46 | 25 | Deribit +21 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **59 · C** | **43.3 · E** | |\n\n## Facts side by side\n\n| Fact | Deribit | HTX trading API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Deribit FZE | HTX |\n| Hosted endpoint | no (local only) | no (local only) |\n| Transports | | |\n| Auth | API key | API key |\n| Pricing | Pay per use | Pay per use |\n| x402 | no | no |\n| Licence | Proprietary hosted exchange. The API is documented under the Deribit docs with an OpenAPI 3.0 file; no official client library is published | none |\n| Tools exposed | 0 | 0 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | no |\n| Last release | 2026-10-13 | 2026-10-21 |\n| Terms last updated | 2026-08-13 | no date given |\n| Privacy policy last updated | no document linked | no document linked |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | yes | not found in the text |\n| Terms restrict benchmarking | not found in the text | not found in the text |\n| Terms or service can change without notice | not found in the text | yes |\n| Arbitration or class-action waiver | not found in the text | yes |\n| Popularity | none | 684 stars |\n\n## Verdicts\n\n**Deribit.** Deribit's JSON-RPC API has scoped keys with IP and expiry limits, asymmetric signing, an OpenAPI file, numeric rate limits and a 64-entry changelog. There is no official MCP server or client library, the fee schedule, terms and privacy policy sit on a support site that refused our reader, and the status page did not resolve.\n\n**HTX trading API.** HTX's API has per-endpoint rate limits, read, trade and withdraw key permissions with IP binding, and SDKs in five languages. No official MCP server exists, the testnet is closed, the public reference is still Huobi's with a 2022 changelog, and the fee schedule, terms and restricted countries are on script-drawn pages we couldn't read.\n\n## Before you call either\n\n### Deribit\n\n1. Create the key with `trade:read_write` and `wallet:none`, an `ip:` limit and an `expires` value; keep `account:read` unless the task edits subaccounts\n2. Authenticate with `client_signature` or an Ed25519 key over WebSocket rather than `client_credentials` over HTTP, which puts the secret in the URL\n3. Watch the `limits` field of `private/get_account_summary` and back off on error 10028; a session that runs out of credits is closed and must reconnect\n4. Send a `nonce` with orders so a retry after a timeout does not place a second order, and treat `order_not_found` on cancel as a possible fill\n5. Develop against https://test.deribit.com/api/v2 first; production and test need separate accounts and keys\n\n### HTX trading API\n\n1. Ask the operator for a key with Read and Trade only and bound to your IP addresses; a key without IP binding expires after 90 days\n2. Send a fresh client-order-id of up to 64 characters with every order and reuse it only on retry; a repeat within 8 hours answers invalid.client.order.id\n3. Watch X-HB-RateLimit-Requests-Remain and pace at under 100 order calls per 2 seconds per UID; limits are shared by every key on the account\n4. There is no testnet; try order logic with the smallest size the market allows\n5. Confirm the person's country is served before trading; the restricted list in the user agreement couldn't be read here\n\n## Questions\n\n### Which is better for AI agents, Deribit or HTX trading API?\n\nDeribit scores 59 (C) on agent readiness against HTX trading API's 43.3 (E), and leads in every scored category.\n\n### Do Deribit and HTX trading API need an API key?\n\nBoth need an API key.\n\n### Can an agent call Deribit and HTX trading API without installing anything?\n\nNo hosted endpoint is listed for Deribit. No hosted endpoint is listed for HTX trading API.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/deribit-vs-htx.json, and with the fewest tokens: https://www.anchorterminal.com/compare/deribit-vs-htx.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"deribit\", \"b\": \"htx\"}`. From a terminal: `anchor compare deribit htx`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/deribit.json and https://www.anchorterminal.com/api/v1/tools/htx.json\n\n## Other comparisons with Deribit or HTX trading API\n\n- [Bitfinex API vs Deribit](https://www.anchorterminal.com/compare/bitfinex-vs-deribit.md)\n- [Bitfinex API vs HTX trading API](https://www.anchorterminal.com/compare/bitfinex-vs-htx.md)\n- [Bitget vs Deribit](https://www.anchorterminal.com/compare/bitget-vs-deribit.md)\n- [Bitget vs HTX trading API](https://www.anchorterminal.com/compare/bitget-vs-htx.md)\n- [Bithumb Open API vs Deribit](https://www.anchorterminal.com/compare/bithumb-vs-deribit.md)\n- [Bithumb Open API vs HTX trading API](https://www.anchorterminal.com/compare/bithumb-vs-htx.md)\n- [Bitstamp API vs Deribit](https://www.anchorterminal.com/compare/bitstamp-vs-deribit.md)\n- [Bitstamp API vs HTX trading API](https://www.anchorterminal.com/compare/bitstamp-vs-htx.md)\n- [Bybit vs Deribit](https://www.anchorterminal.com/compare/bybit-vs-deribit.md)\n- [Bybit vs HTX trading API](https://www.anchorterminal.com/compare/bybit-vs-htx.md)\n- [Crypto.com Exchange API vs Deribit](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-deribit.md)\n- [Crypto.com Exchange API vs HTX trading API](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-htx.md)\n- [Deribit vs Upbit Open API](https://www.anchorterminal.com/compare/deribit-vs-upbit.md)\n- [Gate vs HTX trading API](https://www.anchorterminal.com/compare/gate-io-vs-htx.md)\n- [Gemini Exchange API vs HTX trading API](https://www.anchorterminal.com/compare/gemini-exchange-vs-htx.md)\n- [HTX trading API vs Hyperliquid](https://www.anchorterminal.com/compare/htx-vs-hyperliquid.md)\n- [HTX trading API vs Kraken API](https://www.anchorterminal.com/compare/htx-vs-kraken.md)\n- [HTX trading API vs KuCoin](https://www.anchorterminal.com/compare/htx-vs-kucoin.md)\n- [HTX trading API vs MEXC API](https://www.anchorterminal.com/compare/htx-vs-mexc.md)\n- [HTX trading API vs OKX API](https://www.anchorterminal.com/compare/htx-vs-okx.md)\n- [HTX trading API vs Uniswap Trading API](https://www.anchorterminal.com/compare/htx-vs-uniswap.md)\n- [HTX trading API vs Upbit Open API](https://www.anchorterminal.com/compare/htx-vs-upbit.md)\n- [Binance API vs Deribit](https://www.anchorterminal.com/compare/binance-vs-deribit.md)\n- [Binance API vs HTX trading API](https://www.anchorterminal.com/compare/binance-vs-htx.md)\n- [Coinbase Advanced Trade API vs Deribit](https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-deribit.md)\n- [Coinbase Advanced Trade API vs HTX trading API](https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-htx.md)\n- [Coinbase MCP server (Coinbase for Agents) vs Deribit](https://www.anchorterminal.com/compare/coinbase-mcp-vs-deribit.md)\n- [Coinbase MCP server (Coinbase for Agents) vs HTX trading API](https://www.anchorterminal.com/compare/coinbase-mcp-vs-htx.md)\n- [Deribit vs Uniswap Trading API](https://www.anchorterminal.com/compare/deribit-vs-uniswap.md)\n- [Deribit vs dYdX](https://www.anchorterminal.com/compare/deribit-vs-dydx.md)\n- [Deribit vs Gate](https://www.anchorterminal.com/compare/deribit-vs-gate-io.md)\n- [Deribit vs Gemini Exchange API](https://www.anchorterminal.com/compare/deribit-vs-gemini-exchange.md)\n- [Deribit vs Hyperliquid](https://www.anchorterminal.com/compare/deribit-vs-hyperliquid.md)\n- [Deribit vs Kraken API](https://www.anchorterminal.com/compare/deribit-vs-kraken.md)\n- [Deribit vs KuCoin](https://www.anchorterminal.com/compare/deribit-vs-kucoin.md)\n- [Deribit vs MEXC API](https://www.anchorterminal.com/compare/deribit-vs-mexc.md)\n- [Deribit vs OKX API](https://www.anchorterminal.com/compare/deribit-vs-okx.md)\n- [dYdX vs HTX trading API](https://www.anchorterminal.com/compare/dydx-vs-htx.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-04", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Deribit vs HTX trading API", "url": "" } ], "description": "Deribit scores 59 (C) to HTX trading's 43.3 (E) for exchange derivatives. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Deribit C 59", "HTX trading API E 43.3", "scores" ], "h1": "Deribit vs HTX trading API", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/deribit-vs-htx", "published": "2026-10-01", "section": "tools", "title": "Deribit vs HTX trading for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-04", "url": "https://www.anchorterminal.com/compare/deribit-vs-htx" }, "tokens": { "markdown": 4750, "slim": 2580 }, "version": 1 }