Head to head · Exchange market data · October 2026 research run
Bitpont API and MCP vs Crypto.com Exchange API
Bitpont API and MCP scores 62.9 (B) on agent readiness against Crypto.com Exchange API's 49.3 (D), and leads in 5 of 7 scored categories. Crypto.com Exchange API leads on reliability and maintenance & community. Both do exchange market data.
Best crypto exchange APIs and MCP servers for AI agents · All 231 exchanges comparisons
Which one, for what
Best for An aggregator over DeFi venues (Jupiter, KyberSwap, LI.FI, deBridge, Aave, Morpho, Hyperliquid, GMX, Derive) rather than an exchange with its own order book.
Ahead on
- Schema & documentation, 82 against 42
- Agent ergonomics, 74 against 50
- Security & auth, 63 against 54
- Payments & pricing, 90 against 60
Also in its favour
- A hosted endpoint, with nothing to install
- Free to start without a card
Watch for
No status page, no SLA and no sandbox or testnet in the reviewed documentation
Best 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.
Ahead on
- Reliability, 50 against 45
- Maintenance & community, 29 against 14
Also in its favour
- Runs on your own machine
Watch 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
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Schema & documentation Bitpont API and MCP +40
Bitpont API and MCP 82
OpenAPI 3.1 file Bitpont Developer API 1.33.0 with 1,149 operations, read once as the reference viewer's source (25). llms.txt, Markdown downloads of the developer pages and Markdown agent guides (10). Every operation has a description and most a summary that states its job, and the guides say which tool to use for which task, though few say when not to (14 of 20). Enums, regex patterns and length limits on addresses and base-unit amounts, required fields; some inputs still allow free-form objects and the MCP operation takes a generic params object (12 of 15). Code examples in the guides and a shared error schema with code, requestId and retryable on 400 to 504 (13 of 15). A versioned changelog, but its entries carry no dates and its latest API version (1.9) doesn't match the file's 1.33.0 (8 of 15). Total 82.
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.
Payments & pricing Bitpont API and MCP +30
Bitpont API and MCP 90
No x402, MPP or L402; a verified trading fee lifting quotas for an hour is not a payment protocol (0). The API is free under published limits and the 0.40% interface fee is published per route without a login (30). Free access with no card (30). An agent starts with no signup by creating a private workspace through the API (30). Total 90.
Crypto.com Exchange API 60
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. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.
Agent ergonomics Bitpont API and MCP +24
Bitpont API and MCP 74
Read for the hosted MCP server, whose catalogue has 1,148 tools (5), with 10 added back for ?product= profiles, bitpont_findTools and bitpont_describeTool and paginated tools/list (15 of 25). Cursors, limits, product and network filters and read batches (18 of 20). Errors carry code, retryable and requestId, and checkInputs returns JSON Pointer paths before any provider is called (19 of 20). Idempotent tasks and stable request IDs, with a documented rule never to repeat an unknown submission; readOnlyHint and destructiveHint unchecked because tools/list was not sent, and the catalogue carries no annotations (14 of 20). A JavaScript client with TypeScript declarations, OpenAI function definitions and a Postman collection, one language (8 of 15). Total 74.
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.
Maintenance & community Crypto.com Exchange API +15
Bitpont API and MCP 14
Read as a closed hosted service. The changelog names versions (Bitpont 5.102.20, API 1.9) with no dates, so the time since the last release can't be established (0) and there are no dated entries (0). A public changelog and a support email; no answer observed and the GitHub organisation is closed to our reader (6 of 15). A first-party JavaScript client and TypeScript declarations as downloads, not on a package registry, and no MCP registry entry (8 of 15). No package or public CI seen (0). The public announcement was on 20 November 2026, so the record is days old. Total 14.
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.
Security & auth Bitpont API and MCP +9
Bitpont API and MCP 63
Keyless use with a client-created workspace secret in a header; optional partner bearer keys with scopes, expiry and revocation, rotated by asking the operator; no key in a URL (22 of 30). Four scopes from read to submit, customer approval of exact trading tickets, and the owner's wallet signs every value transfer (18 of 20). The API returns third-party token and protocol data; the pages say symbols are labels and exact addresses identify assets, but nothing on prompt injection (8 of 15). Per-workspace execution receipts, a monthly settlement report and a usage endpoint (10 of 15). A private reporting email on the security page with no bounty, response time or safe harbour, no security.txt (404) and no certification; the page says Bitpont itself has no independent audit (5 of 20). Total 63.
Crypto.com Exchange API 54
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.
Reliability Crypto.com Exchange API +5
Bitpont API and MCP 45
Read with the hosted lines on the REST API and hosted MCP server. No status page linked from any page read (0). No readable incident history (5). Rate limits with numbers, 30 request units a minute per IP for free access, 60 for partner keys, six items a batch (15). RateLimit and Retry-After headers documented, a retryable flag on every error, and stable request IDs and saved tasks for recovering a write after a lost response (15). No SLA (0). Nothing in the reviewed pages marks the API as beta or preview (10). 0 + 5 + 15 + 15 + 0 + 10 = 45.
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.
Score by category
| Category | Weight | Bitpont API and MCP | Crypto.com Exchange API | Edge |
|---|---|---|---|---|
| Reliability | 16% | 45 | 50 | Crypto.com Exchange API +5 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 82 | 42 | Bitpont API and MCP +40 |
| Agent ergonomics | 13% | 74 | 50 | Bitpont API and MCP +24 |
| Security & auth | 14% | 63 | 54 | Bitpont API and MCP +9 |
| Payments & pricing | 10% | 90 | 60 | Bitpont API and MCP +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 14 | 29 | Crypto.com Exchange API +15 |
| Transparency & trust | 7% | 58 | 55 | Bitpont API and MCP +3 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 62.9/100 | D 49.3/100 |
Facts side by side
| Fact | Bitpont API and MCP | Crypto.com Exchange API |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Bitpont (LiMiT) | Foris DAX Limited (Crypto.com) |
| Hosted endpoint | https://www.bitpont.com/api/v1/mcp | no (local only) |
| Transports | Streamable HTTP | stdio |
| Auth | OAuth or key | API key |
| Pricing | Pay per use | Pay per use |
| x402 | no | no |
| Licence | A proprietary hosted service under the Bitpont Terms of Use (LIMIT SRL). The terms licence the published SDK, declarations, examples and API documentation for building integrations, with no copyright fee; the backend is closed | 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 | 1148 | 95 |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| Last release | none | 2026-06-18 |
| Terms last updated | no date given | couldn't be read |
| Privacy policy last updated | 2026-11-11 | 2025-03-12 |
| Customer content may train models | not found in the text | couldn't be read |
| Terms restrict automated access | not found in the text | couldn't be read |
| Terms restrict benchmarking | not found in the text | couldn't be read |
| Terms or service can change without notice | not found in the text | couldn't be read |
| Arbitration or class-action waiver | not found in the text | couldn't be read |
| Popularity | none | 27 stars, 59 npm/wk |
How the scores have moved
Bitpont API and MCP
No score change since it was listed.
Verdicts
Bitpont API and MCP
Public market reads, quotes and unsigned transaction drafts work without an account, every trade is signed in the owner's wallet, and an OpenAPI 3.1 file covers all 1,148 operations. There is no status page, the changelog carries no dates, and the hosted MCP server exposes the same 1,148 tools, narrowed by product filters and a search tool.
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.
Before you call either
Bitpont API and MCP
- Connect with
?product=swapor another product ID, then callbitpont_findToolsandbitpont_describeToolrather than loading all 1,148 tools - Create a private workspace before the first ticket and store its secret and your
requestId; reuse both to recover an order - Call
bitpont_checkInputsbefore preparing a transaction; amounts are base-unit decimal strings - If a request returns 429, wait for the
Retry-Aftervalue. The free budget is 30 units a minute per IP and a batch costs one unit per item - Never repeat a submission whose outcome is unknown; read the execution receipt first
Crypto.com Exchange API
- Enable only the service groups the task needs with
cdcx mcp config --enable trade,account(the default servesmarketalone), and leave--allow-dangerousoff unless the person asks for withdrawals or cancel-all - Rehearse on
--env uatorcdcx paperfirst; 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.tomlat 0600; there is no key flag, and the key should have no withdrawal permission and an IP allow-list - Pass
acknowledged: trueon mutate tools and--dry-runwhile 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
Questions
Which is better for AI agents, Bitpont API and MCP or Crypto.com Exchange API?
Bitpont API and MCP scores 62.9 (B) on agent readiness against Crypto.com Exchange API's 49.3 (D), and leads in 5 of 7 scored categories. Crypto.com Exchange API leads on reliability and maintenance & community.
Do Bitpont API and MCP and Crypto.com Exchange API need an API key?
Bitpont API and MCP takes an API key or an OAuth sign-in. Crypto.com Exchange API needs an API key.
Can an agent call Bitpont API and MCP and Crypto.com Exchange API without installing anything?
Bitpont API and MCP has a hosted endpoint at https://www.bitpont.com/api/v1/mcp. Crypto.com Exchange API runs on your own machine, with no hosted endpoint listed.
Other comparisons with Bitpont API and MCP or Crypto.com Exchange API
- Bitfinex API vs Bitpont API and MCP
- Bitfinex API vs Crypto.com Exchange API
- Bitget vs Bitpont API and MCP
- Bitget vs Crypto.com Exchange API
- Bithumb Open API vs Bitpont API and MCP
- Bithumb Open API vs Crypto.com Exchange API
- Bitpont API and MCP vs Bitstamp API
- Bitpont API and MCP vs Bybit
- Bitpont API and MCP vs Coinbase Advanced Trade API
- Bitpont API and MCP vs Coinbase MCP server (Coinbase for Agents)
- Bitpont API and MCP vs Deribit
- Bitpont API and MCP vs dYdX
- Bitpont API and MCP vs Gate
- Bitpont API and MCP vs Gemini Exchange API
- Bitpont API and MCP vs HTX trading API
- Bitpont API and MCP vs Hyperliquid
- Bitpont API and MCP vs Kraken API
- Bitpont API and MCP vs KuCoin
- Bitpont API and MCP vs MEXC API
- Bitpont API and MCP vs OKX API
- Bitpont API and MCP vs Uniswap Trading API
- Bitpont API and MCP vs Upbit Open API
- Bitstamp API vs Crypto.com Exchange API
- Bybit vs Crypto.com Exchange API
- Crypto.com Exchange API vs Deribit
- Crypto.com Exchange API vs dYdX
- Crypto.com Exchange API vs Gate
- Crypto.com Exchange API vs Gemini Exchange API
- Crypto.com Exchange API vs HTX trading API
- Crypto.com Exchange API vs Hyperliquid
- Crypto.com Exchange API vs Kraken API
- Crypto.com Exchange API vs KuCoin
- Crypto.com Exchange API vs MEXC API
- Crypto.com Exchange API vs OKX API
- Crypto.com Exchange API vs Uniswap Trading API
- Crypto.com Exchange API vs Upbit Open API
- Binance API vs Bitpont API and MCP
- Binance API vs Crypto.com Exchange API
- Coinbase Advanced Trade API vs Crypto.com Exchange API
- Coinbase MCP server (Coinbase for Agents) vs Crypto.com Exchange API
Machine-readable
- This page as Markdown
/compare/bitpont-vs-crypto-com-exchange.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/bitpont.json·/api/v1/tools/crypto-com-exchange.json - From a terminal
anchor compare bitpont crypto-com-exchange(the CLI) - Over MCP
compare_tools {"a": "bitpont", "b": "crypto-com-exchange"}at/mcp, no key