# Crypto.com Exchange API > 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. - Canonical: https://www.anchorterminal.com/tools/crypto-com-exchange - Pricing: https://www.anchorterminal.com/tools/crypto-com-exchange#pricing - Reviews: https://www.anchorterminal.com/tools/crypto-com-exchange#reviews - Markdown: https://www.anchorterminal.com/tools/crypto-com-exchange.md (~9,500 tokens) - Slim: https://www.anchorterminal.com/tools/crypto-com-exchange.min.md (~2,380 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/crypto-com-exchange.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key) - DNS: dig +short TXT crypto-com-exchange.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.. and .vs.. under the zone, and the same under grade.letme.dev) - Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data) - Updated: 2026-11-04 ## Overview **Grade D · 46.8/100 · rank #1100 of 1349 · #20 in Crypto exchanges · not agent-ready · confidence low** ## Assessment 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. ## Facts | Field | Value | | --- | --- | | Vendor | Foris DAX Limited (Crypto.com) (https://crypto.com/exchange) | | Kind | HTTP API | | Category | Crypto exchanges (https://www.anchorterminal.com/categories/crypto-exchanges) | | Transport | stdio | | Auth | API key · API key and secret created in the Exchange under Settings > 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 | Pay per use (0.25% fee) · 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). | | x402 | No · 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. | | 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 | | Tools exposed | 95 | | Packages | npm: `@cryptocom/cdcx-cli` | | Source | https://github.com/crypto-com/cdcx-cli | | Docs | https://exchange-docs.crypto.com/exchange/v1/rest-ws/index.html | | llms.txt | not found | | Last release | 2026-06-18 | | GitHub stars | 27 (as of 2026-11-03) | | npm downloads / week | 59 | | Surface listed | The hosted Exchange API at api.crypto.com/exchange/v1 as an agent calls it, read from crypto.com's Exchange pages (API overview, fees, privacy notice), the cdcx-cli and crypto-agent-trading repositories (shallow clone and READMEs), npm, status.crypto.com, the MCP registry and the help centre on 3 November 2026. The API docs host and the OpenAPI host refused robots.txt and were not fetched. No account, key, session or order | | MCP server | Official. `cdcx mcp` in github.com/crypto-com/cdcx-cli (Rust, MIT or Apache-2.0), stdio, 95 tools generated from the OpenAPI spec at run time, enabled by service group, with read, sensitive_read, mutate and dangerous tiers. npm `@cryptocom/cdcx-cli` 1.2.3 (repository tag v1.2.6, 18 June 2026). Authenticates with the Exchange API key and secret from the environment or config file. Not in the official MCP registry | | Key permissions | Keys are made under Settings > API Keys with 2FA. The official skills say to recommend IP whitelisting in production, that withdrawal addresses must be pre-approved, and the App skill's key has no withdrawal permission. The permission list itself (read, trade, withdraw) is on the docs host we couldn't read | | Rate limits | Unchecked. They are documented on exchange-docs.crypto.com, which answered 403 to robots.txt. cdcx's README does not state them | | Testnet or sandbox | UAT at https://uat-api.3ona.co/exchange/v1 with wss://uat-stream.3ona.co market and user streams, selected in cdcx with `--env uat`; the Exchange skill calls it a sandbox for institutional users. cdcx also has a local paper-trading engine (`cdcx paper`) with no credentials and no MCP tools | | Countries served | Unchecked for the Exchange; its terms loaded empty. The App's geo-restrictions article of 12 May 2026 lists about 70 restricted countries and regions (China, Russia, Iran, Cuba, North Korea, Venezuela, Indonesia and others), New York state and five Ukrainian regions, and says it covers the App | | Fees at the lowest tier | Spot 0.2500% maker and 0.5000% taker under $10,000 of 30-day volume, 0.2425% and 0.4850% with a CRO balance; 0.08% and 0.18% at $500,000 or more. Derivatives fees not on the page; liquidation fee 0.5% | | FIX and WebSocket | REST and WebSocket for spot, perpetuals and OTC (`user.order.{instrument_name}` streams); FIX for spot, perpetuals and the Predictions DCM and FCM venues; REST and WebSocket for Predictions coming soon, per the Exchange API page | | Terms on automated trading | Unchecked. The terms and conditions and trading rules pages at crypto.com/exchange-pro/en-US/document/ draw their text by script and loaded empty. The Exchange API page says only that it is built for automated trading | | Agent skills | crypto-com/crypto-agent-trading holds a Crypto.com App skill (market buys, sells, swaps, balances, a kill switch; Apache-2.0) and an Exchange spot skill documenting 52 endpoints with order groups (OCO, OTO, OTOCO) that requires explicit user confirmation before a production trade (MIT). cdcx-cli ships 13 more skill files | | Legal entity | Foris DAX Limited, an exempted company in the Cayman Islands (registration QH-354886), named as the Exchange's data controller in its privacy notice of 12 March 2025. Regional affiliates (Foris DAX MT Limited in Malta, Foris DAX Middle East FZE) run local services | | Status | status.crypto.com, a Statuspage site shared with the App and Card; the Exchange is named in two of 25 entries since 18 August 2026 and there is no Exchange API component | | 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 | | JSON | https://www.anchorterminal.com/api/v1/tools/crypto-com-exchange.json | ## Score breakdown (methodology v0.7, October 2026 research run) Assessed 2026-11-03 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: low. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 50 | 10.0 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 42 | 6.8 | | Agent ergonomics | 13% | 16.2 | 50 | 8.1 | | Security & auth | 14% | 17.5 | 54 | 9.4 | | Payments & pricing | 10% | 12.5 | 40 | 5.0 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 29 | 2.5 | | Transparency & trust (editorial 32, provenance 77) | 7% | 8.8 | 55 | 4.8 | | Negative events | up to −15 | up to −15 | none recorded | 0 | | **Total** | | | | **46.8 → D** | ### Why each score - Reliability 50 (checked 2026-11-03): 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. - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 42 (checked 2026-11-03): 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. - Agent ergonomics 50 (checked 2026-11-03): 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. - Security & auth 54 (checked 2026-11-03): HMAC-SHA256 API keys made with 2FA; IP whitelisting and pre-approved withdrawal addresses per the official skill, and revocation from the Exchange settings. The permission list (read, trade, withdraw) is on the unread docs host, so scopes are recorded from the skills (20 of 30). On least privilege, the App skill's key has no withdrawal permission, the Exchange skill requires user confirmation before a production trade, and cdcx refuses withdrawals and cancel-all without `--allow-dangerous`; nothing on the server side limits order size (14 of 20). The tools return exchange data, not third-party text, but no guidance on untrusted content was found (6 of 15). An account audit trail is not documented where we could read (4 of 15). No security.txt on crypto.com; cdcx has a SECURITY.md with private reporting and a three-day acknowledgement, and the organisation keeps HackerOne policy guidelines; certifications were not read (10 of 20). 20 + 14 + 6 + 4 + 10 = 54. - Payments & pricing 40 (checked 2026-11-03): 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. - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 29 (checked 2026-11-03): 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. - Transparency & trust 55 (checked 2026-11-03): The editorial half. A closed service whose terms and trading rules loaded empty for our reader; cdcx and the skills are MIT or Apache-2.0 (10 of 30). The Exchange privacy notice of 12 March 2025 names Foris DAX Limited, gives retention examples (6 years for correspondence, 5 years for EEA AML records) and provider categories, with no DPA or subprocessor list (16 of 30). No deprecation policy or notice period was found (0). Transfers outside the Cayman Islands and the EEA are stated with no countries named (6 of 20). 10 + 16 + 0 + 6 = 32. Fix list, everything this grade says the listing lacks, the biggest gain first (21 items). What it covers is at https://www.anchorterminal.com/fixes/crypto-com-exchange.md (JSON https://www.anchorterminal.com/fixes/crypto-com-exchange.json). The whole list for a coding agent comes from `POST https://www.anchorterminal.com/api/v1/fix-list` with `{"listing": "crypto-com-exchange", "plan": "read"}`, free while the beta runs ### What we couldn't check - Kind http-api. The Exchange's own pages lead with REST, WebSocket and FIX; cdcx-cli is the official MCP route and is in `packages` and `transports`. - The MCP server is official, local stdio in cdcx-cli, up to 95 tools generated from the OpenAPI spec, `market` group by default, safety tiers from the source. Not in the official MCP registry. No session was opened; the count is the README's and the generator's, since the spec itself could not be read. - unchecked: everything on exchange-docs.crypto.com and exchange-developer.crypto.com (rate limits, key permissions, error codes, client order ids, idempotency, the OpenAPI spec, the API changelog), because both hosts answered 403 to robots.txt. Reliability's rate-limit and 429 lines and schema's contract line score low for that reason, not because the docs lack them. - unchecked: the Exchange terms and conditions, trading rules and announcements pages (script-drawn, loaded empty), so the legal entity in the terms, the clauses on API use and bots, and the Exchange's restricted-country list are unconfirmed. The App's geo-restriction article is recorded as the App's list. The US Exchange terms PDF is on static2.crypto.com, which refused robots.txt. - firstReleased is 17 April 2026, cdcx-cli's initial public release, the earliest first-hand dated evidence of the agent surface; the Exchange API itself is older and its launch date could not be read first-hand. lastRelease is cdcx v1.2.6 of 18 June 2026. - npm `@cryptocom/cdcx-cli` is at 1.2.3 while the repository's latest tag is v1.2.6; the npm wrapper downloads the binary in a postinstall script and the two versions may track different things. Recorded, not deducted. - unchecked: SOC 2 or ISO 27001 claims on crypto.com's security pages, the help centre's Exchange API key article (not found by search), and whether the status page posts Exchange API incidents at all. - The legal entity is Foris DAX Limited (Cayman Islands), from the Exchange privacy notice. The terms may name a different entity by region (Foris DAX MT Limited in Malta, Foris DAX Middle East FZE), unread. - Our own products. It doesn't do LocalGhost's or letme's job; it trades one exchange account. ### Sources - robots.txt (crypto.com allows; exchange-docs.crypto.com, exchange-developer.crypto.com and static2.crypto.com answered 403; help.crypto.com allows; status.crypto.com disallows /api/): (seen 2026-11-03) - Exchange home page (links to fees, API, terms, privacy, status): (seen 2026-11-03) - Exchange API overview (REST, WebSocket, FIX coverage): (seen 2026-11-03) - fees and limits: (seen 2026-11-03) - terms and conditions (loaded empty): (seen 2026-11-03) - trading rules (loaded empty): (seen 2026-11-03) - Exchange privacy notice (Foris DAX Limited): (seen 2026-11-03) - privacy hub (regional notices): (seen 2026-11-03) - App geo-restrictions article: (seen 2026-11-03) - about page (founders, leadership, skill and CLI links): (seen 2026-11-03) - cdcx-cli repository, shallow clone (README, SECURITY.md, safety tiers, OpenAPI fetcher, environments, CI, tags): (seen 2026-11-03) - cdcx-cli repository metadata and open items: (seen 2026-11-03) - crypto-agent-trading README (agent skills): (seen 2026-11-03) - crypto-com GitHub organisation repositories and search: (seen 2026-11-03) - npm @cryptocom/cdcx-cli latest and weekly downloads: (seen 2026-11-03) - official MCP registry searches (crypto.com, crypto): (seen 2026-11-03) - status history feed: (seen 2026-11-03) - security.txt (404): (seen 2026-11-03) - RDAP for crypto.com: (seen 2026-11-03) ## Score history Every move of a score since the listing was graded, newest first, with its cause. A score can't move without an entry here. JSON: https://www.anchorterminal.com/api/v1/tools/crypto-com-exchange/history.json - 2026-11-03: graded 46.8 D (methodology 0.7) ## Who's behind it (provenance 77/100, checked 2026-11-03) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | Foris DAX Limited | 20/20 | | Domain age | crypto.com, registered 1993-05-06 (33 years) | 15/15 | | Endpoint on the vendor's domain | crypto.com | 15/15 | | Terms of service | published, but our reader couldn't read it | 7/10 | | Privacy policy | read, states 7 of the 8 things a reader expects | 9.3/10 | | Status page | status.crypto.com | 10/10 | | Changelog | not found | 0/10 | | security.txt | not found | 0/10 | | People named | 4 named with their role, none with a public profile | 7/10 | | Support route | a support address, help pages, a community | 5/5 | 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. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service** (https://crypto.com/exchange-pro/en-US/document/tnc), read 2026-11-03. Our reader couldn't read it (the page has 95 words of text without a browser, so the document is drawn by script or sits elsewhere). **Privacy policy** (https://crypto.com/uk/privacy/exchange), read 2026-11-03, dated 2025-03-12, states 7 of the 8 things a reader expects. - Gives the date it was last updated. Last updated 2025-03-12. - Says how long data is kept. Names a period of 6 years. - Not found in the text. Says whether personal data is sold or shared for advertising. - Gives a privacy contact. Names a data protection officer. - Says where data is transferred or stored. Relies on standard contractual clauses. ## Humans behind the project (researched 2026-11-03 from public pages, not part of the grade) ### Key people - Kris Marszalek, Co-founder and CEO, Crypto.com - Rafael Melo, Co-founder and CFO, Crypto.com - Bobby Bao, Co-founder and Head of Crypto.com Capital, Crypto.com - Eric Anziani, President and COO, Crypto.com - Note: Crypto.com's about page, read 3 November 2026, names Kris Marszalek (Co-Founder and CEO, based in Hong Kong), Rafael Melo (Co-Founder and CFO), Bobby Bao (Co-Founder, Head of Crypto.com Capital) and Eric Anziani (President and COO). The founders are the company's, not the Exchange product team's. No personal LinkedIn, X or GitHub accounts are linked from the page. The Exchange is operated by Foris DAX Limited, an exempted company in the Cayman Islands per the Exchange privacy notice, which is a private company form, so ownership is recorded as private. Investors were looked for on the about page, the Exchange pages, the privacy hub and the GitHub organisation; nothing names a funding round or backers, and no outside search was made in this pass, so a later pass should look at the company's press pages. - Crypto.com: LinkedIn https://www.linkedin.com/company/cryptocom X https://x.com/cryptocom GitHub https://github.com/crypto-com ### Getting support - Discord: https://discord.gg/cryptocom - Support email: contact@crypto.com - Help: https://help.crypto.com/en - Help: https://chat.crypto.com/ - Help: https://status.crypto.com/ - Community (r/Crypto_com): https://www.reddit.com/r/Crypto_com/ - Community (cdcx-cli issues): https://github.com/crypto-com/cdcx-cli/issues - Sources: https://crypto.com/about, https://crypto.com/exchange, https://crypto.com/exchange-pro/en-US/api, https://crypto.com/privacy, https://crypto.com/uk/privacy/exchange, https://github.com/crypto-com/cdcx-cli, https://api.github.com/orgs/crypto-com/repos?per_page=100&sort=updated ## Live (updated 2026-11-04 19:31 UTC) - Vendor status page: none, All Systems Operational - security.txt: none - Always current: https://www.anchorterminal.com/api/v1/live/crypto-com-exchange.json ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## Prices | Item | Price | Unit | Note | | --- | --- | --- | --- | | Spot maker fee, Level 1 (under $10,000 of 30-day volume) | 0.25% | percentage fee | 0.2425% with a CRO balance | | Spot taker fee, Level 1 | 0.5% | percentage fee | falls to 0.18% at $500,000 or more of 30-day volume | Across all listings: https://www.anchorterminal.com/prices/index.md ## 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 ## Before you call it (notes for agents) 1. 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 2. Rehearse on `--env uat` or `cdcx paper` first; production keys trade real funds, and the skill requires explicit user confirmation before each live order 3. 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 4. 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 5. 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 ## Connect Install: ```bash curl -sSfL https://raw.githubusercontent.com/crypto-com/cdcx-cli/main/install.sh | sh ``` First request: ```bash curl https://api.crypto.com/exchange/v1/public/get-tickers ``` MCP client configuration: ```json { "mcpServers": { "cdcx": { "args": [ "-y", "@cryptocom/cdcx-cli@latest", "mcp" ], "command": "npx", "env": { "CDCX_API_KEY": "your_api_key", "CDCX_API_SECRET": "your_api_secret" } } } } ``` Through letme: https://letme.dev/crypto-com-exchange. letme answers with the pick and how to call it direct. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | Gemini Exchange API | BB | 74.6 | 70 | exchange.market-data, exchange.spot-trading, exchange.derivatives, exchange.balances, exchange.transfers, exchange.staking, market.crypto | no | https://www.anchorterminal.com/tools/gemini-exchange.md | | Kraken API | BB | 71 | 159 | exchange.spot-trading, exchange.market-data, exchange.derivatives, exchange.balances, exchange.transfers, exchange.staking, market.crypto | no | https://www.anchorterminal.com/tools/kraken.md | | OKX API | B | 64.3 | 413 | exchange.spot-trading, exchange.market-data, exchange.derivatives, exchange.balances, exchange.transfers, exchange.staking, market.crypto | no | https://www.anchorterminal.com/tools/okx.md | | Binance API | B | 63.2 | 448 | exchange.spot-trading, exchange.market-data, exchange.derivatives, exchange.balances, exchange.transfers, exchange.staking, market.crypto | no | https://www.anchorterminal.com/tools/binance.md | | Bitfinex API | C | 58.4 | 687 | exchange.market-data, exchange.spot-trading, exchange.derivatives, exchange.balances, exchange.transfers, exchange.staking, market.crypto | no | https://www.anchorterminal.com/tools/bitfinex.md | | Bybit | C | 57.3 | 745 | exchange.market-data, exchange.spot-trading, exchange.derivatives, exchange.balances, exchange.transfers, exchange.staking, market.crypto | no | https://www.anchorterminal.com/tools/bybit.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - Crypto.com runs an official MCP server as part of cdcx-cli, a Rust binary in github.com/crypto-com/cdcx-cli (initial public release 17 April 2026, v1.2.6 on 18 June 2026). `cdcx mcp` serves up to 95 tools over stdio, generated at run time from the Exchange's OpenAPI spec and enabled by service group (`market` by default; `account`, `trade`, `advanced`, `margin`, `staking`, `funding`, `fiat`, `otc`, `bot` and `stream` with `cdcx mcp config --enable`), with the choice kept in ~/.config/cdcx/mcp.toml. npm wraps it as `@cryptocom/cdcx-cli` 1.2.3, whose postinstall script downloads the binary; Claude Code, Codex and Cursor plugins are in the repository (source: ) - cdcx's safety tiers come from the source. Public endpoints are read, order creation, amendment, cancellation, margin multiplier changes, staking and subaccount transfers are mutate and need `acknowledged: true`, and cancel-all-orders, create-withdrawal, fiat withdrawals and terminating a trading bot are dangerous and refused unless the server starts with `--allow-dangerous` (crates/cdcx-core/src/safety.rs, read 2026-11-03) - Not in the official MCP registry. Searches for crypto.com and crypto on 3 November 2026 found no server from Crypto.com (source: ) - A second official repository, crypto-com/crypto-agent-trading (February 2026), holds two SKILL.md skills, one for the Crypto.com App and one for the Exchange that documents 52 endpoints and requires explicit user confirmation before a production trade; Crypto.com's about page links both under Trading Skill Repo and CDCX CLI (source: ) - The Exchange API docs host, exchange-docs.crypto.com, and the OpenAPI host cdcx reads from, exchange-developer.crypto.com/exchange/v1/openapi/, both answered 403 to robots.txt, so nothing on either was fetched. Rate limits, the key permission list, error codes, client order ids and the API changelog are unchecked for that reason (crates/cdcx-core/src/openapi/fetcher.rs) - cdcx names two environments, production at api.crypto.com/exchange/v1 with wss streams and UAT at uat-api.3ona.co with uat-stream.3ona.co, selected with `--env uat`. The Exchange skill calls UAT a sandbox for institutional users (crates/cdcx-core/src/env.rs) - The Exchange API page says REST and WebSocket cover spot, perpetuals and OTC, FIX covers spot, perpetuals and the two Predictions venues, and REST and WebSocket for Predictions are coming soon (source: ) - The Exchange privacy notice (last updated 12 March 2025) names Foris DAX Limited, an exempted company in the Cayman Islands (QH-354886), keeps chats and letters up to 6 years after the relationship ends and 5 years for EEA AML records, and names provider categories but no subprocessors (source: ) - The Exchange terms and conditions, trading rules and announcements pages draw their text by script and loaded empty for our reader, so the clauses on API use, bots and restricted jurisdictions are unchecked. The App's geo-restrictions article (12 May 2026) lists about 70 restricted countries and New York, and says it applies to the App (source: ) - status.crypto.com's feed for 18 August to 3 November 2026 names the Exchange in two of 25 entries, an 11-minute database upgrade on 18 August and a wallet balance display issue on 6 October; the longer disruptions (Android login, card 3DS, predictions in the Main App) are App incidents (source: ) - #20 of 21 in Best crypto exchange APIs and MCP servers for AI agents: https://www.anchorterminal.com/best/crypto-exchanges/index.md - All 210 exchanges comparisons: https://www.anchorterminal.com/compare/crypto-exchanges/index.md ## Compare - [Bitfinex API vs Crypto.com Exchange API](https://www.anchorterminal.com/compare/bitfinex-vs-crypto-com-exchange.md): C 58.4 vs D 46.8 - [Bitget vs Crypto.com Exchange API](https://www.anchorterminal.com/compare/bitget-vs-crypto-com-exchange.md): D 53.9 vs D 46.8 - [Bithumb Open API vs Crypto.com Exchange API](https://www.anchorterminal.com/compare/bithumb-vs-crypto-com-exchange.md): D 50.6 vs D 46.8 - [Bitstamp API vs Crypto.com Exchange API](https://www.anchorterminal.com/compare/bitstamp-vs-crypto-com-exchange.md): D 50.4 vs D 46.8 - [Bybit vs Crypto.com Exchange API](https://www.anchorterminal.com/compare/bybit-vs-crypto-com-exchange.md): C 57.3 vs D 46.8 - [Crypto.com Exchange API vs Deribit](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-deribit.md): D 46.8 vs C 59 - [Crypto.com Exchange API vs dYdX](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-dydx.md): D 46.8 vs B 69.5 - [Crypto.com Exchange API vs Gate](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-gate-io.md): D 46.8 vs C 56.4 - [Crypto.com Exchange API vs Gemini Exchange API](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-gemini-exchange.md): D 46.8 vs BB 74.6 - [Crypto.com Exchange API vs HTX trading API](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-htx.md): D 46.8 vs E 43.3 - [Crypto.com Exchange API vs Hyperliquid](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-hyperliquid.md): D 46.8 vs D 50 - [Crypto.com Exchange API vs Kraken API](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-kraken.md): D 46.8 vs BB 71 - [Crypto.com Exchange API vs KuCoin](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-kucoin.md): D 46.8 vs D 53.9 - [Crypto.com Exchange API vs MEXC API](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-mexc.md): D 46.8 vs C 56.3 - [Crypto.com Exchange API vs OKX API](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-okx.md): D 46.8 vs B 64.3 - [Crypto.com Exchange API vs Uniswap Trading API](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-uniswap.md): D 46.8 vs B 63.3 - [Crypto.com Exchange API vs Upbit Open API](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-upbit.md): D 46.8 vs C 54.7 - [Binance API vs Crypto.com Exchange API](https://www.anchorterminal.com/compare/binance-vs-crypto-com-exchange.md): B 63.2 vs D 46.8 - [Coinbase Advanced Trade API vs Crypto.com Exchange API](https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-crypto-com-exchange.md): C 61.7 vs D 46.8 - [Coinbase MCP server (Coinbase for Agents) vs Crypto.com Exchange API](https://www.anchorterminal.com/compare/coinbase-mcp-vs-crypto-com-exchange.md): C 60 vs D 46.8 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on crypto.com or one of its subdomains, or the README at the root of github.com/crypto-com/cdcx-cli. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "crypto-com-exchange", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html Crypto.com Exchange API on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![Crypto.com Exchange API on Anchor Terminal](https://www.anchorterminal.com/badges/crypto-com-exchange.svg)](https://www.anchorterminal.com/tools/crypto-com-exchange) ``` Plain link: ```html Crypto.com Exchange API on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Crypto.com Exchange API is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/crypto-com-exchange-dark.png - Light: https://www.anchorterminal.com/assets/share/crypto-com-exchange-light.png --- Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp