{ "data": { "a": { "slug": "crypto-com-exchange", "name": "Crypto.com Exchange API", "vendor": "Foris DAX Limited (Crypto.com)", "vendorUrl": "https://crypto.com/exchange", "kind": "http-api", "category": "crypto-exchanges", "summary": "Crypto.com Exchange's trading API for spot, perpetuals, margin, staking and trading bots, through REST, WebSocket and FIX with HMAC-signed API keys. Crypto.com's cdcx-cli adds an MCP server, agent skills and local paper trading.", "url": "https://www.anchorterminal.com/tools/crypto-com-exchange", "markdownUrl": "https://www.anchorterminal.com/tools/crypto-com-exchange.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/crypto-com-exchange.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/crypto-com-exchange.json", "dns": "crypto-com-exchange.grade.anchorterminal.com", "repo": "https://github.com/crypto-com/cdcx-cli", "license": "Proprietary hosted API under the Exchange terms and conditions, which our reader couldn't load. cdcx-cli, the official CLI and MCP server, is MIT or Apache-2.0", "transports": [ "stdio" ], "packages": [ { "registry": "npm", "name": "@cryptocom/cdcx-cli" } ], "auth": "api-key", "authNotes": "API key and secret created in the Exchange under Settings \u003e API Keys after a browser signup, with HMAC-SHA256 request signing. The official agent skill says IP whitelisting is recommended for production and withdrawal addresses must be pre-approved, and the App skill uses a key with no withdrawal permission; the Exchange docs' own permission list (read, trade, withdraw) sits on exchange-docs.crypto.com, which refused our reader. cdcx reads CDCX_API_KEY and CDCX_API_SECRET or a 0600 config file and has no key flag by design (https://github.com/crypto-com/crypto-agent-trading, https://github.com/crypto-com/cdcx-cli/blob/main/SECURITY.md, checked 2026-11-03).", "pricing": "usage", "pricingNotes": "The API itself costs nothing. Spot fees by 30-day volume, Level 1 (under $10,000) 0.25% maker and 0.50% taker, down to 0.08% and 0.18% at $500,000 or more, with a 3% discount for a CRO balance and 0% maker or rebates at higher CRO levels; rates reset daily at 04:00 UTC. A 0.5% liquidation fee. Derivatives fees are not on the fees page. A UAT environment (uat-api.3ona.co) and cdcx's local paper trading need no money (https://crypto.com/exchange-pro/en-US/document/fees-limits, checked 2026-11-03).", "priceSummary": "0.25% fee", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 on the Exchange pages, in cdcx-cli or the agent skills (checked 2026-11-03). Crypto.com's GitHub has an x402 facilitator client for its Developer Platform, which is a different product.", "endpoints": [] }, "toolCount": 95, "popularity": { "githubStars": 27, "npmWeekly": 59, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://exchange-docs.crypto.com/exchange/v1/rest-ws/index.html", "capabilities": [ "exchange.market-data", "exchange.spot-trading", "exchange.derivatives", "exchange.balances", "exchange.transfers", "exchange.staking", "market.crypto" ], "tags": [ "official", "hosted", "api-key", "mcp", "cli", "agent-skills", "sandbox", "status-page", "rust", "usage-priced" ], "lastRelease": "2026-06-18", "graded": true, "anchor": { "graded": true, "score": 46.8, "grade": "D", "agentReady": false, "rank": 1078, "ranked": true, "rankOf": 1349, "categoryRank": 20, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 50, "maintenance": 29, "payments": 40, "reliability": 50, "schema": 42, "security": 54, "transparency": 55 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "low", "date": "2026-11-03" }, "negative": 0, "verdict": "Crypto.com is one of two exchanges here with an official MCP server, cdcx-cli, whose 95 generated tools are grouped by service and gated by safety tier. The API docs, OpenAPI file, terms and trading rules refused or hid from our reader, so rate limits, key permissions and the automated-trading clauses are unchecked, and cdcx has no release since June 2026.", "bestFor": "An agent trading spot or perpetuals on Crypto.com through a local MCP server with safety tiers, for a person outside the App's restricted list.", "strengths": [ "Official cdcx-cli MCP server with 95 typed tools generated from the Exchange's OpenAPI spec, enabled by service group so a session can load `market` alone", "Safety tiers in the source, where order writes need `acknowledged: true` and cancel-all, withdrawals and bot termination need `--allow-dangerous` on the server", "A UAT environment with the same API paths and a local paper-trading engine that needs no credentials", "Spot fee tiers published without login, from 0.25% maker and 0.50% taker", "Official agent skills for the Exchange and the App that require user confirmation before a production trade" ], "weaknesses": [ "exchange-docs.crypto.com and the OpenAPI host answered 403 to robots.txt, so rate limits, key permissions, errors and the changelog could not be read", "The Exchange terms, trading rules and announcements pages load empty without a browser, so clauses on bots, API use and restricted countries are unchecked", "cdcx-cli's last tag is v1.2.6 of 18 June 2026 with no commit since, five of six open items unanswered, and the npm wrapper at 1.2.3 runs a postinstall download", "Not in the official MCP registry and no official SDK beyond the CLI", "No security.txt on crypto.com, and no SLA or Exchange-API component found on the status page" ], "agentNotes": [ "Enable only the service groups the task needs with `cdcx mcp config --enable trade,account` (the default serves `market` alone), and leave `--allow-dangerous` off unless the person asks for withdrawals or cancel-all", "Rehearse on `--env uat` or `cdcx paper` first; production keys trade real funds, and the skill requires explicit user confirmation before each live order", "Put the key in CDCX_API_KEY and CDCX_API_SECRET or `~/.config/cdcx/config.toml` at 0600; there is no key flag, and the key should have no withdrawal permission and an IP allow-list", "Pass `acknowledged: true` on mutate tools and `--dry-run` while testing; read the tool's generated schema before calling, since the docs host is unreadable to agents without a browser", "Check the person's country against Crypto.com's geo-restriction article and the Exchange terms before trading; New York and about 70 countries are excluded from the App, and the Exchange list was unreadable" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "low", "grade": "D", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 46.8 } ], "editorialScores": { "ergonomics": 50, "maintenance": 29, "payments": 40, "reliability": 50, "schema": 42, "security": 54, "transparency": 32 }, "provenanceScore": 77, "checked": { "categories": { "ergonomics": "2026-11-03", "maintenance": "2026-11-03", "payments": "2026-11-03", "reliability": "2026-11-03", "schema": "2026-11-03", "security": "2026-11-03", "transparency": "2026-11-03" }, "last": "2026-11-03", "oldest": "2026-11-03", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "curl -sSfL https://raw.githubusercontent.com/crypto-com/cdcx-cli/main/install.sh | sh", "http": "curl https://api.crypto.com/exchange/v1/public/get-tickers", "config": { "mcpServers": { "cdcx": { "args": [ "-y", "@cryptocom/cdcx-cli@latest", "mcp" ], "command": "npx", "env": { "CDCX_API_KEY": "your_api_key", "CDCX_API_SECRET": "your_api_secret" } } } } }, "letme": { "capability": "https://letme.dev/exchange.market-data", "tool": "https://letme.dev/crypto-com-exchange" }, "area": "payments", "unitPrices": [ { "item": "Spot maker fee, Level 1 (under $10,000 of 30-day volume)", "unit": "pct", "usd": 0.25, "note": "0.2425% with a CRO balance" }, { "item": "Spot taker fee, Level 1", "unit": "pct", "usd": 0.5, "note": "falls to 0.18% at $500,000 or more of 30-day volume" } ], "provenance": { "legalEntity": "Foris DAX Limited", "domain": "crypto.com", "domainRegistered": "1993-05-06", "endpointOnVendorDomain": true, "terms": "https://crypto.com/exchange-pro/en-US/document/tnc", "privacy": "https://crypto.com/uk/privacy/exchange", "statusPage": "https://status.crypto.com", "changelog": "", "securityTxt": "none", "checked": "2026-11-03", "notes": [ "Foris DAX Limited is named in the Exchange privacy notice (last updated 12 March 2025) as a Cayman Islands exempted company. The terms and conditions page loaded empty, so the entity in the terms is unconfirmed.", "RDAP gives crypto.com a registration date of 6 May 1993.", "https://crypto.com/.well-known/security.txt returns 404. cdcx-cli has a SECURITY.md with private vulnerability reporting through GitHub, and the crypto-com organisation has an h1-policy-guidelines repository.", "crypto.com/robots.txt allows the pages read; exchange-docs.crypto.com, exchange-developer.crypto.com and static2.crypto.com answered 403 to robots.txt and nothing on them was fetched. help.crypto.com allows with Crawl-delay 1.", "No API changelog could be read; the Exchange announcements page loaded empty." ], "score": 77 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/crypto-com-exchange.json", "live": { "slug": "crypto-com-exchange", "vendorStatus": { "page": "https://status.crypto.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-04T20:39:03.504264537Z" }, "versions": [ { "registry": "github", "name": "crypto-com/cdcx-cli", "version": "v1.2.6", "released": "2026-06-18", "seenAt": "2026-11-04T20:09:55.434074077Z" }, { "registry": "npm", "name": "@cryptocom/cdcx-cli", "version": "1.2.3", "seenAt": "2026-11-04T20:09:54.573709836Z" } ], "githubStars": 27, "npmWeekly": 51, "securityTxt": { "url": "https://crypto.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-04T15:54:09.539387255Z" }, "updatedAt": "2026-11-04T20:39:03.504264537Z" } }, "answer": "KuCoin scores 53.9 (D) on agent readiness against Crypto.com Exchange API's 46.8 (D), and leads in 4 of 7 scored categories. Crypto.com Exchange API leads on reliability and payments \u0026 pricing.", "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": 824, "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", "versions": [ { "registry": "github", "name": "Kucoin/kucoin-universal-sdk", "version": "v1.3.1", "released": "2026-05-29", "seenAt": "2026-11-04T20:29:03.487838607Z" } ], "githubStars": 55, "securityTxt": { "url": "https://kucoin.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-04T15:54:04.738329571Z" }, "updatedAt": "2026-11-04T20:29:03.487838607Z" } }, "edges": [ { "by": 44, "category": "maintenance", "leads": "kucoin", "name": "Maintenance \u0026 community", "reasons": { "a": "Read as a closed service with an open CLI. The last change we could date is cdcx-cli v1.2.6 on 18 June 2026, 138 days before the check, with no commit since; the API changelog is unread (10). No three dated releases in the last 90 days (0). Five of six open items on cdcx-cli, all by collaborators or Dependabot since May, have no comment; the Exchange has a support chat and contact@crypto.com (8 of 25). Not in the official MCP registry and no official SDK beyond the CLI (5 of 15). CI tests on three operating systems with clippy and fmt; the npm wrapper's postinstall downloads the binary and two Dependabot bumps are open (6 of 10). 10 + 0 + 8 + 5 + 6 = 29.", "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": 29, "b": 73 } }, { "by": 18, "category": "schema", "leads": "kucoin", "name": "Schema \u0026 documentation", "reasons": { "a": "An OpenAPI spec exists, since cdcx-cli generates its 95 commands and tools from it at run time, but its host (exchange-developer.crypto.com) answered 403 to robots.txt and the spec was not read; the vendor's own tooling is evidence it exists, not of its quality (15 of 25). No llms.txt on crypto.com or the Exchange pages (0). For descriptions, cdcx's tool descriptions come from the spec, which we couldn't read; the Exchange skill documents 52 endpoints in prose (8 of 20). cdcx's README says the tools carry typed parameters and enum validation, a vendor claim not checked against the spec (8 of 15). For examples, the skills and cdcx README carry worked commands, but the API's error codes and response examples sit on the unread host (6 of 15). Versioned path (v1); the API changelog and announcements page could not be read (5 of 15). 15 + 0 + 8 + 8 + 6 + 5 = 42.", "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": 42, "b": 60 } }, { "by": 12, "category": "ergonomics", "leads": "kucoin", "name": "Agent ergonomics", "reasons": { "a": "Graded on the REST API as an agent calls it, with the MCP server noted. cdcx serves up to 95 tools, more than 30, but the default serves the `market` group alone and groups are enabled one by one, which is a read-only subset switch (5 + 10 = 15). Pagination and output controls for the API are on the unread docs host; cdcx adds `-o json|table|ndjson` (8 of 20). cdcx returns structured JSON errors and the safety gate names what is missing; the API's own error table is unread (8 of 20). cdcx's tiers (mutate needs `acknowledged: true`, dangerous needs `--allow-dangerous`), `--dry-run` and paper trading give safe rehearsal, though no MCP annotations or API idempotency keys were seen (12 of 20). No official SDK beyond the CLI; defaults in cdcx are sensible (7 of 15). 15 + 8 + 8 + 12 + 7 = 50.", "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": 50, "b": 62 } }, { "by": 5, "category": "reliability", "leads": "crypto-com-exchange", "name": "Reliability", "reasons": { "a": "Read with the hosted lines on the Exchange API at api.crypto.com. status.crypto.com is a Statuspage site with component history (20). Its feed for 18 August to 3 November 2026 has 25 entries; the Exchange is named in two, an 11-minute database upgrade on 18 August and a one-hour balance display issue on 6 October, while the longer disruptions (Android login on 1 and 5 October, card 3DS on 23 September, Main App predictions on 3 November) are App incidents. There is no Exchange API component, so the record may be incomplete. Minor only (20). Rate limits are documented on exchange-docs.crypto.com, which answered 403 to robots.txt and was not read (0, unchecked). 429 handling and client order ids are on the same host (0, unchecked). No SLA found (0). Generally available (10). 20 + 20 + 0 + 0 + 0 + 10 = 50.", "b": "Graded with the hosted lines on the API at api.kucoin.com. No status page found (status.kucoin.com does not resolve, the docs link none), so 0 for the page and 5 for no readable history. Rate limits are published per VIP level with per-endpoint weights and IP limits for public endpoints (15). Every response carries gw-ratelimit-limit, gw-ratelimit-remaining and gw-ratelimit-reset, 429000 is documented with a wait rule, and orders take a clientOid the docs recommend as a UUID (15). No SLA (0). The UTA V2 API is the production surface (10). 45." }, "scores": { "a": 50, "b": 45 } }, { "by": 5, "category": "payments", "leads": "crypto-com-exchange", "name": "Payments \u0026 pricing", "reasons": { "a": "No machine payment protocol (0). Spot fee tiers published without login, 0.25% maker and 0.50% taker at Level 1 (20). The API is free, public market data needs no key, UAT and paper trading need no money (20). A person must sign up in a browser with identity checks and mint the key (0). 0 + 20 + 20 + 0 = 40.", "b": "No machine payment protocol (0). The spot base fee is stated in support articles without login, the futures base rate and the full tier table sit in images or behind script (15 of 20). Market data needs no key, no card is asked for at sign-up (20). A person registers, verifies identity and mints the key in a browser (0). 35." }, "scores": { "a": 40, "b": 35 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Foris DAX Limited (Crypto.com)", "b": "KuCoin", "name": "Vendor" }, { "a": "no (local only)", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "stdio", "b": "", "name": "Transports" }, { "a": "API key", "b": "API key", "name": "Auth" }, { "a": "Pay per use", "b": "Pay per use", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary hosted API under the Exchange terms and conditions, which our reader couldn't load. cdcx-cli, the official CLI and MCP server, is MIT or Apache-2.0", "b": "none", "name": "Licence" }, { "a": "95", "b": "none", "name": "Tools exposed" }, { "a": "no", "b": "yes", "name": "Read-only variant documented" }, { "a": "no", "b": "no", "name": "llms.txt" }, { "a": "2026-06-18", "b": "2026-11-02", "name": "Last release" }, { "a": "couldn't be read", "b": "no date given", "name": "Terms last updated" }, { "a": "2025-03-12", "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": "27 stars, 59 npm/wk", "b": "55 stars", "name": "Popularity" } ], "faq": [ { "answer": "KuCoin scores 53.9 (D) on agent readiness against Crypto.com Exchange API's 46.8 (D), and leads in 4 of 7 scored categories. Crypto.com Exchange API leads on reliability and payments \u0026 pricing.", "question": "Which is better for AI agents, Crypto.com Exchange API or KuCoin?" }, { "answer": "Both need an API key.", "question": "Do Crypto.com Exchange API and KuCoin need an API key?" }, { "answer": "Crypto.com Exchange API runs on your own machine, with no hosted endpoint listed. No hosted endpoint is listed for KuCoin.", "question": "Can an agent call Crypto.com Exchange API and KuCoin without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 50 against 45", "Payments \u0026 pricing, 40 against 35" ], "also": [ "Runs on your own machine" ], "goodFor": "An agent trading spot or perpetuals on Crypto.com through a local MCP server with safety tiers, for a person outside the App's restricted list.", "slug": "crypto-com-exchange", "watchFor": "exchange-docs.crypto.com and the OpenAPI host answered 403 to robots.txt, so rate limits, key permissions, errors and the changelog could not be read" }, { "aheadOn": [ "Schema \u0026 documentation, 60 against 42", "Agent ergonomics, 62 against 50", "Maintenance \u0026 community, 73 against 29" ], "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.market-data", "name": "Exchange market data" }, "others": [ { "json": "https://www.anchorterminal.com/compare/bitfinex-vs-crypto-com-exchange.json", "title": "Bitfinex API vs Crypto.com Exchange API", "url": "https://www.anchorterminal.com/compare/bitfinex-vs-crypto-com-exchange" }, { "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-crypto-com-exchange.json", "title": "Bitget vs Crypto.com Exchange API", "url": "https://www.anchorterminal.com/compare/bitget-vs-crypto-com-exchange" }, { "json": "https://www.anchorterminal.com/compare/bitget-vs-kucoin.json", "title": "Bitget vs KuCoin", "url": "https://www.anchorterminal.com/compare/bitget-vs-kucoin" }, { "json": "https://www.anchorterminal.com/compare/bithumb-vs-crypto-com-exchange.json", "title": "Bithumb Open API vs Crypto.com Exchange API", "url": "https://www.anchorterminal.com/compare/bithumb-vs-crypto-com-exchange" }, { "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-crypto-com-exchange.json", "title": "Bitstamp API vs Crypto.com Exchange API", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-crypto-com-exchange" }, { "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-crypto-com-exchange.json", "title": "Bybit vs Crypto.com Exchange API", "url": "https://www.anchorterminal.com/compare/bybit-vs-crypto-com-exchange" }, { "json": "https://www.anchorterminal.com/compare/bybit-vs-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-deribit.json", "title": "Crypto.com Exchange API vs Deribit", "url": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-deribit" }, { "json": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-dydx.json", "title": "Crypto.com Exchange API vs dYdX", "url": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-dydx" }, { "json": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-gate-io.json", "title": "Crypto.com Exchange API vs Gate", "url": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-gate-io" }, { "json": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-gemini-exchange.json", "title": "Crypto.com Exchange API vs Gemini Exchange API", "url": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-gemini-exchange" }, { "json": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-htx.json", "title": "Crypto.com Exchange API vs HTX trading API", "url": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-htx" }, { "json": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-hyperliquid.json", "title": "Crypto.com Exchange API vs Hyperliquid", "url": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-hyperliquid" }, { "json": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-kraken.json", "title": "Crypto.com Exchange API vs Kraken API", "url": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-kraken" }, { "json": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-mexc.json", "title": "Crypto.com Exchange API vs MEXC API", "url": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-mexc" }, { "json": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-okx.json", "title": "Crypto.com Exchange API vs OKX API", "url": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-okx" }, { "json": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-uniswap.json", "title": "Crypto.com Exchange API vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-uniswap" }, { "json": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-upbit.json", "title": "Crypto.com Exchange API vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-upbit" }, { "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-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-kucoin.json", "title": "Binance API vs KuCoin", "url": "https://www.anchorterminal.com/compare/binance-vs-kucoin" }, { "json": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-crypto-com-exchange.json", "title": "Coinbase Advanced Trade API vs Crypto.com Exchange API", "url": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-crypto-com-exchange" }, { "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-crypto-com-exchange.json", "title": "Coinbase MCP server (Coinbase for Agents) vs Crypto.com Exchange API", "url": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-crypto-com-exchange" }, { "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/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": [ { "by": 5, "crypto-com-exchange": 50, "edge": "crypto-com-exchange", "key": "reliability", "kucoin": 45, "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 18, "crypto-com-exchange": 42, "edge": "kucoin", "key": "schema", "kucoin": 60, "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 12, "crypto-com-exchange": 50, "edge": "kucoin", "key": "ergonomics", "kucoin": 62, "name": "Agent ergonomics", "weight": 13 }, { "by": 1, "crypto-com-exchange": 54, "edge": "kucoin", "key": "security", "kucoin": 55, "name": "Security \u0026 auth", "weight": 14 }, { "by": 5, "crypto-com-exchange": 40, "edge": "crypto-com-exchange", "key": "payments", "kucoin": 35, "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 44, "crypto-com-exchange": 29, "edge": "kucoin", "key": "maintenance", "kucoin": 73, "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 1, "crypto-com-exchange": 55, "edge": "crypto-com-exchange", "key": "transparency", "kucoin": 54, "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "KuCoin scores 53.9 (D) on agent readiness against Crypto.com Exchange API's 46.8 (D), and leads in 4 of 7 scored categories. Crypto.com Exchange API leads on reliability and payments \u0026 pricing. Both do exchange market data.", "tasks": null, "tutorials": [], "verdicts": { "crypto-com-exchange": "Crypto.com is one of two exchanges here with an official MCP server, cdcx-cli, whose 95 generated tools are grouped by service and gated by safety tier. The API docs, OpenAPI file, terms and trading rules refused or hid from our reader, so rate limits, key permissions and the automated-trading clauses are unchecked, and cdcx has no release since June 2026.", "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/crypto-com-exchange-vs-kucoin", "json": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-kucoin.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-kucoin.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-kucoin.min.md" }, "markdown": "KuCoin scores 53.9 (D) on agent readiness against Crypto.com Exchange API's 46.8 (D), and leads in 4 of 7 scored categories. Crypto.com Exchange API leads on reliability and payments \u0026 pricing. Both do exchange market data.\n\n- Crypto.com Exchange API: grade D, 46.8/100, rank #1078 of 1349. Markdown https://www.anchorterminal.com/tools/crypto-com-exchange.md · JSON https://www.anchorterminal.com/api/v1/tools/crypto-com-exchange.json\n- KuCoin: grade D, 53.9/100, rank #824 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### Crypto.com Exchange API (D)\n\nGood for: An agent trading spot or perpetuals on Crypto.com through a local MCP server with safety tiers, for a person outside the App's restricted list.\n\nAhead on:\n- Reliability, 50 against 45\n- Payments \u0026 pricing, 40 against 35\n\nAlso in its favour:\n- Runs on your own machine\n\nWatch for: exchange-docs.crypto.com and the OpenAPI host answered 403 to robots.txt, so rate limits, key permissions, errors and the changelog could not be read\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- Schema \u0026 documentation, 60 against 42\n- Agent ergonomics, 62 against 50\n- Maintenance \u0026 community, 73 against 29\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### Maintenance \u0026 community: KuCoin +44\n\n- Crypto.com Exchange API (29): Read as a closed service with an open CLI. The last change we could date is cdcx-cli v1.2.6 on 18 June 2026, 138 days before the check, with no commit since; the API changelog is unread (10). No three dated releases in the last 90 days (0). Five of six open items on cdcx-cli, all by collaborators or Dependabot since May, have no comment; the Exchange has a support chat and contact@crypto.com (8 of 25). Not in the official MCP registry and no official SDK beyond the CLI (5 of 15). CI tests on three operating systems with clippy and fmt; the npm wrapper's postinstall downloads the binary and two Dependabot bumps are open (6 of 10). 10 + 0 + 8 + 5 + 6 = 29.\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### Schema \u0026 documentation: KuCoin +18\n\n- Crypto.com Exchange API (42): An OpenAPI spec exists, since cdcx-cli generates its 95 commands and tools from it at run time, but its host (exchange-developer.crypto.com) answered 403 to robots.txt and the spec was not read; the vendor's own tooling is evidence it exists, not of its quality (15 of 25). No llms.txt on crypto.com or the Exchange pages (0). For descriptions, cdcx's tool descriptions come from the spec, which we couldn't read; the Exchange skill documents 52 endpoints in prose (8 of 20). cdcx's README says the tools carry typed parameters and enum validation, a vendor claim not checked against the spec (8 of 15). For examples, the skills and cdcx README carry worked commands, but the API's error codes and response examples sit on the unread host (6 of 15). Versioned path (v1); the API changelog and announcements page could not be read (5 of 15). 15 + 0 + 8 + 8 + 6 + 5 = 42.\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### Agent ergonomics: KuCoin +12\n\n- Crypto.com Exchange API (50): Graded on the REST API as an agent calls it, with the MCP server noted. cdcx serves up to 95 tools, more than 30, but the default serves the `market` group alone and groups are enabled one by one, which is a read-only subset switch (5 + 10 = 15). Pagination and output controls for the API are on the unread docs host; cdcx adds `-o json|table|ndjson` (8 of 20). cdcx returns structured JSON errors and the safety gate names what is missing; the API's own error table is unread (8 of 20). cdcx's tiers (mutate needs `acknowledged: true`, dangerous needs `--allow-dangerous`), `--dry-run` and paper trading give safe rehearsal, though no MCP annotations or API idempotency keys were seen (12 of 20). No official SDK beyond the CLI; defaults in cdcx are sensible (7 of 15). 15 + 8 + 8 + 12 + 7 = 50.\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### Reliability: Crypto.com Exchange API +5\n\n- Crypto.com Exchange API (50): Read with the hosted lines on the Exchange API at api.crypto.com. status.crypto.com is a Statuspage site with component history (20). Its feed for 18 August to 3 November 2026 has 25 entries; the Exchange is named in two, an 11-minute database upgrade on 18 August and a one-hour balance display issue on 6 October, while the longer disruptions (Android login on 1 and 5 October, card 3DS on 23 September, Main App predictions on 3 November) are App incidents. There is no Exchange API component, so the record may be incomplete. Minor only (20). Rate limits are documented on exchange-docs.crypto.com, which answered 403 to robots.txt and was not read (0, unchecked). 429 handling and client order ids are on the same host (0, unchecked). No SLA found (0). Generally available (10). 20 + 20 + 0 + 0 + 0 + 10 = 50.\n- KuCoin (45): Graded with the hosted lines on the API at api.kucoin.com. No status page found (status.kucoin.com does not resolve, the docs link none), so 0 for the page and 5 for no readable history. Rate limits are published per VIP level with per-endpoint weights and IP limits for public endpoints (15). Every response carries gw-ratelimit-limit, gw-ratelimit-remaining and gw-ratelimit-reset, 429000 is documented with a wait rule, and orders take a clientOid the docs recommend as a UUID (15). No SLA (0). The UTA V2 API is the production surface (10). 45.\n\n### Payments \u0026 pricing: Crypto.com Exchange API +5\n\n- Crypto.com Exchange API (40): No machine payment protocol (0). Spot fee tiers published without login, 0.25% maker and 0.50% taker at Level 1 (20). The API is free, public market data needs no key, UAT and paper trading need no money (20). A person must sign up in a browser with identity checks and mint the key (0). 0 + 20 + 20 + 0 = 40.\n- KuCoin (35): No machine payment protocol (0). The spot base fee is stated in support articles without login, the futures base rate and the full tier table sit in images or behind script (15 of 20). Market data needs no key, no card is asked for at sign-up (20). A person registers, verifies identity and mints the key in a browser (0). 35.\n\n## Score by category\n\n| Category | Weight | Crypto.com Exchange API | KuCoin | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 50 | 45 | Crypto.com Exchange API +5 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 42 | 60 | KuCoin +18 |\n| Agent ergonomics | 13% (16.2 this run) | 50 | 62 | KuCoin +12 |\n| Security \u0026 auth | 14% (17.5 this run) | 54 | 55 | KuCoin +1 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 35 | Crypto.com Exchange API +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 29 | 73 | KuCoin +44 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 55 | 54 | Crypto.com Exchange API +1 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **46.8 · D** | **53.9 · D** | |\n\n## Facts side by side\n\n| Fact | Crypto.com Exchange API | KuCoin |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Foris DAX Limited (Crypto.com) | KuCoin |\n| Hosted endpoint | no (local only) | no (local only) |\n| Transports | stdio | |\n| Auth | API key | API key |\n| Pricing | Pay per use | Pay per use |\n| x402 | no | no |\n| Licence | Proprietary hosted API under the Exchange terms and conditions, which our reader couldn't load. cdcx-cli, the official CLI and MCP server, is MIT or Apache-2.0 | none |\n| Tools exposed | 95 | none |\n| Read-only variant documented | no | yes |\n| llms.txt | no | no |\n| Last release | 2026-06-18 | 2026-11-02 |\n| Terms last updated | couldn't be read | no date given |\n| Privacy policy last updated | 2025-03-12 | 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 | 27 stars, 59 npm/wk | 55 stars |\n\n## Verdicts\n\n**Crypto.com Exchange API.** Crypto.com is one of two exchanges here with an official MCP server, cdcx-cli, whose 95 generated tools are grouped by service and gated by safety tier. The API docs, OpenAPI file, terms and trading rules refused or hid from our reader, so rate limits, key permissions and the automated-trading clauses are unchecked, and cdcx has no release since June 2026.\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### Crypto.com Exchange API\n\n1. Enable only the service groups the task needs with `cdcx mcp config --enable trade,account` (the default serves `market` alone), and leave `--allow-dangerous` off unless the person asks for withdrawals or cancel-all\n2. Rehearse on `--env uat` or `cdcx paper` first; production keys trade real funds, and the skill requires explicit user confirmation before each live order\n3. Put the key in CDCX_API_KEY and CDCX_API_SECRET or `~/.config/cdcx/config.toml` at 0600; there is no key flag, and the key should have no withdrawal permission and an IP allow-list\n4. Pass `acknowledged: true` on mutate tools and `--dry-run` while testing; read the tool's generated schema before calling, since the docs host is unreadable to agents without a browser\n5. Check the person's country against Crypto.com's geo-restriction article and the Exchange terms before trading; New York and about 70 countries are excluded from the App, and the Exchange list was unreadable\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, Crypto.com Exchange API or KuCoin?\n\nKuCoin scores 53.9 (D) on agent readiness against Crypto.com Exchange API's 46.8 (D), and leads in 4 of 7 scored categories. Crypto.com Exchange API leads on reliability and payments \u0026 pricing.\n\n### Do Crypto.com Exchange API and KuCoin need an API key?\n\nBoth need an API key.\n\n### Can an agent call Crypto.com Exchange API and KuCoin without installing anything?\n\nCrypto.com Exchange API runs on your own machine, with no hosted endpoint listed. No hosted endpoint is listed for KuCoin.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/crypto-com-exchange-vs-kucoin.json, and with the fewest tokens: https://www.anchorterminal.com/compare/crypto-com-exchange-vs-kucoin.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"crypto-com-exchange\", \"b\": \"kucoin\"}`. From a terminal: `anchor compare crypto-com-exchange kucoin`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/crypto-com-exchange.json and https://www.anchorterminal.com/api/v1/tools/kucoin.json\n\n## Other comparisons with Crypto.com Exchange API or KuCoin\n\n- [Bitfinex API vs Crypto.com Exchange API](https://www.anchorterminal.com/compare/bitfinex-vs-crypto-com-exchange.md)\n- [Bitfinex API vs KuCoin](https://www.anchorterminal.com/compare/bitfinex-vs-kucoin.md)\n- [Bitget vs Crypto.com Exchange API](https://www.anchorterminal.com/compare/bitget-vs-crypto-com-exchange.md)\n- [Bitget vs KuCoin](https://www.anchorterminal.com/compare/bitget-vs-kucoin.md)\n- [Bithumb Open API vs Crypto.com Exchange API](https://www.anchorterminal.com/compare/bithumb-vs-crypto-com-exchange.md)\n- [Bithumb Open API vs KuCoin](https://www.anchorterminal.com/compare/bithumb-vs-kucoin.md)\n- [Bitstamp API vs Crypto.com Exchange API](https://www.anchorterminal.com/compare/bitstamp-vs-crypto-com-exchange.md)\n- [Bitstamp API vs KuCoin](https://www.anchorterminal.com/compare/bitstamp-vs-kucoin.md)\n- [Bybit vs Crypto.com Exchange API](https://www.anchorterminal.com/compare/bybit-vs-crypto-com-exchange.md)\n- [Bybit vs KuCoin](https://www.anchorterminal.com/compare/bybit-vs-kucoin.md)\n- [Crypto.com Exchange API vs Deribit](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-deribit.md)\n- [Crypto.com Exchange API vs dYdX](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-dydx.md)\n- [Crypto.com Exchange API vs Gate](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-gate-io.md)\n- [Crypto.com Exchange API vs Gemini Exchange API](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-gemini-exchange.md)\n- [Crypto.com Exchange API vs HTX trading API](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-htx.md)\n- [Crypto.com Exchange API vs Hyperliquid](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-hyperliquid.md)\n- [Crypto.com Exchange API vs Kraken API](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-kraken.md)\n- [Crypto.com Exchange API vs MEXC API](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-mexc.md)\n- [Crypto.com Exchange API vs OKX API](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-okx.md)\n- [Crypto.com Exchange API vs Uniswap Trading API](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-uniswap.md)\n- [Crypto.com Exchange API vs Upbit Open API](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-upbit.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 Crypto.com Exchange API](https://www.anchorterminal.com/compare/binance-vs-crypto-com-exchange.md)\n- [Binance API vs KuCoin](https://www.anchorterminal.com/compare/binance-vs-kucoin.md)\n- [Coinbase Advanced Trade API vs Crypto.com Exchange API](https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-crypto-com-exchange.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 Crypto.com Exchange API](https://www.anchorterminal.com/compare/coinbase-mcp-vs-crypto-com-exchange.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- [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": "Crypto.com Exchange API vs KuCoin", "url": "" } ], "description": "KuCoin scores 53.9 (D) to Crypto.com Exchange's 46.8 (D) for exchange market data. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Crypto.com Exchange API D 46.8", "KuCoin D 53.9", "scores" ], "h1": "Crypto.com Exchange API vs KuCoin", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/crypto-com-exchange-vs-kucoin", "published": "2026-10-01", "section": "tools", "title": "Crypto.com Exchange vs KuCoin for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-04", "url": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-kucoin" }, "tokens": { "markdown": 4650, "slim": 2330 }, "version": 1 }