{ "data": { "similar": [ { "grade": "BB", "json": "https://www.anchorterminal.com/tools/gemini-exchange.json", "name": "Gemini Exchange API", "score": 74.6, "shared": [ "exchange.market-data", "exchange.spot-trading", "exchange.derivatives", "exchange.balances", "exchange.transfers", "exchange.staking", "market.crypto" ], "slug": "gemini-exchange" }, { "grade": "BB", "json": "https://www.anchorterminal.com/tools/kraken.json", "name": "Kraken API", "score": 71, "shared": [ "exchange.spot-trading", "exchange.market-data", "exchange.derivatives", "exchange.balances", "exchange.transfers", "exchange.staking", "market.crypto" ], "slug": "kraken" }, { "grade": "B", "json": "https://www.anchorterminal.com/tools/okx.json", "name": "OKX API", "score": 64.3, "shared": [ "exchange.spot-trading", "exchange.market-data", "exchange.derivatives", "exchange.balances", "exchange.transfers", "exchange.staking", "market.crypto" ], "slug": "okx" }, { "grade": "C", "json": "https://www.anchorterminal.com/tools/bitfinex.json", "name": "Bitfinex API", "score": 58.4, "shared": [ "exchange.market-data", "exchange.spot-trading", "exchange.derivatives", "exchange.balances", "exchange.transfers", "exchange.staking", "market.crypto" ], "slug": "bitfinex" }, { "grade": "C", "json": "https://www.anchorterminal.com/tools/bybit.json", "name": "Bybit", "score": 57.3, "shared": [ "exchange.market-data", "exchange.spot-trading", "exchange.derivatives", "exchange.balances", "exchange.transfers", "exchange.staking", "market.crypto" ], "slug": "bybit" }, { "grade": "C", "json": "https://www.anchorterminal.com/tools/gate-io.json", "name": "Gate", "score": 56.4, "shared": [ "exchange.market-data", "exchange.spot-trading", "exchange.derivatives", "exchange.balances", "exchange.transfers", "exchange.staking", "market.crypto" ], "slug": "gate-io" } ], "tool": { "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" ], "breakdown": [ { "key": "reliability", "name": "Reliability", "weight": 16, "effectiveWeight": 20, "score": 45, "points": 9, "reason": "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.", "checked": "2026-11-03" }, { "key": "performance", "name": "Performance", "weight": 10, "effectiveWeight": 0, "pending": true, "points": 0, "reason": "Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes." }, { "key": "schema", "name": "Schema \u0026 documentation", "weight": 13, "effectiveWeight": 16.25, "score": 86, "points": 13.98, "reason": "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.", "checked": "2026-11-03" }, { "key": "ergonomics", "name": "Agent ergonomics", "weight": 13, "effectiveWeight": 16.25, "score": 76, "points": 12.35, "reason": "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.", "checked": "2026-11-03" }, { "key": "security", "name": "Security \u0026 auth", "weight": 14, "effectiveWeight": 17.5, "score": 72, "points": 12.6, "reason": "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.", "checked": "2026-11-03" }, { "key": "payments", "name": "Payments \u0026 pricing", "weight": 10, "effectiveWeight": 12.5, "score": 35, "points": 4.38, "reason": "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.", "checked": "2026-11-03" }, { "key": "tasks", "name": "Task success", "weight": 10, "effectiveWeight": 0, "pending": true, "points": 0, "reason": "Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored." }, { "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7, "effectiveWeight": 8.75, "score": 81, "points": 7.09, "reason": "Read as a closed service. The spot changelog's newest entry is 30 October 2026, the MCP docs are dated 30 October and binance-cli v2.2.0 shipped on 20 October (30). Changelog entries on 2 September, 18 September, 27 October and 30 October (20). A public changelog, connectors pushed in October and a Skills Hub merging pull requests weekly; issue replies not read (10 of 15). Official connectors in nine languages current as of October 2026; the MCP server is not in the official registry (15). Connector CI not read; the CLI publishes release installers (6 of 10). 30 + 20 + 10 + 15 + 6 = 81.", "checked": "2026-11-03" }, { "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7, "effectiveWeight": 8.75, "score": 43, "points": 3.76, "note": "editorial 31, provenance 54", "reason": "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.", "checked": "2026-11-03" } ], "assessment": { "date": "2026-11-03", "basis": "public evidence", "confidence": "medium", "notes": { "ergonomics": "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.", "maintenance": "Read as a closed service. The spot changelog's newest entry is 30 October 2026, the MCP docs are dated 30 October and binance-cli v2.2.0 shipped on 20 October (30). Changelog entries on 2 September, 18 September, 27 October and 30 October (20). A public changelog, connectors pushed in October and a Skills Hub merging pull requests weekly; issue replies not read (10 of 15). Official connectors in nine languages current as of October 2026; the MCP server is not in the official registry (15). Connector CI not read; the CLI publishes release installers (6 of 10). 30 + 20 + 10 + 15 + 6 = 81.", "payments": "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.", "reliability": "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.", "schema": "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.", "security": "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.", "transparency": "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." }, "sources": [ { "what": "robots.txt (www.binance.com)", "url": "https://www.binance.com/robots.txt", "seen": "2026-11-03" }, { "what": "general API information (limits model, key types, 429 and 418)", "url": "https://developers.binance.com/docs/binance-spot-api-docs/rest-api/general-api-information", "seen": "2026-11-03" }, { "what": "limits page", "url": "https://developers.binance.com/docs/binance-spot-api-docs/rest-api/limits", "seen": "2026-11-03" }, { "what": "exchangeInfo rateLimits sample", "url": "https://developers.binance.com/docs/binance-spot-api-docs/rest-api/general-endpoints", "seen": "2026-11-03" }, { "what": "FIX API", "url": "https://developers.binance.com/docs/binance-spot-api-docs/fix-api", "seen": "2026-11-03" }, { "what": "spot API changelog (newest 30 October 2026, oldest 14 January 2018)", "url": "https://developers.binance.com/docs/binance-spot-api-docs/CHANGELOG", "seen": "2026-11-03" }, { "what": "Agent Native overview", "url": "https://developers.binance.com/en/docs/agent-native/overview", "seen": "2026-11-03" }, { "what": "MCP server introduction", "url": "https://developers.binance.com/en/docs/agent-native/mcp-server", "seen": "2026-11-03" }, { "what": "Binance MCP Server (scopes, sub-account, setup)", "url": "https://developers.binance.com/en/docs/agent-native/mcp-server/agentic", "seen": "2026-11-03" }, { "what": "MCP protected-resource metadata", "url": "https://agent.binance.com/.well-known/oauth-protected-resource", "seen": "2026-11-03" }, { "what": "spot testnet", "url": "https://testnet.binance.vision/", "seen": "2026-11-03" }, { "what": "API key creation FAQ", "url": "https://www.binance.com/en/support/faq/detail/360002502072", "seen": "2026-11-03" }, { "what": "fee structure FAQ", "url": "https://www.binance.com/en/support/faq/detail/115000429332", "seen": "2026-11-03" }, { "what": "fee page (table loads by script)", "url": "https://www.binance.com/en/fee/trading", "seen": "2026-11-03" }, { "what": "list of prohibited countries", "url": "https://www.binance.com/en/legal/list-of-prohibited-countries", "seen": "2026-11-03" }, { "what": "Terms of Use (navigation only)", "url": "https://www.binance.com/en/terms", "seen": "2026-11-03" }, { "what": "privacy page (navigation only)", "url": "https://www.binance.com/en/privacy", "seen": "2026-11-03" }, { "what": "about page", "url": "https://www.binance.com/en/about", "seen": "2026-11-03" }, { "what": "security.txt", "url": "https://www.binance.com/.well-known/security.txt", "seen": "2026-11-03" }, { "what": "GitHub organisation repositories", "url": "https://api.github.com/orgs/binance/repos?per_page=100\u0026sort=updated", "seen": "2026-11-03" }, { "what": "binance-skills-hub, shallow clone", "url": "https://github.com/binance/binance-skills-hub", "seen": "2026-11-03" }, { "what": "binance-cli, shallow clone (tags)", "url": "https://github.com/binance/binance-cli", "seen": "2026-11-03" }, { "what": "official MCP registry search", "url": "https://registry.modelcontextprotocol.io/v0/servers?search=binance", "seen": "2026-11-03" }, { "what": "RDAP for binance.com", "url": "https://rdap.verisign.com/com/v1/domain/binance.com", "seen": "2026-11-03" } ], "openQuestions": [ "unchecked: the Terms of Use and the privacy notice, which load by script and answered with navigation only, so the contracting entity, governing law, API and bot clauses and data handling are unread. The prohibited-countries list is from a readable legal page dated 27 February 2024.", "unchecked: the maker and taker fee table and futures fees. Only the 0.1 per cent standard spot fee in the fee FAQ was read.", "unchecked: the MCP server's tools and schemas. tools/list needs a signed-in account and was not called; the docs give four scopes and no tool count. Its launch date is not stated; the docs pages carry a last-modified date of 30 October 2026, and press coverage of a Binance Agent OS was not used.", "No status page was found on binance.com or in the docs; Binance.US has one and is a separate exchange. Scored absent.", "firstReleased is 14 January 2018, the oldest entry in the spot API changelog; the exchange launched in July 2017 per the about page.", "Kind http-api, not mcp. The MCP server is one route to the same markets, is weeks old and is documented without a tool list, while the REST, WebSocket and FIX APIs carry the docs, connectors and testnet.", "Legal entity left empty. No readable page names the contracting party; the about page lists ADGM subsidiaries and Wikipedia gives Binance Holdings Ltd.", "api.binance.com and testnet.binance.vision disallow all crawlers in robots.txt, so exchangeInfo was not called; the limit numbers come from the docs' sample response." ] }, "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 }, "scoreHistory": [ { "date": "2026-11-03", "grade": "B", "kind": "listed", "method": "0.7", "score": 63.2 } ] }, "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" }, "notable": [ "Binance runs an official remote MCP server at https://agent.binance.com/mcp/agentic (Streamable HTTP, OAuth in a desktop browser, scopes market data, account, trade and transfer). Agents trade spot, margin, convert and futures inside a dedicated Agentic sub-account that the person funds by hand, with no withdrawal scope and confirmation before orders, cancels and transfers. The docs pages are dated 30 October 2026. It is not in the official MCP registry, where nine Binance servers sit under io.github namespaces (https://developers.binance.com/en/docs/agent-native/mcp-server/agentic, https://registry.modelcontextprotocol.io/v0/servers?search=binance)", "The MCP server's protected-resource metadata names agent.binance.com as its authorisation server and lists no scopes. The tool list is not published outside tools/list, which we did not call (https://agent.binance.com/.well-known/oauth-protected-resource)", "Rate limits are per IP, published per endpoint as weights. exchangeInfo reports 6,000 request weight a minute, 50 orders per 10 seconds, 160,000 orders a day and 61,000 raw requests per 5 minutes. 429 carries Retry-After; an IP that keeps sending after 429 gets a 418 ban of 2 minutes to 3 days (https://developers.binance.com/docs/binance-spot-api-docs/rest-api/general-endpoints)", "FIX 4.4 over TLS for spot only, with order entry, drop copy and market data sessions, Ed25519 keys only, 10,000 messages per 10 seconds on order entry and a FIX_API or FIX_API_READ_ONLY key permission (https://developers.binance.com/docs/binance-spot-api-docs/fix-api)", "The spot testnet at testnet.binance.vision has REST, WebSocket and FIX endpoints, virtual balances and the production limits, and resets about once a month without notice (https://testnet.binance.vision/)", "binance-skills-hub (1,121 stars) publishes 21 agent skills, among them one that drives binance-cli (Rust, v2.2.0 on 20 October 2026) for spot, futures and convert; no local MCP server is in the organisation's repositories (https://github.com/binance/binance-skills-hub)", "The spot API changelog's newest entry is 30 October 2026, a reminder that the SBE 3:3 schema retires on 9 November; the oldest is 14 January 2018 (https://developers.binance.com/docs/binance-spot-api-docs/CHANGELOG)", "Binance lists Canada, the Netherlands, the United States, Cuba, North Korea, Iran, Syria and Crimea and non-government-controlled areas of Ukraine as prohibited, updated 27 February 2024 (https://www.binance.com/en/legal/list-of-prohibited-countries)", "No status page was found on binance.com or in the API docs; the Terms of Use and privacy notice load by script and answered our reader with navigation only" ], "area": "payments", "details": [ { "label": "Surface listed", "value": "The spot REST API at api.binance.com/api/v3, with its WebSocket, FIX and futures siblings, read from developers.binance.com, testnet.binance.vision, binance.com support pages and the binance GitHub organisation on 3 November 2026. No account was made, no key was used and no MCP session was opened" }, { "label": "MCP server", "value": "Official, remote, at https://agent.binance.com/mcp/agentic over Streamable HTTP. OAuth in a desktop browser with scopes market data, account, trade and transfer, on a dedicated Agentic sub-account; no withdrawal scope; confirmation before orders, cancels and transfers. Tool count not published; docs dated 30 October 2026; not in the official MCP registry. Supported clients per the docs are Claude Code, Claude Desktop, Codex CLI, ChatGPT, VS Code and Grok Bot" }, { "label": "Key permissions", "value": "Reading, spot and margin trading, futures and withdrawals, with an IP access restriction. Unrestricted-IP HMAC keys are reading only since 30 January 2023, withdrawals need an IP restriction, and keys need a Verified Plus account. FIX needs the FIX_API or FIX_API_READ_ONLY permission" }, { "label": "Rate limits", "value": "Per IP, as weights per endpoint. 6,000 request weight a minute, 50 orders per 10 seconds, 160,000 orders a day, 61,000 raw requests per 5 minutes, per exchangeInfo. 429 with Retry-After, 418 bans of 2 minutes to 3 days for repeat offenders, 403 for WAF blocks. FIX order entry 10,000 messages per 10 seconds" }, { "label": "Testnet", "value": "testnet.binance.vision with REST (/api only), WebSocket API and streams, and FIX hosts, keys by GitHub login or registered RSA and Ed25519 public keys, virtual balances, resets about monthly with no notice" }, { "label": "Countries", "value": "Prohibited per Binance's list of 27 February 2024 are Canada, the Netherlands, the United States, Cuba, North Korea, Iran, Syria, and Crimea and non-government-controlled areas of Ukraine, plus other places Binance designates. Binance.US is a separate exchange" }, { "label": "Fees", "value": "0.1 per cent standard spot fee for regular users per the fee FAQ. The maker and taker table and futures fees load by script and weren't read" }, { "label": "FIX and WebSocket", "value": "FIX 4.4 over TLS (spot only) with order entry, drop copy and market data sessions and SBE ports, Ed25519 keys only. WebSocket API at ws-api.binance.com and market streams; testnet twins of each" }, { "label": "Terms on automated trading", "value": "Not read. The Terms of Use at binance.com/en/terms load by script and answered with navigation only. The Skills Hub README says the person is responsible for all trading decisions and that Binance may change or discontinue the feature" }, { "label": "Skills and CLI", "value": "binance-skills-hub, 21 skills under MIT for OpenClaw, Claude Code and similar, installed with npx skills add; the binance skill drives binance-cli (Rust, v2.2.0 on 20 October 2026) with profiles for prod, testnet and demo" }, { "label": "SDKs", "value": "Official connectors for Python, JavaScript, TypeScript, Java, Go, Rust, PHP, Ruby and .NET on GitHub, most pushed in October 2026; a Postman collection; a Swagger spec last pushed in October 2024" }, { "label": "Status", "value": "No status page found on binance.com or in the API docs" }, { "label": "Legal entity", "value": "Not named on a page we could read. The about page lists three Abu Dhabi Global Market entities (Nest Exchange Limited, Nest Clearing and Custody Limited, Nest Trading Limited) regulated by the FSRA; Wikipedia gives Binance Holdings Ltd." } ], "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, "checks": [ { "check": "Legal entity named", "value": "not found", "points": 0, "max": 20, "state": "no" }, { "check": "Domain age", "value": "binance.com, registered 2017-04-01 (9 years)", "points": 11, "max": 15, "state": "part" }, { "check": "Endpoint on the vendor's domain", "value": "agent.binance.com", "points": 15, "max": 15, "state": "ok" }, { "check": "Terms of service", "value": "published, but our reader couldn't read it", "points": 7, "max": 10, "state": "part" }, { "check": "Privacy policy", "value": "published, but our reader couldn't read it", "points": 7, "max": 10, "state": "part" }, { "check": "Status page", "value": "not found", "points": 0, "max": 10, "state": "no" }, { "check": "Changelog", "value": "published", "points": 10, "max": 10, "state": "ok" }, { "check": "security.txt", "value": "could not be fetched", "points": 0, "max": 10, "state": "no" }, { "check": "People named", "value": "3 named with their role, none with a public profile", "points": 7, "max": 10, "state": "part" }, { "check": "Support route", "value": "help pages, a community", "points": 5, "max": 5, "state": "ok" } ], "policies": [ { "kind": "terms", "url": "https://www.binance.com/en/terms", "state": "unreadable", "reason": "the page has 0 words of text without a browser, so the document is drawn by script or sits elsewhere", "readAt": "2026-11-03", "points": 7, "max": 10 }, { "kind": "privacy", "url": "https://www.binance.com/en-GB/about-legal/privacy-portal", "state": "unreadable", "reason": "the page has 0 words of text without a browser, so the document is drawn by script or sits elsewhere", "readAt": "2026-11-03", "points": 7, "max": 10 } ] }, "humans": { "slug": "binance", "checked": "2026-11-03", "company": "Binance", "people": [ { "name": "Changpeng Zhao", "role": "Co-founder and former CEO, Binance", "founder": true, "bio": "Changpeng Zhao, known as CZ, started Binance in July 2017 and led it as chief executive until November 2023. Binance's about page lists him as co-founder and former CEO.", "bioSources": [ "https://www.binance.com/en/about", "https://en.wikipedia.org/wiki/Binance" ], "page": "/people/changpeng-zhao/" }, { "name": "Yi He", "role": "Co-founder and co-CEO, Binance", "founder": true, "bio": "Yi He co-founded Binance with Changpeng Zhao and is its co-CEO. Binance's about page says she leads the company's business, marketing and branding strategy.", "bioSources": [ "https://www.binance.com/en/about", "https://en.wikipedia.org/wiki/Binance" ], "page": "/people/yi-he/" }, { "name": "Richard Teng", "role": "Co-CEO, Binance", "bio": "Richard Teng is co-CEO of Binance alongside Yi He, per Wikipedia. He is not named on the about page we read.", "bioSources": [ "https://en.wikipedia.org/wiki/Binance" ], "page": "/people/richard-teng/" } ], "peopleNote": "The about page at binance.com/en/about names Changpeng Zhao as co-founder and former CEO and Yi He as co-CEO and co-founder; it names no other officer. Richard Teng's role rests on Wikipedia's Binance article. The Terms of Use load by script, so no page we read names the contracting company; the about page lists three Abu Dhabi Global Market subsidiaries. Investors were looked for on the about and press pages and in two searches. MGX of Abu Dhabi took a minority stake for $2 billion in March 2025, reported by The Block from a Binance release we could not read first-hand. No earlier outside investor was found; Binance describes the MGX deal as its first institutional investment.", "companySocial": { "x": "https://x.com/binance", "github": "https://github.com/binance" }, "support": { "urls": [ "https://www.binance.com/en/support", "https://developers.binance.com/" ], "community": [ { "label": "Spot API docs issues", "url": "https://github.com/binance/binance-spot-api-docs/issues", "kind": "github" }, { "label": "Skills Hub repository", "url": "https://github.com/binance/binance-skills-hub", "kind": "github" } ] }, "sources": [ "https://www.binance.com/en/about", "https://en.wikipedia.org/wiki/Binance", "https://www.theblock.co/post/345932/binance-secures-2-billion-investment-from-abu-dhabis-mgx-in-landmark-crypto-deal", "https://developers.binance.com/", "https://github.com/binance" ], "ownership": { "status": "private", "checked": "2026-11-03", "sources": [ "https://en.wikipedia.org/wiki/Binance", "https://www.theblock.co/post/345932/binance-secures-2-billion-investment-from-abu-dhabis-mgx-in-landmark-crypto-deal" ] }, "investors": [ { "name": "MGX", "kind": "corporate", "rounds": [ "Minority investment, March 2025" ], "url": "https://www.mgx.ae/", "source": "https://www.theblock.co/post/345932/binance-secures-2-billion-investment-from-abu-dhabis-mgx-in-landmark-crypto-deal", "quote": "Binance secures $2 billion investment from Abu Dhabi's MGX in landmark crypto deal", "page": "/investors/mgx/" } ] }, "pageJsonUrl": "https://www.anchorterminal.com/tools/binance.json", "live": { "slug": "binance", "probe": { "target": "https://agent.binance.com/mcp/agentic", "method": "get", "lastAt": "2026-11-04T19:34:23.262708367Z", "lastOk": true, "lastStatus": 404, "lastMs": 594, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 475, "p95ms24h": 582, "samples24h": 43, "samples30d": 43, "days": [ { "date": "2026-11-04", "probes": 43, "ok": 43 } ] }, "securityTxt": { "url": "https://binance.com/.well-known/security.txt", "state": "valid", "checkedAt": "2026-11-04T15:53:46.658619838Z" }, "updatedAt": "2026-11-04T19:34:23.262708367Z" } }, "verify": { "accepts": "a page on binance.com or one of its subdomains, or the README at the root of github.com/binance/binance-spot-api-docs", "badgeUrl": "https://www.anchorterminal.com/badges/binance.svg", "body": { "slug": "binance", "url": "the page with the badge or the link" }, "docs": "https://www.anchorterminal.com/builders/#verify", "effect": "none, it never changes a grade, rank or review", "endpoint": "https://www.anchorterminal.com/api/v1/verify", "listingUrl": "https://www.anchorterminal.com/tools/binance", "mcpTool": "verify_listing", "recheck": "weekly; two failed checks in a row and it lapses, a later pass restores it", "snippets": { "html": "\u003ca href=\"https://www.anchorterminal.com/tools/binance\"\u003e\u003cimg src=\"https://www.anchorterminal.com/badges/binance.svg\" alt=\"Binance API on Anchor Terminal\" height=\"20\"\u003e\u003c/a\u003e", "markdown": "[![Binance API on Anchor Terminal](https://www.anchorterminal.com/badges/binance.svg)](https://www.anchorterminal.com/tools/binance)", "link": "\u003ca href=\"https://www.anchorterminal.com/tools/binance\"\u003eBinance API on Anchor Terminal\u003c/a\u003e" } } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/tools/binance", "json": "https://www.anchorterminal.com/tools/binance.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/tools/binance.md", "mcp": "https://www.anchorterminal.com/mcp", "pricing": "https://www.anchorterminal.com/tools/binance#pricing", "reviews": "https://www.anchorterminal.com/tools/binance#reviews", "slim": "https://www.anchorterminal.com/tools/binance.min.md" }, "markdown": "## Overview\n\n**Grade B · 63.2/100 · rank #448 of 1349 · #6 in Crypto exchanges · not agent-ready · confidence medium**\n\n\n## Assessment\n\nBinance 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## Facts\n\n| Field | Value |\n| --- | --- |\n| Vendor | Binance (https://developers.binance.com/) |\n| Kind | HTTP API |\n| Category | Crypto exchanges (https://www.anchorterminal.com/categories/crypto-exchanges) |\n| Transport | Streamable HTTP |\n| Endpoint | `https://agent.binance.com/mcp/agentic` |\n| Auth | OAuth or key · 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). |\n| Pricing | Pay per use (0.1% fee) · 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. |\n| x402 | No · 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. |\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 |\n| Source | https://github.com/binance/binance-spot-api-docs |\n| Docs | https://developers.binance.com/docs/binance-spot-api-docs/README |\n| llms.txt | https://developers.binance.com/en/docs/llms.txt |\n| Last release | 2026-10-30 |\n| GitHub stars | 4,903 (as of 2026-11-03) |\n| Surface listed | The spot REST API at api.binance.com/api/v3, with its WebSocket, FIX and futures siblings, read from developers.binance.com, testnet.binance.vision, binance.com support pages and the binance GitHub organisation on 3 November 2026. No account was made, no key was used and no MCP session was opened |\n| MCP server | Official, remote, at https://agent.binance.com/mcp/agentic over Streamable HTTP. OAuth in a desktop browser with scopes market data, account, trade and transfer, on a dedicated Agentic sub-account; no withdrawal scope; confirmation before orders, cancels and transfers. Tool count not published; docs dated 30 October 2026; not in the official MCP registry. Supported clients per the docs are Claude Code, Claude Desktop, Codex CLI, ChatGPT, VS Code and Grok Bot |\n| Key permissions | Reading, spot and margin trading, futures and withdrawals, with an IP access restriction. Unrestricted-IP HMAC keys are reading only since 30 January 2023, withdrawals need an IP restriction, and keys need a Verified Plus account. FIX needs the FIX_API or FIX_API_READ_ONLY permission |\n| Rate limits | Per IP, as weights per endpoint. 6,000 request weight a minute, 50 orders per 10 seconds, 160,000 orders a day, 61,000 raw requests per 5 minutes, per exchangeInfo. 429 with Retry-After, 418 bans of 2 minutes to 3 days for repeat offenders, 403 for WAF blocks. FIX order entry 10,000 messages per 10 seconds |\n| Testnet | testnet.binance.vision with REST (/api only), WebSocket API and streams, and FIX hosts, keys by GitHub login or registered RSA and Ed25519 public keys, virtual balances, resets about monthly with no notice |\n| Countries | Prohibited per Binance's list of 27 February 2024 are Canada, the Netherlands, the United States, Cuba, North Korea, Iran, Syria, and Crimea and non-government-controlled areas of Ukraine, plus other places Binance designates. Binance.US is a separate exchange |\n| Fees | 0.1 per cent standard spot fee for regular users per the fee FAQ. The maker and taker table and futures fees load by script and weren't read |\n| FIX and WebSocket | FIX 4.4 over TLS (spot only) with order entry, drop copy and market data sessions and SBE ports, Ed25519 keys only. WebSocket API at ws-api.binance.com and market streams; testnet twins of each |\n| Terms on automated trading | Not read. The Terms of Use at binance.com/en/terms load by script and answered with navigation only. The Skills Hub README says the person is responsible for all trading decisions and that Binance may change or discontinue the feature |\n| Skills and CLI | binance-skills-hub, 21 skills under MIT for OpenClaw, Claude Code and similar, installed with npx skills add; the binance skill drives binance-cli (Rust, v2.2.0 on 20 October 2026) with profiles for prod, testnet and demo |\n| SDKs | Official connectors for Python, JavaScript, TypeScript, Java, Go, Rust, PHP, Ruby and .NET on GitHub, most pushed in October 2026; a Postman collection; a Swagger spec last pushed in October 2024 |\n| Status | No status page found on binance.com or in the API docs |\n| Legal entity | Not named on a page we could read. The about page lists three Abu Dhabi Global Market entities (Nest Exchange Limited, Nest Clearing and Custody Limited, Nest Trading Limited) regulated by the FSRA; Wikipedia gives Binance Holdings Ltd. |\n| Capabilities | exchange.spot-trading, exchange.market-data, exchange.derivatives, exchange.balances, exchange.transfers, exchange.staking, market.crypto |\n| Tags | hosted, official, closed-source, api-key, oauth, mcp, remote-mcp, llms-txt, sandbox, python, typescript, java, go, cli, usage-priced, no-card |\n| JSON | https://www.anchorterminal.com/api/v1/tools/binance.json |\n\n## Score breakdown (methodology v0.7, October 2026 research run)\n\nAssessed 2026-11-03 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. \"This run\" is each category's share of the 100 points.\n\n| Category | Weight | This run | Score (0–100) | Points |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 20 | 45 | 9.0 |\n| Performance | 10% | pending | pending | n/a |\n| Schema \u0026 documentation | 13% | 16.2 | 86 | 14.0 |\n| Agent ergonomics | 13% | 16.2 | 76 | 12.3 |\n| Security \u0026 auth | 14% | 17.5 | 72 | 12.6 |\n| Payments \u0026 pricing | 10% | 12.5 | 35 | 4.4 |\n| Task success | 10% | pending | pending | n/a |\n| Maintenance \u0026 community | 7% | 8.8 | 81 | 7.1 |\n| Transparency \u0026 trust (editorial 31, provenance 54) | 7% | 8.8 | 43 | 3.8 |\n| Negative events | up to −15 | up to −15 | none recorded | 0 |\n| **Total** | | | | **63.2 → B** |\n\n### Why each score\n\n- Reliability 45 (checked 2026-11-03): 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- Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes.\n- Schema \u0026 documentation 86 (checked 2026-11-03): 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- Agent ergonomics 76 (checked 2026-11-03): 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- Security \u0026 auth 72 (checked 2026-11-03): 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- Payments \u0026 pricing 35 (checked 2026-11-03): 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- Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored.\n- Maintenance \u0026 community 81 (checked 2026-11-03): Read as a closed service. The spot changelog's newest entry is 30 October 2026, the MCP docs are dated 30 October and binance-cli v2.2.0 shipped on 20 October (30). Changelog entries on 2 September, 18 September, 27 October and 30 October (20). A public changelog, connectors pushed in October and a Skills Hub merging pull requests weekly; issue replies not read (10 of 15). Official connectors in nine languages current as of October 2026; the MCP server is not in the official registry (15). Connector CI not read; the CLI publishes release installers (6 of 10). 30 + 20 + 10 + 15 + 6 = 81.\n- Transparency \u0026 trust 43 (checked 2026-11-03): 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\nFix list, everything this grade says the listing lacks, the biggest gain first (22 items). What it covers is at https://www.anchorterminal.com/fixes/binance.md (JSON https://www.anchorterminal.com/fixes/binance.json). The whole list for a coding agent comes from `POST https://www.anchorterminal.com/api/v1/fix-list` with `{\"listing\": \"binance\", \"plan\": \"read\"}`, free while the beta runs\n\n### What we couldn't check\n\n- unchecked: the Terms of Use and the privacy notice, which load by script and answered with navigation only, so the contracting entity, governing law, API and bot clauses and data handling are unread. The prohibited-countries list is from a readable legal page dated 27 February 2024.\n- unchecked: the maker and taker fee table and futures fees. Only the 0.1 per cent standard spot fee in the fee FAQ was read.\n- unchecked: the MCP server's tools and schemas. tools/list needs a signed-in account and was not called; the docs give four scopes and no tool count. Its launch date is not stated; the docs pages carry a last-modified date of 30 October 2026, and press coverage of a Binance Agent OS was not used.\n- No status page was found on binance.com or in the docs; Binance.US has one and is a separate exchange. Scored absent.\n- firstReleased is 14 January 2018, the oldest entry in the spot API changelog; the exchange launched in July 2017 per the about page.\n- Kind http-api, not mcp. The MCP server is one route to the same markets, is weeks old and is documented without a tool list, while the REST, WebSocket and FIX APIs carry the docs, connectors and testnet.\n- Legal entity left empty. No readable page names the contracting party; the about page lists ADGM subsidiaries and Wikipedia gives Binance Holdings Ltd.\n- api.binance.com and testnet.binance.vision disallow all crawlers in robots.txt, so exchangeInfo was not called; the limit numbers come from the docs' sample response.\n\n### Sources\n\n- robots.txt (www.binance.com): \u003chttps://www.binance.com/robots.txt\u003e (seen 2026-11-03)\n- general API information (limits model, key types, 429 and 418): \u003chttps://developers.binance.com/docs/binance-spot-api-docs/rest-api/general-api-information\u003e (seen 2026-11-03)\n- limits page: \u003chttps://developers.binance.com/docs/binance-spot-api-docs/rest-api/limits\u003e (seen 2026-11-03)\n- exchangeInfo rateLimits sample: \u003chttps://developers.binance.com/docs/binance-spot-api-docs/rest-api/general-endpoints\u003e (seen 2026-11-03)\n- FIX API: \u003chttps://developers.binance.com/docs/binance-spot-api-docs/fix-api\u003e (seen 2026-11-03)\n- spot API changelog (newest 30 October 2026, oldest 14 January 2018): \u003chttps://developers.binance.com/docs/binance-spot-api-docs/CHANGELOG\u003e (seen 2026-11-03)\n- Agent Native overview: \u003chttps://developers.binance.com/en/docs/agent-native/overview\u003e (seen 2026-11-03)\n- MCP server introduction: \u003chttps://developers.binance.com/en/docs/agent-native/mcp-server\u003e (seen 2026-11-03)\n- Binance MCP Server (scopes, sub-account, setup): \u003chttps://developers.binance.com/en/docs/agent-native/mcp-server/agentic\u003e (seen 2026-11-03)\n- MCP protected-resource metadata: \u003chttps://agent.binance.com/.well-known/oauth-protected-resource\u003e (seen 2026-11-03)\n- spot testnet: \u003chttps://testnet.binance.vision/\u003e (seen 2026-11-03)\n- API key creation FAQ: \u003chttps://www.binance.com/en/support/faq/detail/360002502072\u003e (seen 2026-11-03)\n- fee structure FAQ: \u003chttps://www.binance.com/en/support/faq/detail/115000429332\u003e (seen 2026-11-03)\n- fee page (table loads by script): \u003chttps://www.binance.com/en/fee/trading\u003e (seen 2026-11-03)\n- list of prohibited countries: \u003chttps://www.binance.com/en/legal/list-of-prohibited-countries\u003e (seen 2026-11-03)\n- Terms of Use (navigation only): \u003chttps://www.binance.com/en/terms\u003e (seen 2026-11-03)\n- privacy page (navigation only): \u003chttps://www.binance.com/en/privacy\u003e (seen 2026-11-03)\n- about page: \u003chttps://www.binance.com/en/about\u003e (seen 2026-11-03)\n- security.txt: \u003chttps://www.binance.com/.well-known/security.txt\u003e (seen 2026-11-03)\n- GitHub organisation repositories: \u003chttps://api.github.com/orgs/binance/repos?per_page=100\u0026sort=updated\u003e (seen 2026-11-03)\n- binance-skills-hub, shallow clone: \u003chttps://github.com/binance/binance-skills-hub\u003e (seen 2026-11-03)\n- binance-cli, shallow clone (tags): \u003chttps://github.com/binance/binance-cli\u003e (seen 2026-11-03)\n- official MCP registry search: \u003chttps://registry.modelcontextprotocol.io/v0/servers?search=binance\u003e (seen 2026-11-03)\n- RDAP for binance.com: \u003chttps://rdap.verisign.com/com/v1/domain/binance.com\u003e (seen 2026-11-03)\n\n## Score history\n\nEvery move of a score since the listing was graded, newest first, with its cause. A score can't move without an entry here. JSON: https://www.anchorterminal.com/api/v1/tools/binance/history.json\n\n- 2026-11-03: graded 63.2 B (methodology 0.7)\n\n## Who's behind it (provenance 54/100, checked 2026-11-03)\n\n| Check | Finding | Points |\n| --- | --- | --- |\n| Legal entity named | not found | 0/20 |\n| Domain age | binance.com, registered 2017-04-01 (9 years) | 11/15 |\n| Endpoint on the vendor's domain | agent.binance.com | 15/15 |\n| Terms of service | published, but our reader couldn't read it | 7/10 |\n| Privacy policy | published, but our reader couldn't read it | 7/10 |\n| Status page | not found | 0/10 |\n| Changelog | published | 10/10 |\n| security.txt | could not be fetched | 0/10 |\n| People named | 3 named with their role, none with a public profile | 7/10 |\n| Support route | help pages, a community | 5/5 |\n\nThe 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.\n\nRDAP gives binance.com a registration date of 1 April 2017.\n\nhttps://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.\n\nNo 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.\n\nThe spot API changelog is dated, newest 30 October 2026.\n\n### Terms and privacy, as read\n\nA reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice.\n\n**Terms of service** (https://www.binance.com/en/terms), read 2026-11-03. Our reader couldn't read it (the page has 0 words of text without a browser, so the document is drawn by script or sits elsewhere).\n\n\n**Privacy policy** (https://www.binance.com/en-GB/about-legal/privacy-portal), read 2026-11-03. Our reader couldn't read it (the page has 0 words of text without a browser, so the document is drawn by script or sits elsewhere).\n\n\n## Humans behind the project (researched 2026-11-03 from public pages, not part of the grade)\n\n### Key people\n\n- Changpeng Zhao, Co-founder and former CEO, Binance\n- Yi He, Co-founder and co-CEO, Binance\n- Richard Teng, Co-CEO, Binance\n- Note: The about page at binance.com/en/about names Changpeng Zhao as co-founder and former CEO and Yi He as co-CEO and co-founder; it names no other officer. Richard Teng's role rests on Wikipedia's Binance article. The Terms of Use load by script, so no page we read names the contracting company; the about page lists three Abu Dhabi Global Market subsidiaries. Investors were looked for on the about and press pages and in two searches. MGX of Abu Dhabi took a minority stake for $2 billion in March 2025, reported by The Block from a Binance release we could not read first-hand. No earlier outside investor was found; Binance describes the MGX deal as its first institutional investment.\n- Binance: X https://x.com/binance GitHub https://github.com/binance\n\n### Ownership and investors\n\n- Backed by: MGX\n\n### Getting support\n\n- Help: https://www.binance.com/en/support\n- Help: https://developers.binance.com/\n- Community (Spot API docs issues): https://github.com/binance/binance-spot-api-docs/issues\n- Community (Skills Hub repository): https://github.com/binance/binance-skills-hub\n- Sources: https://www.binance.com/en/about, https://en.wikipedia.org/wiki/Binance, https://www.theblock.co/post/345932/binance-secures-2-billion-investment-from-abu-dhabis-mgx-in-landmark-crypto-deal, https://developers.binance.com/, https://github.com/binance\n\n## Live (updated 2026-11-04 19:34 UTC)\n\n- Right now: up, HTTP 404, 594 ms, checked 2026-11-04 19:34 UTC (get on `https://agent.binance.com/mcp/agentic`)\n- Uptime 24h 100.0% (43 probes) · 30 days 100.0% (43 probes) · p50 475 ms · p95 582 ms\n- security.txt: valid\n- Always current: https://www.anchorterminal.com/api/v1/live/binance.json\n\n## Probe metrics\n\nNot measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score.\n\n## Prices\n\n| Item | Price | Unit | Note |\n| --- | --- | --- | --- |\n| Spot trade, regular user | 0.1% | percentage fee | standard fee per the fee FAQ; maker and taker table not read |\n\nAcross all listings: https://www.anchorterminal.com/prices/index.md\n\n## Strengths\n\n- Rate limits published as per-endpoint weights with 6,000 a minute, 50 orders per 10 seconds and Retry-After on 429 and 418\n- Spot testnet with REST, WebSocket and FIX endpoints, virtual balances and production limits, free with a GitHub login\n- Official remote MCP server with OAuth scopes, an isolated Agentic sub-account, no withdrawal scope and confirmation before writes\n- Keys with reading, trading, futures and withdrawal permissions; unrestricted-IP HMAC keys can only read and withdrawals need an IP restriction\n- Dated changelog since 2018 with retirement dates announced months ahead, llms.txt and llms-full.txt\n\n## Weaknesses\n\n- No status page or incident history found on binance.com or in the API docs\n- 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\n- The MCP server's tool list and schemas are not published; the docs describe four scopes\n- The maker and taker fee table loads by script; only the 0.1 per cent standard rate in a FAQ was read\n- binance-api-swagger was last pushed in October 2024, so the machine-readable spec lags the docs\n\n\n\n## Before you call it (notes for agents)\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## Connect\n\nFirst request:\n\n```bash\ncurl https://api.binance.com/api/v3/ticker/price?symbol=BTCUSDT\n```\n\nClaude Code:\n\n```bash\nclaude mcp add binance-mcp-server --transport http https://agent.binance.com/mcp/agentic\n```\n\nMCP client configuration:\n\n```json\n{\n \"mcpServers\": {\n \"binance-mcp-server\": {\n \"url\": \"https://agent.binance.com/mcp/agentic\"\n }\n }\n}\n```\n\nThrough letme: https://letme.dev/binance. letme answers with the pick and how to call it direct. How it works: https://www.anchorterminal.com/letme/index.md\n\n## Similar tools\n\nRanked by shared capabilities, then score. Same-category tools with no shared capability key are listed last.\n\n| Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown |\n| --- | --- | --- | --- | --- | --- | --- |\n| Gemini Exchange API | BB | 74.6 | 70 | exchange.market-data, exchange.spot-trading, exchange.derivatives, exchange.balances, exchange.transfers, exchange.staking, market.crypto | no | https://www.anchorterminal.com/tools/gemini-exchange.md |\n| Kraken API | BB | 71 | 159 | exchange.spot-trading, exchange.market-data, exchange.derivatives, exchange.balances, exchange.transfers, exchange.staking, market.crypto | no | https://www.anchorterminal.com/tools/kraken.md |\n| OKX API | B | 64.3 | 413 | exchange.spot-trading, exchange.market-data, exchange.derivatives, exchange.balances, exchange.transfers, exchange.staking, market.crypto | no | https://www.anchorterminal.com/tools/okx.md |\n| Bitfinex API | C | 58.4 | 687 | exchange.market-data, exchange.spot-trading, exchange.derivatives, exchange.balances, exchange.transfers, exchange.staking, market.crypto | no | https://www.anchorterminal.com/tools/bitfinex.md |\n| Bybit | C | 57.3 | 745 | exchange.market-data, exchange.spot-trading, exchange.derivatives, exchange.balances, exchange.transfers, exchange.staking, market.crypto | no | https://www.anchorterminal.com/tools/bybit.md |\n| Gate | C | 56.4 | 786 | exchange.market-data, exchange.spot-trading, exchange.derivatives, exchange.balances, exchange.transfers, exchange.staking, market.crypto | no | https://www.anchorterminal.com/tools/gate-io.md |\n\n## Panel reviews (0)\n\nReviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): .\n\nDesk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md\n\n## Notable\n\n- Binance runs an official remote MCP server at https://agent.binance.com/mcp/agentic (Streamable HTTP, OAuth in a desktop browser, scopes market data, account, trade and transfer). Agents trade spot, margin, convert and futures inside a dedicated Agentic sub-account that the person funds by hand, with no withdrawal scope and confirmation before orders, cancels and transfers. The docs pages are dated 30 October 2026. It is not in the official MCP registry, where nine Binance servers sit under io.github namespaces (source: \u003chttps://developers.binance.com/en/docs/agent-native/mcp-server/agentic, https://registry.modelcontextprotocol.io/v0/servers?search=binance\u003e)\n- The MCP server's protected-resource metadata names agent.binance.com as its authorisation server and lists no scopes. The tool list is not published outside tools/list, which we did not call (source: \u003chttps://agent.binance.com/.well-known/oauth-protected-resource\u003e)\n- Rate limits are per IP, published per endpoint as weights. exchangeInfo reports 6,000 request weight a minute, 50 orders per 10 seconds, 160,000 orders a day and 61,000 raw requests per 5 minutes. 429 carries Retry-After; an IP that keeps sending after 429 gets a 418 ban of 2 minutes to 3 days (source: \u003chttps://developers.binance.com/docs/binance-spot-api-docs/rest-api/general-endpoints\u003e)\n- FIX 4.4 over TLS for spot only, with order entry, drop copy and market data sessions, Ed25519 keys only, 10,000 messages per 10 seconds on order entry and a FIX_API or FIX_API_READ_ONLY key permission (source: \u003chttps://developers.binance.com/docs/binance-spot-api-docs/fix-api\u003e)\n- The spot testnet at testnet.binance.vision has REST, WebSocket and FIX endpoints, virtual balances and the production limits, and resets about once a month without notice (source: \u003chttps://testnet.binance.vision/\u003e)\n- binance-skills-hub (1,121 stars) publishes 21 agent skills, among them one that drives binance-cli (Rust, v2.2.0 on 20 October 2026) for spot, futures and convert; no local MCP server is in the organisation's repositories (source: \u003chttps://github.com/binance/binance-skills-hub\u003e)\n- The spot API changelog's newest entry is 30 October 2026, a reminder that the SBE 3:3 schema retires on 9 November; the oldest is 14 January 2018 (source: \u003chttps://developers.binance.com/docs/binance-spot-api-docs/CHANGELOG\u003e)\n- Binance lists Canada, the Netherlands, the United States, Cuba, North Korea, Iran, Syria and Crimea and non-government-controlled areas of Ukraine as prohibited, updated 27 February 2024 (source: \u003chttps://www.binance.com/en/legal/list-of-prohibited-countries\u003e)\n- No status page was found on binance.com or in the API docs; the Terms of Use and privacy notice load by script and answered our reader with navigation only\n\n- #6 of 21 in 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## Compare\n\n- [Binance API vs Bitfinex API](https://www.anchorterminal.com/compare/binance-vs-bitfinex.md): B 63.2 vs C 58.4\n- [Binance API vs Bitget](https://www.anchorterminal.com/compare/binance-vs-bitget.md): B 63.2 vs D 53.9\n- [Binance API vs Bithumb Open API](https://www.anchorterminal.com/compare/binance-vs-bithumb.md): B 63.2 vs D 50.6\n- [Binance API vs Bitstamp API](https://www.anchorterminal.com/compare/binance-vs-bitstamp.md): B 63.2 vs D 50.4\n- [Binance API vs Bybit](https://www.anchorterminal.com/compare/binance-vs-bybit.md): B 63.2 vs C 57.3\n- [Binance API vs Coinbase Advanced Trade API](https://www.anchorterminal.com/compare/binance-vs-coinbase-advanced-trade.md): B 63.2 vs C 61.7\n- [Binance API vs Coinbase MCP server (Coinbase for Agents)](https://www.anchorterminal.com/compare/binance-vs-coinbase-mcp.md): B 63.2 vs C 60\n- [Binance API vs Crypto.com Exchange API](https://www.anchorterminal.com/compare/binance-vs-crypto-com-exchange.md): B 63.2 vs D 46.8\n- [Binance API vs Deribit](https://www.anchorterminal.com/compare/binance-vs-deribit.md): B 63.2 vs C 59\n- [Binance API vs Gate](https://www.anchorterminal.com/compare/binance-vs-gate-io.md): B 63.2 vs C 56.4\n- [Binance API vs Gemini Exchange API](https://www.anchorterminal.com/compare/binance-vs-gemini-exchange.md): B 63.2 vs BB 74.6\n- [Binance API vs HTX trading API](https://www.anchorterminal.com/compare/binance-vs-htx.md): B 63.2 vs E 43.3\n- [Binance API vs Hyperliquid](https://www.anchorterminal.com/compare/binance-vs-hyperliquid.md): B 63.2 vs D 50\n- [Binance API vs Kraken API](https://www.anchorterminal.com/compare/binance-vs-kraken.md): B 63.2 vs BB 71\n- [Binance API vs KuCoin](https://www.anchorterminal.com/compare/binance-vs-kucoin.md): B 63.2 vs D 53.9\n- [Binance API vs MEXC API](https://www.anchorterminal.com/compare/binance-vs-mexc.md): B 63.2 vs C 56.3\n- [Binance API vs OKX API](https://www.anchorterminal.com/compare/binance-vs-okx.md): B 63.2 vs B 64.3\n- [Binance API vs Uniswap Trading API](https://www.anchorterminal.com/compare/binance-vs-uniswap.md): B 63.2 vs B 63.3\n- [Binance API vs Upbit Open API](https://www.anchorterminal.com/compare/binance-vs-upbit.md): B 63.2 vs C 54.7\n- [Binance API vs dYdX](https://www.anchorterminal.com/compare/binance-vs-dydx.md): B 63.2 vs B 69.5\n\n## Verify this listing\n\nFor the vendor. The badge or a plain link to this page verifies the listing, from a page on binance.com or one of its subdomains, or the README at the root of github.com/binance/binance-spot-api-docs. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{\"slug\": \"binance\", \"url\": \"…\"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify\n\nHTML badge:\n\n```html\n\u003ca href=\"https://www.anchorterminal.com/tools/binance\"\u003e\u003cimg src=\"https://www.anchorterminal.com/badges/binance.svg\" alt=\"Binance API on Anchor Terminal\" height=\"20\"\u003e\u003c/a\u003e\n```\n\nMarkdown badge, for a README:\n\n```markdown\n[![Binance API on Anchor Terminal](https://www.anchorterminal.com/badges/binance.svg)](https://www.anchorterminal.com/tools/binance)\n```\n\nPlain link:\n\n```html\n\u003ca href=\"https://www.anchorterminal.com/tools/binance\"\u003eBinance API on Anchor Terminal\u003c/a\u003e\n```\n\n## Share this listing\n\nFor the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Binance API is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score.\n\n- Dark: https://www.anchorterminal.com/assets/share/binance-dark.png\n- Light: https://www.anchorterminal.com/assets/share/binance-light.png\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": "Terminal", "url": "https://www.anchorterminal.com/tools/" }, { "name": "Crypto exchanges", "url": "https://www.anchorterminal.com/categories/crypto-exchanges" }, { "name": "Binance API", "url": "" } ], "description": "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.", "facts": [ "rank #448 of 1349", "OAuth or key auth", "0 desk reviews" ], "h1": "Binance API", "image": "https://www.anchorterminal.com/assets/og/tools-binance.png", "path": "/tools/binance", "published": "2026-10-01", "section": "tools", "title": "Binance review (2026): pricing, alternatives and grade B", "toc": null, "updated": "2026-11-04", "url": "https://www.anchorterminal.com/tools/binance" }, "tokens": { "markdown": 8400, "slim": 2180 }, "version": 1 }