# Bitfinex API vs Bitpont API and MCP

> Bitpont scores 62.9 (B) to Bitfinex's 60.9 (C) for exchange market data. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/bitfinex-vs-bitpont
- Markdown: https://www.anchorterminal.com/compare/bitfinex-vs-bitpont.md (~5,150 tokens)
- Slim: https://www.anchorterminal.com/compare/bitfinex-vs-bitpont.min.md (~1,130 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/bitfinex-vs-bitpont.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 <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. 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-20

Bitpont API and MCP scores 62.9 (B) on agent readiness against Bitfinex API's 60.9 (C), and leads in 5 of 7 scored categories. Bitfinex API leads on reliability and maintenance & community. Both do exchange market data.

- Bitfinex API: grade C, 60.9/100, rank #758 of 1563. Markdown https://www.anchorterminal.com/tools/bitfinex.md · JSON https://www.anchorterminal.com/api/v1/tools/bitfinex.json
- Bitpont API and MCP: grade B, 62.9/100, rank #659 of 1563. Markdown https://www.anchorterminal.com/tools/bitpont.md · JSON https://www.anchorterminal.com/api/v1/tools/bitpont.json
- Best crypto exchange APIs and MCP servers for AI agents: https://www.anchorterminal.com/best/crypto-exchanges/index.md
- All 231 exchanges comparisons: https://www.anchorterminal.com/compare/crypto-exchanges/index.md

## Which one, for what

### Bitfinex API (C)

Good for: An agent trading spot, margin or derivatives, or lending on the funding market, with scoped keys, official clients and paper trading.

Ahead on:
- Reliability, 85 against 45
- Maintenance & community, 41 against 14

Watch for: No official MCP server, OpenAPI file or AsyncAPI file; the registry's Bitfinex servers are third parties proxying public market data

### Bitpont API and MCP (B)

Good 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 48
- Agent ergonomics, 74 against 61
- Payments & pricing, 90 against 60
- Transparency & trust, 58 against 49

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


## Why the edge

### Reliability: Bitfinex API +40

- Bitfinex API (85): Read with the hosted lines on the v2 API at api.bitfinex.com. bitfinex.statuspage.io is a Statuspage site with history back to May 2021 (20). Its feed has no entry between 25 March 2026 and 3 November 2026, so the last 90 days are clean on the record; the feed logs platform-wide outages only (a 14-hour maintenance in March 2026, a 3-hour outage in August 2025), so smaller incidents may go unrecorded. Judgement call (30). Rate limits with numbers, 10 to 90 a minute per IP and the WebSocket connection limits (15). `ERR_RATE_LIMIT` and the 60-second block are documented, with no Retry-After; orders take a `cid` but no idempotency key or retry guidance was found (10 of 15). No SLA found (0). Generally available (10). 20 + 30 + 15 + 10 + 0 + 10 = 85.
- 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.

### Schema & documentation: Bitpont API and MCP +34

- Bitfinex API (48): No OpenAPI or AsyncAPI file was found on docs.bitfinex.com, in llms.txt or in the client repositories (0). llms.txt and a .md twin of every docs page (10). Each reference page states the endpoint's purpose and fields, and the introduction says when to use api-pub against api, but nothing says when not to use an endpoint (14 of 20). Responses are positional arrays described in field tables, inputs are typed in prose with some enumerations (wallet names, order types) and required fields marked; the withdrawal CODE field is work in progress (7 of 15). Signed-request recipes in five languages, but authenticated errors are documented as 400 with an empty object and there is no error reference (9 of 15). Version v2 in the path and a dated changelog, whose last entry is October 2024 and whose v1 deprecation has no date (8 of 15). 0 + 10 + 14 + 7 + 9 + 8 = 48.
- 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.

### Payments & pricing: Bitpont API and MCP +30

- Bitfinex API (60): No machine payment protocol (0). The fees page is public without login (20), though it shows zero maker and taker with no tiers or date. The API is free, public endpoints need no account, and paper trading needs 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.
- 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.

### Maintenance & community: Bitfinex API +27

- Bitfinex API (41): Read as a closed service with open clients. The last dated change we could read is bitfinex-api-node 9.1.0 on 18 July 2026, 108 days before the check; the docs changelog stops in October 2024 (10). Not three dated releases in the last 90 days (0). The bitfinexcom organisation pushes often (bfx-report on 3 November 2026) and the clients have issue trackers, but support articles answered 403 and no reply times were read (10 of 25). Official clients current in four languages, Node 9.1.0 of July 2026 and Python 4.0.0 of October 2025; not in the MCP registry (15). The Node client has a dependency history of security fixes (its last GitHub release notes name two) and no CI was read (6 of 10). 10 + 0 + 10 + 15 + 6 = 41.
- 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.

### Agent ergonomics: Bitpont API and MCP +13

- Bitfinex API (61): Graded on the REST API. Limits on trades, candles and book depth, and `pub:list` config endpoints keep responses small, but positional arrays make every field a lookup (14 of 25). `start`, `end`, `limit` and `sort` on history endpoints and per-symbol variants (16 of 20). `ERR_RATE_LIMIT` is actionable; authenticated 400s return `{}` and withdrawal status strings may change, so an agent cannot branch on causes (8 of 20). A client id on orders, order multi-op and cancel-multiple, but no idempotency key and no retry contract (8 of 20). Few required parameters and official clients in Node, Python, Go and Ruby (15). 14 + 16 + 8 + 8 + 15 = 61.
- 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.

### Transparency & trust: Bitpont API and MCP +9

- Bitfinex API (49): The editorial half. A closed service whose Exchange Terms and API Terms of Service loaded only navigation, so the licence terms are unknown; the clients are MIT and Apache-2.0 (8 of 30). The privacy statement loaded only navigation, so retention and data handling are unchecked (0 of 30). The docs say v1 will be deprecated "at some point in the future" with no date, and the Python client's 4.0.0 removed endpoints with a release note (5 of 20). Subprocessors and data locations are in the unread privacy statement (0). 8 + 0 + 5 + 0 = 13.
- 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.

## Score by category

| Category | Weight | Bitfinex API | Bitpont API and MCP | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% | 85 | 45 | Bitfinex API +40 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 48 | 82 | Bitpont API and MCP +34 |
| Agent ergonomics | 13% | 61 | 74 | Bitpont API and MCP +13 |
| Security & auth | 14% | 62 | 63 | Bitpont API and MCP +1 |
| Payments & pricing | 10% | 60 | 90 | Bitpont API and MCP +30 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 41 | 14 | Bitfinex API +27 |
| Transparency & trust | 7% | 49 | 58 | Bitpont API and MCP +9 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **60.9 · C** | **62.9 · B** | |

## Facts side by side

| Fact | Bitfinex API | Bitpont API and MCP |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | iFinex Inc. | Bitpont (LiMiT) |
| Hosted endpoint | no (local only) | `https://www.bitpont.com/api/v1/mcp` |
| Transports |  | Streamable HTTP |
| Auth | API key | OAuth or key |
| Pricing | Pay per use | Pay per use |
| x402 | no | no |
| Licence | Proprietary hosted API under Bitfinex's API Terms of Service, which our reader couldn't load. The official client libraries (Node, Python, Go, Ruby) are MIT or Apache-2.0 | 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 |
| Tools exposed | none | 1148 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-07-18 | none |
| Terms last updated | couldn't be read | no date given |
| Privacy policy last updated | couldn't be read | 2026-11-11 |
| Customer content may train models | couldn't be read | not found in the text |
| Terms restrict automated access | couldn't be read | not found in the text |
| Terms restrict benchmarking | couldn't be read | not found in the text |
| Terms or service can change without notice | couldn't be read | not found in the text |
| Arbitration or class-action waiver | couldn't be read | not found in the text |
| Popularity | 480 stars | none |

## How the scores have moved

### Bitfinex API

- +2.5 on 13 November 2026: checklist

### Bitpont API and MCP

No score change since it was listed.

## Verdicts

**Bitfinex API.** Bitfinex gives an agent scoped keys with a separate withdraw permission, paper-trading sub-accounts on the production API, llms.txt and official clients in four languages. There is no official MCP server, responses are positional arrays with empty error bodies, rate limits run 10 to 90 a minute per IP, and the terms, API terms and privacy statement could not be read.

**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.

## Before you call either

### Bitfinex API

1. Mint a key with read on the scopes the task needs and write only on `orders`; never grant `withdraw` to a trading key, and bind the key to known IPs
2. Use one key per client process, since each key keeps its own strictly increasing nonce and a reused nonce is rejected
3. Rehearse on a paper-trading sub-account with the TEST symbols before touching real balances; the sub-account cannot be converted later
4. Plan requests against the per-endpoint limit of 10 to 90 a minute per IP; `ERR_RATE_LIMIT` blocks the IP for 60 seconds with no Retry-After
5. Map each response by position from the docs' field tables and set a `cid` on orders, because responses are arrays and a 400 carries no reason

### 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

## Questions

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

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

### Do Bitfinex API and Bitpont API and MCP need an API key?

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

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

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


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/bitfinex-vs-bitpont.json, and with the fewest tokens: https://www.anchorterminal.com/compare/bitfinex-vs-bitpont.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "bitfinex", "b": "bitpont"}`. From a terminal: `anchor compare bitfinex bitpont`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/bitfinex.json and https://www.anchorterminal.com/api/v1/tools/bitpont.json

## Other comparisons with Bitfinex API or Bitpont API and MCP

- [Bitfinex API vs Bitget](https://www.anchorterminal.com/compare/bitfinex-vs-bitget.md)
- [Bitfinex API vs Bithumb Open API](https://www.anchorterminal.com/compare/bitfinex-vs-bithumb.md)
- [Bitfinex API vs Bitstamp API](https://www.anchorterminal.com/compare/bitfinex-vs-bitstamp.md)
- [Bitfinex API vs Bybit](https://www.anchorterminal.com/compare/bitfinex-vs-bybit.md)
- [Bitfinex API vs Coinbase Advanced Trade API](https://www.anchorterminal.com/compare/bitfinex-vs-coinbase-advanced-trade.md)
- [Bitfinex API vs Coinbase MCP server (Coinbase for Agents)](https://www.anchorterminal.com/compare/bitfinex-vs-coinbase-mcp.md)
- [Bitfinex API vs Crypto.com Exchange API](https://www.anchorterminal.com/compare/bitfinex-vs-crypto-com-exchange.md)
- [Bitfinex API vs Deribit](https://www.anchorterminal.com/compare/bitfinex-vs-deribit.md)
- [Bitfinex API vs dYdX](https://www.anchorterminal.com/compare/bitfinex-vs-dydx.md)
- [Bitfinex API vs Gate](https://www.anchorterminal.com/compare/bitfinex-vs-gate-io.md)
- [Bitfinex API vs Gemini Exchange API](https://www.anchorterminal.com/compare/bitfinex-vs-gemini-exchange.md)
- [Bitfinex API vs HTX trading API](https://www.anchorterminal.com/compare/bitfinex-vs-htx.md)
- [Bitfinex API vs Hyperliquid](https://www.anchorterminal.com/compare/bitfinex-vs-hyperliquid.md)
- [Bitfinex API vs Kraken API](https://www.anchorterminal.com/compare/bitfinex-vs-kraken.md)
- [Bitfinex API vs KuCoin](https://www.anchorterminal.com/compare/bitfinex-vs-kucoin.md)
- [Bitfinex API vs MEXC API](https://www.anchorterminal.com/compare/bitfinex-vs-mexc.md)
- [Bitfinex API vs OKX API](https://www.anchorterminal.com/compare/bitfinex-vs-okx.md)
- [Bitfinex API vs Uniswap Trading API](https://www.anchorterminal.com/compare/bitfinex-vs-uniswap.md)
- [Bitfinex API vs Upbit Open API](https://www.anchorterminal.com/compare/bitfinex-vs-upbit.md)
- [Bitget vs Bitpont API and MCP](https://www.anchorterminal.com/compare/bitget-vs-bitpont.md)
- [Bithumb Open API vs Bitpont API and MCP](https://www.anchorterminal.com/compare/bithumb-vs-bitpont.md)
- [Bitpont API and MCP vs Bitstamp API](https://www.anchorterminal.com/compare/bitpont-vs-bitstamp.md)
- [Bitpont API and MCP vs Bybit](https://www.anchorterminal.com/compare/bitpont-vs-bybit.md)
- [Bitpont API and MCP vs Coinbase Advanced Trade API](https://www.anchorterminal.com/compare/bitpont-vs-coinbase-advanced-trade.md)
- [Bitpont API and MCP vs Coinbase MCP server (Coinbase for Agents)](https://www.anchorterminal.com/compare/bitpont-vs-coinbase-mcp.md)
- [Bitpont API and MCP vs Crypto.com Exchange API](https://www.anchorterminal.com/compare/bitpont-vs-crypto-com-exchange.md)
- [Bitpont API and MCP vs Deribit](https://www.anchorterminal.com/compare/bitpont-vs-deribit.md)
- [Bitpont API and MCP vs dYdX](https://www.anchorterminal.com/compare/bitpont-vs-dydx.md)
- [Bitpont API and MCP vs Gate](https://www.anchorterminal.com/compare/bitpont-vs-gate-io.md)
- [Bitpont API and MCP vs Gemini Exchange API](https://www.anchorterminal.com/compare/bitpont-vs-gemini-exchange.md)
- [Bitpont API and MCP vs HTX trading API](https://www.anchorterminal.com/compare/bitpont-vs-htx.md)
- [Bitpont API and MCP vs Hyperliquid](https://www.anchorterminal.com/compare/bitpont-vs-hyperliquid.md)
- [Bitpont API and MCP vs Kraken API](https://www.anchorterminal.com/compare/bitpont-vs-kraken.md)
- [Bitpont API and MCP vs KuCoin](https://www.anchorterminal.com/compare/bitpont-vs-kucoin.md)
- [Bitpont API and MCP vs MEXC API](https://www.anchorterminal.com/compare/bitpont-vs-mexc.md)
- [Bitpont API and MCP vs OKX API](https://www.anchorterminal.com/compare/bitpont-vs-okx.md)
- [Bitpont API and MCP vs Uniswap Trading API](https://www.anchorterminal.com/compare/bitpont-vs-uniswap.md)
- [Bitpont API and MCP vs Upbit Open API](https://www.anchorterminal.com/compare/bitpont-vs-upbit.md)
- [Binance API vs Bitfinex API](https://www.anchorterminal.com/compare/binance-vs-bitfinex.md)
- [Binance API vs Bitpont API and MCP](https://www.anchorterminal.com/compare/binance-vs-bitpont.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
