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

Bitpont API and MCP vs Hyperliquid

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

  • Reliability, 45 against 40
  • Schema & documentation, 82 against 42
  • Payments & pricing, 90 against 83
  • Transparency & trust, 58 against 26

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

Hyperliquid D

Best for An agent trading perpetuals or spot on chain from its own wallet with no account, or acting for a master account through an approved API wallet.

Ahead on

  • Maintenance & community, 39 against 14

Watch for

No official MCP server; the 23 registry entries are all third parties, several selling data by x402

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.

Hyperliquid 42

No OpenAPI or other machine-readable contract; request and response shapes are tables and JSON examples in the docs (0 of 25). llms.txt and a Markdown twin of every page by appending .md (10). Each info type and exchange action has a short description of what it does, and the signing page lists common mistakes, but little says when to use one call over another (12 of 20). Fields are one-letter keys (a, b, p, s, r, t, c) with numbers as strings, enums such as tif Alo, Ioc or Gtc, and required fields marked in tables (9 of 15). An example for every call and a list of order and cancel error strings, with no HTTP error table (11 of 15). No API version, no changelog and no dated release notes; deprecated actions such as userDexAbstraction are marked in place (0 of 15). Total 42.

Transparency & trust Bitpont API and MCP +32

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.

Hyperliquid 26

The editorial half. The SDKs are MIT and the node repository Apache-2.0 with a Dockerfile around a binary; the API servers and front end are closed and the terms were unreadable (12 of 30). No privacy policy read and nothing in the docs on data handling (0 of 30). Deprecated actions are marked in the docs without dates or a policy (8 of 20). No subprocessors or data locations (0 of 20). Total 20.

Maintenance & community Hyperliquid +25

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.

Hyperliquid 39

Read as a closed hosted service with open SDKs. The API has no dated changelog, so the last dated change is the Python SDK's 0.24.0 on 4 June 2026, 152 days before this check; the node repository was pushed on 10 August 2026 and the docs describe newer actions (HIP-4 outcome markets, borrow and lend) without dates. Judgement call (10 of 30). No three dated releases in 90 days (0). Support through Discord and the docs' FAQ, 112 open issues on the SDK whose replies couldn't be read (8 of 25). Official Python and Rust SDKs, the Rust one last pushed 21 October 2025; no MCP registry entry (15). CI on Python 3.9 and 3.13 with Poetry, Dependabot badge, a lock file (6 of 10). Total 39.

Payments & pricing Bitpont API and MCP +7

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.

Hyperliquid 83

No machine payment protocol (0). Fees published per tier without login (20). No card anywhere; public info endpoints are free and the testnet faucet gives 1,000 mock USDC, though only to an address that has deposited on mainnet (15 of 20). No signup; an agent with a funded EVM wallet deposits USDC on a bridged chain and trades, subject to the unread terms (20). Total 55. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 55 is 83.

Reliability Bitpont API and MCP +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.

Hyperliquid 40

Read with the hosted lines on the REST API at api.hyperliquid.xyz, the surface an agent calls; the chain behind it is noted under details. No status page found in the docs, on hyperliquid.xyz or at status.hyperliquid.xyz, which did not resolve (0). No readable history (5). Rate limits documented with numbers per IP, per address and per WebSocket connection (15). When limited, an address gets one request every 10 seconds; no 429 shape or Retry-After is documented, but cloid, per-signer nonces, expiresAfter and noop make retries safe (10 of 15). No SLA (0). Mainnet is generally available (10). 0 + 5 + 15 + 10 + 0 + 10 = 40.

Score by category

CategoryWeightBitpont API and MCPHyperliquidEdge
Reliability16%4540Bitpont API and MCP +5
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8242Bitpont API and MCP +40
Agent ergonomics13%7470Bitpont API and MCP +4
Security & auth14%6364Hyperliquid +1
Payments & pricing10%9083Bitpont API and MCP +7
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%1439Hyperliquid +25
Transparency & trust7%5826Bitpont API and MCP +32
Negative events≤1500
TotalB 62.9/100D 53.5/100

Facts side by side

FactBitpont API and MCPHyperliquid
KindHTTP APIHTTP API
VendorBitpont (LiMiT)Hyperliquid Labs
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 exchange runs on the Hyperliquid chain (HyperCore), whose node is distributed as a binary under an Apache-2.0 repository; the Python and Rust SDKs are MIT. The API servers and front end are closed
Tools exposed11480
Read-only variant documentednono
llms.txtyesyes
Last releasenone2026-06-04
Terms last updatedno date givencouldn't be read
Privacy policy last updated2026-11-11no document linked
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
Popularitynone1.9k stars, 167k PyPI/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.

Hyperliquid

Hyperliquid's API needs no signup or key, an approved API wallet can trade but not withdraw, fees and rate limits are published with numbers, and a testnet mirrors mainnet. There is no official MCP server, OpenAPI file, status page, changelog or readable terms, and signing uses two schemes the docs say to leave to an SDK.

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

Hyperliquid

  1. Generate a fresh API wallet, approve it with approveAgent with a name and expiry, sign with it, and query with the master address, never the agent address
  2. Use the Python SDK's sign_l1_action and sign_user_signed_action; mixing the two, field order in msgpack or an uppercase address gives "User or API Wallet ... does not exist"
  3. Set a cloid on every order and read the per-order statuses array; one batch-level error rejects the whole batch
  4. Budget address limits by volume (one action per 1 USDC traded after 10,000); batch orders to lower IP weight, and use WebSocket for data
  5. Arm scheduleCancel before unattended trading so open orders are cancelled if the agent stops

Questions

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

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

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

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

Can an agent call Bitpont API and MCP and Hyperliquid 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 Hyperliquid.

Other comparisons with Bitpont API and MCP or Hyperliquid

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.