{ "data": { "a": { "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": 675, "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" ], "assessment": { "confidence": "low", "date": "2026-11-03" }, "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 } }, "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" }, "area": "payments", "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 }, "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-04T21:25:16.420431998Z" }, "versions": [ { "registry": "github", "name": "bitfinexcom/bitfinex-api-node", "version": "4.0.15", "released": "2020-07-02", "seenAt": "2026-11-04T20:02:46.845797373Z" }, { "registry": "npm", "name": "bitfinex-api-node", "version": "9.1.0", "seenAt": "2026-11-04T20:02:45.764784853Z" }, { "registry": "pypi", "name": "bitfinex-api-py", "version": "4.0.0", "released": "2025-10-18", "seenAt": "2026-11-04T20:02:46.619664479Z" } ], "githubStars": 480, "npmWeekly": 6284, "pypiWeekly": 832, "securityTxt": { "url": "https://bitfinex.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-04T15:53:26.210646703Z" }, "updatedAt": "2026-11-04T21:25:16.420431998Z" } }, "answer": "Bitfinex API scores 58.4 (C) on agent readiness against Upbit Open API's 54.7 (C), and leads in 3 of 7 scored categories. Upbit Open API leads on schema \u0026 documentation, agent ergonomics, maintenance \u0026 community and transparency \u0026 trust.", "b": { "slug": "upbit", "name": "Upbit Open API", "vendor": "Dunamu Inc.", "vendorUrl": "https://docs.upbit.com", "kind": "http-api", "category": "crypto-exchanges", "summary": "Upbit, the Korean exchange run by Dunamu, has a REST and WebSocket Open API for KRW, BTC and USDT market data, orders, balances, deposits and withdrawals, with official SDKs, a CLI and agent skills but no MCP server.", "url": "https://www.anchorterminal.com/tools/upbit", "markdownUrl": "https://www.anchorterminal.com/tools/upbit.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/upbit.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/upbit.json", "dns": "upbit.grade.anchorterminal.com", "repo": "https://github.com/upbit-official", "transports": [], "packages": [ { "registry": "npm", "name": "@upbit-official/upbit-cli" }, { "registry": "pypi", "name": "upbit-sdk" } ], "auth": "api-key", "authNotes": "Access and secret keys issued on the PC web site under My Page \u003e Open API Management after identity verification and two-factor authentication. At issuance the person picks the functions the key may use and must register at least one public IPv4 address, since the allow-list is mandatory. Each request carries a JWT signed with HMAC SHA512 over the access key, a fresh nonce and a SHA512 hash of the query, as a Bearer token. A key with withdrawal permission gets a withdrawal safe-lock by default that is lifted only in the mobile app. Up to 10 keys on the main pocket and 5 per sub-pocket; expired keys answer expired_access_key (https://docs.upbit.com/kr/docs/api-key.md, checked 2026-11-03).", "pricing": "usage", "pricingNotes": "Trading fees per fill. The fee schedule is on upbit.com, whose robots.txt disallows every path for our crawler, so no rate is recorded. Public quotation endpoints need no key and no account (https://upbit.com/robots.txt, checked 2026-11-03).", "priceSummary": "Pay per use", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the developer docs, llms.txt, the SDK licence or the CLI docs (checked 2026-11-03). Fees are taken from each fill.", "endpoints": [] }, "toolCount": 0, "popularity": { "githubStars": 91, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://docs.upbit.com/kr/reference/api-overview", "llmsTxt": "https://docs.upbit.com/llms.txt", "capabilities": [ "exchange.market-data", "exchange.spot-trading", "exchange.balances", "exchange.transfers", "market.crypto" ], "tags": [ "hosted", "api-key", "closed-source", "usage-priced", "cli", "agent-skills", "llms-txt", "python", "typescript", "go", "no-status-page" ], "lastRelease": "2026-10-20", "graded": true, "anchor": { "graded": true, "score": 54.7, "grade": "C", "agentReady": false, "rank": 802, "ranked": true, "rankOf": 1349, "categoryRank": 14, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 70, "maintenance": 83, "payments": 15, "reliability": 42, "schema": 66, "security": 59, "transparency": 54 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-03" }, "negative": 0, "verdict": "Upbit's Open API has a mandatory IP allow-list, scoped keys with a default withdrawal lock, per-group rate limits with 429 and 418 signalling, an order-test endpoint, official SDKs, a CLI and agent skills with a CONFIRM gate. There is no MCP server, sandbox or status page, and the fees and terms sit on a host our crawler may not read.", "bestFor": "KRW-market trading for agents acting for a verified Korean account, with first-party SDKs, a CLI and skills but no MCP.", "strengths": [ "Keys need a registered public IP, carry only the chosen functions and get a withdrawal safe-lock by default that only the mobile app lifts", "Rate limits published per group with numbers, a Remaining-Req header on every response, 429 then 418 with a stated block length", "POST /v1/orders/test checks an order and the pair's state at no cost, and the skills run it before a live order", "Official Python, TypeScript and Go SDKs at v1.1.0 (20 October 2026), a CLI with JSON output and agent skills that require a typed CONFIRM before any write", "Notices carry effective dates, such as the path-format change of 16 November 2026" ], "weaknesses": [ "No MCP server; the agent route is the CLI through skills, which need a terminal", "No sandbox or testnet beyond the order-test endpoint, and no status page or SLA", "Keys can only be issued on the PC web site after Korean identity verification and 2FA, and the exchange serves the Korean market", "The fee schedule, user terms and Open API terms are on upbit.com, which disallows every crawler path, so none is recorded first-hand", "The SDK licence page says the SDK material is not open source while the GitHub repositories carry Apache-2.0" ], "agentNotes": [ "Ask the person for a key with only the functions the task needs and your server's public IPv4 address registered; a private or unregistered IP is refused", "Sign every request with a fresh JWT (HS512, new nonce, SHA512 query hash) and branch on error.name, not error.message", "Run POST /v1/orders/test before a live order; it costs nothing and shares the 8-a-second order-test group", "Read Remaining-Req and keep orders under 12 a second per pocket; on 429 wait for the next second and on 418 wait out the stated block", "Leave the withdrawal safe-lock on unless the person lifts it in the app, and send paths with single slashes and no trailing slash before 16 November 2026" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 54.7 } ], "editorialScores": { "ergonomics": 70, "maintenance": 83, "payments": 15, "reliability": 42, "schema": 66, "security": 59, "transparency": 42 }, "provenanceScore": 66, "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 } }, "connect": { "install": "npm install -g @upbit-official/upbit-cli", "http": "curl 'https://api.upbit.com/v1/ticker?markets=KRW-BTC'" }, "letme": { "capability": "https://letme.dev/exchange.market-data", "tool": "https://letme.dev/upbit" }, "area": "payments", "provenance": { "legalEntity": "Dunamu Inc.", "domain": "upbit.com", "domainRegistered": "2004-01-10", "endpointOnVendorDomain": true, "terms": "", "privacy": "https://docs.upbit.com/kr/page/privacy_policy_v1_5.md", "statusPage": "", "changelog": "https://docs.upbit.com/kr/changelog", "securityTxt": "unknown", "checked": "2026-11-03", "notes": [ "Dunamu Inc. is named as the licensor in the Upbit Developer SDK License v1.0 and as the company in the developer centre's privacy policy V1.5 (from 18 May 2026).", "upbit.com/robots.txt disallows every path for User-agent * (a second group adds /terms_and_policy and others), allowing only Googlebot, MSNBot, Yeti and Daumoa; sg.upbit.com and www.dunamu.com do the same. The user terms, the Open API terms, the fee schedule and security.txt on those hosts were therefore not fetched; the terms URL is left empty.", "docs.upbit.com/robots.txt allows everything but edit, login and api-next paths and points to llms.txt, with Content-Signal ai-train=yes, search=yes, ai-input=yes.", "RDAP gives upbit.com a registration date of 10 January 2004.", "No status page found; the API has a service-status (wallet status) endpoint and an announcements WebSocket stream." ], "score": 66 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/upbit.json", "live": { "slug": "upbit", "versions": [ { "registry": "npm", "name": "@upbit-official/upbit-cli", "version": "1.0.0", "seenAt": "2026-11-04T21:03:15.347083898Z" }, { "registry": "pypi", "name": "upbit-sdk", "version": "1.1.0", "released": "2026-10-20", "seenAt": "2026-11-04T21:03:16.288654002Z" } ], "npmWeekly": 71, "pypiWeekly": 122, "securityTxt": { "url": "https://upbit.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-04T15:53:27.560288922Z" }, "updatedAt": "2026-11-04T21:03:16.288654002Z" } }, "edges": [ { "by": 43, "category": "reliability", "leads": "bitfinex", "name": "Reliability", "reasons": { "a": "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.", "b": "Read with the hosted lines. No status page found on docs.upbit.com or in llms.txt; a wallet-status endpoint and an announcements stream stand in (0). No readable incident history (5). Rate limits documented with numbers per group, per IP and per pocket, updated 7 October 2026 (15). 429 then 418 with a stated block length and a Remaining-Req header, an order-test endpoint and a self-match-prevention default; an order identifier for safe retries was not checked (12 of 15). No SLA found (0). Generally available (10). 0 + 5 + 15 + 12 + 0 + 10 = 42." }, "scores": { "a": 85, "b": 42 } }, { "by": 42, "category": "maintenance", "leads": "upbit", "name": "Maintenance \u0026 community", "reasons": { "a": "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.", "b": "Read as a closed service. SDK v1.1.0 on 20 October 2026 (30). The CLI 1.0.0 on 1 September, the rate-limit update of 7 October, the SDK on 20 October and the path-format notice for 16 November 2026 (20). open-api@upbit.com answers in turn on weekdays per the support notice, notices carry dates, and the six upbit-official repositories show no open issues (12 of 15). Current official SDKs in Python, TypeScript and Go (15). Apache-2.0 repositories pushed in October 2026; CI not checked (6 of 10). 30 + 20 + 12 + 15 + 6 = 83." }, "scores": { "a": 41, "b": 83 } }, { "by": 25, "category": "payments", "leads": "bitfinex", "name": "Payments \u0026 pricing", "reasons": { "a": "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.", "b": "No machine payment protocol (0). The fee schedule is on upbit.com, which disallows every crawler path, so no price is recorded (0 of 20, unchecked). Public quotation endpoints need no key, card or account; trading needs a verified Korean account. Judgement call (15 of 20). A person must sign up, pass identity checks and issue keys on the PC web site (0). 0 + 0 + 15 + 0 = 15." }, "scores": { "a": 40, "b": 15 } }, { "by": 18, "category": "schema", "leads": "upbit", "name": "Schema \u0026 documentation", "reasons": { "a": "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.", "b": "No OpenAPI found; the reference is a readme.io site with a Markdown twin of every page (5 of 25). llms.txt on docs.upbit.com and a kr/llms.txt index (10). Each reference page states what the endpoint does, its group and its errors, with warnings such as market_offline after maintenance (14 of 20). Typed parameters with enums for order type, side and time in force and required flags (11 of 15). Recipes in Python, Java and Node.js and an error format of error.name and error.message with HTTP statuses (13 of 15). Feature versions in page histories (v1.6.1) and dated notices with effective dates, no single API version (13 of 15). 5 + 10 + 14 + 11 + 13 + 13 = 66." }, "scores": { "a": 48, "b": 66 } }, { "by": 9, "category": "ergonomics", "leads": "upbit", "name": "Agent ergonomics", "reasons": { "a": "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.", "b": "Graded on the REST API with the CLI. Candle counts, list limits and the CLI's --max-items and --transform size responses (16 of 25). Paging and filters on orders and history (15 of 20). error.name codes to branch on, which the November 2026 notice tells clients to use, and 418 with its block length (15 of 20). An order-test endpoint and a CONFIRM gate in the skills; an order identifier for idempotent placement was not checked (11 of 20). Few required parameters, SDKs in three languages and a CLI, but keys need the PC web site and a registered IP (13 of 15). 16 + 15 + 15 + 11 + 13 = 70." }, "scores": { "a": 61, "b": 70 } }, { "by": 5, "category": "transparency", "leads": "upbit", "name": "Transparency \u0026 trust", "reasons": { "a": "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.", "b": "The editorial half. A closed service whose user and Open API terms could not be fetched under upbit.com's robots.txt, and whose SDK licence page calls the SDK material not open source while the repositories carry Apache-2.0 (8 of 30). The developer centre's privacy policy names Dunamu Inc., gives retention periods and names Zendesk in Japan; the main privacy policy was not read (14 of 30). Notices with effective dates, including the path-format change and the deprecated Remaining-Req min field (12 of 20). Zendesk and Google Analytics named with a location for the developer centre only (8 of 20). 8 + 14 + 12 + 8 = 42." }, "scores": { "a": 49, "b": 54 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "iFinex Inc.", "b": "Dunamu Inc.", "name": "Vendor" }, { "a": "no (local only)", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "", "b": "", "name": "Transports" }, { "a": "API key", "b": "API key", "name": "Auth" }, { "a": "Pay per use", "b": "Pay per use", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "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", "b": "none", "name": "Licence" }, { "a": "none", "b": "0", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-07-18", "b": "2026-10-20", "name": "Last release" }, { "a": "couldn't be read", "b": "no document linked", "name": "Terms last updated" }, { "a": "couldn't be read", "b": "no date given", "name": "Privacy policy last updated" }, { "a": "couldn't be read", "b": "not read yet", "name": "Customer content may train models" }, { "a": "couldn't be read", "b": "not read yet", "name": "Terms restrict automated access" }, { "a": "couldn't be read", "b": "not read yet", "name": "Terms restrict benchmarking" }, { "a": "couldn't be read", "b": "not read yet", "name": "Terms or service can change without notice" }, { "a": "couldn't be read", "b": "not read yet", "name": "Arbitration or class-action waiver" }, { "a": "480 stars", "b": "91 stars", "name": "Popularity" } ], "faq": [ { "answer": "Bitfinex API scores 58.4 (C) on agent readiness against Upbit Open API's 54.7 (C), and leads in 3 of 7 scored categories. Upbit Open API leads on schema \u0026 documentation, agent ergonomics, maintenance \u0026 community and transparency \u0026 trust.", "question": "Which is better for AI agents, Bitfinex API or Upbit Open API?" }, { "answer": "Both need an API key.", "question": "Do Bitfinex API and Upbit Open API need an API key?" }, { "answer": "No hosted endpoint is listed for Bitfinex API. No hosted endpoint is listed for Upbit Open API.", "question": "Can an agent call Bitfinex API and Upbit Open API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 85 against 42", "Payments \u0026 pricing, 40 against 15" ], "also": null, "goodFor": "An agent trading spot, margin or derivatives, or lending on the funding market, with scoped keys, official clients and paper trading.", "slug": "bitfinex", "watchFor": "No official MCP server, OpenAPI file or AsyncAPI file; the registry's Bitfinex servers are third parties proxying public market data" }, { "aheadOn": [ "Schema \u0026 documentation, 66 against 48", "Agent ergonomics, 70 against 61", "Maintenance \u0026 community, 83 against 41", "Transparency \u0026 trust, 54 against 49" ], "also": null, "goodFor": "KRW-market trading for agents acting for a verified Korean account, with first-party SDKs, a CLI and skills but no MCP.", "slug": "upbit", "watchFor": "No MCP server; the agent route is the CLI through skills, which need a terminal" } ], "history": null, "job": { "capability": "exchange.market-data", "name": "Exchange market data" }, "others": [ { "json": "https://www.anchorterminal.com/compare/bitfinex-vs-bitget.json", "title": "Bitfinex API vs Bitget", "url": "https://www.anchorterminal.com/compare/bitfinex-vs-bitget" }, { "json": "https://www.anchorterminal.com/compare/bitfinex-vs-bithumb.json", "title": "Bitfinex API vs Bithumb Open API", "url": "https://www.anchorterminal.com/compare/bitfinex-vs-bithumb" }, { "json": "https://www.anchorterminal.com/compare/bitfinex-vs-bitstamp.json", "title": "Bitfinex API vs Bitstamp API", "url": "https://www.anchorterminal.com/compare/bitfinex-vs-bitstamp" }, { "json": "https://www.anchorterminal.com/compare/bitfinex-vs-bybit.json", "title": "Bitfinex API vs Bybit", "url": "https://www.anchorterminal.com/compare/bitfinex-vs-bybit" }, { "json": "https://www.anchorterminal.com/compare/bitfinex-vs-coinbase-advanced-trade.json", "title": "Bitfinex API vs Coinbase Advanced Trade API", "url": "https://www.anchorterminal.com/compare/bitfinex-vs-coinbase-advanced-trade" }, { "json": "https://www.anchorterminal.com/compare/bitfinex-vs-coinbase-mcp.json", "title": "Bitfinex API vs Coinbase MCP server (Coinbase for Agents)", "url": "https://www.anchorterminal.com/compare/bitfinex-vs-coinbase-mcp" }, { "json": "https://www.anchorterminal.com/compare/bitfinex-vs-crypto-com-exchange.json", "title": "Bitfinex API vs Crypto.com Exchange API", "url": "https://www.anchorterminal.com/compare/bitfinex-vs-crypto-com-exchange" }, { "json": "https://www.anchorterminal.com/compare/bitfinex-vs-deribit.json", "title": "Bitfinex API vs Deribit", "url": "https://www.anchorterminal.com/compare/bitfinex-vs-deribit" }, { "json": "https://www.anchorterminal.com/compare/bitfinex-vs-dydx.json", "title": "Bitfinex API vs dYdX", "url": "https://www.anchorterminal.com/compare/bitfinex-vs-dydx" }, { "json": "https://www.anchorterminal.com/compare/bitfinex-vs-gate-io.json", "title": "Bitfinex API vs Gate", "url": "https://www.anchorterminal.com/compare/bitfinex-vs-gate-io" }, { "json": "https://www.anchorterminal.com/compare/bitfinex-vs-gemini-exchange.json", "title": "Bitfinex API vs Gemini Exchange API", "url": "https://www.anchorterminal.com/compare/bitfinex-vs-gemini-exchange" }, { "json": "https://www.anchorterminal.com/compare/bitfinex-vs-htx.json", "title": "Bitfinex API vs HTX trading API", "url": "https://www.anchorterminal.com/compare/bitfinex-vs-htx" }, { "json": "https://www.anchorterminal.com/compare/bitfinex-vs-hyperliquid.json", "title": "Bitfinex API vs Hyperliquid", "url": "https://www.anchorterminal.com/compare/bitfinex-vs-hyperliquid" }, { "json": "https://www.anchorterminal.com/compare/bitfinex-vs-kraken.json", "title": "Bitfinex API vs Kraken API", "url": "https://www.anchorterminal.com/compare/bitfinex-vs-kraken" }, { "json": "https://www.anchorterminal.com/compare/bitfinex-vs-kucoin.json", "title": "Bitfinex API vs KuCoin", "url": "https://www.anchorterminal.com/compare/bitfinex-vs-kucoin" }, { "json": "https://www.anchorterminal.com/compare/bitfinex-vs-mexc.json", "title": "Bitfinex API vs MEXC API", "url": "https://www.anchorterminal.com/compare/bitfinex-vs-mexc" }, { "json": "https://www.anchorterminal.com/compare/bitfinex-vs-okx.json", "title": "Bitfinex API vs OKX API", "url": "https://www.anchorterminal.com/compare/bitfinex-vs-okx" }, { "json": "https://www.anchorterminal.com/compare/bitfinex-vs-uniswap.json", "title": "Bitfinex API vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/bitfinex-vs-uniswap" }, { "json": "https://www.anchorterminal.com/compare/bitget-vs-upbit.json", "title": "Bitget vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/bitget-vs-upbit" }, { "json": "https://www.anchorterminal.com/compare/bithumb-vs-upbit.json", "title": "Bithumb Open API vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/bithumb-vs-upbit" }, { "json": "https://www.anchorterminal.com/compare/bitstamp-vs-upbit.json", "title": "Bitstamp API vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-upbit" }, { "json": "https://www.anchorterminal.com/compare/bybit-vs-upbit.json", "title": "Bybit vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/bybit-vs-upbit" }, { "json": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-upbit.json", "title": "Crypto.com Exchange API vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-upbit" }, { "json": "https://www.anchorterminal.com/compare/deribit-vs-upbit.json", "title": "Deribit vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/deribit-vs-upbit" }, { "json": "https://www.anchorterminal.com/compare/dydx-vs-upbit.json", "title": "dYdX vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/dydx-vs-upbit" }, { "json": "https://www.anchorterminal.com/compare/gate-io-vs-upbit.json", "title": "Gate vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/gate-io-vs-upbit" }, { "json": "https://www.anchorterminal.com/compare/gemini-exchange-vs-upbit.json", "title": "Gemini Exchange API vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/gemini-exchange-vs-upbit" }, { "json": "https://www.anchorterminal.com/compare/htx-vs-upbit.json", "title": "HTX trading API vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/htx-vs-upbit" }, { "json": "https://www.anchorterminal.com/compare/hyperliquid-vs-upbit.json", "title": "Hyperliquid vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/hyperliquid-vs-upbit" }, { "json": "https://www.anchorterminal.com/compare/kucoin-vs-upbit.json", "title": "KuCoin vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/kucoin-vs-upbit" }, { "json": "https://www.anchorterminal.com/compare/mexc-vs-upbit.json", "title": "MEXC API vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/mexc-vs-upbit" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-bitfinex.json", "title": "Binance API vs Bitfinex API", "url": "https://www.anchorterminal.com/compare/binance-vs-bitfinex" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-upbit.json", "title": "Binance API vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/binance-vs-upbit" }, { "json": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-upbit.json", "title": "Coinbase Advanced Trade API vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-upbit" }, { "json": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-upbit.json", "title": "Coinbase MCP server (Coinbase for Agents) vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-upbit" }, { "json": "https://www.anchorterminal.com/compare/kraken-vs-upbit.json", "title": "Kraken API vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/kraken-vs-upbit" }, { "json": "https://www.anchorterminal.com/compare/okx-vs-upbit.json", "title": "OKX API vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/okx-vs-upbit" }, { "json": "https://www.anchorterminal.com/compare/uniswap-vs-upbit.json", "title": "Uniswap Trading API vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/uniswap-vs-upbit" } ], "panel": null, "scores": [ { "bitfinex": 85, "by": 43, "edge": "bitfinex", "key": "reliability", "name": "Reliability", "upbit": 42, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "bitfinex": 48, "by": 18, "edge": "upbit", "key": "schema", "name": "Schema \u0026 documentation", "upbit": 66, "weight": 13 }, { "bitfinex": 61, "by": 9, "edge": "upbit", "key": "ergonomics", "name": "Agent ergonomics", "upbit": 70, "weight": 13 }, { "bitfinex": 62, "by": 3, "edge": "bitfinex", "key": "security", "name": "Security \u0026 auth", "upbit": 59, "weight": 14 }, { "bitfinex": 40, "by": 25, "edge": "bitfinex", "key": "payments", "name": "Payments \u0026 pricing", "upbit": 15, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "bitfinex": 41, "by": 42, "edge": "upbit", "key": "maintenance", "name": "Maintenance \u0026 community", "upbit": 83, "weight": 7 }, { "bitfinex": 49, "by": 5, "edge": "upbit", "key": "transparency", "name": "Transparency \u0026 trust", "upbit": 54, "weight": 7 } ], "summary": "Bitfinex API scores 58.4 (C) on agent readiness against Upbit Open API's 54.7 (C), and leads in 3 of 7 scored categories. Upbit Open API leads on schema \u0026 documentation, agent ergonomics, maintenance \u0026 community and transparency \u0026 trust. Both do exchange market data.", "tasks": null, "tutorials": [], "verdicts": { "bitfinex": "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.", "upbit": "Upbit's Open API has a mandatory IP allow-list, scoped keys with a default withdrawal lock, per-group rate limits with 429 and 418 signalling, an order-test endpoint, official SDKs, a CLI and agent skills with a CONFIRM gate. There is no MCP server, sandbox or status page, and the fees and terms sit on a host our crawler may not read." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/bitfinex-vs-upbit", "json": "https://www.anchorterminal.com/compare/bitfinex-vs-upbit.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/bitfinex-vs-upbit.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/bitfinex-vs-upbit.min.md" }, "markdown": "Bitfinex API scores 58.4 (C) on agent readiness against Upbit Open API's 54.7 (C), and leads in 3 of 7 scored categories. Upbit Open API leads on schema \u0026 documentation, agent ergonomics, maintenance \u0026 community and transparency \u0026 trust. Both do exchange market data.\n\n- Bitfinex API: grade C, 58.4/100, rank #675 of 1349. Markdown https://www.anchorterminal.com/tools/bitfinex.md · JSON https://www.anchorterminal.com/api/v1/tools/bitfinex.json\n- Upbit Open API: grade C, 54.7/100, rank #802 of 1349. Markdown https://www.anchorterminal.com/tools/upbit.md · JSON https://www.anchorterminal.com/api/v1/tools/upbit.json\n- 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## Which one, for what\n\n### Bitfinex API (C)\n\nGood for: An agent trading spot, margin or derivatives, or lending on the funding market, with scoped keys, official clients and paper trading.\n\nAhead on:\n- Reliability, 85 against 42\n- Payments \u0026 pricing, 40 against 15\n\nWatch for: No official MCP server, OpenAPI file or AsyncAPI file; the registry's Bitfinex servers are third parties proxying public market data\n\n### Upbit Open API (C)\n\nGood for: KRW-market trading for agents acting for a verified Korean account, with first-party SDKs, a CLI and skills but no MCP.\n\nAhead on:\n- Schema \u0026 documentation, 66 against 48\n- Agent ergonomics, 70 against 61\n- Maintenance \u0026 community, 83 against 41\n- Transparency \u0026 trust, 54 against 49\n\nWatch for: No MCP server; the agent route is the CLI through skills, which need a terminal\n\n\n## Why the edge\n\n### Reliability: Bitfinex API +43\n\n- 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.\n- Upbit Open API (42): Read with the hosted lines. No status page found on docs.upbit.com or in llms.txt; a wallet-status endpoint and an announcements stream stand in (0). No readable incident history (5). Rate limits documented with numbers per group, per IP and per pocket, updated 7 October 2026 (15). 429 then 418 with a stated block length and a Remaining-Req header, an order-test endpoint and a self-match-prevention default; an order identifier for safe retries was not checked (12 of 15). No SLA found (0). Generally available (10). 0 + 5 + 15 + 12 + 0 + 10 = 42.\n\n### Maintenance \u0026 community: Upbit Open API +42\n\n- 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.\n- Upbit Open API (83): Read as a closed service. SDK v1.1.0 on 20 October 2026 (30). The CLI 1.0.0 on 1 September, the rate-limit update of 7 October, the SDK on 20 October and the path-format notice for 16 November 2026 (20). open-api@upbit.com answers in turn on weekdays per the support notice, notices carry dates, and the six upbit-official repositories show no open issues (12 of 15). Current official SDKs in Python, TypeScript and Go (15). Apache-2.0 repositories pushed in October 2026; CI not checked (6 of 10). 30 + 20 + 12 + 15 + 6 = 83.\n\n### Payments \u0026 pricing: Bitfinex API +25\n\n- Bitfinex API (40): 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- Upbit Open API (15): No machine payment protocol (0). The fee schedule is on upbit.com, which disallows every crawler path, so no price is recorded (0 of 20, unchecked). Public quotation endpoints need no key, card or account; trading needs a verified Korean account. Judgement call (15 of 20). A person must sign up, pass identity checks and issue keys on the PC web site (0). 0 + 0 + 15 + 0 = 15.\n\n### Schema \u0026 documentation: Upbit Open API +18\n\n- 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.\n- Upbit Open API (66): No OpenAPI found; the reference is a readme.io site with a Markdown twin of every page (5 of 25). llms.txt on docs.upbit.com and a kr/llms.txt index (10). Each reference page states what the endpoint does, its group and its errors, with warnings such as market_offline after maintenance (14 of 20). Typed parameters with enums for order type, side and time in force and required flags (11 of 15). Recipes in Python, Java and Node.js and an error format of error.name and error.message with HTTP statuses (13 of 15). Feature versions in page histories (v1.6.1) and dated notices with effective dates, no single API version (13 of 15). 5 + 10 + 14 + 11 + 13 + 13 = 66.\n\n### Agent ergonomics: Upbit Open API +9\n\n- 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.\n- Upbit Open API (70): Graded on the REST API with the CLI. Candle counts, list limits and the CLI's --max-items and --transform size responses (16 of 25). Paging and filters on orders and history (15 of 20). error.name codes to branch on, which the November 2026 notice tells clients to use, and 418 with its block length (15 of 20). An order-test endpoint and a CONFIRM gate in the skills; an order identifier for idempotent placement was not checked (11 of 20). Few required parameters, SDKs in three languages and a CLI, but keys need the PC web site and a registered IP (13 of 15). 16 + 15 + 15 + 11 + 13 = 70.\n\n### Transparency \u0026 trust: Upbit Open API +5\n\n- 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.\n- Upbit Open API (54): The editorial half. A closed service whose user and Open API terms could not be fetched under upbit.com's robots.txt, and whose SDK licence page calls the SDK material not open source while the repositories carry Apache-2.0 (8 of 30). The developer centre's privacy policy names Dunamu Inc., gives retention periods and names Zendesk in Japan; the main privacy policy was not read (14 of 30). Notices with effective dates, including the path-format change and the deprecated Remaining-Req min field (12 of 20). Zendesk and Google Analytics named with a location for the developer centre only (8 of 20). 8 + 14 + 12 + 8 = 42.\n\n## Score by category\n\n| Category | Weight | Bitfinex API | Upbit Open API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 85 | 42 | Bitfinex API +43 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 48 | 66 | Upbit Open API +18 |\n| Agent ergonomics | 13% (16.2 this run) | 61 | 70 | Upbit Open API +9 |\n| Security \u0026 auth | 14% (17.5 this run) | 62 | 59 | Bitfinex API +3 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 15 | Bitfinex API +25 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 41 | 83 | Upbit Open API +42 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 49 | 54 | Upbit Open API +5 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **58.4 · C** | **54.7 · C** | |\n\n## Facts side by side\n\n| Fact | Bitfinex API | Upbit Open API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | iFinex Inc. | Dunamu Inc. |\n| Hosted endpoint | no (local only) | no (local only) |\n| Transports | | |\n| Auth | API key | API key |\n| Pricing | Pay per use | Pay per use |\n| x402 | no | no |\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 | none |\n| Tools exposed | none | 0 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-07-18 | 2026-10-20 |\n| Terms last updated | couldn't be read | no document linked |\n| Privacy policy last updated | couldn't be read | no date given |\n| Customer content may train models | couldn't be read | not read yet |\n| Terms restrict automated access | couldn't be read | not read yet |\n| Terms restrict benchmarking | couldn't be read | not read yet |\n| Terms or service can change without notice | couldn't be read | not read yet |\n| Arbitration or class-action waiver | couldn't be read | not read yet |\n| Popularity | 480 stars | 91 stars |\n\n## Verdicts\n\n**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.\n\n**Upbit Open API.** Upbit's Open API has a mandatory IP allow-list, scoped keys with a default withdrawal lock, per-group rate limits with 429 and 418 signalling, an order-test endpoint, official SDKs, a CLI and agent skills with a CONFIRM gate. There is no MCP server, sandbox or status page, and the fees and terms sit on a host our crawler may not read.\n\n## Before you call either\n\n### Bitfinex API\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### Upbit Open API\n\n1. Ask the person for a key with only the functions the task needs and your server's public IPv4 address registered; a private or unregistered IP is refused\n2. Sign every request with a fresh JWT (HS512, new nonce, SHA512 query hash) and branch on error.name, not error.message\n3. Run POST /v1/orders/test before a live order; it costs nothing and shares the 8-a-second order-test group\n4. Read Remaining-Req and keep orders under 12 a second per pocket; on 429 wait for the next second and on 418 wait out the stated block\n5. Leave the withdrawal safe-lock on unless the person lifts it in the app, and send paths with single slashes and no trailing slash before 16 November 2026\n\n## Questions\n\n### Which is better for AI agents, Bitfinex API or Upbit Open API?\n\nBitfinex API scores 58.4 (C) on agent readiness against Upbit Open API's 54.7 (C), and leads in 3 of 7 scored categories. Upbit Open API leads on schema \u0026 documentation, agent ergonomics, maintenance \u0026 community and transparency \u0026 trust.\n\n### Do Bitfinex API and Upbit Open API need an API key?\n\nBoth need an API key.\n\n### Can an agent call Bitfinex API and Upbit Open API without installing anything?\n\nNo hosted endpoint is listed for Bitfinex API. No hosted endpoint is listed for Upbit Open API.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/bitfinex-vs-upbit.json, and with the fewest tokens: https://www.anchorterminal.com/compare/bitfinex-vs-upbit.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"bitfinex\", \"b\": \"upbit\"}`. From a terminal: `anchor compare bitfinex upbit`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/bitfinex.json and https://www.anchorterminal.com/api/v1/tools/upbit.json\n\n## Other comparisons with Bitfinex API or Upbit Open API\n\n- [Bitfinex API vs Bitget](https://www.anchorterminal.com/compare/bitfinex-vs-bitget.md)\n- [Bitfinex API vs Bithumb Open API](https://www.anchorterminal.com/compare/bitfinex-vs-bithumb.md)\n- [Bitfinex API vs Bitstamp API](https://www.anchorterminal.com/compare/bitfinex-vs-bitstamp.md)\n- [Bitfinex API vs Bybit](https://www.anchorterminal.com/compare/bitfinex-vs-bybit.md)\n- [Bitfinex API vs Coinbase Advanced Trade API](https://www.anchorterminal.com/compare/bitfinex-vs-coinbase-advanced-trade.md)\n- [Bitfinex API vs Coinbase MCP server (Coinbase for Agents)](https://www.anchorterminal.com/compare/bitfinex-vs-coinbase-mcp.md)\n- [Bitfinex API vs Crypto.com Exchange API](https://www.anchorterminal.com/compare/bitfinex-vs-crypto-com-exchange.md)\n- [Bitfinex API vs Deribit](https://www.anchorterminal.com/compare/bitfinex-vs-deribit.md)\n- [Bitfinex API vs dYdX](https://www.anchorterminal.com/compare/bitfinex-vs-dydx.md)\n- [Bitfinex API vs Gate](https://www.anchorterminal.com/compare/bitfinex-vs-gate-io.md)\n- [Bitfinex API vs Gemini Exchange API](https://www.anchorterminal.com/compare/bitfinex-vs-gemini-exchange.md)\n- [Bitfinex API vs HTX trading API](https://www.anchorterminal.com/compare/bitfinex-vs-htx.md)\n- [Bitfinex API vs Hyperliquid](https://www.anchorterminal.com/compare/bitfinex-vs-hyperliquid.md)\n- [Bitfinex API vs Kraken API](https://www.anchorterminal.com/compare/bitfinex-vs-kraken.md)\n- [Bitfinex API vs KuCoin](https://www.anchorterminal.com/compare/bitfinex-vs-kucoin.md)\n- [Bitfinex API vs MEXC API](https://www.anchorterminal.com/compare/bitfinex-vs-mexc.md)\n- [Bitfinex API vs OKX API](https://www.anchorterminal.com/compare/bitfinex-vs-okx.md)\n- [Bitfinex API vs Uniswap Trading API](https://www.anchorterminal.com/compare/bitfinex-vs-uniswap.md)\n- [Bitget vs Upbit Open API](https://www.anchorterminal.com/compare/bitget-vs-upbit.md)\n- [Bithumb Open API vs Upbit Open API](https://www.anchorterminal.com/compare/bithumb-vs-upbit.md)\n- [Bitstamp API vs Upbit Open API](https://www.anchorterminal.com/compare/bitstamp-vs-upbit.md)\n- [Bybit vs Upbit Open API](https://www.anchorterminal.com/compare/bybit-vs-upbit.md)\n- [Crypto.com Exchange API vs Upbit Open API](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-upbit.md)\n- [Deribit vs Upbit Open API](https://www.anchorterminal.com/compare/deribit-vs-upbit.md)\n- [dYdX vs Upbit Open API](https://www.anchorterminal.com/compare/dydx-vs-upbit.md)\n- [Gate vs Upbit Open API](https://www.anchorterminal.com/compare/gate-io-vs-upbit.md)\n- [Gemini Exchange API vs Upbit Open API](https://www.anchorterminal.com/compare/gemini-exchange-vs-upbit.md)\n- [HTX trading API vs Upbit Open API](https://www.anchorterminal.com/compare/htx-vs-upbit.md)\n- [Hyperliquid vs Upbit Open API](https://www.anchorterminal.com/compare/hyperliquid-vs-upbit.md)\n- [KuCoin vs Upbit Open API](https://www.anchorterminal.com/compare/kucoin-vs-upbit.md)\n- [MEXC API vs Upbit Open API](https://www.anchorterminal.com/compare/mexc-vs-upbit.md)\n- [Binance API vs Bitfinex API](https://www.anchorterminal.com/compare/binance-vs-bitfinex.md)\n- [Binance API vs Upbit Open API](https://www.anchorterminal.com/compare/binance-vs-upbit.md)\n- [Coinbase Advanced Trade API vs Upbit Open API](https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-upbit.md)\n- [Coinbase MCP server (Coinbase for Agents) vs Upbit Open API](https://www.anchorterminal.com/compare/coinbase-mcp-vs-upbit.md)\n- [Kraken API vs Upbit Open API](https://www.anchorterminal.com/compare/kraken-vs-upbit.md)\n- [OKX API vs Upbit Open API](https://www.anchorterminal.com/compare/okx-vs-upbit.md)\n- [Uniswap Trading API vs Upbit Open API](https://www.anchorterminal.com/compare/uniswap-vs-upbit.md)\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": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Bitfinex API vs Upbit Open API", "url": "" } ], "description": "Bitfinex scores 58.4 (C) to Upbit Open's 54.7 (C) for exchange market data. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Bitfinex API C 58.4", "Upbit Open API C 54.7", "scores" ], "h1": "Bitfinex API vs Upbit Open API", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/bitfinex-vs-upbit", "published": "2026-10-01", "section": "tools", "title": "Bitfinex vs Upbit Open for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-04", "url": "https://www.anchorterminal.com/compare/bitfinex-vs-upbit" }, "tokens": { "markdown": 4800, "slim": 2630 }, "version": 1 }