{ "data": { "a": { "slug": "bybit", "name": "Bybit", "vendor": "Bybit", "vendorUrl": "https://www.bybit.com", "kind": "http-api", "category": "crypto-exchanges", "summary": "Bybit is a centralised crypto exchange for spot, perpetual and futures contracts, options and earn products, reached through its V5 REST and WebSocket API, a FIX order-entry gateway and an official stdio MCP server published from its GitHub organisation.", "url": "https://www.anchorterminal.com/tools/bybit", "markdownUrl": "https://www.anchorterminal.com/tools/bybit.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/bybit.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/bybit.json", "dns": "bybit.grade.anchorterminal.com", "repo": "https://github.com/bybit-exchange/trading-mcp", "transports": [ "stdio" ], "packages": [ { "registry": "npm", "name": "bybit-official-trading-server" }, { "registry": "pypi", "name": "pybit" } ], "auth": "api-key", "authNotes": "API key minted on the API management page after a browser sign-up and identity verification, signed per request with HMAC-SHA256 (system-generated secret) or RSA-SHA256 (self-generated key pair) in the X-BAPI-API-KEY, X-BAPI-TIMESTAMP, X-BAPI-SIGN and X-BAPI-RECV-WINDOW headers. Permissions are granted per group (ContractTrade, Spot, Wallet with a separate Withdraw value, Options, Derivatives, Exchange, Earn, Affiliate, BlockTrade) with a readOnly flag, and keys can be bound to IP addresses. A key with no IP binding expires 90 days after creation and can be extended on the management page with email and 2FA codes. Keys for testnet come from testnet.bybit.com and keys for demo trading from the production account in demo mode (https://bybit-exchange.github.io/docs/v5/user/apikey-info and https://bybit-exchange.github.io/docs/faq, checked 2026-11-03).", "pricing": "usage", "pricingNotes": "The API and the MCP server cost nothing; trades carry Bybit's fees. At VIP 0 the spot fee is 0.1 per cent maker and taker, perpetual and futures contracts 0.02 per cent maker and 0.055 per cent taker, options 0.02 per cent maker and 0.03 per cent taker, with lower tiers by 30-day volume or asset balance and a note that rates vary by region. Fiat pairs, the Adventure Zone, xStocks and pre-market perpetuals have their own tables (https://www.bybit.com/en/help-center/article/Trading-Fee-Structure, last updated 2 September 2026, read 2026-11-03).", "priceSummary": "0.1% fee", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the V5 docs, the MCP server's README or source, or the fee schedule (checked 2026-11-03). Trading fees are taken from the account balance.", "endpoints": [] }, "toolCount": 398, "popularity": { "githubStars": 43, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://bybit-exchange.github.io/docs/v5/intro", "capabilities": [ "exchange.market-data", "exchange.spot-trading", "exchange.derivatives", "exchange.balances", "exchange.transfers", "exchange.staking", "market.crypto" ], "tags": [ "hosted", "closed-source", "api-key", "usage-priced", "sandbox", "no-status-page", "mcp", "official", "python", "typescript", "go", "java", "dotnet" ], "lastRelease": "2026-10-30", "graded": true, "anchor": { "graded": true, "score": 57.3, "grade": "C", "agentReady": false, "rank": 745, "ranked": true, "rankOf": 1349, "categoryRank": 11, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 66, "maintenance": 66, "payments": 40, "reliability": 45, "schema": 73, "security": 60, "transparency": 51 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-03" }, "negative": 0, "verdict": "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.", "bestFor": "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.", "strengths": [ "Official MCP server from Bybit's GitHub organisation with 398 generated tools, each annotated readOnlyHint, destructiveHint and openWorldHint, and market data tools that need no key", "Rate limits published per endpoint and per UID with limit, remaining and reset headers on every response, and a documented 403 ban rule for the IP limit", "API keys scoped by product group with a read-only flag, a separate Withdraw permission, IP binding and a 90-day expiry for unbound keys", "Demo trading at api-demo.bybit.com with self-served demo funds, plus a testnet with its own keys", "VIP 0 fees published without login, 0.1 per cent spot and 0.02 per cent maker and 0.055 per cent taker on contracts" ], "weaknesses": [ "No status page, incident history or SLA was found; the terms say the API is not guaranteed to be available", "No OpenAPI or llms.txt for the V5 API, and the MCP server exposes all 398 tools with no toolset, module or read-only switch", "Not in the official MCP registry; the hosted `bybit` entry there is a third party's server, not Bybit's", "The global terms, privacy policy and about pages on bybit.com render by script and were not read; the terms read are the UAE-regulated entity's PDF", "Changelog entries change response shapes and remove fields without a notice period, such as the Asset Overview restructure of 18 August 2026" ], "agentNotes": [ "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", "Send a unique orderLinkId on every order and reuse it when amending or cancelling, since create-order is asynchronous and confirmed over WebSocket", "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", "Test on api-demo.bybit.com with a demo key from the production account, not on testnet demo mode, which the docs call meaningless", "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" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 57.3 } ], "editorialScores": { "ergonomics": 66, "maintenance": 66, "payments": 40, "reliability": 45, "schema": 73, "security": 60, "transparency": 27 }, "provenanceScore": 75, "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": { "install": "npm install -g bybit-official-trading-server", "http": "curl https://api.bybit.com/v5/market/tickers?category=spot\u0026symbol=BTCUSDT", "claudeCode": "claude mcp add bybit -- npx -y bybit-official-trading-server@latest", "config": { "mcpServers": { "bybit": { "args": [ "-y", "bybit-official-trading-server@latest" ], "command": "npx", "env": { "BYBIT_API_KEY": "YOUR_API_KEY", "BYBIT_API_SECRET": "YOUR_API_SECRET", "BYBIT_TESTNET": "true" } } } } }, "letme": { "capability": "https://letme.dev/exchange.market-data", "tool": "https://letme.dev/bybit" }, "area": "payments", "unitPrices": [ { "item": "Spot trade, VIP 0 maker or taker", "unit": "pct", "usd": 0.1, "note": "crypto-crypto pairs" }, { "item": "Perpetual or futures trade, VIP 0 taker", "unit": "pct", "usd": 0.055, "note": "maker 0.02 per cent" }, { "item": "Options trade, VIP 0 taker", "unit": "pct", "usd": 0.03, "note": "maker 0.02 per cent" } ], "provenance": { "legalEntity": "Bybit Virtual Asset Platform Operator L.L.C. S.P.C", "domain": "bybit.com", "domainRegistered": "1999-08-05", "endpointOnVendorDomain": true, "terms": "https://www.bybit.com/en/terms-service", "privacy": "https://www.bybit.com/en/privacy-policy", "statusPage": "", "changelog": "https://bybit-exchange.github.io/docs/changelog/v5", "securityTxt": "none", "checked": "2026-11-03", "notes": [ "www.bybit.com answers WebFetch with a timeout; its robots.txt (read with curl) allows the help centre, legal and static paths and disallows query-string URLs and x-api endpoints. The terms and privacy pages render by script, so the terms read are the PDF at /common-static/compliance/legal/BYBIT/b2e1c94c53ee5e12e165919de919337e.pdf (Bybit Virtual Asset Platform Operator L.L.C. S.P.C, last updated 23 January 2026, English and Welsh law, SIAC arbitration). The privacy policy was not read.", "RDAP gives bybit.com a registration date of 5 August 1999 (CSC Corporate Domains), earlier than the company, so the domain was bought.", "https://www.bybit.com/.well-known/security.txt answers 404. bybit-exchange.github.io has no robots.txt and no security.txt.", "No status page found; status.bybit.com does not resolve, the docs link none, and a search found only third-party monitors.", "The V5 changelog is dated by day; the MCP server's versions are on npm. The P2P service terms on bybit.com name Bybit Technology Limited as the company." ], "score": 75 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/bybit.json", "live": { "slug": "bybit", "versions": [ { "registry": "github", "name": "bybit-exchange/trading-mcp", "version": "2.1.26", "released": "2026-10-30", "seenAt": "2026-11-04T20:04:41.294958912Z" }, { "registry": "npm", "name": "bybit-official-trading-server", "version": "2.1.26", "seenAt": "2026-11-04T20:04:40.287082189Z" }, { "registry": "pypi", "name": "pybit", "version": "5.17.0", "released": "2026-07-14", "seenAt": "2026-11-04T20:04:41.10004853Z" } ], "githubStars": 43, "npmWeekly": 1294, "pypiWeekly": 97932, "securityTxt": { "url": "https://bybit.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-04T15:54:01.70982249Z" }, "updatedAt": "2026-11-04T20:04:41.294958912Z" } }, "answer": "dYdX scores 69.5 (B) on agent readiness against Bybit's 57.3 (C), and leads in 4 of 7 scored categories. Bybit leads on schema \u0026 documentation.", "b": { "slug": "dydx", "name": "dYdX", "vendor": "dYdX Trading Inc.", "vendorUrl": "https://www.dydx.xyz", "kind": "http-api", "category": "crypto-exchanges", "summary": "dYdX is a perpetuals exchange on its own Cosmos chain. Agents read markets and accounts from the indexer REST and WebSocket API at indexer.dydx.trade and place orders as signed chain transactions through the official TypeScript, Python and Rust clients.", "url": "https://www.anchorterminal.com/tools/dydx", "markdownUrl": "https://www.anchorterminal.com/tools/dydx.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/dydx.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/dydx.json", "dns": "dydx.grade.anchorterminal.com", "repo": "https://github.com/dydxprotocol/v4-clients", "license": "The clients are AGPL-3.0 with a use condition tied to the v4 Terms of Use; the chain software (dydxprotocol/v4-chain) carries a custom licence GitHub cannot classify. The hosted indexer at indexer.dydx.trade and the front end are run by third parties, not dYdX Trading Inc.", "transports": [], "packages": [ { "registry": "npm", "name": "@dydxprotocol/v4-client-js" }, { "registry": "pypi", "name": "dydx-v4-client" } ], "auth": "mixed", "authNotes": "Indexer reads need no credential. Orders, cancels and transfers are chain messages signed with the account's key (a mnemonic or private key in the clients). Permissioned keys let an owner add an authenticator that lets another key act within limits, composed from SignatureVerification, MessageFilter (for example only /dydxprotocol.clob.MsgPlaceOrder), SubaccountFilter and ClobPairIdFilter under AllOf or AnyOf, and removed with remove_authenticator. The dydx.trade interface generates an API wallet with default permission to trade all cross-margin pairs and shows its private key once (https://docs.dydx.xyz/concepts/trading/authenticators, checked 2026-11-03).", "pricing": "usage", "pricingNotes": "The indexer and clients have no charge. Trading fees at the lowest tier (under $1 million of 30-day volume) are 5.0 bps taker and 1.0 bps maker, set by governance, uniform across markets, with gas on each transaction; fees flow to validators and stakers (https://docs.dydx.xyz/concepts/trading/rewards, checked 2026-11-03).", "priceSummary": "0.05% fee", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs or clients (checked 2026-11-03). Accounts are funded with USDC through Noble or an onboarding partner.", "endpoints": [] }, "toolCount": 0, "popularity": { "githubStars": 119, "npmWeekly": 86394, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://docs.dydx.xyz/", "llmsTxt": "https://docs.dydx.xyz/llms.txt", "capabilities": [ "exchange.derivatives", "exchange.market-data", "exchange.balances", "exchange.transfers", "exchange.staking", "market.crypto", "wallet.onchain" ], "tags": [ "official", "hosted", "open-source", "llms-txt", "typescript", "python", "rust", "sandbox", "usage-priced", "status-page", "bug-bounty", "no-key", "rest" ], "lastRelease": "2026-10-29", "graded": true, "anchor": { "graded": true, "score": 69.5, "grade": "B", "agentReady": false, "rank": 221, "ranked": true, "rankOf": 1349, "categoryRank": 3, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 66, "maintenance": 83, "payments": 60, "reliability": 83, "schema": 58, "security": 78, "transparency": 50 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-03" }, "negative": 0, "verdict": "dYdX gives an agent keyless indexer reads, permissioned keys limited by message type, subaccount and market, a Statuspage with a clean 90 days, published fees and a testnet with a faucet. There is no official MCP server or OpenAPI file, orders are chain transactions signed by the clients, and no one entity operates the hosted endpoints.", "bestFor": "An agent trading perpetuals from its own Cosmos wallet or through a permissioned key on an owner's account, outside the US, Canada and UK.", "strengths": [ "Permissioned keys limit a delegated key to chosen message types, subaccounts and markets, exclude withdrawals and transfers, and are removed with `remove_authenticator`", "status.dydx.trade lists Indexer, Chain, Order Gateway and Client Libraries components, with only maintenance windows and one partner deposit delay in the last 90 days", "Fees public at 5.0 bps taker and 1.0 bps maker at the lowest tier, with rate limits and block limits stated with numbers", "Official TypeScript, Python and Rust clients with CI and trusted publishing, and a testnet with a faucet", "A Cantina bug bounty up to $1,000,000 sponsored by dYdX Trading Inc. covering the protocol, indexer, web client and client SDKs" ], "weaknesses": [ "No official MCP server; the one registry entry is a third party's analytics server", "No OpenAPI file for the indexer; error responses are described by HTTP status only, and chain rejections surface as transaction results", "No 429 handling or Retry-After documented for the indexer; permissioned keys cannot cap position or order size", "The hosted indexer and front end are run by unnamed third parties; dYdX Trading Inc. says it runs none of the components", "Restricted to persons outside the United States, Canada and the United Kingdom, with geo-blocking left to each integrator" ], "agentNotes": [ "Ask the account owner for an authenticator limited to `/dydxprotocol.clob.MsgPlaceOrder` and `MsgCancelOrder` on one subaccount, and keep its private key out of prompts", "Set a unique 32-bit `clientId` on every order and look it up on `/v4/orders` after a timeout; short-term orders expire with `goodTilBlock` (at most 20 blocks ahead)", "Stay under 2 stateful orders a block and 20 per 100 blocks; failed placements count, so use short-term orders for active trading", "Enable permessage-deflate on the indexer WebSocket; since 26 October 2026 connections without compression may be refused with 426", "Check `/v4/geo` and the compliance screen before trading for a person, since the terms exclude the United States, Canada and the United Kingdom" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 69.5 } ], "editorialScores": { "ergonomics": 66, "maintenance": 83, "payments": 60, "reliability": 83, "schema": 58, "security": 78, "transparency": 50 }, "provenanceScore": 50, "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": { "install": "npm install @dydxprotocol/v4-client-js", "http": "curl https://indexer.dydx.trade/v4/orderbooks/perpetualMarket/ETH-USD" }, "letme": { "capability": "https://letme.dev/exchange.derivatives", "tool": "https://letme.dev/dydx" }, "area": "payments", "unitPrices": [ { "item": "Taker fee, tier 1", "unit": "pct", "usd": 0.05, "note": "5.0 bps of notional; maker 1.0 bps" } ], "provenance": { "legalEntity": "dYdX Trading Inc.", "domain": "dydx.xyz", "domainRegistered": "", "endpointOnVendorDomain": false, "terms": "https://dydx.exchange/v4-terms", "privacy": "https://www.dydx.xyz/legal/privacy-policy", "statusPage": "https://status.dydx.trade", "changelog": "", "securityTxt": "unknown", "checked": "2026-11-03", "notes": [ "dYdX Trading Inc. is the entity in the v4 Terms of Use (last updated 12 March 2026), the clients' licence and the Cantina bug bounty. dydx.xyz's terms and privacy policy (6 June 2025) name dYdX International Ltd, Cayman Islands, and its footer reads dYdX International Ltd.", "The indexer at indexer.dydx.trade is not on dydx.xyz and the docs say dYdX Trading Inc. runs none of the hosted components, so the endpoint is recorded as off the vendor's domain.", "RDAP for dydx.trade answered 404 at the Identity Digital and rdap.org services, so the domain age is unchecked; the vendor domain dydx.xyz was not queried.", "status.dydx.trade is an Atlassian Statuspage with five components and an RSS history; its robots.txt disallows /api/ and /embed/, so the history was read from /history.rss.", "https://dydx.trade/.well-known/security.txt answered the app's HTML page, so security.txt is unknown. No API changelog; protocol upgrades appear as status maintenance entries." ], "score": 50 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/dydx.json", "live": { "slug": "dydx", "vendorStatus": { "page": "https://status.dydx.trade", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-04T20:05:06.117120724Z" }, "securityTxt": { "url": "https://dydx.xyz/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-04T15:54:03.349495473Z" }, "updatedAt": "2026-11-04T20:05:06.117120724Z" } }, "edges": [ { "by": 38, "category": "reliability", "leads": "dydx", "name": "Reliability", "reasons": { "a": "Graded with the hosted lines on the V5 API at api.bybit.com. No status page found (status.bybit.com does not resolve, the docs link none), so 0 for the page and 5 for no readable history. Rate limits are published per endpoint and per UID with numbers, plus a 600 per 5 second IP limit (15). Every response carries X-Bapi-Limit, X-Bapi-Limit-Status and X-Bapi-Limit-Reset-Timestamp, retCode 10006 and HTTP 403 are documented with a wait rule, and orders take a unique orderLinkId that amend and cancel accept (15). No SLA (0). V5 is the current production API, not a beta (10). 45.", "b": "Read with the hosted lines on the indexer API and the chain endpoints the clients submit to. status.dydx.trade is an Atlassian Statuspage with Frontends, dYdX Chain, Indexer, Order Gateway and Client Libraries components and an RSS history (20). From 1 August to 3 November 2026 the feed has eight items, seven scheduled maintenance windows of 29 minutes to 2 hours (indexer on 9 September, 8 and 15 October, protocol v9.7 on 11 September and v9.8.0 on 12 October, WebSocket compression on 26 and 28 October) and one degraded instant-deposit path through an onboarding partner from 24 to 29 September, outside the trading API. Clean or trivial (30). Rate limits documented with numbers for the indexer, the block limits and the public nodes (15). No 429 shape or Retry-After for the indexer; short-term orders expire by `goodTilBlock` and client IDs let an agent find an order after a timeout (8 of 15). No SLA (0). Mainnet generally available; the Order Entry Gateway is marked testnet-only (10). 20 + 30 + 15 + 8 + 0 + 10 = 83." }, "scores": { "a": 45, "b": 83 } }, { "by": 20, "category": "payments", "leads": "dydx", "name": "Payments \u0026 pricing", "reasons": { "a": "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.", "b": "No machine payment protocol (0). Fees public per tier without login (20). Testnet with a faucet and no card anywhere (20). No signup; an agent with a funded wallet trades, subject to the geographic terms (20). Total 60." }, "scores": { "a": 40, "b": 60 } }, { "by": 18, "category": "security", "leads": "dydx", "name": "Security \u0026 auth", "reasons": { "a": "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.", "b": "Orders are signed by the account key or by a permissioned key the owner adds as an authenticator, limited by message type, subaccount and market with AllOf or AnyOf, and revoked by `remove_authenticator`; no shared secret and nothing in a URL (28 of 30). A key can be confined to placing and cancelling orders on one subaccount with withdrawals and transfers excluded, though not to a position or order size, and the interface's default API wallet trades all cross-margin pairs (16 of 20). The API returns no untrusted content (10). Every action is a chain transaction and the indexer lists fills, orders and transfers per subaccount, and authenticators can be listed; no per-key log (10 of 15). A Cantina bug bounty up to $1,000,000 sponsored by dYdX Trading Inc. over the protocol, indexer, web client and SDKs, an Informal Systems audit; no security.txt and no certification (14 of 20). Total 78." }, "scores": { "a": 60, "b": 78 } }, { "by": 17, "category": "maintenance", "leads": "dydx", "name": "Maintenance \u0026 community", "reasons": { "a": "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.", "b": "Read on the clients and the chain. v4-clients was pushed on 29 October 2026 and protocol v9.8.0 shipped on 12 October (30). Protocol v9.7 on 11 September, v9.8.0 on 12 October, v4-client-js tags 3.5.0 and 3.6.0, three or more in 90 days (20). A Discord, a help centre and 36 open issues on v4-clients whose replies couldn't be read (12 of 25). Official SDKs current, the TypeScript client at 3.6.0 and the Python client at 1.1.6 from February 2026 (12 of 15). CI workflows for lint, test, publish and audit, with trusted publishing and provenance on npm (9 of 10). Total 83." }, "scores": { "a": 66, "b": 83 } }, { "by": 15, "category": "schema", "leads": "bybit", "name": "Schema \u0026 documentation", "reasons": { "a": "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.", "b": "No OpenAPI file found for the indexer; the docs publish a types reference of about 200 pages (OrderSide, TimeInForce, OrderStatus and the rest) and the chain's protobuf messages are in the clients (8 of 25). llms.txt and Markdown docs (10). Endpoint pages describe each call and the guides say when to use short-term against long-term orders and the indexer against the node, but descriptions are short (12 of 20). Enums and types on every field in the reference, with pagination and cursor parameters typed (11 of 15). Examples in Python, TypeScript and Rust for each step; errors are described by HTTP status (400 malformed, 404 not found) with no code list (9 of 15). A /v4 path, protocol releases dated on the status page, deprecated rate-limit fields marked, but no API changelog (8 of 15). Total 58." }, "scores": { "a": 73, "b": 58 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Bybit", "b": "dYdX Trading Inc.", "name": "Vendor" }, { "a": "no (local only)", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "stdio", "b": "", "name": "Transports" }, { "a": "API key", "b": "OAuth or key", "name": "Auth" }, { "a": "Pay per use", "b": "Pay per use", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "none", "b": "The clients are AGPL-3.0 with a use condition tied to the v4 Terms of Use; the chain software (dydxprotocol/v4-chain) carries a custom licence GitHub cannot classify. The hosted indexer at indexer.dydx.trade and the front end are run by third parties, not dYdX Trading Inc.", "name": "Licence" }, { "a": "398", "b": "0", "name": "Tools exposed" }, { "a": "yes", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-30", "b": "2026-10-29", "name": "Last release" }, { "a": "couldn't be read", "b": "2026-03-12", "name": "Terms last updated" }, { "a": "couldn't be read", "b": "2025-06-06", "name": "Privacy policy last updated" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "couldn't be read", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "couldn't be read", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "43 stars", "b": "119 stars, 86k npm/wk", "name": "Popularity" } ], "faq": [ { "answer": "dYdX scores 69.5 (B) on agent readiness against Bybit's 57.3 (C), and leads in 4 of 7 scored categories. Bybit leads on schema \u0026 documentation.", "question": "Which is better for AI agents, Bybit or dYdX?" }, { "answer": "Bybit needs an API key. dYdX takes an API key or an OAuth sign-in.", "question": "Do Bybit and dYdX need an API key?" }, { "answer": "Bybit runs on your own machine, with no hosted endpoint listed. No hosted endpoint is listed for dYdX.", "question": "Can an agent call Bybit and dYdX without installing anything?" }, { "answer": "No open-source release is listed for Bybit. dYdX is open source (The clients are AGPL-3.0 with a use condition tied to the v4 Terms of Use; the chain software (dydxprotocol/v4-chain) carries a custom licence GitHub cannot classify. The hosted indexer at indexer.dydx.trade and the front end are run by third parties, not dYdX Trading Inc.).", "question": "Are Bybit and dYdX open source?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 73 against 58" ], "also": [ "Runs on your own machine" ], "goodFor": "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.", "slug": "bybit", "watchFor": "No status page, incident history or SLA was found; the terms say the API is not guaranteed to be available" }, { "aheadOn": [ "Reliability, 83 against 45", "Security \u0026 auth, 78 against 60", "Payments \u0026 pricing, 60 against 40", "Maintenance \u0026 community, 83 against 66" ], "also": [ "Open source" ], "goodFor": "An agent trading perpetuals from its own Cosmos wallet or through a permissioned key on an owner's account, outside the US, Canada and UK.", "slug": "dydx", "watchFor": "No official MCP server; the one registry entry is a third party's analytics server" } ], "history": null, "job": { "capability": "exchange.market-data", "name": "Exchange market data" }, "others": [ { "json": "https://www.anchorterminal.com/compare/bitfinex-vs-bybit.json", "title": "Bitfinex API vs Bybit", "url": "https://www.anchorterminal.com/compare/bitfinex-vs-bybit" }, { "json": "https://www.anchorterminal.com/compare/bitfinex-vs-dydx.json", "title": "Bitfinex API vs dYdX", "url": "https://www.anchorterminal.com/compare/bitfinex-vs-dydx" }, { "json": "https://www.anchorterminal.com/compare/bitget-vs-bybit.json", "title": "Bitget vs Bybit", "url": "https://www.anchorterminal.com/compare/bitget-vs-bybit" }, { "json": "https://www.anchorterminal.com/compare/bitget-vs-dydx.json", "title": "Bitget vs dYdX", "url": "https://www.anchorterminal.com/compare/bitget-vs-dydx" }, { "json": "https://www.anchorterminal.com/compare/bithumb-vs-bybit.json", "title": "Bithumb Open API vs Bybit", "url": "https://www.anchorterminal.com/compare/bithumb-vs-bybit" }, { "json": "https://www.anchorterminal.com/compare/bithumb-vs-dydx.json", "title": "Bithumb Open API vs dYdX", "url": "https://www.anchorterminal.com/compare/bithumb-vs-dydx" }, { "json": "https://www.anchorterminal.com/compare/bitstamp-vs-bybit.json", "title": "Bitstamp API vs Bybit", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-bybit" }, { "json": "https://www.anchorterminal.com/compare/bitstamp-vs-dydx.json", "title": "Bitstamp API vs dYdX", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-dydx" }, { "json": "https://www.anchorterminal.com/compare/bybit-vs-coinbase-advanced-trade.json", "title": "Bybit vs Coinbase Advanced Trade API", "url": "https://www.anchorterminal.com/compare/bybit-vs-coinbase-advanced-trade" }, { "json": "https://www.anchorterminal.com/compare/bybit-vs-coinbase-mcp.json", "title": "Bybit vs Coinbase MCP server (Coinbase for Agents)", "url": "https://www.anchorterminal.com/compare/bybit-vs-coinbase-mcp" }, { "json": "https://www.anchorterminal.com/compare/bybit-vs-crypto-com-exchange.json", "title": "Bybit vs Crypto.com Exchange API", "url": "https://www.anchorterminal.com/compare/bybit-vs-crypto-com-exchange" }, { "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-gate-io.json", "title": "Bybit vs Gate", "url": "https://www.anchorterminal.com/compare/bybit-vs-gate-io" }, { "json": "https://www.anchorterminal.com/compare/bybit-vs-gemini-exchange.json", "title": "Bybit vs Gemini Exchange API", "url": "https://www.anchorterminal.com/compare/bybit-vs-gemini-exchange" }, { "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/bybit-vs-hyperliquid.json", "title": "Bybit vs Hyperliquid", "url": "https://www.anchorterminal.com/compare/bybit-vs-hyperliquid" }, { "json": "https://www.anchorterminal.com/compare/bybit-vs-kraken.json", "title": "Bybit vs Kraken API", "url": "https://www.anchorterminal.com/compare/bybit-vs-kraken" }, { "json": "https://www.anchorterminal.com/compare/bybit-vs-kucoin.json", "title": "Bybit vs KuCoin", "url": "https://www.anchorterminal.com/compare/bybit-vs-kucoin" }, { "json": "https://www.anchorterminal.com/compare/bybit-vs-mexc.json", "title": "Bybit vs MEXC API", "url": "https://www.anchorterminal.com/compare/bybit-vs-mexc" }, { "json": "https://www.anchorterminal.com/compare/bybit-vs-okx.json", "title": "Bybit vs OKX API", "url": "https://www.anchorterminal.com/compare/bybit-vs-okx" }, { "json": "https://www.anchorterminal.com/compare/bybit-vs-uniswap.json", "title": "Bybit vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/bybit-vs-uniswap" }, { "json": "https://www.anchorterminal.com/compare/bybit-vs-upbit.json", "title": "Bybit vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/bybit-vs-upbit" }, { "json": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-dydx.json", "title": "Crypto.com Exchange API vs dYdX", "url": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-dydx" }, { "json": "https://www.anchorterminal.com/compare/dydx-vs-uniswap.json", "title": "dYdX vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/dydx-vs-uniswap" }, { "json": "https://www.anchorterminal.com/compare/dydx-vs-upbit.json", "title": "dYdX vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/dydx-vs-upbit" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-bybit.json", "title": "Binance API vs Bybit", "url": "https://www.anchorterminal.com/compare/binance-vs-bybit" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-dydx.json", "title": "Binance API vs dYdX", "url": "https://www.anchorterminal.com/compare/binance-vs-dydx" }, { "json": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-dydx.json", "title": "Coinbase Advanced Trade API vs dYdX", "url": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-dydx" }, { "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/dydx-vs-gate-io.json", "title": "dYdX vs Gate", "url": "https://www.anchorterminal.com/compare/dydx-vs-gate-io" }, { "json": "https://www.anchorterminal.com/compare/dydx-vs-gemini-exchange.json", "title": "dYdX vs Gemini Exchange API", "url": "https://www.anchorterminal.com/compare/dydx-vs-gemini-exchange" }, { "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" }, { "json": "https://www.anchorterminal.com/compare/dydx-vs-hyperliquid.json", "title": "dYdX vs Hyperliquid", "url": "https://www.anchorterminal.com/compare/dydx-vs-hyperliquid" }, { "json": "https://www.anchorterminal.com/compare/dydx-vs-kraken.json", "title": "dYdX vs Kraken API", "url": "https://www.anchorterminal.com/compare/dydx-vs-kraken" }, { "json": "https://www.anchorterminal.com/compare/dydx-vs-kucoin.json", "title": "dYdX vs KuCoin", "url": "https://www.anchorterminal.com/compare/dydx-vs-kucoin" }, { "json": "https://www.anchorterminal.com/compare/dydx-vs-mexc.json", "title": "dYdX vs MEXC API", "url": "https://www.anchorterminal.com/compare/dydx-vs-mexc" }, { "json": "https://www.anchorterminal.com/compare/dydx-vs-okx.json", "title": "dYdX vs OKX API", "url": "https://www.anchorterminal.com/compare/dydx-vs-okx" }, { "json": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-dydx.json", "title": "Coinbase MCP server (Coinbase for Agents) vs dYdX", "url": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-dydx" } ], "panel": null, "scores": [ { "by": 38, "bybit": 45, "dydx": 83, "edge": "dydx", "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 15, "bybit": 73, "dydx": 58, "edge": "bybit", "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 0, "bybit": 66, "dydx": 66, "edge": "", "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "by": 18, "bybit": 60, "dydx": 78, "edge": "dydx", "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "by": 20, "bybit": 40, "dydx": 60, "edge": "dydx", "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 17, "bybit": 66, "dydx": 83, "edge": "dydx", "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 1, "bybit": 51, "dydx": 50, "edge": "bybit", "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "dYdX scores 69.5 (B) on agent readiness against Bybit's 57.3 (C), and leads in 4 of 7 scored categories. Bybit leads on schema \u0026 documentation. Both do exchange market data.", "tasks": null, "tutorials": [], "verdicts": { "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.", "dydx": "dYdX gives an agent keyless indexer reads, permissioned keys limited by message type, subaccount and market, a Statuspage with a clean 90 days, published fees and a testnet with a faucet. There is no official MCP server or OpenAPI file, orders are chain transactions signed by the clients, and no one entity operates the hosted endpoints." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/bybit-vs-dydx", "json": "https://www.anchorterminal.com/compare/bybit-vs-dydx.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/bybit-vs-dydx.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/bybit-vs-dydx.min.md" }, "markdown": "dYdX scores 69.5 (B) on agent readiness against Bybit's 57.3 (C), and leads in 4 of 7 scored categories. Bybit leads on schema \u0026 documentation. Both do exchange market data.\n\n- 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\n- dYdX: grade B, 69.5/100, rank #221 of 1349. Markdown https://www.anchorterminal.com/tools/dydx.md · JSON https://www.anchorterminal.com/api/v1/tools/dydx.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### Bybit (C)\n\nGood 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.\n\nAhead on:\n- Schema \u0026 documentation, 73 against 58\n\nAlso in its favour:\n- Runs on your own machine\n\nWatch for: No status page, incident history or SLA was found; the terms say the API is not guaranteed to be available\n\n### dYdX (B)\n\nGood for: An agent trading perpetuals from its own Cosmos wallet or through a permissioned key on an owner's account, outside the US, Canada and UK.\n\nAhead on:\n- Reliability, 83 against 45\n- Security \u0026 auth, 78 against 60\n- Payments \u0026 pricing, 60 against 40\n- Maintenance \u0026 community, 83 against 66\n\nAlso in its favour:\n- Open source\n\nWatch for: No official MCP server; the one registry entry is a third party's analytics server\n\n\n## Why the edge\n\n### Reliability: dYdX +38\n\n- Bybit (45): Graded with the hosted lines on the V5 API at api.bybit.com. No status page found (status.bybit.com does not resolve, the docs link none), so 0 for the page and 5 for no readable history. Rate limits are published per endpoint and per UID with numbers, plus a 600 per 5 second IP limit (15). Every response carries X-Bapi-Limit, X-Bapi-Limit-Status and X-Bapi-Limit-Reset-Timestamp, retCode 10006 and HTTP 403 are documented with a wait rule, and orders take a unique orderLinkId that amend and cancel accept (15). No SLA (0). V5 is the current production API, not a beta (10). 45.\n- dYdX (83): Read with the hosted lines on the indexer API and the chain endpoints the clients submit to. status.dydx.trade is an Atlassian Statuspage with Frontends, dYdX Chain, Indexer, Order Gateway and Client Libraries components and an RSS history (20). From 1 August to 3 November 2026 the feed has eight items, seven scheduled maintenance windows of 29 minutes to 2 hours (indexer on 9 September, 8 and 15 October, protocol v9.7 on 11 September and v9.8.0 on 12 October, WebSocket compression on 26 and 28 October) and one degraded instant-deposit path through an onboarding partner from 24 to 29 September, outside the trading API. Clean or trivial (30). Rate limits documented with numbers for the indexer, the block limits and the public nodes (15). No 429 shape or Retry-After for the indexer; short-term orders expire by `goodTilBlock` and client IDs let an agent find an order after a timeout (8 of 15). No SLA (0). Mainnet generally available; the Order Entry Gateway is marked testnet-only (10). 20 + 30 + 15 + 8 + 0 + 10 = 83.\n\n### Payments \u0026 pricing: dYdX +20\n\n- 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.\n- dYdX (60): No machine payment protocol (0). Fees public per tier without login (20). Testnet with a faucet and no card anywhere (20). No signup; an agent with a funded wallet trades, subject to the geographic terms (20). Total 60.\n\n### Security \u0026 auth: dYdX +18\n\n- 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.\n- dYdX (78): Orders are signed by the account key or by a permissioned key the owner adds as an authenticator, limited by message type, subaccount and market with AllOf or AnyOf, and revoked by `remove_authenticator`; no shared secret and nothing in a URL (28 of 30). A key can be confined to placing and cancelling orders on one subaccount with withdrawals and transfers excluded, though not to a position or order size, and the interface's default API wallet trades all cross-margin pairs (16 of 20). The API returns no untrusted content (10). Every action is a chain transaction and the indexer lists fills, orders and transfers per subaccount, and authenticators can be listed; no per-key log (10 of 15). A Cantina bug bounty up to $1,000,000 sponsored by dYdX Trading Inc. over the protocol, indexer, web client and SDKs, an Informal Systems audit; no security.txt and no certification (14 of 20). Total 78.\n\n### Maintenance \u0026 community: dYdX +17\n\n- 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.\n- dYdX (83): Read on the clients and the chain. v4-clients was pushed on 29 October 2026 and protocol v9.8.0 shipped on 12 October (30). Protocol v9.7 on 11 September, v9.8.0 on 12 October, v4-client-js tags 3.5.0 and 3.6.0, three or more in 90 days (20). A Discord, a help centre and 36 open issues on v4-clients whose replies couldn't be read (12 of 25). Official SDKs current, the TypeScript client at 3.6.0 and the Python client at 1.1.6 from February 2026 (12 of 15). CI workflows for lint, test, publish and audit, with trusted publishing and provenance on npm (9 of 10). Total 83.\n\n### Schema \u0026 documentation: Bybit +15\n\n- 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.\n- dYdX (58): No OpenAPI file found for the indexer; the docs publish a types reference of about 200 pages (OrderSide, TimeInForce, OrderStatus and the rest) and the chain's protobuf messages are in the clients (8 of 25). llms.txt and Markdown docs (10). Endpoint pages describe each call and the guides say when to use short-term against long-term orders and the indexer against the node, but descriptions are short (12 of 20). Enums and types on every field in the reference, with pagination and cursor parameters typed (11 of 15). Examples in Python, TypeScript and Rust for each step; errors are described by HTTP status (400 malformed, 404 not found) with no code list (9 of 15). A /v4 path, protocol releases dated on the status page, deprecated rate-limit fields marked, but no API changelog (8 of 15). Total 58.\n\n## Score by category\n\n| Category | Weight | Bybit | dYdX | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 45 | 83 | dYdX +38 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 73 | 58 | Bybit +15 |\n| Agent ergonomics | 13% (16.2 this run) | 66 | 66 | even |\n| Security \u0026 auth | 14% (17.5 this run) | 60 | 78 | dYdX +18 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 60 | dYdX +20 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 66 | 83 | dYdX +17 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 51 | 50 | Bybit +1 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **57.3 · C** | **69.5 · B** | |\n\n## Facts side by side\n\n| Fact | Bybit | dYdX |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Bybit | dYdX Trading Inc. |\n| Hosted endpoint | no (local only) | no (local only) |\n| Transports | stdio | |\n| Auth | API key | OAuth or key |\n| Pricing | Pay per use | Pay per use |\n| x402 | no | no |\n| Licence | none | The clients are AGPL-3.0 with a use condition tied to the v4 Terms of Use; the chain software (dydxprotocol/v4-chain) carries a custom licence GitHub cannot classify. The hosted indexer at indexer.dydx.trade and the front end are run by third parties, not dYdX Trading Inc. |\n| Tools exposed | 398 | 0 |\n| Read-only variant documented | yes | no |\n| llms.txt | no | yes |\n| Last release | 2026-10-30 | 2026-10-29 |\n| Terms last updated | couldn't be read | 2026-03-12 |\n| Privacy policy last updated | couldn't be read | 2025-06-06 |\n| Customer content may train models | couldn't be read | not found in the text |\n| Terms restrict automated access | couldn't be read | not found in the text |\n| Terms restrict benchmarking | couldn't be read | not found in the text |\n| Terms or service can change without notice | couldn't be read | yes |\n| Arbitration or class-action waiver | couldn't be read | yes |\n| Popularity | 43 stars | 119 stars, 86k npm/wk |\n\n## Verdicts\n\n**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.\n\n**dYdX.** dYdX gives an agent keyless indexer reads, permissioned keys limited by message type, subaccount and market, a Statuspage with a clean 90 days, published fees and a testnet with a faucet. There is no official MCP server or OpenAPI file, orders are chain transactions signed by the clients, and no one entity operates the hosted endpoints.\n\n## Before you call either\n\n### Bybit\n\n1. 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\n2. Send a unique orderLinkId on every order and reuse it when amending or cancelling, since create-order is asynchronous and confirmed over WebSocket\n3. 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\n4. Test on api-demo.bybit.com with a demo key from the production account, not on testnet demo mode, which the docs call meaningless\n5. 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\n\n### dYdX\n\n1. Ask the account owner for an authenticator limited to `/dydxprotocol.clob.MsgPlaceOrder` and `MsgCancelOrder` on one subaccount, and keep its private key out of prompts\n2. Set a unique 32-bit `clientId` on every order and look it up on `/v4/orders` after a timeout; short-term orders expire with `goodTilBlock` (at most 20 blocks ahead)\n3. Stay under 2 stateful orders a block and 20 per 100 blocks; failed placements count, so use short-term orders for active trading\n4. Enable permessage-deflate on the indexer WebSocket; since 26 October 2026 connections without compression may be refused with 426\n5. Check `/v4/geo` and the compliance screen before trading for a person, since the terms exclude the United States, Canada and the United Kingdom\n\n## Questions\n\n### Which is better for AI agents, Bybit or dYdX?\n\ndYdX scores 69.5 (B) on agent readiness against Bybit's 57.3 (C), and leads in 4 of 7 scored categories. Bybit leads on schema \u0026 documentation.\n\n### Do Bybit and dYdX need an API key?\n\nBybit needs an API key. dYdX takes an API key or an OAuth sign-in.\n\n### Can an agent call Bybit and dYdX without installing anything?\n\nBybit runs on your own machine, with no hosted endpoint listed. No hosted endpoint is listed for dYdX.\n\n### Are Bybit and dYdX open source?\n\nNo open-source release is listed for Bybit. dYdX is open source (The clients are AGPL-3.0 with a use condition tied to the v4 Terms of Use; the chain software (dydxprotocol/v4-chain) carries a custom licence GitHub cannot classify. The hosted indexer at indexer.dydx.trade and the front end are run by third parties, not dYdX Trading Inc.).\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/bybit-vs-dydx.json, and with the fewest tokens: https://www.anchorterminal.com/compare/bybit-vs-dydx.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"bybit\", \"b\": \"dydx\"}`. From a terminal: `anchor compare bybit dydx`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/bybit.json and https://www.anchorterminal.com/api/v1/tools/dydx.json\n\n## Other comparisons with Bybit or dYdX\n\n- [Bitfinex API vs Bybit](https://www.anchorterminal.com/compare/bitfinex-vs-bybit.md)\n- [Bitfinex API vs dYdX](https://www.anchorterminal.com/compare/bitfinex-vs-dydx.md)\n- [Bitget vs Bybit](https://www.anchorterminal.com/compare/bitget-vs-bybit.md)\n- [Bitget vs dYdX](https://www.anchorterminal.com/compare/bitget-vs-dydx.md)\n- [Bithumb Open API vs Bybit](https://www.anchorterminal.com/compare/bithumb-vs-bybit.md)\n- [Bithumb Open API vs dYdX](https://www.anchorterminal.com/compare/bithumb-vs-dydx.md)\n- [Bitstamp API vs Bybit](https://www.anchorterminal.com/compare/bitstamp-vs-bybit.md)\n- [Bitstamp API vs dYdX](https://www.anchorterminal.com/compare/bitstamp-vs-dydx.md)\n- [Bybit vs Coinbase Advanced Trade API](https://www.anchorterminal.com/compare/bybit-vs-coinbase-advanced-trade.md)\n- [Bybit vs Coinbase MCP server (Coinbase for Agents)](https://www.anchorterminal.com/compare/bybit-vs-coinbase-mcp.md)\n- [Bybit vs Crypto.com Exchange API](https://www.anchorterminal.com/compare/bybit-vs-crypto-com-exchange.md)\n- [Bybit vs Deribit](https://www.anchorterminal.com/compare/bybit-vs-deribit.md)\n- [Bybit vs Gate](https://www.anchorterminal.com/compare/bybit-vs-gate-io.md)\n- [Bybit vs Gemini Exchange API](https://www.anchorterminal.com/compare/bybit-vs-gemini-exchange.md)\n- [Bybit vs HTX trading API](https://www.anchorterminal.com/compare/bybit-vs-htx.md)\n- [Bybit vs Hyperliquid](https://www.anchorterminal.com/compare/bybit-vs-hyperliquid.md)\n- [Bybit vs Kraken API](https://www.anchorterminal.com/compare/bybit-vs-kraken.md)\n- [Bybit vs KuCoin](https://www.anchorterminal.com/compare/bybit-vs-kucoin.md)\n- [Bybit vs MEXC API](https://www.anchorterminal.com/compare/bybit-vs-mexc.md)\n- [Bybit vs OKX API](https://www.anchorterminal.com/compare/bybit-vs-okx.md)\n- [Bybit vs Uniswap Trading API](https://www.anchorterminal.com/compare/bybit-vs-uniswap.md)\n- [Bybit vs Upbit Open API](https://www.anchorterminal.com/compare/bybit-vs-upbit.md)\n- [Crypto.com Exchange API vs dYdX](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-dydx.md)\n- [dYdX vs Uniswap Trading API](https://www.anchorterminal.com/compare/dydx-vs-uniswap.md)\n- [dYdX vs Upbit Open API](https://www.anchorterminal.com/compare/dydx-vs-upbit.md)\n- [Binance API vs Bybit](https://www.anchorterminal.com/compare/binance-vs-bybit.md)\n- [Binance API vs dYdX](https://www.anchorterminal.com/compare/binance-vs-dydx.md)\n- [Coinbase Advanced Trade API vs dYdX](https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-dydx.md)\n- [Deribit vs dYdX](https://www.anchorterminal.com/compare/deribit-vs-dydx.md)\n- [dYdX vs Gate](https://www.anchorterminal.com/compare/dydx-vs-gate-io.md)\n- [dYdX vs Gemini Exchange API](https://www.anchorterminal.com/compare/dydx-vs-gemini-exchange.md)\n- [dYdX vs HTX trading API](https://www.anchorterminal.com/compare/dydx-vs-htx.md)\n- [dYdX vs Hyperliquid](https://www.anchorterminal.com/compare/dydx-vs-hyperliquid.md)\n- [dYdX vs Kraken API](https://www.anchorterminal.com/compare/dydx-vs-kraken.md)\n- [dYdX vs KuCoin](https://www.anchorterminal.com/compare/dydx-vs-kucoin.md)\n- [dYdX vs MEXC API](https://www.anchorterminal.com/compare/dydx-vs-mexc.md)\n- [dYdX vs OKX API](https://www.anchorterminal.com/compare/dydx-vs-okx.md)\n- [Coinbase MCP server (Coinbase for Agents) vs dYdX](https://www.anchorterminal.com/compare/coinbase-mcp-vs-dydx.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": "Bybit vs dYdX", "url": "" } ], "description": "dYdX scores 69.5 (B) to Bybit's 57.3 (C) for exchange market data. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Bybit C 57.3", "dYdX B 69.5", "scores" ], "h1": "Bybit vs dYdX", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/bybit-vs-dydx", "published": "2026-10-01", "section": "tools", "title": "Bybit vs dYdX for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-03", "url": "https://www.anchorterminal.com/compare/bybit-vs-dydx" }, "tokens": { "markdown": 4600, "slim": 2430 }, "version": 1 }