Head to head · Exchange market data · October 2026 research run

Bitpont API and MCP vs dYdX

dYdX scores 73.3 (BB) on agent readiness against Bitpont API and MCP's 62.9 (B), and leads in 3 of 7 scored categories. Bitpont API and MCP leads on schema & documentation, agent ergonomics and transparency & trust. Both do exchange market data.

Best crypto exchange APIs and MCP servers for AI agents · All 231 exchanges comparisons

Which one, for what

Bitpont API and MCP B

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 58
  • Agent ergonomics, 74 against 66
  • Transparency & trust, 58 against 50

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

dYdX BB

Best for An agent trading perpetuals from its own Cosmos wallet or through a permissioned key on an owner's account, outside the US, Canada and UK.

Ahead on

  • Reliability, 83 against 45
  • Security & auth, 78 against 63
  • Maintenance & community, 83 against 14

Also in its favour

  • Agent-ready, a grade of BB or better
  • Open source

Watch for

No official MCP server; the one registry entry is a third party's analytics server

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.

Maintenance & community dYdX +69

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.

dYdX 83

Read on the clients and the chain. v4-clients was pushed on 29 October 2026 and protocol v9.8.0 shipped on 12 October (30). Protocol v9.7 on 11 September, v9.8.0 on 12 October, v4-client-js tags 3.5.0 and 3.6.0, three or more in 90 days (20). A Discord, a help centre and 36 open issues on v4-clients whose replies couldn't be read (12 of 25). Official SDKs current, the TypeScript client at 3.6.0 and the Python client at 1.1.6 from February 2026 (12 of 15). CI workflows for lint, test, publish and audit, with trusted publishing and provenance on npm (9 of 10). Total 83.

Reliability dYdX +38

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.

dYdX 83

Read with the hosted lines on the indexer API and the chain endpoints the clients submit to. status.dydx.trade is an Atlassian Statuspage with Frontends, dYdX Chain, Indexer, Order Gateway and Client Libraries components and an RSS history (20). From 1 August to 3 November 2026 the feed has eight items, seven scheduled maintenance windows of 29 minutes to 2 hours (indexer on 9 September, 8 and 15 October, protocol v9.7 on 11 September and v9.8.0 on 12 October, WebSocket compression on 26 and 28 October) and one degraded instant-deposit path through an onboarding partner from 24 to 29 September, outside the trading API. Clean or trivial (30). Rate limits documented with numbers for the indexer, the block limits and the public nodes (15). No 429 shape or Retry-After for the indexer; short-term orders expire by goodTilBlock and client IDs let an agent find an order after a timeout (8 of 15). No SLA (0). Mainnet generally available; the Order Entry Gateway is marked testnet-only (10). 20 + 30 + 15 + 8 + 0 + 10 = 83.

Schema & documentation Bitpont API and MCP +24

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.

dYdX 58

No OpenAPI file found for the indexer; the docs publish a types reference of about 200 pages (OrderSide, TimeInForce, OrderStatus and the rest) and the chain's protobuf messages are in the clients (8 of 25). llms.txt and Markdown docs (10). Endpoint pages describe each call and the guides say when to use short-term against long-term orders and the indexer against the node, but descriptions are short (12 of 20). Enums and types on every field in the reference, with pagination and cursor parameters typed (11 of 15). Examples in Python, TypeScript and Rust for each step; errors are described by HTTP status (400 malformed, 404 not found) with no code list (9 of 15). A /v4 path, protocol releases dated on the status page, deprecated rate-limit fields marked, but no API changelog (8 of 15). Total 58.

Security & auth dYdX +15

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.

dYdX 78

Orders are signed by the account key or by a permissioned key the owner adds as an authenticator, limited by message type, subaccount and market with AllOf or AnyOf, and revoked by remove_authenticator; no shared secret and nothing in a URL (28 of 30). A key can be confined to placing and cancelling orders on one subaccount with withdrawals and transfers excluded, though not to a position or order size, and the interface's default API wallet trades all cross-margin pairs (16 of 20). The API returns no untrusted content (10). Every action is a chain transaction and the indexer lists fills, orders and transfers per subaccount, and authenticators can be listed; no per-key log (10 of 15). A Cantina bug bounty up to $1,000,000 sponsored by dYdX Trading Inc. over the protocol, indexer, web client and SDKs, an Informal Systems audit; no security.txt and no certification (14 of 20). Total 78.

Agent ergonomics Bitpont API and MCP +8

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.

dYdX 66

An API, read for response sizing. limit on list endpoints, candles by resolution, sparklines by period; the order book comes whole (16 of 25). limit, page on fills, transfers and funding, and height or time cursors (16 of 20). Indexer errors are a status and a sentence; order rejections come back from the chain as transaction results the clients surface (8 of 20). Unique 32-bit client IDs, goodTilBlock expiry on short-term orders, cancel by order ID; no MCP annotations apply (14 of 20). Few required fields with market parameters fetched for unit conversion, and official clients in TypeScript, Python and Rust (12 of 15). Total 66.

Transparency & trust Bitpont API and MCP +8

Bitpont API and MCP 58

The editorial half. Closed source under readable terms, which licence the published SDK and documentation for integrations (15 of 30). A detailed privacy notice naming the operator, bases, recipients and browser storage, but it promises no deletion period for server logs and support records and no DPA was found (18 of 30). No deprecation policy or dated notices; the changelog only says changes are additive (5 of 20). Integration providers named by function (Jupiter, deBridge, Velocity, Jito, Kamino, KyberSwap, LI.FI, 1inch); the hosting provider and data locations are given only on request (10 of 20). Total 48.

dYdX 50

The editorial half. Clients AGPL-3.0 with a terms-bound use condition, the chain under a custom licence, two terms documents (dYdX Trading Inc.'s v4 terms of 12 March 2026 and dYdX International Ltd's of 6 June 2025) that are clear about who runs nothing (22 of 30). The privacy policy of 6 June 2025 names dYdX International Ltd, keeps technical data until no longer necessary with no periods, and names no subprocessors; nothing covers the unnamed indexer operator (12 of 30). Protocol upgrades and the WebSocket compression change were posted as dated maintenance notices, deprecated rate-limit fields are marked, but no deprecation policy or notice period is stated (10 of 20). The policy says data may be processed in the EEA and elsewhere, with no subprocessor list (6 of 20). Total 50.

Score by category

CategoryWeightBitpont API and MCPdYdXEdge
Reliability16%4583dYdX +38
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8258Bitpont API and MCP +24
Agent ergonomics13%7466Bitpont API and MCP +8
Security & auth14%6378dYdX +15
Payments & pricing10%9090even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%1483dYdX +69
Transparency & trust7%5850Bitpont API and MCP +8
Negative events≤1500
TotalB 62.9/100BB 73.3/100

Facts side by side

FactBitpont API and MCPdYdX
KindHTTP APIHTTP API
VendorBitpont (LiMiT)dYdX Trading Inc.
Hosted endpointhttps://www.bitpont.com/api/v1/mcpno (local only)
TransportsStreamable HTTP
AuthOAuth or keyOAuth or key
PricingPay per usePay per use
x402nono
LicenceA 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 closedThe clients are AGPL-3.0 with a use condition tied to the v4 Terms of Use; the chain software (dydxprotocol/v4-chain) carries a custom licence GitHub cannot classify. The hosted indexer at indexer.dydx.trade and the front end are run by third parties, not dYdX Trading Inc.
Tools exposed11480
Read-only variant documentednono
llms.txtyesyes
Last releasenone2026-10-29
Terms last updatedno date given2026-03-12
Privacy policy last updated2026-11-112025-06-06
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textyes
Popularitynone119 stars, 86k npm/wk

How the scores have moved

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.

dYdX

dYdX gives an agent keyless indexer reads, permissioned keys limited by message type, subaccount and market, a Statuspage with a clean 90 days, published fees and a testnet with a faucet. There is no official MCP server or OpenAPI file, orders are chain transactions signed by the clients, and no one entity operates the hosted endpoints.

Before you call either

Bitpont API and MCP

  1. Connect with ?product=swap or another product ID, then call bitpont_findTools and bitpont_describeTool rather than loading all 1,148 tools
  2. Create a private workspace before the first ticket and store its secret and your requestId; reuse both to recover an order
  3. Call bitpont_checkInputs before preparing a transaction; amounts are base-unit decimal strings
  4. If a request returns 429, wait for the Retry-After value. The free budget is 30 units a minute per IP and a batch costs one unit per item
  5. Never repeat a submission whose outcome is unknown; read the execution receipt first

dYdX

  1. Ask the account owner for an authenticator limited to /dydxprotocol.clob.MsgPlaceOrder and MsgCancelOrder on one subaccount, and keep its private key out of prompts
  2. Set a unique 32-bit clientId on every order and look it up on /v4/orders after a timeout; short-term orders expire with goodTilBlock (at most 20 blocks ahead)
  3. Stay under 2 stateful orders a block and 20 per 100 blocks; failed placements count, so use short-term orders for active trading
  4. Enable permessage-deflate on the indexer WebSocket; since 26 October 2026 connections without compression may be refused with 426
  5. Check /v4/geo and the compliance screen before trading for a person, since the terms exclude the United States, Canada and the United Kingdom

Questions

Which is better for AI agents, Bitpont API and MCP or dYdX?

dYdX scores 73.3 (BB) on agent readiness against Bitpont API and MCP's 62.9 (B), and leads in 3 of 7 scored categories. Bitpont API and MCP leads on schema & documentation, agent ergonomics and transparency & trust.

Do Bitpont API and MCP and dYdX need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call Bitpont API and MCP and dYdX without installing anything?

Bitpont API and MCP has a hosted endpoint at https://www.bitpont.com/api/v1/mcp. No hosted endpoint is listed for dYdX.

Are Bitpont API and MCP and dYdX open source?

No open-source release is listed for Bitpont API and MCP. dYdX is open source (The clients are AGPL-3.0 with a use condition tied to the v4 Terms of Use; the chain software (dydxprotocol/v4-chain) carries a custom licence GitHub cannot classify. The hosted indexer at indexer.dydx.trade and the front end are run by third parties, not dYdX Trading Inc.).

Other comparisons with Bitpont API and MCP or dYdX

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.