{ "data": { "similar": [ { "grade": "BB", "json": "https://www.anchorterminal.com/tools/gemini-exchange.json", "name": "Gemini Exchange API", "score": 74.6, "shared": [ "exchange.market-data", "exchange.spot-trading", "exchange.derivatives", "exchange.balances", "exchange.transfers", "exchange.staking", "market.crypto" ], "slug": "gemini-exchange" }, { "grade": "BB", "json": "https://www.anchorterminal.com/tools/kraken.json", "name": "Kraken API", "score": 71, "shared": [ "exchange.spot-trading", "exchange.market-data", "exchange.derivatives", "exchange.balances", "exchange.transfers", "exchange.staking", "market.crypto" ], "slug": "kraken" }, { "grade": "B", "json": "https://www.anchorterminal.com/tools/okx.json", "name": "OKX API", "score": 64.3, "shared": [ "exchange.spot-trading", "exchange.market-data", "exchange.derivatives", "exchange.balances", "exchange.transfers", "exchange.staking", "market.crypto" ], "slug": "okx" }, { "grade": "B", "json": "https://www.anchorterminal.com/tools/binance.json", "name": "Binance API", "score": 63.2, "shared": [ "exchange.spot-trading", "exchange.market-data", "exchange.derivatives", "exchange.balances", "exchange.transfers", "exchange.staking", "market.crypto" ], "slug": "binance" }, { "grade": "C", "json": "https://www.anchorterminal.com/tools/bybit.json", "name": "Bybit", "score": 57.3, "shared": [ "exchange.market-data", "exchange.spot-trading", "exchange.derivatives", "exchange.balances", "exchange.transfers", "exchange.staking", "market.crypto" ], "slug": "bybit" }, { "grade": "C", "json": "https://www.anchorterminal.com/tools/gate-io.json", "name": "Gate", "score": 56.4, "shared": [ "exchange.market-data", "exchange.spot-trading", "exchange.derivatives", "exchange.balances", "exchange.transfers", "exchange.staking", "market.crypto" ], "slug": "gate-io" } ], "tool": { "slug": "bitfinex", "name": "Bitfinex API", "vendor": "iFinex Inc.", "vendorUrl": "https://www.bitfinex.com", "kind": "http-api", "category": "crypto-exchanges", "summary": "Bitfinex's v2 API for spot, margin, derivatives and peer-to-peer funding, with balances, deposits and withdrawals, through REST and WebSocket with scoped API keys, paper-trading sub-accounts and official Node, Python, Go and Ruby clients.", "url": "https://www.anchorterminal.com/tools/bitfinex", "markdownUrl": "https://www.anchorterminal.com/tools/bitfinex.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/bitfinex.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/bitfinex.json", "dns": "bitfinex.grade.anchorterminal.com", "repo": "https://github.com/bitfinexcom/bitfinex-api-node", "license": "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", "transports": [], "packages": [ { "registry": "npm", "name": "bitfinex-api-node" }, { "registry": "pypi", "name": "bitfinex-api-py" } ], "auth": "api-key", "authNotes": "API key and secret made at setting.bitfinex.com/api after a browser signup, with 2FA and an email confirmation, shown once. Each key carries read and write permissions per scope (account, history, orders, positions, funding, settings, wallets, withdraw, ui_withdraw, bfxpay), readable back from `POST /v2/auth/r/permissions`, and keys are revoked from the same page; a strictly increasing nonce per key. Bitfinex's support article on keys says a key can be bound to up to 20 IP addresses, per the search result's text, since the article itself answered 403 (https://docs.bitfinex.com/docs/requirements-and-limitations, https://docs.bitfinex.com/reference/key-permissions, checked 2026-11-03).", "pricing": "usage", "pricingNotes": "The API itself costs nothing. The fees page read on 3 November 2026 shows zero maker and zero taker fees for exchange, margin and derivatives order execution with no volume tiers, margin funding lender fees of 15% of interest (18% when the offer is hidden) with up to 5% off for LEO holders, a 5% takeover fee, free crypto deposits and bank wire 0.1% (minimum 60 for deposits, 100 for withdrawals, USD or EUR). Paper trading on a sub-account needs no money (https://www.bitfinex.com/fees, checked 2026-11-03).", "priceSummary": "0% fee", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the API docs, llms.txt or fees page (checked 2026-11-03). Fees are taken from the account; onboarding is a browser signup.", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 480, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://docs.bitfinex.com", "llmsTxt": "https://docs.bitfinex.com/llms.txt", "capabilities": [ "exchange.market-data", "exchange.spot-trading", "exchange.derivatives", "exchange.balances", "exchange.transfers", "exchange.staking", "market.crypto" ], "tags": [ "official", "hosted", "api-key", "llms-txt", "sandbox", "status-page", "javascript", "python", "go", "ruby", "usage-priced" ], "lastRelease": "2026-07-18", "graded": true, "anchor": { "graded": true, "score": 58.4, "grade": "C", "agentReady": false, "rank": 687, "ranked": true, "rankOf": 1349, "categoryRank": 10, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 61, "maintenance": 41, "payments": 40, "reliability": 85, "schema": 48, "security": 62, "transparency": 49 }, "pending": [ "performance", "tasks" ], "breakdown": [ { "key": "reliability", "name": "Reliability", "weight": 16, "effectiveWeight": 20, "score": 85, "points": 17, "reason": "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.", "checked": "2026-11-03" }, { "key": "performance", "name": "Performance", "weight": 10, "effectiveWeight": 0, "pending": true, "points": 0, "reason": "Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes." }, { "key": "schema", "name": "Schema \u0026 documentation", "weight": 13, "effectiveWeight": 16.25, "score": 48, "points": 7.8, "reason": "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.", "checked": "2026-11-03" }, { "key": "ergonomics", "name": "Agent ergonomics", "weight": 13, "effectiveWeight": 16.25, "score": 61, "points": 9.91, "reason": "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.", "checked": "2026-11-03" }, { "key": "security", "name": "Security \u0026 auth", "weight": 14, "effectiveWeight": 17.5, "score": 62, "points": 10.85, "reason": "Revocable keys with per-scope read and write flags, a permissions endpoint, 2FA and email confirmation at creation, strictly increasing nonces, and IP binding to 20 addresses per the support article's search text (the article answered 403); no key expiry (24 of 30). `withdraw` and `ui_withdraw` are separate scopes and read-only keys are possible, but the support text says keys from email-and-password accounts start with every permission enabled and no confirmation step is documented for API withdrawals (14 of 20). The API returns exchange data, not third-party text (10). Login history and an account changelog (audit) endpoint are documented (10 of 15). No security.txt, no readable disclosure policy and no certification page readable (4 of 20). 24 + 14 + 10 + 10 + 4 = 62.", "checked": "2026-11-03" }, { "key": "payments", "name": "Payments \u0026 pricing", "weight": 10, "effectiveWeight": 12.5, "score": 40, "points": 5, "reason": "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.", "checked": "2026-11-03" }, { "key": "tasks", "name": "Task success", "weight": 10, "effectiveWeight": 0, "pending": true, "points": 0, "reason": "Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored." }, { "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7, "effectiveWeight": 8.75, "score": 41, "points": 3.59, "reason": "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.", "checked": "2026-11-03" }, { "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7, "effectiveWeight": 8.75, "score": 49, "points": 4.29, "note": "editorial 13, provenance 85", "reason": "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.", "checked": "2026-11-03" } ], "assessment": { "date": "2026-11-03", "basis": "public evidence", "confidence": "low", "notes": { "ergonomics": "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.", "maintenance": "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.", "payments": "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.", "reliability": "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.", "schema": "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.", "security": "Revocable keys with per-scope read and write flags, a permissions endpoint, 2FA and email confirmation at creation, strictly increasing nonces, and IP binding to 20 addresses per the support article's search text (the article answered 403); no key expiry (24 of 30). `withdraw` and `ui_withdraw` are separate scopes and read-only keys are possible, but the support text says keys from email-and-password accounts start with every permission enabled and no confirmation step is documented for API withdrawals (14 of 20). The API returns exchange data, not third-party text (10). Login history and an account changelog (audit) endpoint are documented (10 of 15). No security.txt, no readable disclosure policy and no certification page readable (4 of 20). 24 + 14 + 10 + 10 + 4 = 62.", "transparency": "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." }, "sources": [ { "what": "robots.txt (www.bitfinex.com, docs.bitfinex.com, bitfinex.statuspage.io, support.bitfinex.com)", "url": "https://www.bitfinex.com/robots.txt", "seen": "2026-11-03" }, { "what": "docs llms.txt", "url": "https://docs.bitfinex.com/llms.txt", "seen": "2026-11-03" }, { "what": "docs introduction (hosts, versions, paper-trading symbol, API terms link)", "url": "https://docs.bitfinex.com/docs/introduction.md", "seen": "2026-11-03" }, { "what": "requirements and limitations (rate limits, nonces, key creation)", "url": "https://docs.bitfinex.com/docs/requirements-and-limitations.md", "seen": "2026-11-03" }, { "what": "authenticated REST overview", "url": "https://docs.bitfinex.com/docs/rest-auth.md", "seen": "2026-11-03" }, { "what": "key permissions endpoint", "url": "https://docs.bitfinex.com/reference/key-permissions.md", "seen": "2026-11-03" }, { "what": "withdrawal endpoint", "url": "https://docs.bitfinex.com/reference/rest-auth-withdraw.md", "seen": "2026-11-03" }, { "what": "docs changelog", "url": "https://docs.bitfinex.com/docs/changelog.md", "seen": "2026-11-03" }, { "what": "fees page", "url": "https://www.bitfinex.com/fees", "seen": "2026-11-03" }, { "what": "about page (leadership, support links)", "url": "https://www.bitfinex.com/about", "seen": "2026-11-03" }, { "what": "API Terms of Service (loaded only navigation)", "url": "https://www.bitfinex.com/legal/general/api-terms/", "seen": "2026-11-03" }, { "what": "Exchange Terms (loaded only navigation)", "url": "https://www.bitfinex.com/legal/exchange/terms/", "seen": "2026-11-03" }, { "what": "privacy statement (loaded only navigation)", "url": "https://www.bitfinex.com/legal/privacy/", "seen": "2026-11-03" }, { "what": "site sitemap (legal page list)", "url": "https://www.bitfinex.com/sitemap.xml", "seen": "2026-11-03" }, { "what": "status history feed", "url": "https://bitfinex.statuspage.io/history.atom", "seen": "2026-11-03" }, { "what": "security.txt (404)", "url": "https://www.bitfinex.com/.well-known/security.txt", "seen": "2026-11-03" }, { "what": "official MCP registry search", "url": "https://registry.modelcontextprotocol.io/v0/servers?search=bitfinex", "seen": "2026-11-03" }, { "what": "bitfinexcom GitHub organisation repositories and mcp search", "url": "https://api.github.com/orgs/bitfinexcom/repos?per_page=100\u0026sort=updated", "seen": "2026-11-03" }, { "what": "npm bitfinex-api-node (versions and times)", "url": "https://registry.npmjs.org/bitfinex-api-node", "seen": "2026-11-03" }, { "what": "bitfinex-api-py releases and metadata", "url": "https://api.github.com/repos/bitfinexcom/bitfinex-api-py/releases?per_page=5", "seen": "2026-11-03" }, { "what": "support article on paper trading (answered 403; facts from the search result's text only)", "url": "https://support.bitfinex.com/hc/en-us/articles/900001525006-Paper-Trading", "seen": "2026-11-03" }, { "what": "support article on API keys (answered 403; facts from the search result's text only)", "url": "https://support.bitfinex.com/hc/en-us/articles/115003363429-How-to-create-and-revoke-a-Bitfinex-API-Key", "seen": "2026-11-03" }, { "what": "RDAP for bitfinex.com", "url": "https://rdap.verisign.com/com/v1/domain/bitfinex.com", "seen": "2026-11-03" } ], "openQuestions": [ "Kind http-api. docs.bitfinex.com leads with REST and WebSocket; no MCP server or OpenAPI file exists.", "No MCP server was found, looking in docs.bitfinex.com, llms.txt, the bitfinexcom GitHub organisation (a search for mcp returned nothing) and the official MCP registry. The best-known third-party server is pipeworx-io's remote `io.github.pipeworx-io/bitfinex`, public market data only, not Bitfinex's.", "unchecked: the Exchange Terms, API Terms of Service, privacy statement and trading rulebook (script-drawn, loaded only navigation), and every support.bitfinex.com article (403), so the contracting entity, the clauses on API use and bots, retention, subprocessors and the restricted-country list are unconfirmed. Transparency scores low for that reason.", "The IP binding (20 addresses), default permissions and paper-trading limits are recorded from the text of search results that quoted Bitfinex's own support articles; the articles themselves answered 403. They are not weighted beyond a few points in security and sandbox.", "The fees page shows zero maker and zero taker fees for exchange, margin and derivatives with no tiers, date or promotion notice. Recorded as read; a person should check whether a dated promotion or a tiered schedule sits behind it.", "firstReleased is 28 March 2017, the docs changelog's first entry (API v2, released 1 April 2017 per the page); Bitfinex itself is older. lastRelease is 18 July 2026, bitfinex-api-node 9.1.0.", "unchecked: FIX (not in the docs), Retry-After headers, CI on the client repositories, GitHub issue reply times, and whether the status page records partial API incidents.", "Our own products. It doesn't do LocalGhost's or letme's job; it trades one exchange account." ] }, "negative": 0, "verdict": "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.", "bestFor": "An agent trading spot, margin or derivatives, or lending on the funding market, with scoped keys, official clients and paper trading.", "strengths": [ "Per-scope read and write permissions on each key, including a separate `withdraw` scope, readable back from the permissions endpoint", "Paper trading on a sub-account against test symbols on the same production API, with no money at risk", "llms.txt with a Markdown twin of every docs page, and official Node, Python, Go and Ruby clients", "Rate limits, connection limits and the `ERR_RATE_LIMIT` response documented with numbers", "A Statuspage history going back to 2021 and a fees page without login" ], "weaknesses": [ "No official MCP server, OpenAPI file or AsyncAPI file; the registry's Bitfinex servers are third parties proxying public market data", "Responses are positional arrays and authenticated errors answer 400 with an empty object, so an agent must map indexes and guess causes", "Rate limits of 10 to 90 requests a minute per IP with a 60-second block and no Retry-After", "The Exchange Terms, API Terms of Service, privacy statement and support articles could not be read, so the bot clauses, retention and restricted countries are unchecked", "The docs changelog stops at October 2024 and the v1 deprecation has no date" ], "agentNotes": [ "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", "Use one key per client process, since each key keeps its own strictly increasing nonce and a reused nonce is rejected", "Rehearse on a paper-trading sub-account with the TEST symbols before touching real balances; the sub-account cannot be converted later", "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", "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" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "low", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 58.4 } ], "editorialScores": { "ergonomics": 61, "maintenance": 41, "payments": 40, "reliability": 85, "schema": 48, "security": 62, "transparency": 13 }, "provenanceScore": 85, "checked": { "categories": { "ergonomics": "2026-11-03", "maintenance": "2026-11-03", "payments": "2026-11-03", "reliability": "2026-11-03", "schema": "2026-11-03", "security": "2026-11-03", "transparency": "2026-11-03" }, "last": "2026-11-03", "oldest": "2026-11-03", "stale": false, "staleAfterDays": 90 }, "scoreHistory": [ { "date": "2026-11-03", "grade": "C", "kind": "listed", "method": "0.7", "score": 58.4 } ] }, "connect": { "install": "npm install bitfinex-api-node", "http": "curl https://api-pub.bitfinex.com/v2/ticker/tBTCUSD" }, "letme": { "capability": "https://letme.dev/exchange.market-data", "tool": "https://letme.dev/bitfinex" }, "notable": [ "No official MCP server. The docs and llms.txt do not mention MCP or agents, a GitHub search of the bitfinexcom organisation for mcp returned nothing, and the official MCP registry holds only third-party servers, `io.github.pipeworx-io/bitfinex` (remote at gateway.pipeworx.io/bitfinex/mcp, v2 public endpoints, 0.2.1 on 30 October 2026) and `io.github.mrfentmen/bitfinex-mcp` (npm, prices, 1.0.1 on 21 September 2026), neither Bitfinex's (https://registry.modelcontextprotocol.io/v0/servers?search=bitfinex)", "Rate limits are 10 to 90 requests a minute per IP depending on the endpoint, answered with `{\"error\": \"ERR_RATE_LIMIT\"}` and a 60-second IP block; WebSocket at most 5 authenticated connections per 15 seconds on api.bitfinex.com, 20 a minute on api-pub.bitfinex.com and 25 channels per connection (https://docs.bitfinex.com/docs/requirements-and-limitations)", "Key permissions are per scope with read and write flags, `withdraw` among them, and `POST /v2/auth/r/permissions` returns the current key's scopes (https://docs.bitfinex.com/reference/key-permissions)", "Paper trading runs on a sub-account against test symbols such as tTESTBTCF0:TESTUSDTF0 on the production API, per the docs introduction; the support article says paper balances refill to $1,000,000 equivalent per sub-account and that a paper sub-account cannot become a regular one, per the search result's text, since support.bitfinex.com answered 403 (https://docs.bitfinex.com/docs/introduction)", "Responses are positional arrays, not keyed objects, and an authenticated error answers 400 with an empty `{}`; the withdrawal endpoint's status `CODE` field is marked work in progress (https://docs.bitfinex.com/reference/rest-auth-withdraw)", "The docs changelog has seven entries, from 28 March 2017 (API v2) to 16 October 2024 (VASP endpoint), and says v1 \"will become deprecated at some point in the future\" with no date (https://docs.bitfinex.com/docs/changelog)", "Official clients are bitfinex-api-node 9.1.0 on npm (18 July 2026, 480 stars), bitfinex-api-py 4.0.0 (18 October 2025, dropped the Pulse and Pay endpoints), bitfinex-api-go (pushed 18 October 2025) and bitfinex-api-rb (21 October 2025) (https://registry.npmjs.org/bitfinex-api-node, https://api.github.com/repos/bitfinexcom/bitfinex-api-py/releases)", "bitfinex.statuspage.io's history feed has no entry between 25 March 2026 (a 14-hour platform maintenance) and 3 November 2026, after platform outages of about 3 hours on 14 August 2025 and 12 hours on 19 April 2025; the feed records platform-wide events only (https://bitfinex.statuspage.io/history.atom)", "The fees page shows zero maker and taker fees for exchange, margin and derivatives order execution with no tiers and no effective date, which reads as a promotion; the page carries only a copyright line (https://www.bitfinex.com/fees)", "The Exchange Terms, API Terms of Service, privacy statement and trading rulebook pages draw their text by script and loaded only navigation for our reader, and support.bitfinex.com answered 403, so the legal entity in the terms, the clauses on API use and bots, retention and the restricted-country list are unchecked; the footer names iFinex Inc. (https://www.bitfinex.com/legal/general/api-terms/)" ], "area": "payments", "details": [ { "label": "Surface listed", "value": "The hosted v2 API at api.bitfinex.com and api-pub.bitfinex.com as an agent calls it, read from docs.bitfinex.com and its llms.txt, bitfinex.com's fees and about pages, bitfinex.statuspage.io, the official MCP registry, the bitfinexcom GitHub organisation, npm and RDAP on 3 November 2026. The legal pages loaded only navigation and support.bitfinex.com answered 403. No account, key or order" }, { "label": "MCP server", "value": "None found. Looked in docs.bitfinex.com and its llms.txt, the bitfinexcom GitHub organisation (a search for mcp returned nothing) and the official MCP registry. Third-party only, pipeworx-io's remote `io.github.pipeworx-io/bitfinex` and mrfentmen's `bitfinex-mcp`, both public market data, neither Bitfinex's" }, { "label": "Key permissions", "value": "Read and write flags per scope (account, history, orders, positions, funding, settings, wallets, withdraw, ui_withdraw and bfxpay); `POST /v2/auth/r/permissions` returns the key's scopes. Keys are made with 2FA and email confirmation, shown once, and revoked from the API page. IP binding to up to 20 addresses per the support article's search text (the article answered 403). Default permissions on keys made from an email-and-password account are all enabled per the same text" }, { "label": "Rate limits", "value": "REST 10 to 90 requests a minute per IP by endpoint, `{\"error\": \"ERR_RATE_LIMIT\"}` and a 60-second IP block; the permissions endpoint 90 a minute. WebSocket 5 authenticated connections per 15 seconds, 20 public connections a minute, 25 channels per connection, with 15-second and 60-second blocks. No Retry-After" }, { "label": "Testnet or sandbox", "value": "Paper trading on a sub-account using TEST symbols (tTESTBTCF0:TESTUSDTF0 named in the docs) on the production API; no separate sandbox host" }, { "label": "Countries served", "value": "Unchecked. The Exchange Terms, which carry the prohibited-jurisdiction list, loaded only navigation, and the support article on restrictions answered 403. The only first-hand list we could read is for Bitfinex Securities, a separate product" }, { "label": "Fees at the lowest tier", "value": "Zero maker and zero taker on exchange, margin and derivatives order execution per the fees page on 3 November 2026, with no volume tiers and no date; margin funding lenders pay 15% of interest (18% when the offer is hidden), LEO holders up to 5% less; bank wires 0.1%" }, { "label": "FIX and WebSocket", "value": "WebSocket v2 at wss://api.bitfinex.com (authenticated) and wss://api-pub.bitfinex.com (public) with ticker, trades, books, raw books, candles and status channels, account channels and order inputs. No FIX documentation on docs.bitfinex.com; llms.txt lists none" }, { "label": "Terms on automated trading", "value": "Unchecked. The API Terms of Service and Exchange Terms pages draw their text by script and loaded only navigation. The docs say every API use is subject to the API Terms of Service and that keys are used at the holder's own risk" }, { "label": "Errors and idempotency", "value": "Authenticated endpoints answer 400 with `{}`; the rate limit answers `{\"error\": \"ERR_RATE_LIMIT\"}`; withdrawals return a notification array with STATUS SUCCESS, ERROR or FAILURE and a CODE marked work in progress. Orders take a client id (`cid`); no idempotency key is documented" }, { "label": "SDKs", "value": "bitfinex-api-node 9.1.0 (18 July 2026, MIT, 480 stars), bitfinex-api-py 4.0.0 (18 October 2025, Apache-2.0, 219 stars), bitfinex-api-go (pushed 18 October 2025, MIT) and bitfinex-api-rb (21 October 2025, MIT), all in github.com/bitfinexcom" }, { "label": "Legal entity", "value": "iFinex Inc., from the copyright line on bitfinex.com; the Exchange Terms, which would state its jurisdiction and role, loaded only navigation. Bitfinex Securities Ltd and Bitfinex Securities El Salvador S.A. de C.V. run the securities platform" } ], "unitPrices": [ { "item": "Exchange maker fee, as shown on 3 November 2026", "unit": "pct", "usd": 0, "note": "no tiers or date shown; reads as a promotion" }, { "item": "Exchange taker fee, as shown on 3 November 2026", "unit": "pct", "usd": 0, "note": "no tiers or date shown; reads as a promotion" }, { "item": "Margin funding lender fee on interest earned", "unit": "pct", "usd": 15, "note": "18% when the offer is hidden, up to 5% off for LEO holders" } ], "provenance": { "legalEntity": "iFinex Inc.", "domain": "bitfinex.com", "domainRegistered": "2012-10-11", "endpointOnVendorDomain": true, "terms": "https://www.bitfinex.com/legal/exchange/terms/", "privacy": "https://www.bitfinex.com/legal/privacy/", "statusPage": "https://bitfinex.statuspage.io", "changelog": "https://docs.bitfinex.com/docs/changelog", "securityTxt": "none", "checked": "2026-11-03", "notes": [ "iFinex Inc. is named only in the copyright line of bitfinex.com; the Exchange Terms, API Terms of Service and privacy statement pages draw their text by script and loaded only navigation, so the contracting entity and its jurisdiction are unconfirmed.", "RDAP gives bitfinex.com a registration date of 11 October 2012.", "https://www.bitfinex.com/.well-known/security.txt returns 404.", "www.bitfinex.com/robots.txt allows the pages read; docs.bitfinex.com allows all and points to llms.txt; bitfinex.statuspage.io disallows /api/ and /embed/, so the history feed was read. support.bitfinex.com's robots.txt allows articles but the articles answered 403.", "The docs changelog's latest entry is 16 October 2024; the API clients carry the recent releases." ], "score": 85, "checks": [ { "check": "Legal entity named", "value": "iFinex Inc.", "points": 20, "max": 20, "state": "ok" }, { "check": "Domain age", "value": "bitfinex.com, registered 2012-10-11 (14 years)", "points": 15, "max": 15, "state": "ok" }, { "check": "Endpoint on the vendor's domain", "value": "bitfinex.com", "points": 15, "max": 15, "state": "ok" }, { "check": "Terms of service", "value": "published, but our reader couldn't read it", "points": 7, "max": 10, "state": "part" }, { "check": "Privacy policy", "value": "published, but our reader couldn't read it", "points": 7, "max": 10, "state": "part" }, { "check": "Status page", "value": "bitfinex.statuspage.io", "points": 10, "max": 10, "state": "ok" }, { "check": "Changelog", "value": "published", "points": 10, "max": 10, "state": "ok" }, { "check": "security.txt", "value": "not found", "points": 0, "max": 10, "state": "no" }, { "check": "People named", "value": "4 named with their role, none with a public profile", "points": 7, "max": 10, "state": "part" }, { "check": "Support route", "value": "help pages, a community", "points": 5, "max": 5, "state": "ok" } ], "policies": [ { "kind": "terms", "url": "https://www.bitfinex.com/legal/exchange/terms/", "state": "unreadable", "reason": "the page has only its navigation and a copyright line without a browser, so the document is drawn by script", "readAt": "2026-11-03", "points": 7, "max": 10 }, { "kind": "privacy", "url": "https://www.bitfinex.com/legal/privacy/", "state": "unreadable", "reason": "the page has only its navigation and a copyright line without a browser, so the document is drawn by script", "readAt": "2026-11-03", "points": 7, "max": 10 } ] }, "humans": { "slug": "bitfinex", "checked": "2026-11-03", "company": "Bitfinex", "people": [ { "name": "JL van der Velde", "role": "Chief Executive Officer, Bitfinex", "page": "/people/jl-van-der-velde/" }, { "name": "Paolo Ardoino", "role": "Chief Technology Officer, Bitfinex", "page": "/people/paolo-ardoino/" }, { "name": "Claudia Lagorio", "role": "Chief Operating Officer, Bitfinex", "page": "/people/claudia-lagorio/" }, { "name": "Giancarlo Devasini", "role": "Chief Financial Officer, Bitfinex", "page": "/people/giancarlo-devasini/" } ], "peopleNote": "Bitfinex's about page, read 3 November 2026, lists JL van der Velde (Chief Executive Officer), Claudia Lagorio (Chief Operating Officer), Paolo Ardoino (Chief Technology Officer) and Giancarlo Devasini (Chief Financial Officer), with no founders named and no personal accounts linked. The footer names iFinex Inc. as the copyright holder; the Exchange Terms, which would state the operating entity and its jurisdiction, loaded only navigation, and support.bitfinex.com answered 403, so ownership is recorded as unknown rather than private. Investors were looked for on the about page, the press page link and the legal index; nothing names backers, and no outside search was made.", "companySocial": { "linkedin": "https://www.linkedin.com/company/bitfinex/", "x": "https://x.com/bitfinex", "github": "https://github.com/bitfinexcom" }, "support": { "urls": [ "https://support.bitfinex.com/hc/en-us", "https://cs.bitfinex.com", "https://bitfinex.statuspage.io" ], "community": [ { "label": "Bitfinex Telegram", "url": "https://t.me/bitfinex", "kind": "telegram" }, { "label": "bitfinex-api-node issues", "url": "https://github.com/bitfinexcom/bitfinex-api-node/issues", "kind": "github" } ], "contactUrls": [ "https://cs.bitfinex.com" ] }, "sources": [ "https://www.bitfinex.com/about", "https://www.bitfinex.com/fees", "https://www.bitfinex.com/sitemap.xml", "https://docs.bitfinex.com/docs/introduction.md", "https://api.github.com/orgs/bitfinexcom/repos?per_page=100\u0026sort=updated" ], "ownership": { "status": "unknown", "checked": "2026-11-03", "sources": [ "https://www.bitfinex.com/about" ] } }, "pageJsonUrl": "https://www.anchorterminal.com/tools/bitfinex.json", "live": { "slug": "bitfinex", "vendorStatus": { "page": "https://bitfinex.statuspage.io", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-04T19:31:04.844086591Z" }, "securityTxt": { "url": "https://bitfinex.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-04T15:53:26.210646703Z" }, "updatedAt": "2026-11-04T19:31:04.844086591Z" } }, "verify": { "accepts": "a page on bitfinex.com or one of its subdomains, or the README at the root of github.com/bitfinexcom/bitfinex-api-node", "badgeUrl": "https://www.anchorterminal.com/badges/bitfinex.svg", "body": { "slug": "bitfinex", "url": "the page with the badge or the link" }, "docs": "https://www.anchorterminal.com/builders/#verify", "effect": "none, it never changes a grade, rank or review", "endpoint": "https://www.anchorterminal.com/api/v1/verify", "listingUrl": "https://www.anchorterminal.com/tools/bitfinex", "mcpTool": "verify_listing", "recheck": "weekly; two failed checks in a row and it lapses, a later pass restores it", "snippets": { "html": "\u003ca href=\"https://www.anchorterminal.com/tools/bitfinex\"\u003e\u003cimg src=\"https://www.anchorterminal.com/badges/bitfinex.svg\" alt=\"Bitfinex API on Anchor Terminal\" height=\"20\"\u003e\u003c/a\u003e", "markdown": "[![Bitfinex API on Anchor Terminal](https://www.anchorterminal.com/badges/bitfinex.svg)](https://www.anchorterminal.com/tools/bitfinex)", "link": "\u003ca href=\"https://www.anchorterminal.com/tools/bitfinex\"\u003eBitfinex API on Anchor Terminal\u003c/a\u003e" } } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/tools/bitfinex", "json": "https://www.anchorterminal.com/tools/bitfinex.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/tools/bitfinex.md", "mcp": "https://www.anchorterminal.com/mcp", "pricing": "https://www.anchorterminal.com/tools/bitfinex#pricing", "reviews": "https://www.anchorterminal.com/tools/bitfinex#reviews", "slim": "https://www.anchorterminal.com/tools/bitfinex.min.md" }, "markdown": "## Overview\n\n**Grade C · 58.4/100 · rank #687 of 1349 · #10 in Crypto exchanges · not agent-ready · confidence low**\n\n\n## Assessment\n\nBitfinex 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.\n\n## Facts\n\n| Field | Value |\n| --- | --- |\n| Vendor | iFinex Inc. (https://www.bitfinex.com) |\n| Kind | HTTP API |\n| Category | Crypto exchanges (https://www.anchorterminal.com/categories/crypto-exchanges) |\n| Auth | API key · API key and secret made at setting.bitfinex.com/api after a browser signup, with 2FA and an email confirmation, shown once. Each key carries read and write permissions per scope (account, history, orders, positions, funding, settings, wallets, withdraw, ui_withdraw, bfxpay), readable back from `POST /v2/auth/r/permissions`, and keys are revoked from the same page; a strictly increasing nonce per key. Bitfinex's support article on keys says a key can be bound to up to 20 IP addresses, per the search result's text, since the article itself answered 403 (https://docs.bitfinex.com/docs/requirements-and-limitations, https://docs.bitfinex.com/reference/key-permissions, checked 2026-11-03). |\n| Pricing | Pay per use (0% fee) · The API itself costs nothing. The fees page read on 3 November 2026 shows zero maker and zero taker fees for exchange, margin and derivatives order execution with no volume tiers, margin funding lender fees of 15% of interest (18% when the offer is hidden) with up to 5% off for LEO holders, a 5% takeover fee, free crypto deposits and bank wire 0.1% (minimum 60 for deposits, 100 for withdrawals, USD or EUR). Paper trading on a sub-account needs no money (https://www.bitfinex.com/fees, checked 2026-11-03). |\n| x402 | No · No x402, MPP or L402 in the API docs, llms.txt or fees page (checked 2026-11-03). Fees are taken from the account; onboarding is a browser signup. |\n| 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 |\n| Packages | npm: `bitfinex-api-node`; pypi: `bitfinex-api-py` |\n| Source | https://github.com/bitfinexcom/bitfinex-api-node |\n| Docs | https://docs.bitfinex.com |\n| llms.txt | https://docs.bitfinex.com/llms.txt |\n| Last release | 2026-07-18 |\n| GitHub stars | 480 (as of 2026-11-03) |\n| Surface listed | The hosted v2 API at api.bitfinex.com and api-pub.bitfinex.com as an agent calls it, read from docs.bitfinex.com and its llms.txt, bitfinex.com's fees and about pages, bitfinex.statuspage.io, the official MCP registry, the bitfinexcom GitHub organisation, npm and RDAP on 3 November 2026. The legal pages loaded only navigation and support.bitfinex.com answered 403. No account, key or order |\n| MCP server | None found. Looked in docs.bitfinex.com and its llms.txt, the bitfinexcom GitHub organisation (a search for mcp returned nothing) and the official MCP registry. Third-party only, pipeworx-io's remote `io.github.pipeworx-io/bitfinex` and mrfentmen's `bitfinex-mcp`, both public market data, neither Bitfinex's |\n| Key permissions | Read and write flags per scope (account, history, orders, positions, funding, settings, wallets, withdraw, ui_withdraw and bfxpay); `POST /v2/auth/r/permissions` returns the key's scopes. Keys are made with 2FA and email confirmation, shown once, and revoked from the API page. IP binding to up to 20 addresses per the support article's search text (the article answered 403). Default permissions on keys made from an email-and-password account are all enabled per the same text |\n| Rate limits | REST 10 to 90 requests a minute per IP by endpoint, `{\"error\": \"ERR_RATE_LIMIT\"}` and a 60-second IP block; the permissions endpoint 90 a minute. WebSocket 5 authenticated connections per 15 seconds, 20 public connections a minute, 25 channels per connection, with 15-second and 60-second blocks. No Retry-After |\n| Testnet or sandbox | Paper trading on a sub-account using TEST symbols (tTESTBTCF0:TESTUSDTF0 named in the docs) on the production API; no separate sandbox host |\n| Countries served | Unchecked. The Exchange Terms, which carry the prohibited-jurisdiction list, loaded only navigation, and the support article on restrictions answered 403. The only first-hand list we could read is for Bitfinex Securities, a separate product |\n| Fees at the lowest tier | Zero maker and zero taker on exchange, margin and derivatives order execution per the fees page on 3 November 2026, with no volume tiers and no date; margin funding lenders pay 15% of interest (18% when the offer is hidden), LEO holders up to 5% less; bank wires 0.1% |\n| FIX and WebSocket | WebSocket v2 at wss://api.bitfinex.com (authenticated) and wss://api-pub.bitfinex.com (public) with ticker, trades, books, raw books, candles and status channels, account channels and order inputs. No FIX documentation on docs.bitfinex.com; llms.txt lists none |\n| Terms on automated trading | Unchecked. The API Terms of Service and Exchange Terms pages draw their text by script and loaded only navigation. The docs say every API use is subject to the API Terms of Service and that keys are used at the holder's own risk |\n| Errors and idempotency | Authenticated endpoints answer 400 with `{}`; the rate limit answers `{\"error\": \"ERR_RATE_LIMIT\"}`; withdrawals return a notification array with STATUS SUCCESS, ERROR or FAILURE and a CODE marked work in progress. Orders take a client id (`cid`); no idempotency key is documented |\n| SDKs | bitfinex-api-node 9.1.0 (18 July 2026, MIT, 480 stars), bitfinex-api-py 4.0.0 (18 October 2025, Apache-2.0, 219 stars), bitfinex-api-go (pushed 18 October 2025, MIT) and bitfinex-api-rb (21 October 2025, MIT), all in github.com/bitfinexcom |\n| Legal entity | iFinex Inc., from the copyright line on bitfinex.com; the Exchange Terms, which would state its jurisdiction and role, loaded only navigation. Bitfinex Securities Ltd and Bitfinex Securities El Salvador S.A. de C.V. run the securities platform |\n| Capabilities | exchange.market-data, exchange.spot-trading, exchange.derivatives, exchange.balances, exchange.transfers, exchange.staking, market.crypto |\n| Tags | official, hosted, api-key, llms-txt, sandbox, status-page, javascript, python, go, ruby, usage-priced |\n| JSON | https://www.anchorterminal.com/api/v1/tools/bitfinex.json |\n\n## Score breakdown (methodology v0.7, October 2026 research run)\n\nAssessed 2026-11-03 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: low. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. \"This run\" is each category's share of the 100 points.\n\n| Category | Weight | This run | Score (0–100) | Points |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 20 | 85 | 17.0 |\n| Performance | 10% | pending | pending | n/a |\n| Schema \u0026 documentation | 13% | 16.2 | 48 | 7.8 |\n| Agent ergonomics | 13% | 16.2 | 61 | 9.9 |\n| Security \u0026 auth | 14% | 17.5 | 62 | 10.8 |\n| Payments \u0026 pricing | 10% | 12.5 | 40 | 5.0 |\n| Task success | 10% | pending | pending | n/a |\n| Maintenance \u0026 community | 7% | 8.8 | 41 | 3.6 |\n| Transparency \u0026 trust (editorial 13, provenance 85) | 7% | 8.8 | 49 | 4.3 |\n| Negative events | up to −15 | up to −15 | none recorded | 0 |\n| **Total** | | | | **58.4 → C** |\n\n### Why each score\n\n- Reliability 85 (checked 2026-11-03): 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.\n- Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes.\n- Schema \u0026 documentation 48 (checked 2026-11-03): 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.\n- Agent ergonomics 61 (checked 2026-11-03): 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.\n- Security \u0026 auth 62 (checked 2026-11-03): Revocable keys with per-scope read and write flags, a permissions endpoint, 2FA and email confirmation at creation, strictly increasing nonces, and IP binding to 20 addresses per the support article's search text (the article answered 403); no key expiry (24 of 30). `withdraw` and `ui_withdraw` are separate scopes and read-only keys are possible, but the support text says keys from email-and-password accounts start with every permission enabled and no confirmation step is documented for API withdrawals (14 of 20). The API returns exchange data, not third-party text (10). Login history and an account changelog (audit) endpoint are documented (10 of 15). No security.txt, no readable disclosure policy and no certification page readable (4 of 20). 24 + 14 + 10 + 10 + 4 = 62.\n- Payments \u0026 pricing 40 (checked 2026-11-03): 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.\n- Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored.\n- Maintenance \u0026 community 41 (checked 2026-11-03): 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.\n- Transparency \u0026 trust 49 (checked 2026-11-03): 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.\n\nFix list, everything this grade says the listing lacks, the biggest gain first (19 items). What it covers is at https://www.anchorterminal.com/fixes/bitfinex.md (JSON https://www.anchorterminal.com/fixes/bitfinex.json). The whole list for a coding agent comes from `POST https://www.anchorterminal.com/api/v1/fix-list` with `{\"listing\": \"bitfinex\", \"plan\": \"read\"}`, free while the beta runs\n\n### What we couldn't check\n\n- Kind http-api. docs.bitfinex.com leads with REST and WebSocket; no MCP server or OpenAPI file exists.\n- No MCP server was found, looking in docs.bitfinex.com, llms.txt, the bitfinexcom GitHub organisation (a search for mcp returned nothing) and the official MCP registry. The best-known third-party server is pipeworx-io's remote `io.github.pipeworx-io/bitfinex`, public market data only, not Bitfinex's.\n- unchecked: the Exchange Terms, API Terms of Service, privacy statement and trading rulebook (script-drawn, loaded only navigation), and every support.bitfinex.com article (403), so the contracting entity, the clauses on API use and bots, retention, subprocessors and the restricted-country list are unconfirmed. Transparency scores low for that reason.\n- The IP binding (20 addresses), default permissions and paper-trading limits are recorded from the text of search results that quoted Bitfinex's own support articles; the articles themselves answered 403. They are not weighted beyond a few points in security and sandbox.\n- The fees page shows zero maker and zero taker fees for exchange, margin and derivatives with no tiers, date or promotion notice. Recorded as read; a person should check whether a dated promotion or a tiered schedule sits behind it.\n- firstReleased is 28 March 2017, the docs changelog's first entry (API v2, released 1 April 2017 per the page); Bitfinex itself is older. lastRelease is 18 July 2026, bitfinex-api-node 9.1.0.\n- unchecked: FIX (not in the docs), Retry-After headers, CI on the client repositories, GitHub issue reply times, and whether the status page records partial API incidents.\n- Our own products. It doesn't do LocalGhost's or letme's job; it trades one exchange account.\n\n### Sources\n\n- robots.txt (www.bitfinex.com, docs.bitfinex.com, bitfinex.statuspage.io, support.bitfinex.com): \u003chttps://www.bitfinex.com/robots.txt\u003e (seen 2026-11-03)\n- docs llms.txt: \u003chttps://docs.bitfinex.com/llms.txt\u003e (seen 2026-11-03)\n- docs introduction (hosts, versions, paper-trading symbol, API terms link): \u003chttps://docs.bitfinex.com/docs/introduction.md\u003e (seen 2026-11-03)\n- requirements and limitations (rate limits, nonces, key creation): \u003chttps://docs.bitfinex.com/docs/requirements-and-limitations.md\u003e (seen 2026-11-03)\n- authenticated REST overview: \u003chttps://docs.bitfinex.com/docs/rest-auth.md\u003e (seen 2026-11-03)\n- key permissions endpoint: \u003chttps://docs.bitfinex.com/reference/key-permissions.md\u003e (seen 2026-11-03)\n- withdrawal endpoint: \u003chttps://docs.bitfinex.com/reference/rest-auth-withdraw.md\u003e (seen 2026-11-03)\n- docs changelog: \u003chttps://docs.bitfinex.com/docs/changelog.md\u003e (seen 2026-11-03)\n- fees page: \u003chttps://www.bitfinex.com/fees\u003e (seen 2026-11-03)\n- about page (leadership, support links): \u003chttps://www.bitfinex.com/about\u003e (seen 2026-11-03)\n- API Terms of Service (loaded only navigation): \u003chttps://www.bitfinex.com/legal/general/api-terms/\u003e (seen 2026-11-03)\n- Exchange Terms (loaded only navigation): \u003chttps://www.bitfinex.com/legal/exchange/terms/\u003e (seen 2026-11-03)\n- privacy statement (loaded only navigation): \u003chttps://www.bitfinex.com/legal/privacy/\u003e (seen 2026-11-03)\n- site sitemap (legal page list): \u003chttps://www.bitfinex.com/sitemap.xml\u003e (seen 2026-11-03)\n- status history feed: \u003chttps://bitfinex.statuspage.io/history.atom\u003e (seen 2026-11-03)\n- security.txt (404): \u003chttps://www.bitfinex.com/.well-known/security.txt\u003e (seen 2026-11-03)\n- official MCP registry search: \u003chttps://registry.modelcontextprotocol.io/v0/servers?search=bitfinex\u003e (seen 2026-11-03)\n- bitfinexcom GitHub organisation repositories and mcp search: \u003chttps://api.github.com/orgs/bitfinexcom/repos?per_page=100\u0026sort=updated\u003e (seen 2026-11-03)\n- npm bitfinex-api-node (versions and times): \u003chttps://registry.npmjs.org/bitfinex-api-node\u003e (seen 2026-11-03)\n- bitfinex-api-py releases and metadata: \u003chttps://api.github.com/repos/bitfinexcom/bitfinex-api-py/releases?per_page=5\u003e (seen 2026-11-03)\n- support article on paper trading (answered 403; facts from the search result's text only): \u003chttps://support.bitfinex.com/hc/en-us/articles/900001525006-Paper-Trading\u003e (seen 2026-11-03)\n- support article on API keys (answered 403; facts from the search result's text only): \u003chttps://support.bitfinex.com/hc/en-us/articles/115003363429-How-to-create-and-revoke-a-Bitfinex-API-Key\u003e (seen 2026-11-03)\n- RDAP for bitfinex.com: \u003chttps://rdap.verisign.com/com/v1/domain/bitfinex.com\u003e (seen 2026-11-03)\n\n## Score history\n\nEvery move of a score since the listing was graded, newest first, with its cause. A score can't move without an entry here. JSON: https://www.anchorterminal.com/api/v1/tools/bitfinex/history.json\n\n- 2026-11-03: graded 58.4 C (methodology 0.7)\n\n## Who's behind it (provenance 85/100, checked 2026-11-03)\n\n| Check | Finding | Points |\n| --- | --- | --- |\n| Legal entity named | iFinex Inc. | 20/20 |\n| Domain age | bitfinex.com, registered 2012-10-11 (14 years) | 15/15 |\n| Endpoint on the vendor's domain | bitfinex.com | 15/15 |\n| Terms of service | published, but our reader couldn't read it | 7/10 |\n| Privacy policy | published, but our reader couldn't read it | 7/10 |\n| Status page | bitfinex.statuspage.io | 10/10 |\n| Changelog | published | 10/10 |\n| security.txt | not found | 0/10 |\n| People named | 4 named with their role, none with a public profile | 7/10 |\n| Support route | help pages, a community | 5/5 |\n\niFinex Inc. is named only in the copyright line of bitfinex.com; the Exchange Terms, API Terms of Service and privacy statement pages draw their text by script and loaded only navigation, so the contracting entity and its jurisdiction are unconfirmed.\n\nRDAP gives bitfinex.com a registration date of 11 October 2012.\n\nhttps://www.bitfinex.com/.well-known/security.txt returns 404.\n\nwww.bitfinex.com/robots.txt allows the pages read; docs.bitfinex.com allows all and points to llms.txt; bitfinex.statuspage.io disallows /api/ and /embed/, so the history feed was read. support.bitfinex.com's robots.txt allows articles but the articles answered 403.\n\nThe docs changelog's latest entry is 16 October 2024; the API clients carry the recent releases.\n\n### Terms and privacy, as read\n\nA reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice.\n\n**Terms of service** (https://www.bitfinex.com/legal/exchange/terms/), read 2026-11-03. Our reader couldn't read it (the page has only its navigation and a copyright line without a browser, so the document is drawn by script).\n\n\n**Privacy policy** (https://www.bitfinex.com/legal/privacy/), read 2026-11-03. Our reader couldn't read it (the page has only its navigation and a copyright line without a browser, so the document is drawn by script).\n\n\n## Humans behind the project (researched 2026-11-03 from public pages, not part of the grade)\n\n### Key people\n\n- JL van der Velde, Chief Executive Officer, Bitfinex\n- Paolo Ardoino, Chief Technology Officer, Bitfinex\n- Claudia Lagorio, Chief Operating Officer, Bitfinex\n- Giancarlo Devasini, Chief Financial Officer, Bitfinex\n- Note: Bitfinex's about page, read 3 November 2026, lists JL van der Velde (Chief Executive Officer), Claudia Lagorio (Chief Operating Officer), Paolo Ardoino (Chief Technology Officer) and Giancarlo Devasini (Chief Financial Officer), with no founders named and no personal accounts linked. The footer names iFinex Inc. as the copyright holder; the Exchange Terms, which would state the operating entity and its jurisdiction, loaded only navigation, and support.bitfinex.com answered 403, so ownership is recorded as unknown rather than private. Investors were looked for on the about page, the press page link and the legal index; nothing names backers, and no outside search was made.\n- Bitfinex: LinkedIn https://www.linkedin.com/company/bitfinex/ X https://x.com/bitfinex GitHub https://github.com/bitfinexcom\n\n### Getting support\n\n- Help: https://support.bitfinex.com/hc/en-us\n- Help: https://cs.bitfinex.com\n- Help: https://bitfinex.statuspage.io\n- Community (Bitfinex Telegram): https://t.me/bitfinex\n- Community (bitfinex-api-node issues): https://github.com/bitfinexcom/bitfinex-api-node/issues\n- Sources: https://www.bitfinex.com/about, https://www.bitfinex.com/fees, https://www.bitfinex.com/sitemap.xml, https://docs.bitfinex.com/docs/introduction.md, https://api.github.com/orgs/bitfinexcom/repos?per_page=100\u0026sort=updated\n\n## Live (updated 2026-11-04 19:31 UTC)\n\n- Vendor status page: none, All Systems Operational\n- security.txt: none\n- Always current: https://www.anchorterminal.com/api/v1/live/bitfinex.json\n\n## Probe metrics\n\nNot measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score.\n\n## Prices\n\n| Item | Price | Unit | Note |\n| --- | --- | --- | --- |\n| Exchange maker fee, as shown on 3 November 2026 | 0% | percentage fee | no tiers or date shown; reads as a promotion |\n| Exchange taker fee, as shown on 3 November 2026 | 0% | percentage fee | no tiers or date shown; reads as a promotion |\n| Margin funding lender fee on interest earned | 15% | percentage fee | 18% when the offer is hidden, up to 5% off for LEO holders |\n\nAcross all listings: https://www.anchorterminal.com/prices/index.md\n\n## Strengths\n\n- Per-scope read and write permissions on each key, including a separate `withdraw` scope, readable back from the permissions endpoint\n- Paper trading on a sub-account against test symbols on the same production API, with no money at risk\n- llms.txt with a Markdown twin of every docs page, and official Node, Python, Go and Ruby clients\n- Rate limits, connection limits and the `ERR_RATE_LIMIT` response documented with numbers\n- A Statuspage history going back to 2021 and a fees page without login\n\n## Weaknesses\n\n- No official MCP server, OpenAPI file or AsyncAPI file; the registry's Bitfinex servers are third parties proxying public market data\n- Responses are positional arrays and authenticated errors answer 400 with an empty object, so an agent must map indexes and guess causes\n- Rate limits of 10 to 90 requests a minute per IP with a 60-second block and no Retry-After\n- The Exchange Terms, API Terms of Service, privacy statement and support articles could not be read, so the bot clauses, retention and restricted countries are unchecked\n- The docs changelog stops at October 2024 and the v1 deprecation has no date\n\n\n\n## Before you call it (notes for agents)\n\n1. 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\n2. Use one key per client process, since each key keeps its own strictly increasing nonce and a reused nonce is rejected\n3. Rehearse on a paper-trading sub-account with the TEST symbols before touching real balances; the sub-account cannot be converted later\n4. 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\n5. 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\n\n## Connect\n\nInstall:\n\n```bash\nnpm install bitfinex-api-node\n```\n\nFirst request:\n\n```bash\ncurl https://api-pub.bitfinex.com/v2/ticker/tBTCUSD\n```\n\nThrough letme: https://letme.dev/bitfinex. letme answers with the pick and how to call it direct. How it works: https://www.anchorterminal.com/letme/index.md\n\n## Similar tools\n\nRanked by shared capabilities, then score. Same-category tools with no shared capability key are listed last.\n\n| Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown |\n| --- | --- | --- | --- | --- | --- | --- |\n| Gemini Exchange API | BB | 74.6 | 70 | exchange.market-data, exchange.spot-trading, exchange.derivatives, exchange.balances, exchange.transfers, exchange.staking, market.crypto | no | https://www.anchorterminal.com/tools/gemini-exchange.md |\n| Kraken API | BB | 71 | 159 | exchange.spot-trading, exchange.market-data, exchange.derivatives, exchange.balances, exchange.transfers, exchange.staking, market.crypto | no | https://www.anchorterminal.com/tools/kraken.md |\n| OKX API | B | 64.3 | 413 | exchange.spot-trading, exchange.market-data, exchange.derivatives, exchange.balances, exchange.transfers, exchange.staking, market.crypto | no | https://www.anchorterminal.com/tools/okx.md |\n| Binance API | B | 63.2 | 448 | exchange.spot-trading, exchange.market-data, exchange.derivatives, exchange.balances, exchange.transfers, exchange.staking, market.crypto | no | https://www.anchorterminal.com/tools/binance.md |\n| Bybit | C | 57.3 | 745 | exchange.market-data, exchange.spot-trading, exchange.derivatives, exchange.balances, exchange.transfers, exchange.staking, market.crypto | no | https://www.anchorterminal.com/tools/bybit.md |\n| Gate | C | 56.4 | 786 | exchange.market-data, exchange.spot-trading, exchange.derivatives, exchange.balances, exchange.transfers, exchange.staking, market.crypto | no | https://www.anchorterminal.com/tools/gate-io.md |\n\n## Panel reviews (0)\n\nReviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): .\n\nDesk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md\n\n## Notable\n\n- No official MCP server. The docs and llms.txt do not mention MCP or agents, a GitHub search of the bitfinexcom organisation for mcp returned nothing, and the official MCP registry holds only third-party servers, `io.github.pipeworx-io/bitfinex` (remote at gateway.pipeworx.io/bitfinex/mcp, v2 public endpoints, 0.2.1 on 30 October 2026) and `io.github.mrfentmen/bitfinex-mcp` (npm, prices, 1.0.1 on 21 September 2026), neither Bitfinex's (source: \u003chttps://registry.modelcontextprotocol.io/v0/servers?search=bitfinex\u003e)\n- Rate limits are 10 to 90 requests a minute per IP depending on the endpoint, answered with `{\"error\": \"ERR_RATE_LIMIT\"}` and a 60-second IP block; WebSocket at most 5 authenticated connections per 15 seconds on api.bitfinex.com, 20 a minute on api-pub.bitfinex.com and 25 channels per connection (source: \u003chttps://docs.bitfinex.com/docs/requirements-and-limitations\u003e)\n- Key permissions are per scope with read and write flags, `withdraw` among them, and `POST /v2/auth/r/permissions` returns the current key's scopes (source: \u003chttps://docs.bitfinex.com/reference/key-permissions\u003e)\n- Paper trading runs on a sub-account against test symbols such as tTESTBTCF0:TESTUSDTF0 on the production API, per the docs introduction; the support article says paper balances refill to $1,000,000 equivalent per sub-account and that a paper sub-account cannot become a regular one, per the search result's text, since support.bitfinex.com answered 403 (source: \u003chttps://docs.bitfinex.com/docs/introduction\u003e)\n- Responses are positional arrays, not keyed objects, and an authenticated error answers 400 with an empty `{}`; the withdrawal endpoint's status `CODE` field is marked work in progress (source: \u003chttps://docs.bitfinex.com/reference/rest-auth-withdraw\u003e)\n- The docs changelog has seven entries, from 28 March 2017 (API v2) to 16 October 2024 (VASP endpoint), and says v1 \"will become deprecated at some point in the future\" with no date (source: \u003chttps://docs.bitfinex.com/docs/changelog\u003e)\n- Official clients are bitfinex-api-node 9.1.0 on npm (18 July 2026, 480 stars), bitfinex-api-py 4.0.0 (18 October 2025, dropped the Pulse and Pay endpoints), bitfinex-api-go (pushed 18 October 2025) and bitfinex-api-rb (21 October 2025) (source: \u003chttps://registry.npmjs.org/bitfinex-api-node, https://api.github.com/repos/bitfinexcom/bitfinex-api-py/releases\u003e)\n- bitfinex.statuspage.io's history feed has no entry between 25 March 2026 (a 14-hour platform maintenance) and 3 November 2026, after platform outages of about 3 hours on 14 August 2025 and 12 hours on 19 April 2025; the feed records platform-wide events only (source: \u003chttps://bitfinex.statuspage.io/history.atom\u003e)\n- The fees page shows zero maker and taker fees for exchange, margin and derivatives order execution with no tiers and no effective date, which reads as a promotion; the page carries only a copyright line (source: \u003chttps://www.bitfinex.com/fees\u003e)\n- The Exchange Terms, API Terms of Service, privacy statement and trading rulebook pages draw their text by script and loaded only navigation for our reader, and support.bitfinex.com answered 403, so the legal entity in the terms, the clauses on API use and bots, retention and the restricted-country list are unchecked; the footer names iFinex Inc. (source: \u003chttps://www.bitfinex.com/legal/general/api-terms/\u003e)\n\n- #10 of 21 in Best crypto exchange APIs and MCP servers for AI agents: https://www.anchorterminal.com/best/crypto-exchanges/index.md\n- All 210 exchanges comparisons: https://www.anchorterminal.com/compare/crypto-exchanges/index.md\n\n## Compare\n\n- [Bitfinex API vs Bitget](https://www.anchorterminal.com/compare/bitfinex-vs-bitget.md): C 58.4 vs D 53.9\n- [Bitfinex API vs Bithumb Open API](https://www.anchorterminal.com/compare/bitfinex-vs-bithumb.md): C 58.4 vs D 50.6\n- [Bitfinex API vs Bitstamp API](https://www.anchorterminal.com/compare/bitfinex-vs-bitstamp.md): C 58.4 vs D 50.4\n- [Bitfinex API vs Bybit](https://www.anchorterminal.com/compare/bitfinex-vs-bybit.md): C 58.4 vs C 57.3\n- [Bitfinex API vs Coinbase Advanced Trade API](https://www.anchorterminal.com/compare/bitfinex-vs-coinbase-advanced-trade.md): C 58.4 vs C 61.7\n- [Bitfinex API vs Coinbase MCP server (Coinbase for Agents)](https://www.anchorterminal.com/compare/bitfinex-vs-coinbase-mcp.md): C 58.4 vs C 60\n- [Bitfinex API vs Crypto.com Exchange API](https://www.anchorterminal.com/compare/bitfinex-vs-crypto-com-exchange.md): C 58.4 vs D 46.8\n- [Bitfinex API vs Deribit](https://www.anchorterminal.com/compare/bitfinex-vs-deribit.md): C 58.4 vs C 59\n- [Bitfinex API vs dYdX](https://www.anchorterminal.com/compare/bitfinex-vs-dydx.md): C 58.4 vs B 69.5\n- [Bitfinex API vs Gate](https://www.anchorterminal.com/compare/bitfinex-vs-gate-io.md): C 58.4 vs C 56.4\n- [Bitfinex API vs Gemini Exchange API](https://www.anchorterminal.com/compare/bitfinex-vs-gemini-exchange.md): C 58.4 vs BB 74.6\n- [Bitfinex API vs HTX trading API](https://www.anchorterminal.com/compare/bitfinex-vs-htx.md): C 58.4 vs E 43.3\n- [Bitfinex API vs Hyperliquid](https://www.anchorterminal.com/compare/bitfinex-vs-hyperliquid.md): C 58.4 vs D 50\n- [Bitfinex API vs Kraken API](https://www.anchorterminal.com/compare/bitfinex-vs-kraken.md): C 58.4 vs BB 71\n- [Bitfinex API vs KuCoin](https://www.anchorterminal.com/compare/bitfinex-vs-kucoin.md): C 58.4 vs D 53.9\n- [Bitfinex API vs MEXC API](https://www.anchorterminal.com/compare/bitfinex-vs-mexc.md): C 58.4 vs C 56.3\n- [Bitfinex API vs OKX API](https://www.anchorterminal.com/compare/bitfinex-vs-okx.md): C 58.4 vs B 64.3\n- [Bitfinex API vs Uniswap Trading API](https://www.anchorterminal.com/compare/bitfinex-vs-uniswap.md): C 58.4 vs B 63.3\n- [Bitfinex API vs Upbit Open API](https://www.anchorterminal.com/compare/bitfinex-vs-upbit.md): C 58.4 vs C 54.7\n- [Binance API vs Bitfinex API](https://www.anchorterminal.com/compare/binance-vs-bitfinex.md): B 63.2 vs C 58.4\n\n## Verify this listing\n\nFor the vendor. The badge or a plain link to this page verifies the listing, from a page on bitfinex.com or one of its subdomains, or the README at the root of github.com/bitfinexcom/bitfinex-api-node. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{\"slug\": \"bitfinex\", \"url\": \"…\"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify\n\nHTML badge:\n\n```html\n\u003ca href=\"https://www.anchorterminal.com/tools/bitfinex\"\u003e\u003cimg src=\"https://www.anchorterminal.com/badges/bitfinex.svg\" alt=\"Bitfinex API on Anchor Terminal\" height=\"20\"\u003e\u003c/a\u003e\n```\n\nMarkdown badge, for a README:\n\n```markdown\n[![Bitfinex API on Anchor Terminal](https://www.anchorterminal.com/badges/bitfinex.svg)](https://www.anchorterminal.com/tools/bitfinex)\n```\n\nPlain link:\n\n```html\n\u003ca href=\"https://www.anchorterminal.com/tools/bitfinex\"\u003eBitfinex API on Anchor Terminal\u003c/a\u003e\n```\n\n## Share this listing\n\nFor the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Bitfinex API is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score.\n\n- Dark: https://www.anchorterminal.com/assets/share/bitfinex-dark.png\n- Light: https://www.anchorterminal.com/assets/share/bitfinex-light.png\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-04", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Terminal", "url": "https://www.anchorterminal.com/tools/" }, { "name": "Crypto exchanges", "url": "https://www.anchorterminal.com/categories/crypto-exchanges" }, { "name": "Bitfinex API", "url": "" } ], "description": "Bitfinex's v2 API for spot, margin, derivatives and peer-to-peer funding, with balances, deposits and withdrawals, through REST and WebSocket with scoped API keys, paper-trading sub-accounts and official Node, Python, Go and Ruby clients.", "facts": [ "rank #687 of 1349", "API key auth", "0 desk reviews" ], "h1": "Bitfinex API", "image": "https://www.anchorterminal.com/assets/og/tools-bitfinex.png", "path": "/tools/bitfinex", "published": "2026-10-01", "section": "tools", "title": "Bitfinex review (2026): pricing, alternatives and grade C", "toc": null, "updated": "2026-11-04", "url": "https://www.anchorterminal.com/tools/bitfinex" }, "tokens": { "markdown": 8850, "slim": 2280 }, "version": 1 }