{ "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 KuCoin's 53.9 (D), and leads in 4 of 7 scored categories. KuCoin leads on transparency \u0026 trust.", "b": { "slug": "kucoin", "name": "KuCoin", "vendor": "KuCoin", "vendorUrl": "https://www.kucoin.com", "kind": "http-api", "category": "crypto-exchanges", "summary": "KuCoin is a centralised crypto exchange for spot, margin and futures trading and earn products, reached through its REST and WebSocket API with a unified trading account, an official multi-language SDK and read-only agent skills. It runs no MCP server.", "url": "https://www.anchorterminal.com/tools/kucoin", "markdownUrl": "https://www.anchorterminal.com/tools/kucoin.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/kucoin.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/kucoin.json", "dns": "kucoin.grade.anchorterminal.com", "repo": "https://github.com/Kucoin/kucoin-universal-sdk", "transports": [], "packages": [], "auth": "api-key", "authNotes": "API key, secret and user-set passphrase minted under API Management after a browser sign-up and identity verification, with KC-API-KEY, KC-API-SIGN (HMAC-SHA256 over timestamp, method, path and body, Base64), KC-API-TIMESTAMP, KC-API-PASSPHRASE (the passphrase signed with the secret) and KC-API-KEY-VERSION headers. Permissions are General (read-only), Spot, Margin, Futures, Earn, Withdrawal, FlexTransfers, LeadtradeFutures and Unified; Withdrawal and FlexTransfers need an IP allow-list, and a key with trading permissions and no IP bound has trading disabled or is deleted after 30 days of inactivity. General-only keys do not expire (https://www.kucoin.com/docs-new/authentication, https://www.kucoin.com/docs-new/ and https://www.kucoin.com/support/360015102174, checked 2026-11-03).", "pricing": "usage", "pricingNotes": "The API costs nothing; trades carry KuCoin's fees. Spot fee levels are set against a base of 0.1 per cent maker and 0.1 per cent taker at LV0, with some pairs priced differently and a 20 per cent discount when fees are paid in KCS. The futures LV0 rate (0.02 per cent maker and 0.06 per cent taker per a KuCoin blog post) sits in an image on the support page and was not read first-hand. The fee page itself loads its table by script (https://www.kucoin.com/support/360015188494 and https://www.kucoin.com/en-eu/support/360015207133, checked 2026-11-03).", "priceSummary": "0.1% fee", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the API docs, the skills hub or the fee pages (checked 2026-11-03).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 55, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://www.kucoin.com/docs-new/", "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", "no-status-page", "agent-skills", "python", "typescript", "go", "java", "php" ], "lastRelease": "2026-11-02", "graded": true, "anchor": { "graded": true, "score": 53.9, "grade": "D", "agentReady": false, "rank": 891, "ranked": true, "rankOf": 1349, "categoryRank": 16, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 62, "maintenance": 73, "payments": 35, "reliability": 45, "schema": 60, "security": 55, "transparency": 54 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-03" }, "negative": 0, "verdict": "KuCoin publishes pooled rate limits with remaining and reset headers, scoped keys where withdrawals and transfers need an IP allow-list, an official SDK in five languages and read-only agent skills. It runs no MCP server, has no sandbox, status page or OpenAPI file, and its terms name no legal entity.", "bestFor": "An agent trading spot, margin and futures in a person's KuCoin account outside the restricted list, with no sandbox and no MCP server, so through the SDK or raw REST.", "strengths": [ "Rate limits published per VIP level with per-endpoint weights and gw-ratelimit-limit, gw-ratelimit-remaining and gw-ratelimit-reset headers, 429000 on breach", "API key permissions split into General, Spot, Margin, Futures, Earn, Withdrawal, FlexTransfers and Unified, with Withdrawal and FlexTransfers requiring an IP allow-list", "Official kucoin-universal-sdk for Go, Python, Node.js, PHP and Java, MIT, pushed September 2026", "Unified Trading Account API V2 with a dated changelog and unified six-digit error codes", "Seven read-only agent skills in a KuCoin-published repository, installable with the skills CLI" ], "weaknesses": [ "No official MCP server; the registry's `kucoin` entry is a third party's keyless market-data package", "No sandbox or testnet; the legacy sandbox is offline and the docs point to mocking", "No status page, incident history or SLA found", "No OpenAPI file or llms.txt; the SDK page links a Postman workspace instead", "Terms name no company and fix the Turks and Caicos Islands as the deemed place of every transaction; the privacy policy names only KuCoin" ], "agentNotes": [ "Mint a key with General only for research; add Spot or Futures only with an IP allow-list, since unbound trading keys are disabled after 30 days of inactivity", "Send a UUID clientOid on every order and keep it for the retry, and read the order back by clientOid before placing again", "Budget requests by weight against gw-ratelimit-remaining and sleep for gw-ratelimit-reset milliseconds on 429000; sub-accounts share the pool", "There is no sandbox, so rehearse with the smallest order size on a dedicated sub-account", "Use the UTA V2 endpoints and hosts; the Classic API loses endpoints without notice, as the margin credit endpoints did on 21 October 2026" ], "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": 62, "maintenance": 73, "payments": 35, "reliability": 45, "schema": 60, "security": 55, "transparency": 52 }, "provenanceScore": 55, "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.kucoin.com/api/v1/market/orderbook/level1?symbol=BTC-USDT" }, "letme": { "capability": "https://letme.dev/exchange.market-data", "tool": "https://letme.dev/kucoin" }, "area": "payments", "unitPrices": [ { "item": "Spot trade, LV0 maker or taker", "unit": "pct", "usd": 0.1, "note": "base rate; some pairs differ, 20 per cent off in KCS" } ], "provenance": { "legalEntity": "", "domain": "kucoin.com", "domainRegistered": "2013-11-13", "endpointOnVendorDomain": true, "terms": "https://www.kucoin.com/support/47185419968079", "privacy": "https://www.kucoin.com/legal/privacy-policy", "statusPage": "", "changelog": "https://www.kucoin.com/docs-new/change-log", "securityTxt": "none", "checked": "2026-11-03", "notes": [ "The terms (last updated 29 October 2026) name no company; they deem all activity to occur in the Turks and Caicos Islands under its law with SIAC arbitration. /legal/terms-of-use is a shell page that links the support article recorded here. The privacy policy (dated 10/05/2026 in an ambiguous format) names KuCoin as controller with no company name.", "www.kucoin.com/robots.txt disallows assets, order and account paths only; docs-new and support pages are allowed.", "RDAP gives kucoin.com a registration date of 13 November 2013 (Amazon Registrar).", "https://www.kucoin.com/.well-known/security.txt answers 404. No status page found; status.kucoin.com does not resolve and the docs link none.", "The docs changelog is dated by day; its newest entry is dated 6 November 2026, three days ahead of the check, and the newest past entry 2 November 2026." ], "score": 55 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/kucoin.json", "live": { "slug": "kucoin", "securityTxt": { "url": "https://kucoin.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-04T15:54:04.738329571Z" }, "updatedAt": "2026-11-04T15:54:04.738329571Z" } }, "edges": [ { "by": 26, "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": "No OpenAPI or other machine-readable contract was found; the docs link a Postman workspace and the universal SDK is generated from an internal spec (8 of 25). No llms.txt; the skills hub ships Markdown SKILL.md files with endpoint tables for seven product areas, read-only (6 of 10). One docs page per endpoint with a description, permission and weight, but no when-to-use guidance (12 of 20). Typed parameter tables with enums for type and side and required flags (11 of 15). Request and response examples per endpoint and a unified six-digit error code scheme introduced with V2 (10 of 15). Dated changelog with V1 to V2 versioning (13 of 15). 60." }, "scores": { "a": 86, "b": 60 } }, { "by": 17, "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 key with a user-set passphrase, HMAC-SHA256 signing, nine permission groups, IP allow-lists required for Withdrawal and FlexTransfers, trading keys without an IP disabled after 30 days of inactivity, revocation on the management page; no OAuth and no expiry on General keys (24 of 30). A General-only key is a true read-only mode and withdrawals are a separate permission; no confirmation step for writes beyond the key scope (12 of 20). Tools return the exchange's own data (10). The API key info endpoint shows permissions and IP lists; no per-call audit log was found (5 of 15). No security.txt, no disclosure policy or bounty on a page we could read, a whistleblower notice on the legal page (4 of 20). 55." }, "scores": { "a": 72, "b": 55 } }, { "by": 14, "category": "ergonomics", "leads": "binance", "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 alone, since there is no MCP server. Responses take limit and cursor parameters on list endpoints and the order book depth is a parameter (14 of 25). Pagination and symbol filters on orders, fills and ledgers (15 of 20). Codes and messages per response, with the V2 scheme claimed to be clearer; the rate-limit page's own examples contradict its table, which costs an agent a turn (12 of 20). clientOid on orders makes retries safe; no MCP annotations to read (10 of 20). Three required fields on a spot order, official SDKs in five languages (11 of 15). 62." }, "scores": { "a": 76, "b": 62 } }, { "by": 11, "category": "transparency", "leads": "kucoin", "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 terms that are clear on use, liability and law but name no company (12 of 30). The privacy policy gives retention periods by purpose and provider (2 years after closure, 14 months for Firebase, 3 years for Jumio, 5 years for Sumsub) and names 41 services, with no data centre locations (22 of 30). Endpoints are removed and fields deprecated in dated changelog entries with no notice period or policy (8 of 20). Third parties named by service, locations not stated beyond transfers around the globe (10 of 20). 52." }, "scores": { "a": 43, "b": 54 } }, { "by": 8, "category": "maintenance", "leads": "binance", "name": "Maintenance \u0026 community", "reasons": { "a": "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.", "b": "Read as a closed hosted service. The changelog's newest past entry is 2 November 2026 and the universal SDK was pushed 15 September (30). Nine dated changelog entries since 5 August 2026 (20). A Telegram API group (t.me/KuCoin_API) and api@kucoin.com for limit requests, no public issue tracker for the API; the SDK repository's issues were not checked (10 of 25). Official SDKs current in five languages, no MCP registry presence (13 of 15). No package health signal checked (0 of 10). 73." }, "scores": { "a": 81, "b": 73 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Binance", "b": "KuCoin", "name": "Vendor" }, { "a": "https://agent.binance.com/mcp/agentic", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "Streamable HTTP", "b": "", "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": "no", "b": "yes", "name": "Read-only variant documented" }, { "a": "yes", "b": "no", "name": "llms.txt" }, { "a": "2026-10-30", "b": "2026-11-02", "name": "Last release" }, { "a": "couldn't be read", "b": "no date given", "name": "Terms last updated" }, { "a": "couldn't be read", "b": "no date given", "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": "55 stars", "name": "Popularity" } ], "faq": [ { "answer": "Binance API scores 63.2 (B) on agent readiness against KuCoin's 53.9 (D), and leads in 4 of 7 scored categories. KuCoin leads on transparency \u0026 trust.", "question": "Which is better for AI agents, Binance API or KuCoin?" }, { "answer": "Binance API takes an API key or an OAuth sign-in. KuCoin needs an API key.", "question": "Do Binance API and KuCoin need an API key?" }, { "answer": "Binance API has a hosted endpoint at https://agent.binance.com/mcp/agentic. No hosted endpoint is listed for KuCoin.", "question": "Can an agent call Binance API and KuCoin without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 86 against 60", "Agent ergonomics, 76 against 62", "Security \u0026 auth, 72 against 55", "Maintenance \u0026 community, 81 against 73" ], "also": [ "A hosted endpoint, with nothing to install", "Free to start without a card" ], "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": [ "Transparency \u0026 trust, 54 against 43" ], "also": null, "goodFor": "An agent trading spot, margin and futures in a person's KuCoin account outside the restricted list, with no sandbox and no MCP server, so through the SDK or raw REST.", "slug": "kucoin", "watchFor": "No official MCP server; the registry's `kucoin` entry is a third party's keyless market-data package" } ], "history": null, "job": { "capability": "exchange.spot-trading", "name": "Exchange spot trading" }, "others": [ { "json": "https://www.anchorterminal.com/compare/bitfinex-vs-kucoin.json", "title": "Bitfinex API vs KuCoin", "url": "https://www.anchorterminal.com/compare/bitfinex-vs-kucoin" }, { "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/bithumb-vs-kucoin.json", "title": "Bithumb Open API vs KuCoin", "url": "https://www.anchorterminal.com/compare/bithumb-vs-kucoin" }, { "json": "https://www.anchorterminal.com/compare/bitstamp-vs-kucoin.json", "title": "Bitstamp API vs KuCoin", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-kucoin" }, { "json": "https://www.anchorterminal.com/compare/bybit-vs-kucoin.json", "title": "Bybit vs KuCoin", "url": "https://www.anchorterminal.com/compare/bybit-vs-kucoin" }, { "json": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-kucoin.json", "title": "Crypto.com Exchange API vs KuCoin", "url": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-kucoin" }, { "json": "https://www.anchorterminal.com/compare/gate-io-vs-kucoin.json", "title": "Gate vs KuCoin", "url": "https://www.anchorterminal.com/compare/gate-io-vs-kucoin" }, { "json": "https://www.anchorterminal.com/compare/gemini-exchange-vs-kucoin.json", "title": "Gemini Exchange API vs KuCoin", "url": "https://www.anchorterminal.com/compare/gemini-exchange-vs-kucoin" }, { "json": "https://www.anchorterminal.com/compare/htx-vs-kucoin.json", "title": "HTX trading API vs KuCoin", "url": "https://www.anchorterminal.com/compare/htx-vs-kucoin" }, { "json": "https://www.anchorterminal.com/compare/kucoin-vs-mexc.json", "title": "KuCoin vs MEXC API", "url": "https://www.anchorterminal.com/compare/kucoin-vs-mexc" }, { "json": "https://www.anchorterminal.com/compare/kucoin-vs-okx.json", "title": "KuCoin vs OKX API", "url": "https://www.anchorterminal.com/compare/kucoin-vs-okx" }, { "json": "https://www.anchorterminal.com/compare/kucoin-vs-uniswap.json", "title": "KuCoin vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/kucoin-vs-uniswap" }, { "json": "https://www.anchorterminal.com/compare/kucoin-vs-upbit.json", "title": "KuCoin vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/kucoin-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-bitget.json", "title": "Binance API vs Bitget", "url": "https://www.anchorterminal.com/compare/binance-vs-bitget" }, { "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-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/coinbase-advanced-trade-vs-kucoin.json", "title": "Coinbase Advanced Trade API vs KuCoin", "url": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-kucoin" }, { "json": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-kucoin.json", "title": "Coinbase MCP server (Coinbase for Agents) vs KuCoin", "url": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-kucoin" }, { "json": "https://www.anchorterminal.com/compare/kraken-vs-kucoin.json", "title": "Kraken API vs KuCoin", "url": "https://www.anchorterminal.com/compare/kraken-vs-kucoin" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-dydx.json", "title": "Binance API vs dYdX", "url": "https://www.anchorterminal.com/compare/binance-vs-dydx" }, { "json": "https://www.anchorterminal.com/compare/deribit-vs-kucoin.json", "title": "Deribit vs KuCoin", "url": "https://www.anchorterminal.com/compare/deribit-vs-kucoin" }, { "json": "https://www.anchorterminal.com/compare/dydx-vs-kucoin.json", "title": "dYdX vs KuCoin", "url": "https://www.anchorterminal.com/compare/dydx-vs-kucoin" }, { "json": "https://www.anchorterminal.com/compare/hyperliquid-vs-kucoin.json", "title": "Hyperliquid vs KuCoin", "url": "https://www.anchorterminal.com/compare/hyperliquid-vs-kucoin" } ], "panel": null, "scores": [ { "binance": 45, "by": 0, "edge": "", "key": "reliability", "kucoin": 45, "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "binance": 86, "by": 26, "edge": "binance", "key": "schema", "kucoin": 60, "name": "Schema \u0026 documentation", "weight": 13 }, { "binance": 76, "by": 14, "edge": "binance", "key": "ergonomics", "kucoin": 62, "name": "Agent ergonomics", "weight": 13 }, { "binance": 72, "by": 17, "edge": "binance", "key": "security", "kucoin": 55, "name": "Security \u0026 auth", "weight": 14 }, { "binance": 35, "by": 0, "edge": "", "key": "payments", "kucoin": 35, "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "binance": 81, "by": 8, "edge": "binance", "key": "maintenance", "kucoin": 73, "name": "Maintenance \u0026 community", "weight": 7 }, { "binance": 43, "by": 11, "edge": "kucoin", "key": "transparency", "kucoin": 54, "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Binance API scores 63.2 (B) on agent readiness against KuCoin's 53.9 (D), and leads in 4 of 7 scored categories. KuCoin leads on 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.", "kucoin": "KuCoin publishes pooled rate limits with remaining and reset headers, scoped keys where withdrawals and transfers need an IP allow-list, an official SDK in five languages and read-only agent skills. It runs no MCP server, has no sandbox, status page or OpenAPI file, and its terms name no legal entity." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/binance-vs-kucoin", "json": "https://www.anchorterminal.com/compare/binance-vs-kucoin.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/binance-vs-kucoin.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/binance-vs-kucoin.min.md" }, "markdown": "Binance API scores 63.2 (B) on agent readiness against KuCoin's 53.9 (D), and leads in 4 of 7 scored categories. KuCoin leads on 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- KuCoin: grade D, 53.9/100, rank #891 of 1349. Markdown https://www.anchorterminal.com/tools/kucoin.md · JSON https://www.anchorterminal.com/api/v1/tools/kucoin.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- Schema \u0026 documentation, 86 against 60\n- Agent ergonomics, 76 against 62\n- Security \u0026 auth, 72 against 55\n- Maintenance \u0026 community, 81 against 73\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n- Free to start without a card\n\nWatch for: No status page or incident history found on binance.com or in the API docs\n\n### KuCoin (D)\n\nGood for: An agent trading spot, margin and futures in a person's KuCoin account outside the restricted list, with no sandbox and no MCP server, so through the SDK or raw REST.\n\nAhead on:\n- Transparency \u0026 trust, 54 against 43\n\nWatch for: No official MCP server; the registry's `kucoin` entry is a third party's keyless market-data package\n\n\n## Why the edge\n\n### Schema \u0026 documentation: Binance API +26\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- KuCoin (60): No OpenAPI or other machine-readable contract was found; the docs link a Postman workspace and the universal SDK is generated from an internal spec (8 of 25). No llms.txt; the skills hub ships Markdown SKILL.md files with endpoint tables for seven product areas, read-only (6 of 10). One docs page per endpoint with a description, permission and weight, but no when-to-use guidance (12 of 20). Typed parameter tables with enums for type and side and required flags (11 of 15). Request and response examples per endpoint and a unified six-digit error code scheme introduced with V2 (10 of 15). Dated changelog with V1 to V2 versioning (13 of 15). 60.\n\n### Security \u0026 auth: Binance API +17\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- KuCoin (55): API key with a user-set passphrase, HMAC-SHA256 signing, nine permission groups, IP allow-lists required for Withdrawal and FlexTransfers, trading keys without an IP disabled after 30 days of inactivity, revocation on the management page; no OAuth and no expiry on General keys (24 of 30). A General-only key is a true read-only mode and withdrawals are a separate permission; no confirmation step for writes beyond the key scope (12 of 20). Tools return the exchange's own data (10). The API key info endpoint shows permissions and IP lists; no per-call audit log was found (5 of 15). No security.txt, no disclosure policy or bounty on a page we could read, a whistleblower notice on the legal page (4 of 20). 55.\n\n### Agent ergonomics: Binance API +14\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- KuCoin (62): Read for the API alone, since there is no MCP server. Responses take limit and cursor parameters on list endpoints and the order book depth is a parameter (14 of 25). Pagination and symbol filters on orders, fills and ledgers (15 of 20). Codes and messages per response, with the V2 scheme claimed to be clearer; the rate-limit page's own examples contradict its table, which costs an agent a turn (12 of 20). clientOid on orders makes retries safe; no MCP annotations to read (10 of 20). Three required fields on a spot order, official SDKs in five languages (11 of 15). 62.\n\n### Transparency \u0026 trust: KuCoin +11\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- KuCoin (54): The editorial half. A closed hosted service with terms that are clear on use, liability and law but name no company (12 of 30). The privacy policy gives retention periods by purpose and provider (2 years after closure, 14 months for Firebase, 3 years for Jumio, 5 years for Sumsub) and names 41 services, with no data centre locations (22 of 30). Endpoints are removed and fields deprecated in dated changelog entries with no notice period or policy (8 of 20). Third parties named by service, locations not stated beyond transfers around the globe (10 of 20). 52.\n\n### Maintenance \u0026 community: Binance API +8\n\n- Binance API (81): 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- KuCoin (73): Read as a closed hosted service. The changelog's newest past entry is 2 November 2026 and the universal SDK was pushed 15 September (30). Nine dated changelog entries since 5 August 2026 (20). A Telegram API group (t.me/KuCoin_API) and api@kucoin.com for limit requests, no public issue tracker for the API; the SDK repository's issues were not checked (10 of 25). Official SDKs current in five languages, no MCP registry presence (13 of 15). No package health signal checked (0 of 10). 73.\n\n## Score by category\n\n| Category | Weight | Binance API | KuCoin | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 45 | 45 | even |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 86 | 60 | Binance API +26 |\n| Agent ergonomics | 13% (16.2 this run) | 76 | 62 | Binance API +14 |\n| Security \u0026 auth | 14% (17.5 this run) | 72 | 55 | Binance API +17 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 35 | 35 | even |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 81 | 73 | Binance API +8 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 43 | 54 | KuCoin +11 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **63.2 · B** | **53.9 · D** | |\n\n## Facts side by side\n\n| Fact | Binance API | KuCoin |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Binance | KuCoin |\n| Hosted endpoint | `https://agent.binance.com/mcp/agentic` | no (local only) |\n| Transports | Streamable HTTP | |\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| Read-only variant documented | no | yes |\n| llms.txt | yes | no |\n| Last release | 2026-10-30 | 2026-11-02 |\n| Terms last updated | couldn't be read | no date given |\n| Privacy policy last updated | couldn't be read | no date given |\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 | 55 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**KuCoin.** KuCoin publishes pooled rate limits with remaining and reset headers, scoped keys where withdrawals and transfers need an IP allow-list, an official SDK in five languages and read-only agent skills. It runs no MCP server, has no sandbox, status page or OpenAPI file, and its terms name no legal entity.\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### KuCoin\n\n1. Mint a key with General only for research; add Spot or Futures only with an IP allow-list, since unbound trading keys are disabled after 30 days of inactivity\n2. Send a UUID clientOid on every order and keep it for the retry, and read the order back by clientOid before placing again\n3. Budget requests by weight against gw-ratelimit-remaining and sleep for gw-ratelimit-reset milliseconds on 429000; sub-accounts share the pool\n4. There is no sandbox, so rehearse with the smallest order size on a dedicated sub-account\n5. Use the UTA V2 endpoints and hosts; the Classic API loses endpoints without notice, as the margin credit endpoints did on 21 October 2026\n\n## Questions\n\n### Which is better for AI agents, Binance API or KuCoin?\n\nBinance API scores 63.2 (B) on agent readiness against KuCoin's 53.9 (D), and leads in 4 of 7 scored categories. KuCoin leads on transparency \u0026 trust.\n\n### Do Binance API and KuCoin need an API key?\n\nBinance API takes an API key or an OAuth sign-in. KuCoin needs an API key.\n\n### Can an agent call Binance API and KuCoin without installing anything?\n\nBinance API has a hosted endpoint at https://agent.binance.com/mcp/agentic. No hosted endpoint is listed for KuCoin.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/binance-vs-kucoin.json, and with the fewest tokens: https://www.anchorterminal.com/compare/binance-vs-kucoin.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"binance\", \"b\": \"kucoin\"}`. From a terminal: `anchor compare binance kucoin`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/binance.json and https://www.anchorterminal.com/api/v1/tools/kucoin.json\n\n## Other comparisons with Binance API or KuCoin\n\n- [Bitfinex API vs KuCoin](https://www.anchorterminal.com/compare/bitfinex-vs-kucoin.md)\n- [Bitget vs KuCoin](https://www.anchorterminal.com/compare/bitget-vs-kucoin.md)\n- [Bithumb Open API vs KuCoin](https://www.anchorterminal.com/compare/bithumb-vs-kucoin.md)\n- [Bitstamp API vs KuCoin](https://www.anchorterminal.com/compare/bitstamp-vs-kucoin.md)\n- [Bybit vs KuCoin](https://www.anchorterminal.com/compare/bybit-vs-kucoin.md)\n- [Crypto.com Exchange API vs KuCoin](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-kucoin.md)\n- [Gate vs KuCoin](https://www.anchorterminal.com/compare/gate-io-vs-kucoin.md)\n- [Gemini Exchange API vs KuCoin](https://www.anchorterminal.com/compare/gemini-exchange-vs-kucoin.md)\n- [HTX trading API vs KuCoin](https://www.anchorterminal.com/compare/htx-vs-kucoin.md)\n- [KuCoin vs MEXC API](https://www.anchorterminal.com/compare/kucoin-vs-mexc.md)\n- [KuCoin vs OKX API](https://www.anchorterminal.com/compare/kucoin-vs-okx.md)\n- [KuCoin vs Uniswap Trading API](https://www.anchorterminal.com/compare/kucoin-vs-uniswap.md)\n- [KuCoin vs Upbit Open API](https://www.anchorterminal.com/compare/kucoin-vs-upbit.md)\n- [Binance API vs Bitfinex API](https://www.anchorterminal.com/compare/binance-vs-bitfinex.md)\n- [Binance API vs Bitget](https://www.anchorterminal.com/compare/binance-vs-bitget.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 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- [Coinbase Advanced Trade API vs KuCoin](https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-kucoin.md)\n- [Coinbase MCP server (Coinbase for Agents) vs KuCoin](https://www.anchorterminal.com/compare/coinbase-mcp-vs-kucoin.md)\n- [Kraken API vs KuCoin](https://www.anchorterminal.com/compare/kraken-vs-kucoin.md)\n- [Binance API vs dYdX](https://www.anchorterminal.com/compare/binance-vs-dydx.md)\n- [Deribit vs KuCoin](https://www.anchorterminal.com/compare/deribit-vs-kucoin.md)\n- [dYdX vs KuCoin](https://www.anchorterminal.com/compare/dydx-vs-kucoin.md)\n- [Hyperliquid vs KuCoin](https://www.anchorterminal.com/compare/hyperliquid-vs-kucoin.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 KuCoin", "url": "" } ], "description": "Binance scores 63.2 (B) to KuCoin's 53.9 (D) for exchange spot trading. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Binance API B 63.2", "KuCoin D 53.9", "scores" ], "h1": "Binance API vs KuCoin", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/binance-vs-kucoin", "published": "2026-10-01", "section": "tools", "title": "Binance vs KuCoin for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-03", "url": "https://www.anchorterminal.com/compare/binance-vs-kucoin" }, "tokens": { "markdown": 4400, "slim": 2330 }, "version": 1 }