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

Bitpont API and MCP vs Bybit

Bitpont API and MCP scores 62.9 (B) on agent readiness against Bybit's 59.8 (C), and leads in 5 of 7 scored categories. Bybit leads on 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

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 73
  • Agent ergonomics, 74 against 66
  • Payments & pricing, 90 against 60
  • Transparency & trust, 58 against 51

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

Bybit C

Best for An agent trading spot, perpetuals, futures and options in a person's Bybit account outside the excluded jurisdictions, with a demo environment to rehearse on.

Ahead on

  • Maintenance & community, 66 against 14

Also in its favour

  • Runs on your own machine

Watch for

No status page, incident history or SLA was found; the terms say the API is not guaranteed to be available

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 Bybit +52

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.

Bybit 66

Read as a hosted service with an open-source MCP server. The MCP package shipped 2.1.26 on 30 October 2026 and the V5 changelog's latest entry is 29 October (30). 31 npm versions since 16 April 2026, 11 of them in the last 90 days, and 24 changelog entries in the same window (20). The trading-mcp repository has 4 open issues and 18 forks; whether issues get answers was not checked, and the API has no public forum we could read (10 of 25). Not in the official MCP registry (0). The package has four dependencies, no install scripts, a publish workflow and no test workflow (6 of 10). 66.

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.

Bybit 60

No machine payment protocol (0). The fee schedule is public without login, with VIP 0 maker and taker rates per product and the tier criteria (20). Reading market data needs no key and the demo environment costs nothing, no card is asked for at sign-up (20). A person must register, pass identity verification and mint the key in a browser (0). 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Schema & documentation Bitpont API and MCP +9

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.

Bybit 73

No OpenAPI or other machine-readable contract for the REST API; the MCP server's 398 tools have zod schemas turned into JSON Schema, so the contract exists for the MCP surface only (12 of 25). No llms.txt; the docs are a public Docusaurus repository (bybit-exchange/docs) whose MDX source an agent can read (5 of 10). The MCP tool descriptions state purpose, rules and an agent hint per tool, and the API reference gives one page per endpoint (15 of 20). Parameters are typed with enums such as category and orderType and required flags (12 of 15). Request and response examples on each endpoint page and an error code page of about 750 codes with text (14 of 15). A dated changelog with 24 entries in the last 90 days, versioned V3 to V5 (15). 73.

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.

Bybit 66

Read for the API with the MCP server beside it. The MCP server has 398 tools in one list with no toolset, module or read-only switch (5 of 25, nothing added back). V5 reads take limit and cursor and category filters (15 of 20). retCode and retMsg on every response with a code list an agent can branch on, though create-order answers before the order is final and the docs say to confirm over WebSocket (14 of 20). orderLinkId makes order retries safe and every MCP tool carries readOnlyHint and destructiveHint (17 of 20). Five required fields on an order, official SDKs in Python, Go, Java and .NET (15). 66.

Transparency & trust Bitpont API and MCP +7

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.

Bybit 51

The editorial half. A closed hosted service. The terms read are the UAE entity's PDF served from bybit.com, clear on API use and availability, but the global terms page renders by script and was not read; the MCP server is MIT (12 of 30). The privacy policy was not read, so data handling is unscored (5 of 30). The changelog dates removals and response changes but gives no notice period or deprecation policy (10 of 20). No subprocessor list or data location statement was read (0 of 20). 27.

Score by category

CategoryWeightBitpont API and MCPBybitEdge
Reliability16%4545even
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8273Bitpont API and MCP +9
Agent ergonomics13%7466Bitpont API and MCP +8
Security & auth14%6360Bitpont API and MCP +3
Payments & pricing10%9060Bitpont API and MCP +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%1466Bybit +52
Transparency & trust7%5851Bitpont API and MCP +7
Negative events≤1500
TotalB 62.9/100C 59.8/100

Facts side by side

FactBitpont API and MCPBybit
KindHTTP APIHTTP API
VendorBitpont (LiMiT)Bybit
Hosted endpointhttps://www.bitpont.com/api/v1/mcpno (local only)
TransportsStreamable HTTPstdio
AuthOAuth or keyAPI 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 closednone
Tools exposed1148398
Read-only variant documentednoyes
llms.txtyesno
Last releasenone2026-10-30
Terms last updatedno date givencouldn't be read
Privacy policy last updated2026-11-11couldn't be read
Customer content may train modelsnot found in the textcouldn't be read
Terms restrict automated accessnot found in the textcouldn't be read
Terms restrict benchmarkingnot found in the textcouldn't be read
Terms or service can change without noticenot found in the textcouldn't be read
Arbitration or class-action waivernot found in the textcouldn't be read
Popularitynone43 stars

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.

Bybit

Bybit publishes per-endpoint rate limits, a demo environment, scoped keys with a read-only flag and IP binding, and an official stdio MCP server whose 398 tools carry read-only and destructive annotations. There is no status page, no OpenAPI file, no SLA, the MCP server has no toolsets, and the global terms and privacy pages are drawn by script.

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

Bybit

  1. Create a key with only the permission groups the task needs, set readOnly for research keys, leave Withdraw off and bind an IP, or the key expires after 90 days
  2. Send a unique orderLinkId on every order and reuse it when amending or cancelling, since create-order is asynchronous and confirmed over WebSocket
  3. Read X-Bapi-Limit-Status before bursts and wait until X-Bapi-Limit-Reset-Timestamp on retCode 10006; on HTTP 403 stop all sessions for at least 10 minutes
  4. Test on api-demo.bybit.com with a demo key from the production account, not on testnet demo mode, which the docs call meaningless
  5. Run the MCP server with BYBIT_TESTNET=true first, and only in a client that shows a per-call approval, because the server has no read-only mode of its own

Questions

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

Bitpont API and MCP scores 62.9 (B) on agent readiness against Bybit's 59.8 (C), and leads in 5 of 7 scored categories. Bybit leads on maintenance & community.

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

Bitpont API and MCP takes an API key or an OAuth sign-in. Bybit needs an API key.

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

Bitpont API and MCP has a hosted endpoint at https://www.bitpont.com/api/v1/mcp. Bybit runs on your own machine, with no hosted endpoint listed.

Other comparisons with Bitpont API and MCP or Bybit

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.