{ "data": { "a": { "slug": "binance", "name": "Binance API", "vendor": "Binance", "vendorUrl": "https://developers.binance.com/", "kind": "http-api", "category": "crypto-exchanges", "summary": "Binance's API covers spot, margin and futures trading, market data and account endpoints over REST, WebSocket and FIX, with a free spot testnet and a remote MCP server, documented on 30 October 2026, that trades inside a dedicated Agentic sub-account.", "url": "https://www.anchorterminal.com/tools/binance", "markdownUrl": "https://www.anchorterminal.com/tools/binance.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/binance.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/binance.json", "dns": "binance.grade.anchorterminal.com", "repo": "https://github.com/binance/binance-spot-api-docs", "license": "Proprietary hosted service under Binance's Terms of Use, which load by script and weren't read. The API docs, connectors, CLI and Skills Hub are open on GitHub under MIT", "transports": [ "streamable-http" ], "remoteUrl": "https://agent.binance.com/mcp/agentic", "packages": [], "auth": "mixed", "authNotes": "API key with an HMAC secret, or a self-generated RSA or Ed25519 key pair whose public key is registered, sent as X-MBX-APIKEY with a signed query and timestamp (recvWindow 5000 ms by default). Permissions are reading, spot and margin trading, futures and withdrawals; an HMAC key without an IP restriction can only read since 30 January 2023, and withdrawals need an IP restriction. Only Verified Plus accounts can create keys. The MCP server uses OAuth in a desktop browser with four scopes (market data, account, trade, transfer) on a dedicated Agentic sub-account and no withdrawal scope (https://www.binance.com/en/support/faq/detail/360002502072, https://developers.binance.com/en/docs/agent-native/mcp-server/agentic, checked 2026-11-03).", "pricing": "usage", "pricingNotes": "The API costs nothing to call. Spot trades carry a standard fee of 0.1 per cent for regular users per the fee FAQ; the maker and taker table on the fee page loads by script and wasn't read, nor were futures fees. Public market data and the spot testnet need no account; the testnet needs a GitHub login.", "priceSummary": "0.1% fee", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 on the exchange API or the MCP server in the docs read (checked 2026-11-03). A separate Binance x402 product is named in press coverage of Agent OS, which wasn't read first-hand.", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 4903, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://developers.binance.com/docs/binance-spot-api-docs/README", "llmsTxt": "https://developers.binance.com/en/docs/llms.txt", "capabilities": [ "exchange.spot-trading", "exchange.market-data", "exchange.derivatives", "exchange.balances", "exchange.transfers", "exchange.staking", "market.crypto" ], "tags": [ "hosted", "official", "closed-source", "api-key", "oauth", "mcp", "remote-mcp", "llms-txt", "sandbox", "python", "typescript", "java", "go", "cli", "usage-priced", "no-card" ], "lastRelease": "2026-10-30", "graded": true, "anchor": { "graded": true, "score": 63.2, "grade": "B", "agentReady": false, "rank": 448, "ranked": true, "rankOf": 1349, "categoryRank": 6, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 76, "maintenance": 81, "payments": 35, "reliability": 45, "schema": 86, "security": 72, "transparency": 43 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-03" }, "negative": 0, "verdict": "Binance publishes numeric rate limits, a free testnet with FIX, connectors in eight languages and, since late October 2026, a remote MCP server that trades only in a dedicated sub-account with no withdrawal scope. There is no status page, the terms and privacy notice could not be read, and the MCP tool list is not published.", "bestFor": "An agent trading a funded Binance account outside the prohibited countries, with the deepest set of markets in this group and a free testnet.", "strengths": [ "Rate limits published as per-endpoint weights with 6,000 a minute, 50 orders per 10 seconds and Retry-After on 429 and 418", "Spot testnet with REST, WebSocket and FIX endpoints, virtual balances and production limits, free with a GitHub login", "Official remote MCP server with OAuth scopes, an isolated Agentic sub-account, no withdrawal scope and confirmation before writes", "Keys with reading, trading, futures and withdrawal permissions; unrestricted-IP HMAC keys can only read and withdrawals need an IP restriction", "Dated changelog since 2018 with retirement dates announced months ahead, llms.txt and llms-full.txt" ], "weaknesses": [ "No status page or incident history found on binance.com or in the API docs", "The Terms of Use and privacy notice load by script and weren't read, so what they say about bots and API use is unknown", "The MCP server's tool list and schemas are not published; the docs describe four scopes", "The maker and taker fee table loads by script; only the 0.1 per cent standard rate in a FAQ was read", "binance-api-swagger was last pushed in October 2024, so the machine-readable spec lags the docs" ], "agentNotes": [ "Read the X-MBX-USED-WEIGHT and X-MBX-ORDER-COUNT headers and stop on 429 for the Retry-After seconds; a 418 ban runs 2 minutes to 3 days", "Treat a 5xx on an order as unknown, not failed, and query the order by origClientOrderId before retrying", "Use an Ed25519 key with an IP restriction and only the reading and trading permissions; never enable withdrawals for an agent key", "Develop on testnet.binance.vision with BINANCE_API_ENV=testnet; it resets about monthly without notice", "For the MCP route, the person must fund the Agentic sub-account from the web UI first; the agent cannot move funds in from the main account" ], "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": 63.2 } ], "editorialScores": { "ergonomics": 76, "maintenance": 81, "payments": 35, "reliability": 45, "schema": 86, "security": 72, "transparency": 31 }, "provenanceScore": 54, "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.binance.com/api/v3/ticker/price?symbol=BTCUSDT", "claudeCode": "claude mcp add binance-mcp-server --transport http https://agent.binance.com/mcp/agentic", "config": { "mcpServers": { "binance-mcp-server": { "url": "https://agent.binance.com/mcp/agentic" } } } }, "letme": { "capability": "https://letme.dev/exchange.spot-trading", "tool": "https://letme.dev/binance" }, "area": "payments", "unitPrices": [ { "item": "Spot trade, regular user", "unit": "pct", "usd": 0.1, "note": "standard fee per the fee FAQ; maker and taker table not read" } ], "provenance": { "legalEntity": "", "domain": "binance.com", "domainRegistered": "2017-04-01", "endpointOnVendorDomain": true, "terms": "https://www.binance.com/en/terms", "privacy": "https://www.binance.com/en-GB/about-legal/privacy-portal", "statusPage": "", "changelog": "https://developers.binance.com/docs/binance-spot-api-docs/CHANGELOG", "securityTxt": "unknown", "checked": "2026-11-03", "notes": [ "The Terms of Use and the privacy pages answered our reader with navigation and footer only, so no contracting entity, governing law or data-handling statement was read. The about page names three ADGM entities as regulated subsidiaries, not as the contracting party.", "RDAP gives binance.com a registration date of 1 April 2017.", "https://www.binance.com/.well-known/security.txt has a Contact line (security@binance.com) and no Expires or Policy line, so its validity is unknown under RFC 9116.", "No status page was found. www.binance.com/robots.txt allows the pages read and disallows */api/, */bapi/ and */my/; developers.binance.com and agent.binance.com have no robots.txt (404); api.binance.com and testnet.binance.vision disallow all crawlers, so no API call was made to either.", "The spot API changelog is dated, newest 30 October 2026." ], "score": 54 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/binance.json", "live": { "slug": "binance", "probe": { "target": "https://agent.binance.com/mcp/agentic", "method": "get", "lastAt": "2026-11-04T20:04:53.146241263Z", "lastOk": true, "lastStatus": 404, "lastMs": 554, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 474, "p95ms24h": 582, "samples24h": 48, "samples30d": 48, "days": [ { "date": "2026-11-04", "probes": 48, "ok": 48 } ] }, "githubStars": 4902, "securityTxt": { "url": "https://binance.com/.well-known/security.txt", "state": "valid", "checkedAt": "2026-11-04T15:53:46.658619838Z" }, "updatedAt": "2026-11-04T20:04:53.146241263Z" } }, "answer": "Binance API scores 63.2 (B) on agent readiness against Bitget's 53.9 (D), and leads in 4 of 7 scored categories. Bitget leads on agent ergonomics, payments \u0026 pricing and transparency \u0026 trust.", "b": { "slug": "bitget", "name": "Bitget", "vendor": "BTG Technology Holdings Limited", "vendorUrl": "https://www.bitget.com", "kind": "http-api", "category": "crypto-exchanges", "summary": "Bitget is a centralised crypto exchange for spot, margin, futures, earn and tokenised stocks, reached through its Unified Trading Account v3 REST and WebSocket API and an Agent Hub toolkit with a stdio MCP server, CLI and agent skills.", "url": "https://www.anchorterminal.com/tools/bitget", "markdownUrl": "https://www.anchorterminal.com/tools/bitget.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/bitget.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/bitget.json", "dns": "bitget.grade.anchorterminal.com", "repo": "https://github.com/Bitget-AI/agent-mcp", "transports": [ "stdio" ], "packages": [ { "registry": "npm", "name": "@bitget-ai/bitget-agent-mcp" }, { "registry": "npm", "name": "bitget-mcp-server" } ], "auth": "api-key", "authNotes": "API key, system-generated secret and user-set passphrase minted under API Key Management after a browser sign-up and identity verification, up to 50 keys per UID, each with read or read-and-write permission, signed per request with HMAC-SHA256 or RSA over timestamp, method, path and body in the ACCESS-KEY, ACCESS-SIGN, ACCESS-TIMESTAMP and ACCESS-PASSPHRASE headers. Binding an IP is recommended, not required. Sub-account keys carry trade or management permission, read-only or read-write, once the main account enables key management for them. Demo keys are minted in demo mode and sent with the paptrading header set to 1 (https://www.bitget.com/legacy-docs/uta/guide, checked 2026-11-03).", "pricing": "usage", "pricingNotes": "The API and the Agent Hub packages cost nothing; trades carry Bitget's fees. Base rates are 0.1 per cent maker and taker on spot and 0.02 per cent maker and 0.06 per cent taker on futures before VIP tiers or the BGB discount, which applies to spot only at a rate the article says to read on the live schedule. The fee page draws its table by script (https://www.bitget.com/support/articles/12560603892734, 20 August 2026, checked 2026-11-03).", "priceSummary": "0.1% fee", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the UTA docs, the Agent Hub READMEs, the SDK's openapi.yaml or the fee article (checked 2026-11-03).", "endpoints": [] }, "toolCount": 14, "popularity": { "githubStars": 234, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://www.bitget.com/api-doc/uta/intro", "registryName": "io.github.Bitget-AI/bitget-agent-mcp", "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", "mcp-registry", "official", "read-only-mode", "agent-skills", "cli", "python", "typescript", "go", "java", "php" ], "lastRelease": "2026-10-30", "graded": true, "anchor": { "graded": true, "score": 53.9, "grade": "D", "agentReady": false, "rank": 890, "ranked": true, "rankOf": 1349, "categoryRank": 15, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 83, "maintenance": 78, "payments": 40, "reliability": 40, "schema": 74, "security": 62, "transparency": 65 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-03" }, "negative": -8, "negativeNotes": [ "Security incident of 24 September 2026. An attacker who had obtained high-level internal credentials through a vulnerability in a third-party security product injected forged withdrawal commands into Bitget's wallet back end and moved about 388 million dollars in 13 assets on 11 chains from hot and warm wallets. Withdrawals, fiat and C2C were paused from 24 September and restored in phases from 28 September to 2 October 2026; trading, deposits and the API kept running. Bitget says user balances were unaffected, the Protection Fund covered the loss and was topped above 300 million dollars, private keys and cold wallets were untouched, and Mandiant and SlowMist reports of 30 September agree with its account. A fixed, documented incident with a public root cause, so below the top of the range. Sources https://www.bitget.com/academy/12560603896113 (updated 20 October 2026) and https://www.bitget.com/support/articles/12560603896110 (26 September 2026), read 2026-11-03." ], "verdict": "Bitget's official MCP server keeps the default surface to 14 intent tools with discovery, read-only and paper-trading switches, dry runs and a confirmation gate on withdrawals, over an API with demo trading. A 388 million dollar wallet breach in September 2026 paused withdrawals for eight days, and there is no status page, SLA or readable fee table.", "bestFor": "An agent trading spot, futures and earn products in a person's Bitget account outside the prohibited list, with the smallest default MCP surface of the exchanges graded and a paper-trading switch.", "strengths": [ "Official stdio MCP server with 14 intent tools by default, progressive discovery, `--read-only`, `--paper-trading`, `dryRun: true` on writes and `confirm: true` required for withdrawals and cancel-all", "Demo trading on the production host with demo keys and a paptrading header, and a TypeScript agent SDK whose openapi.yaml types all 109 UTA v3 operations", "Terms name BTG Technology Holdings Limited with Hong Kong law, and the privacy notice gives retention periods of 7 and up to 10 years", "Changelog with 58 dated entries since 5 August 2026, including preview notices with demo and live dates for WebSocket changes", "Base fees public in a help article, 0.1 per cent spot and 0.02 per cent maker and 0.06 per cent taker on futures" ], "weaknesses": [ "Hot and warm wallets lost about 388 million dollars on 24 September 2026 to forged withdrawal commands, and withdrawals were paused until 2 October", "No status page, incident history or SLA; the terms disclaim uninterrupted access", "Two official MCP servers coexist, the V2-based bitget-mcp-server on Bitget's own Agent Hub page and the v3 bitget-agent-mcp on GitHub and npm, with different tool counts", "The current api-doc site renders every page as the UTA overview for a reader without script; the legacy docs were used instead", "Keys have read or read-and-write only, with no separate withdrawal permission in the docs read, and IP binding is recommended rather than required" ], "agentNotes": [ "Run `npx -y @bitget-ai/bitget-agent-mcp --read-only` for research and `--paper-trading` with a demo key before any live order; the two flags cannot be combined", "Call discover({}) first, then the intent verbs; add `dryRun: true` to any write to preview it, and pass `confirm: true` only after the person has agreed to a withdraw or cancelAll", "Send a unique clientOid of at most 64 characters on every order and reuse it on retry; orderId wins when both are sent", "Stay under 10 requests a second per endpoint on a new account and 6,000 a minute per IP; the SDK retries on 429, so do not add a second retry loop", "Bind the key to an IP and keep write permission off a research key; the docs read show no separate withdrawal scope" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 53.9 } ], "editorialScores": { "ergonomics": 83, "maintenance": 78, "payments": 40, "reliability": 40, "schema": 74, "security": 62, "transparency": 53 }, "provenanceScore": 76, "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": "npx -y @bitget-ai/bitget-agent-mcp", "http": "curl https://api.bitget.com/api/v3/market/tickers?category=SPOT\u0026symbol=BTCUSDT", "claudeCode": "claude mcp add bitget -- npx -y @bitget-ai/bitget-agent-mcp --read-only", "config": { "mcpServers": { "bitget": { "args": [ "-y", "@bitget-ai/bitget-agent-mcp", "--read-only" ], "command": "npx", "env": { "BITGET_API_KEY": "YOUR_API_KEY", "BITGET_PASSPHRASE": "YOUR_PASSPHRASE", "BITGET_SECRET_KEY": "YOUR_SECRET_KEY" } } } } }, "letme": { "capability": "https://letme.dev/exchange.market-data", "tool": "https://letme.dev/bitget" }, "area": "payments", "unitPrices": [ { "item": "Spot trade, base maker or taker", "unit": "pct", "usd": 0.1, "note": "before VIP tiers and the BGB discount" }, { "item": "Futures trade, base taker", "unit": "pct", "usd": 0.06, "note": "maker 0.02 per cent" } ], "provenance": { "legalEntity": "BTG Technology Holdings Limited", "domain": "bitget.com", "domainRegistered": "2003-02-03", "endpointOnVendorDomain": true, "terms": "https://www.bitget.com/support/articles/360014944032-terms-of-use", "privacy": "https://www.bitget.com/support/articles/360015150651", "statusPage": "", "changelog": "https://www.bitget.com/legacy-docs/uta/changelog", "securityTxt": "none", "checked": "2026-11-03", "notes": [ "Terms of Use last updated 20 October 2026 name BTG Technology Holdings Limited under Hong Kong law with HKIAC arbitration; the privacy notice (5 December 2025) names the same company as controller under the Seychelles Data Protection Act 2023 with BTGT Europe Limited, UAB as EEA representative. /user-agreement and /privacy-policy answer 404; the documents live in the support centre.", "www.bitget.com/robots.txt disallows internal, search, calendar, wiki and register paths; the api-doc, legacy-docs, support, academy, blog and activity-hub paths are allowed.", "RDAP gives bitget.com a registration date of 3 February 2003 (MarkMonitor), earlier than the exchange, so the domain was bought.", "https://www.bitget.com/.well-known/security.txt answers 404; the Agent Hub README gives security@bitget.com for reports. No status page found; status.bitget.com does not resolve and the docs link none.", "The current api-doc site answers every path with the UTA overview for a reader without script; the legacy docs at /legacy-docs/uta/ were read for the guide, rate limits and changelog." ], "score": 76 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/bitget.json", "live": { "slug": "bitget", "versions": [ { "registry": "mcp-registry", "name": "io.github.Bitget-AI/bitget-agent-mcp", "version": "3.0.2", "seenAt": "2026-11-04T17:11:44.552009456Z" }, { "registry": "npm", "name": "@bitget-ai/bitget-agent-mcp", "version": "3.3.1", "seenAt": "2026-11-04T20:02:49.846993208Z" }, { "registry": "npm", "name": "bitget-mcp-server", "version": "1.1.0", "seenAt": "2026-11-04T20:02:50.714916236Z" } ], "githubStars": 1, "npmWeekly": 255, "securityTxt": { "url": "https://bitget.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-04T15:53:53.864777414Z" }, "updatedAt": "2026-11-04T20:02:53.43909091Z" } }, "edges": [ { "by": 22, "category": "transparency", "leads": "bitget", "name": "Transparency \u0026 trust", "reasons": { "a": "The editorial half. A closed service whose Terms of Use couldn't be read; the docs, connectors, CLI and skills are MIT on GitHub (10 of 30). The privacy notice couldn't be read, so no retention or subprocessor statement was checked; the prohibited-countries list is public and dated (5 of 30). The changelog gives retirement dates for SBE schemas and FIX fields months ahead (16 of 20). No subprocessor or data-location statement read (0 of 20). 10 + 5 + 16 + 0 = 31.", "b": "The editorial half. A closed hosted service with clear terms naming BTG Technology Holdings Limited; the toolkit is MIT (15 of 30). The privacy notice names the controller and EEA representative, gives 7-year and up to 10-year retention for compliance and litigation, and names recipients by category only (18 of 30). Deprecations and parameter changes carry effective dates (delta mode deprecated 27 August, symbol and category required from 30 September, snapshot changes with demo and live dates) but no written policy (15 of 20). Recipients by category, transfers under Seychelles law with no locations or provider names (5 of 20). 53." }, "scores": { "a": 43, "b": 65 } }, { "by": 12, "category": "schema", "leads": "binance", "name": "Schema \u0026 documentation", "reasons": { "a": "The docs are Markdown in a public repository with a Postman collection and a Swagger spec, but the spec was last pushed in October 2024 (20 of 25). llms.txt and llms-full.txt on developers.binance.com (10). Each endpoint states its weight, parameters and notes on behaviour, with less on when not to use one (15 of 20). Enums for order types, time in force and symbol filters, required columns in the parameter tables (12 of 15). Request and response examples throughout and an error code list with messages (14 of 15). A dated changelog since 2018 with retirements announced months ahead, such as the 2 September 2026 field removal notified on 2 December 2025 (15). 20 + 10 + 15 + 12 + 14 + 15 = 86.", "b": "The agent SDK ships openapi.yaml with 109 typed UTA v3 operations from which the tools are generated, a machine-readable contract from the vendor's own organisation though not on the docs site (20 of 25). llms.txt in the SDK and MCP repositories; the docs site has none (6 of 10). Intent tools with a discover tool that explains each verb, action and its risk level, and the server's initialize instructions state surface, modules and read-only posture (15 of 20). Typed inputs with enums and required fields from the OpenAPI source (12 of 15). Examples in the quick start and READMEs, a REST error code page in the legacy docs that we did not read in full (9 of 15). Changelog by day with preview notices and effective dates (12 of 15). 74." }, "scores": { "a": 86, "b": 74 } }, { "by": 10, "category": "security", "leads": "binance", "name": "Security \u0026 auth", "reasons": { "a": "API keys with HMAC, RSA or Ed25519 signatures, permissions for reading, trading, futures and withdrawals, an IP restriction, revocation in API Management, and OAuth with four scopes on the MCP server; no key expiry found (28 of 30). Read-only keys, sub-accounts, withdrawals only with an IP restriction, and the MCP server's isolated Agentic sub-account with no withdrawal scope and confirmation before writes (18 of 20). The API returns no untrusted content (10). Keys are listed in API Management and used weight is returned per call, but no per-call log for the operator was found (6 of 15). security.txt with a contact and no expiry, a Bugcrowd programme named in the proof-of-solvency repository, no certification read (10 of 20). 28 + 18 + 10 + 6 + 10 = 72.", "b": "API keys with read or read-and-write permission, a passphrase, HMAC-SHA256 or RSA signing, IP binding recommended, 50 keys per UID, revocation on the management page; no OAuth and no separate withdrawal scope in the docs read (22 of 30). --read-only strips write tools at start, --paper-trading routes to demo, and high-risk writes need `confirm: true` (18 of 20). Tools return the exchange's own data (10). Request and response hooks are forwarded as MCP log notifications; no per-call audit log on Bitget's side was found (6 of 15). security@bitget.com in the toolkit README, no security.txt, Mandiant and SlowMist reports on the September breach, a proof-of-reserves repository, no bounty page read (6 of 20). 62." }, "scores": { "a": 72, "b": 62 } }, { "by": 7, "category": "ergonomics", "leads": "bitget", "name": "Agent ergonomics", "reasons": { "a": "limit on depth, trades and klines, a symbols filter on exchangeInfo and tickers, and SBE encoding, though fields cannot be selected (16 of 25). fromId, startTime, endTime and limit on history endpoints (16 of 20). Error codes with messages an agent can branch on, such as the rate limit and timestamp errors (17 of 20). newClientOrderId on orders, a cancel-replace endpoint and the 5xx unknown-status rule, but no idempotency key on other writes (12 of 20). Connectors in nine languages, a CLI with testnet and demo profiles, and a timestamped HMAC or Ed25519 signature on every private call (15). 16 + 16 + 17 + 12 + 15 = 76.", "b": "Read for the API with the MCP server as the agent route. 14 compact tools by default, module filters, a full surface on request and progressive discovery (25). Cursor pagination on CFD order history since 15 October 2026 and limit parameters on lists (15 of 20). Uniform ok or error result shape from the SDK with typed error classes and compact JSON in the text channel (13 of 20). clientOid on orders, `dryRun: true` on every write, `confirm: true` gating cancelAll and withdraw, annotations derived from risk level including readOnlyHint, destructiveHint and idempotentHint (18 of 20). Few required fields, official SDKs in five languages plus the TypeScript agent SDK and a CLI (12 of 15). 83." }, "scores": { "a": 76, "b": 83 } }, { "by": 5, "category": "reliability", "leads": "binance", "name": "Reliability", "reasons": { "a": "Read with the hosted lines on the spot REST API. No status page was found on binance.com or in the API docs (0), so no incident record (5). Rate limits are published as per-endpoint weights with numbers from exchangeInfo, 6,000 request weight a minute, 50 orders per 10 seconds, 160,000 a day and 61,000 raw requests per 5 minutes, and FIX limits per session (15). 429 and 418 carry Retry-After, a 5xx is documented as unknown status to be queried, and orders take a client order id (15). No SLA (0). Generally available (10). 0 + 5 + 15 + 15 + 0 + 10 = 45.", "b": "Graded with the hosted lines on the UTA v3 API at api.bitget.com. No status page found (status.bitget.com does not resolve, the docs link none), so 0 for the page and 5 for no readable history; the September 2026 breach is in the deduction, not here. Rate limits are published as 6,000 per IP per minute and per-endpoint UID limits by VIP level (15). An x-mbx-used-remain-limit header is documented and the agent SDK backs off on 429, orders take a clientOid of up to 64 characters, but the breach error code and a Retry-After rule were not read (10 of 15). No SLA (0). UTA v3 is the production API (10). 40." }, "scores": { "a": 45, "b": 40 } }, { "by": 5, "category": "payments", "leads": "bitget", "name": "Payments \u0026 pricing", "reasons": { "a": "No machine payment protocol (0). A 0.1 per cent standard spot fee is stated in the fee FAQ; the maker and taker table and futures fees load by script and weren't read (15 of 20). Public market data needs no key and the testnet is free with a GitHub login (20). A person signs up, passes Verified Plus verification, deposits and mints a key (0). 0 + 15 + 20 + 0 = 35.", "b": "No machine payment protocol (0). Base spot and futures rates are stated in a help article without login, the tier table draws by script (20). Market data needs no key, demo trading costs nothing and no card is asked for at sign-up (20). A person registers, verifies identity and mints the key in a browser (0). 40." }, "scores": { "a": 35, "b": 40 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Binance", "b": "BTG Technology Holdings Limited", "name": "Vendor" }, { "a": "https://agent.binance.com/mcp/agentic", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "Streamable HTTP", "b": "stdio", "name": "Transports" }, { "a": "OAuth or 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 service under Binance's Terms of Use, which load by script and weren't read. The API docs, connectors, CLI and Skills Hub are open on GitHub under MIT", "b": "none", "name": "Licence" }, { "a": "none", "b": "14", "name": "Tools exposed" }, { "a": "no", "b": "yes", "name": "Read-only variant documented" }, { "a": "yes", "b": "no", "name": "llms.txt" }, { "a": "not listed", "b": "io.github.Bitget-AI/bitget-agent-mcp", "name": "MCP registry" }, { "a": "2026-10-30", "b": "2026-10-30", "name": "Last release" }, { "a": "couldn't be read", "b": "2026-10-20", "name": "Terms last updated" }, { "a": "couldn't be read", "b": "2025-12-05", "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": "yes", "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": "4.9k stars", "b": "234 stars", "name": "Popularity" } ], "faq": [ { "answer": "Binance API scores 63.2 (B) on agent readiness against Bitget's 53.9 (D), and leads in 4 of 7 scored categories. Bitget leads on agent ergonomics, payments \u0026 pricing and transparency \u0026 trust.", "question": "Which is better for AI agents, Binance API or Bitget?" }, { "answer": "Binance API takes an API key or an OAuth sign-in. Bitget needs an API key.", "question": "Do Binance API and Bitget need an API key?" }, { "answer": "Binance API has a hosted endpoint at https://agent.binance.com/mcp/agentic. Bitget runs on your own machine, with no hosted endpoint listed.", "question": "Can an agent call Binance API and Bitget without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 45 against 40", "Schema \u0026 documentation, 86 against 74", "Security \u0026 auth, 72 against 62" ], "also": [ "A hosted endpoint, with nothing to install", "Free to start without a card", "No incidents deducted, where Bitget loses 8 points for them" ], "goodFor": "An agent trading a funded Binance account outside the prohibited countries, with the deepest set of markets in this group and a free testnet.", "slug": "binance", "watchFor": "No status page or incident history found on binance.com or in the API docs" }, { "aheadOn": [ "Agent ergonomics, 83 against 76", "Payments \u0026 pricing, 40 against 35", "Transparency \u0026 trust, 65 against 43" ], "also": [ "Runs on your own machine" ], "goodFor": "An agent trading spot, futures and earn products in a person's Bitget account outside the prohibited list, with the smallest default MCP surface of the exchanges graded and a paper-trading switch.", "slug": "bitget", "watchFor": "Hot and warm wallets lost about 388 million dollars on 24 September 2026 to forged withdrawal commands, and withdrawals were paused until 2 October" } ], "history": null, "job": { "capability": "exchange.spot-trading", "name": "Exchange spot trading" }, "others": [ { "json": "https://www.anchorterminal.com/compare/bitfinex-vs-bitget.json", "title": "Bitfinex API vs Bitget", "url": "https://www.anchorterminal.com/compare/bitfinex-vs-bitget" }, { "json": "https://www.anchorterminal.com/compare/bitget-vs-bithumb.json", "title": "Bitget vs Bithumb Open API", "url": "https://www.anchorterminal.com/compare/bitget-vs-bithumb" }, { "json": "https://www.anchorterminal.com/compare/bitget-vs-bitstamp.json", "title": "Bitget vs Bitstamp API", "url": "https://www.anchorterminal.com/compare/bitget-vs-bitstamp" }, { "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-coinbase-advanced-trade.json", "title": "Bitget vs Coinbase Advanced Trade API", "url": "https://www.anchorterminal.com/compare/bitget-vs-coinbase-advanced-trade" }, { "json": "https://www.anchorterminal.com/compare/bitget-vs-coinbase-mcp.json", "title": "Bitget vs Coinbase MCP server (Coinbase for Agents)", "url": "https://www.anchorterminal.com/compare/bitget-vs-coinbase-mcp" }, { "json": "https://www.anchorterminal.com/compare/bitget-vs-crypto-com-exchange.json", "title": "Bitget vs Crypto.com Exchange API", "url": "https://www.anchorterminal.com/compare/bitget-vs-crypto-com-exchange" }, { "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-dydx.json", "title": "Bitget vs dYdX", "url": "https://www.anchorterminal.com/compare/bitget-vs-dydx" }, { "json": "https://www.anchorterminal.com/compare/bitget-vs-gate-io.json", "title": "Bitget vs Gate", "url": "https://www.anchorterminal.com/compare/bitget-vs-gate-io" }, { "json": "https://www.anchorterminal.com/compare/bitget-vs-gemini-exchange.json", "title": "Bitget vs Gemini Exchange API", "url": "https://www.anchorterminal.com/compare/bitget-vs-gemini-exchange" }, { "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/bitget-vs-hyperliquid.json", "title": "Bitget vs Hyperliquid", "url": "https://www.anchorterminal.com/compare/bitget-vs-hyperliquid" }, { "json": "https://www.anchorterminal.com/compare/bitget-vs-kraken.json", "title": "Bitget vs Kraken API", "url": "https://www.anchorterminal.com/compare/bitget-vs-kraken" }, { "json": "https://www.anchorterminal.com/compare/bitget-vs-kucoin.json", "title": "Bitget vs KuCoin", "url": "https://www.anchorterminal.com/compare/bitget-vs-kucoin" }, { "json": "https://www.anchorterminal.com/compare/bitget-vs-mexc.json", "title": "Bitget vs MEXC API", "url": "https://www.anchorterminal.com/compare/bitget-vs-mexc" }, { "json": "https://www.anchorterminal.com/compare/bitget-vs-okx.json", "title": "Bitget vs OKX API", "url": "https://www.anchorterminal.com/compare/bitget-vs-okx" }, { "json": "https://www.anchorterminal.com/compare/bitget-vs-uniswap.json", "title": "Bitget vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/bitget-vs-uniswap" }, { "json": "https://www.anchorterminal.com/compare/bitget-vs-upbit.json", "title": "Bitget vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/bitget-vs-upbit" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-bitfinex.json", "title": "Binance API vs Bitfinex API", "url": "https://www.anchorterminal.com/compare/binance-vs-bitfinex" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-bithumb.json", "title": "Binance API vs Bithumb Open API", "url": "https://www.anchorterminal.com/compare/binance-vs-bithumb" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-bitstamp.json", "title": "Binance API vs Bitstamp API", "url": "https://www.anchorterminal.com/compare/binance-vs-bitstamp" }, { "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-coinbase-advanced-trade.json", "title": "Binance API vs Coinbase Advanced Trade API", "url": "https://www.anchorterminal.com/compare/binance-vs-coinbase-advanced-trade" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-coinbase-mcp.json", "title": "Binance API vs Coinbase MCP server (Coinbase for Agents)", "url": "https://www.anchorterminal.com/compare/binance-vs-coinbase-mcp" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-crypto-com-exchange.json", "title": "Binance API vs Crypto.com Exchange API", "url": "https://www.anchorterminal.com/compare/binance-vs-crypto-com-exchange" }, { "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-gate-io.json", "title": "Binance API vs Gate", "url": "https://www.anchorterminal.com/compare/binance-vs-gate-io" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-gemini-exchange.json", "title": "Binance API vs Gemini Exchange API", "url": "https://www.anchorterminal.com/compare/binance-vs-gemini-exchange" }, { "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/binance-vs-hyperliquid.json", "title": "Binance API vs Hyperliquid", "url": "https://www.anchorterminal.com/compare/binance-vs-hyperliquid" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-kraken.json", "title": "Binance API vs Kraken API", "url": "https://www.anchorterminal.com/compare/binance-vs-kraken" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-kucoin.json", "title": "Binance API vs KuCoin", "url": "https://www.anchorterminal.com/compare/binance-vs-kucoin" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-mexc.json", "title": "Binance API vs MEXC API", "url": "https://www.anchorterminal.com/compare/binance-vs-mexc" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-okx.json", "title": "Binance API vs OKX API", "url": "https://www.anchorterminal.com/compare/binance-vs-okx" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-uniswap.json", "title": "Binance API vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/binance-vs-uniswap" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-upbit.json", "title": "Binance API vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/binance-vs-upbit" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-dydx.json", "title": "Binance API vs dYdX", "url": "https://www.anchorterminal.com/compare/binance-vs-dydx" } ], "panel": null, "scores": [ { "binance": 45, "bitget": 40, "by": 5, "edge": "binance", "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "binance": 86, "bitget": 74, "by": 12, "edge": "binance", "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "binance": 76, "bitget": 83, "by": 7, "edge": "bitget", "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "binance": 72, "bitget": 62, "by": 10, "edge": "binance", "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "binance": 35, "bitget": 40, "by": 5, "edge": "bitget", "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "binance": 81, "bitget": 78, "by": 3, "edge": "binance", "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "binance": 43, "bitget": 65, "by": 22, "edge": "bitget", "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Binance API scores 63.2 (B) on agent readiness against Bitget's 53.9 (D), and leads in 4 of 7 scored categories. Bitget leads on agent ergonomics, payments \u0026 pricing and transparency \u0026 trust. Both do exchange spot trading.", "tasks": null, "tutorials": [], "verdicts": { "binance": "Binance publishes numeric rate limits, a free testnet with FIX, connectors in eight languages and, since late October 2026, a remote MCP server that trades only in a dedicated sub-account with no withdrawal scope. There is no status page, the terms and privacy notice could not be read, and the MCP tool list is not published.", "bitget": "Bitget's official MCP server keeps the default surface to 14 intent tools with discovery, read-only and paper-trading switches, dry runs and a confirmation gate on withdrawals, over an API with demo trading. A 388 million dollar wallet breach in September 2026 paused withdrawals for eight days, and there is no status page, SLA or readable fee table." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/binance-vs-bitget", "json": "https://www.anchorterminal.com/compare/binance-vs-bitget.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/binance-vs-bitget.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/binance-vs-bitget.min.md" }, "markdown": "Binance API scores 63.2 (B) on agent readiness against Bitget's 53.9 (D), and leads in 4 of 7 scored categories. Bitget leads on agent ergonomics, payments \u0026 pricing and transparency \u0026 trust. Both do exchange spot trading.\n\n- Binance API: grade B, 63.2/100, rank #448 of 1349. Markdown https://www.anchorterminal.com/tools/binance.md · JSON https://www.anchorterminal.com/api/v1/tools/binance.json\n- Bitget: grade D, 53.9/100, rank #890 of 1349. Markdown https://www.anchorterminal.com/tools/bitget.md · JSON https://www.anchorterminal.com/api/v1/tools/bitget.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### Binance API (B)\n\nGood for: An agent trading a funded Binance account outside the prohibited countries, with the deepest set of markets in this group and a free testnet.\n\nAhead on:\n- Reliability, 45 against 40\n- Schema \u0026 documentation, 86 against 74\n- Security \u0026 auth, 72 against 62\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n- Free to start without a card\n- No incidents deducted, where Bitget loses 8 points for them\n\nWatch for: No status page or incident history found on binance.com or in the API docs\n\n### Bitget (D)\n\nGood for: An agent trading spot, futures and earn products in a person's Bitget account outside the prohibited list, with the smallest default MCP surface of the exchanges graded and a paper-trading switch.\n\nAhead on:\n- Agent ergonomics, 83 against 76\n- Payments \u0026 pricing, 40 against 35\n- Transparency \u0026 trust, 65 against 43\n\nAlso in its favour:\n- Runs on your own machine\n\nWatch for: Hot and warm wallets lost about 388 million dollars on 24 September 2026 to forged withdrawal commands, and withdrawals were paused until 2 October\n\n\n## Why the edge\n\n### Transparency \u0026 trust: Bitget +22\n\n- Binance API (43): The editorial half. A closed service whose Terms of Use couldn't be read; the docs, connectors, CLI and skills are MIT on GitHub (10 of 30). The privacy notice couldn't be read, so no retention or subprocessor statement was checked; the prohibited-countries list is public and dated (5 of 30). The changelog gives retirement dates for SBE schemas and FIX fields months ahead (16 of 20). No subprocessor or data-location statement read (0 of 20). 10 + 5 + 16 + 0 = 31.\n- Bitget (65): The editorial half. A closed hosted service with clear terms naming BTG Technology Holdings Limited; the toolkit is MIT (15 of 30). The privacy notice names the controller and EEA representative, gives 7-year and up to 10-year retention for compliance and litigation, and names recipients by category only (18 of 30). Deprecations and parameter changes carry effective dates (delta mode deprecated 27 August, symbol and category required from 30 September, snapshot changes with demo and live dates) but no written policy (15 of 20). Recipients by category, transfers under Seychelles law with no locations or provider names (5 of 20). 53.\n\n### Schema \u0026 documentation: Binance API +12\n\n- Binance API (86): The docs are Markdown in a public repository with a Postman collection and a Swagger spec, but the spec was last pushed in October 2024 (20 of 25). llms.txt and llms-full.txt on developers.binance.com (10). Each endpoint states its weight, parameters and notes on behaviour, with less on when not to use one (15 of 20). Enums for order types, time in force and symbol filters, required columns in the parameter tables (12 of 15). Request and response examples throughout and an error code list with messages (14 of 15). A dated changelog since 2018 with retirements announced months ahead, such as the 2 September 2026 field removal notified on 2 December 2025 (15). 20 + 10 + 15 + 12 + 14 + 15 = 86.\n- Bitget (74): The agent SDK ships openapi.yaml with 109 typed UTA v3 operations from which the tools are generated, a machine-readable contract from the vendor's own organisation though not on the docs site (20 of 25). llms.txt in the SDK and MCP repositories; the docs site has none (6 of 10). Intent tools with a discover tool that explains each verb, action and its risk level, and the server's initialize instructions state surface, modules and read-only posture (15 of 20). Typed inputs with enums and required fields from the OpenAPI source (12 of 15). Examples in the quick start and READMEs, a REST error code page in the legacy docs that we did not read in full (9 of 15). Changelog by day with preview notices and effective dates (12 of 15). 74.\n\n### Security \u0026 auth: Binance API +10\n\n- Binance API (72): API keys with HMAC, RSA or Ed25519 signatures, permissions for reading, trading, futures and withdrawals, an IP restriction, revocation in API Management, and OAuth with four scopes on the MCP server; no key expiry found (28 of 30). Read-only keys, sub-accounts, withdrawals only with an IP restriction, and the MCP server's isolated Agentic sub-account with no withdrawal scope and confirmation before writes (18 of 20). The API returns no untrusted content (10). Keys are listed in API Management and used weight is returned per call, but no per-call log for the operator was found (6 of 15). security.txt with a contact and no expiry, a Bugcrowd programme named in the proof-of-solvency repository, no certification read (10 of 20). 28 + 18 + 10 + 6 + 10 = 72.\n- Bitget (62): API keys with read or read-and-write permission, a passphrase, HMAC-SHA256 or RSA signing, IP binding recommended, 50 keys per UID, revocation on the management page; no OAuth and no separate withdrawal scope in the docs read (22 of 30). --read-only strips write tools at start, --paper-trading routes to demo, and high-risk writes need `confirm: true` (18 of 20). Tools return the exchange's own data (10). Request and response hooks are forwarded as MCP log notifications; no per-call audit log on Bitget's side was found (6 of 15). security@bitget.com in the toolkit README, no security.txt, Mandiant and SlowMist reports on the September breach, a proof-of-reserves repository, no bounty page read (6 of 20). 62.\n\n### Agent ergonomics: Bitget +7\n\n- Binance API (76): limit on depth, trades and klines, a symbols filter on exchangeInfo and tickers, and SBE encoding, though fields cannot be selected (16 of 25). fromId, startTime, endTime and limit on history endpoints (16 of 20). Error codes with messages an agent can branch on, such as the rate limit and timestamp errors (17 of 20). newClientOrderId on orders, a cancel-replace endpoint and the 5xx unknown-status rule, but no idempotency key on other writes (12 of 20). Connectors in nine languages, a CLI with testnet and demo profiles, and a timestamped HMAC or Ed25519 signature on every private call (15). 16 + 16 + 17 + 12 + 15 = 76.\n- Bitget (83): Read for the API with the MCP server as the agent route. 14 compact tools by default, module filters, a full surface on request and progressive discovery (25). Cursor pagination on CFD order history since 15 October 2026 and limit parameters on lists (15 of 20). Uniform ok or error result shape from the SDK with typed error classes and compact JSON in the text channel (13 of 20). clientOid on orders, `dryRun: true` on every write, `confirm: true` gating cancelAll and withdraw, annotations derived from risk level including readOnlyHint, destructiveHint and idempotentHint (18 of 20). Few required fields, official SDKs in five languages plus the TypeScript agent SDK and a CLI (12 of 15). 83.\n\n### Reliability: Binance API +5\n\n- Binance API (45): Read with the hosted lines on the spot REST API. No status page was found on binance.com or in the API docs (0), so no incident record (5). Rate limits are published as per-endpoint weights with numbers from exchangeInfo, 6,000 request weight a minute, 50 orders per 10 seconds, 160,000 a day and 61,000 raw requests per 5 minutes, and FIX limits per session (15). 429 and 418 carry Retry-After, a 5xx is documented as unknown status to be queried, and orders take a client order id (15). No SLA (0). Generally available (10). 0 + 5 + 15 + 15 + 0 + 10 = 45.\n- Bitget (40): Graded with the hosted lines on the UTA v3 API at api.bitget.com. No status page found (status.bitget.com does not resolve, the docs link none), so 0 for the page and 5 for no readable history; the September 2026 breach is in the deduction, not here. Rate limits are published as 6,000 per IP per minute and per-endpoint UID limits by VIP level (15). An x-mbx-used-remain-limit header is documented and the agent SDK backs off on 429, orders take a clientOid of up to 64 characters, but the breach error code and a Retry-After rule were not read (10 of 15). No SLA (0). UTA v3 is the production API (10). 40.\n\n### Payments \u0026 pricing: Bitget +5\n\n- Binance API (35): No machine payment protocol (0). A 0.1 per cent standard spot fee is stated in the fee FAQ; the maker and taker table and futures fees load by script and weren't read (15 of 20). Public market data needs no key and the testnet is free with a GitHub login (20). A person signs up, passes Verified Plus verification, deposits and mints a key (0). 0 + 15 + 20 + 0 = 35.\n- Bitget (40): No machine payment protocol (0). Base spot and futures rates are stated in a help article without login, the tier table draws by script (20). Market data needs no key, demo trading costs nothing and no card is asked for at sign-up (20). A person registers, verifies identity and mints the key in a browser (0). 40.\n\n## Score by category\n\n| Category | Weight | Binance API | Bitget | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 45 | 40 | Binance API +5 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 86 | 74 | Binance API +12 |\n| Agent ergonomics | 13% (16.2 this run) | 76 | 83 | Bitget +7 |\n| Security \u0026 auth | 14% (17.5 this run) | 72 | 62 | Binance API +10 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 35 | 40 | Bitget +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 81 | 78 | Binance API +3 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 43 | 65 | Bitget +22 |\n| Negative events | ≤15 | 0 | -8 | |\n| **Total** | | **63.2 · B** | **53.9 · D** | |\n\n## Facts side by side\n\n| Fact | Binance API | Bitget |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Binance | BTG Technology Holdings Limited |\n| Hosted endpoint | `https://agent.binance.com/mcp/agentic` | no (local only) |\n| Transports | Streamable HTTP | stdio |\n| Auth | OAuth or key | API key |\n| Pricing | Pay per use | Pay per use |\n| x402 | no | no |\n| Licence | Proprietary hosted service under Binance's Terms of Use, which load by script and weren't read. The API docs, connectors, CLI and Skills Hub are open on GitHub under MIT | none |\n| Tools exposed | none | 14 |\n| Read-only variant documented | no | yes |\n| llms.txt | yes | no |\n| MCP registry | not listed | `io.github.Bitget-AI/bitget-agent-mcp` |\n| Last release | 2026-10-30 | 2026-10-30 |\n| Terms last updated | couldn't be read | 2026-10-20 |\n| Privacy policy last updated | couldn't be read | 2025-12-05 |\n| Customer content may train models | couldn't be read | not found in the text |\n| Terms restrict automated access | couldn't be read | yes |\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 | 4.9k stars | 234 stars |\n\n## Verdicts\n\n**Binance API.** Binance publishes numeric rate limits, a free testnet with FIX, connectors in eight languages and, since late October 2026, a remote MCP server that trades only in a dedicated sub-account with no withdrawal scope. There is no status page, the terms and privacy notice could not be read, and the MCP tool list is not published.\n\n**Bitget.** Bitget's official MCP server keeps the default surface to 14 intent tools with discovery, read-only and paper-trading switches, dry runs and a confirmation gate on withdrawals, over an API with demo trading. A 388 million dollar wallet breach in September 2026 paused withdrawals for eight days, and there is no status page, SLA or readable fee table.\n\n## Before you call either\n\n### Binance API\n\n1. Read the X-MBX-USED-WEIGHT and X-MBX-ORDER-COUNT headers and stop on 429 for the Retry-After seconds; a 418 ban runs 2 minutes to 3 days\n2. Treat a 5xx on an order as unknown, not failed, and query the order by origClientOrderId before retrying\n3. Use an Ed25519 key with an IP restriction and only the reading and trading permissions; never enable withdrawals for an agent key\n4. Develop on testnet.binance.vision with BINANCE_API_ENV=testnet; it resets about monthly without notice\n5. For the MCP route, the person must fund the Agentic sub-account from the web UI first; the agent cannot move funds in from the main account\n\n### Bitget\n\n1. Run `npx -y @bitget-ai/bitget-agent-mcp --read-only` for research and `--paper-trading` with a demo key before any live order; the two flags cannot be combined\n2. Call discover({}) first, then the intent verbs; add `dryRun: true` to any write to preview it, and pass `confirm: true` only after the person has agreed to a withdraw or cancelAll\n3. Send a unique clientOid of at most 64 characters on every order and reuse it on retry; orderId wins when both are sent\n4. Stay under 10 requests a second per endpoint on a new account and 6,000 a minute per IP; the SDK retries on 429, so do not add a second retry loop\n5. Bind the key to an IP and keep write permission off a research key; the docs read show no separate withdrawal scope\n\n## Questions\n\n### Which is better for AI agents, Binance API or Bitget?\n\nBinance API scores 63.2 (B) on agent readiness against Bitget's 53.9 (D), and leads in 4 of 7 scored categories. Bitget leads on agent ergonomics, payments \u0026 pricing and transparency \u0026 trust.\n\n### Do Binance API and Bitget need an API key?\n\nBinance API takes an API key or an OAuth sign-in. Bitget needs an API key.\n\n### Can an agent call Binance API and Bitget without installing anything?\n\nBinance API has a hosted endpoint at https://agent.binance.com/mcp/agentic. Bitget runs on your own machine, with no hosted endpoint listed.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/binance-vs-bitget.json, and with the fewest tokens: https://www.anchorterminal.com/compare/binance-vs-bitget.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"binance\", \"b\": \"bitget\"}`. From a terminal: `anchor compare binance bitget`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/binance.json and https://www.anchorterminal.com/api/v1/tools/bitget.json\n\n## Other comparisons with Binance API or Bitget\n\n- [Bitfinex API vs Bitget](https://www.anchorterminal.com/compare/bitfinex-vs-bitget.md)\n- [Bitget vs Bithumb Open API](https://www.anchorterminal.com/compare/bitget-vs-bithumb.md)\n- [Bitget vs Bitstamp API](https://www.anchorterminal.com/compare/bitget-vs-bitstamp.md)\n- [Bitget vs Bybit](https://www.anchorterminal.com/compare/bitget-vs-bybit.md)\n- [Bitget vs Coinbase Advanced Trade API](https://www.anchorterminal.com/compare/bitget-vs-coinbase-advanced-trade.md)\n- [Bitget vs Coinbase MCP server (Coinbase for Agents)](https://www.anchorterminal.com/compare/bitget-vs-coinbase-mcp.md)\n- [Bitget vs Crypto.com Exchange API](https://www.anchorterminal.com/compare/bitget-vs-crypto-com-exchange.md)\n- [Bitget vs Deribit](https://www.anchorterminal.com/compare/bitget-vs-deribit.md)\n- [Bitget vs dYdX](https://www.anchorterminal.com/compare/bitget-vs-dydx.md)\n- [Bitget vs Gate](https://www.anchorterminal.com/compare/bitget-vs-gate-io.md)\n- [Bitget vs Gemini Exchange API](https://www.anchorterminal.com/compare/bitget-vs-gemini-exchange.md)\n- [Bitget vs HTX trading API](https://www.anchorterminal.com/compare/bitget-vs-htx.md)\n- [Bitget vs Hyperliquid](https://www.anchorterminal.com/compare/bitget-vs-hyperliquid.md)\n- [Bitget vs Kraken API](https://www.anchorterminal.com/compare/bitget-vs-kraken.md)\n- [Bitget vs KuCoin](https://www.anchorterminal.com/compare/bitget-vs-kucoin.md)\n- [Bitget vs MEXC API](https://www.anchorterminal.com/compare/bitget-vs-mexc.md)\n- [Bitget vs OKX API](https://www.anchorterminal.com/compare/bitget-vs-okx.md)\n- [Bitget vs Uniswap Trading API](https://www.anchorterminal.com/compare/bitget-vs-uniswap.md)\n- [Bitget vs Upbit Open API](https://www.anchorterminal.com/compare/bitget-vs-upbit.md)\n- [Binance API vs Bitfinex API](https://www.anchorterminal.com/compare/binance-vs-bitfinex.md)\n- [Binance API vs Bithumb Open API](https://www.anchorterminal.com/compare/binance-vs-bithumb.md)\n- [Binance API vs Bitstamp API](https://www.anchorterminal.com/compare/binance-vs-bitstamp.md)\n- [Binance API vs Bybit](https://www.anchorterminal.com/compare/binance-vs-bybit.md)\n- [Binance API vs Coinbase Advanced Trade API](https://www.anchorterminal.com/compare/binance-vs-coinbase-advanced-trade.md)\n- [Binance API vs Coinbase MCP server (Coinbase for Agents)](https://www.anchorterminal.com/compare/binance-vs-coinbase-mcp.md)\n- [Binance API vs Crypto.com Exchange API](https://www.anchorterminal.com/compare/binance-vs-crypto-com-exchange.md)\n- [Binance API vs Deribit](https://www.anchorterminal.com/compare/binance-vs-deribit.md)\n- [Binance API vs Gate](https://www.anchorterminal.com/compare/binance-vs-gate-io.md)\n- [Binance API vs Gemini Exchange API](https://www.anchorterminal.com/compare/binance-vs-gemini-exchange.md)\n- [Binance API vs HTX trading API](https://www.anchorterminal.com/compare/binance-vs-htx.md)\n- [Binance API vs Hyperliquid](https://www.anchorterminal.com/compare/binance-vs-hyperliquid.md)\n- [Binance API vs Kraken API](https://www.anchorterminal.com/compare/binance-vs-kraken.md)\n- [Binance API vs KuCoin](https://www.anchorterminal.com/compare/binance-vs-kucoin.md)\n- [Binance API vs MEXC API](https://www.anchorterminal.com/compare/binance-vs-mexc.md)\n- [Binance API vs OKX API](https://www.anchorterminal.com/compare/binance-vs-okx.md)\n- [Binance API vs Uniswap Trading API](https://www.anchorterminal.com/compare/binance-vs-uniswap.md)\n- [Binance API vs Upbit Open API](https://www.anchorterminal.com/compare/binance-vs-upbit.md)\n- [Binance API vs dYdX](https://www.anchorterminal.com/compare/binance-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": "Binance API vs Bitget", "url": "" } ], "description": "Binance scores 63.2 (B) to Bitget's 53.9 (D) for exchange spot trading. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Binance API B 63.2", "Bitget D 53.9", "scores" ], "h1": "Binance API vs Bitget", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/binance-vs-bitget", "published": "2026-10-01", "section": "tools", "title": "Binance vs Bitget for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-03", "url": "https://www.anchorterminal.com/compare/binance-vs-bitget" }, "tokens": { "markdown": 4800, "slim": 2680 }, "version": 1 }