{ "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": 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" ], "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-04T20:04:41.688156046Z" }, "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-04T20:04:41.688156046Z" } }, "answer": "Bitfinex API scores 58.4 (C) on agent readiness against MEXC API's 56.3 (C), and leads in 2 of 7 scored categories. MEXC API leads on schema \u0026 documentation, maintenance \u0026 community and transparency \u0026 trust.", "b": { "slug": "mexc", "name": "MEXC API", "vendor": "MEXC (Comoros) Ltd", "vendorUrl": "https://www.mexc.com/mexc-api", "kind": "http-api", "category": "crypto-exchanges", "summary": "MEXC's spot and futures API gives programmatic access to market data, orders, balances, transfers and withdrawals over REST and WebSocket, with an official command-line tool that also runs as a local MCP server for AI agents.", "url": "https://www.anchorterminal.com/tools/mexc", "markdownUrl": "https://www.anchorterminal.com/tools/mexc.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/mexc.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/mexc.json", "dns": "mexc.grade.anchorterminal.com", "repo": "https://github.com/mexcdevelop", "transports": [ "stdio" ], "packages": [ { "registry": "npm", "name": "@mexc-ai/cli" } ], "auth": "api-key", "authNotes": "API keys made at mexc.com/user/openapi after a browser sign-up; the futures API also needs identity verification. The key goes in the X-MEXC-APIKEY header and signed endpoints carry an HMAC SHA256 signature with a timestamp and a recvWindow of up to 60 seconds. Permissions are granular (SPOT_ACCOUNT_READ, SPOT_DEAL_WRITE, SPOT_WITHDRAW_WRITE, SPOT_TRANSFER_WRITE and the futures equivalents), a key can be limited to chosen trading pairs and linked to up to 10 IP addresses, and a key with no linked IP is valid for 90 days and can be renewed for 90 more from 5 days before expiry. Up to 30 keys per account (https://www.mexc.com/api-docs/spot-v3/introduction, checked 2026-11-03).", "pricing": "usage", "pricingNotes": "Trading fees per fill. MEXC's own fee guide of 20 October 2026 gives spot 0 per cent maker and 0.05 per cent taker (0.04 per cent with MX deduction), futures from 0 per cent maker and 0.02 per cent taker on BTCUSDT to 0.01 and 0.04 per cent on standard contracts, and a separate API futures schedule of 0.06 per cent maker and 0.08 per cent taker since 1 June 2026. Zero-fee campaigns and MX discounts don't apply to API trading. The fee page itself is drawn by script. Market data needs no key (https://www.mexc.com/learn/article/17827791510370, checked 2026-11-03).", "priceSummary": "0.05% fee", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the API docs, the CLI docs, llms.txt or the terms (checked 2026-11-03). Fees are taken from each fill.", "endpoints": [] }, "toolCount": 299, "popularity": { "githubStars": 315, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://www.mexc.com/api-docs/spot-v3/introduction", "llmsTxt": "https://www.mexc.com/llms.txt", "capabilities": [ "exchange.market-data", "exchange.spot-trading", "exchange.derivatives", "exchange.balances", "exchange.transfers", "market.crypto" ], "tags": [ "hosted", "api-key", "closed-source", "usage-priced", "mcp", "cli", "agent-skills", "read-only-mode", "llms-txt", "python", "java", "go", "no-status-page" ], "lastRelease": "2026-10-23", "graded": true, "anchor": { "graded": true, "score": 56.3, "grade": "C", "agentReady": false, "rank": 791, "ranked": true, "rankOf": 1349, "categoryRank": 13, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 64, "maintenance": 75, "payments": 31, "reliability": 43, "schema": 64, "security": 65, "transparency": 58 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-03" }, "negative": 0, "verdict": "MEXC publishes granular key permissions, per-pair key limits, weighted rate limits with Retry-After and a dated changelog, and its official CLI runs a read-only-capable MCP server with confirmation before any fund movement. There is no sandbox or status page, API futures orders pay a higher fee schedule, and the user agreement excludes the US, UK, EU members and others.", "bestFor": "Spot and futures for agents in served countries that want a vendor-built MCP server with read-only and confirmation modes.", "strengths": [ "Granular key permissions (account read, trade, withdraw, transfer), per-pair restriction, up to 10 linked IPs and a 90-day expiry for unbound keys", "An official MCP mode in the `@mexc-ai/cli` tool with `--read-only`, a read-only market subset of 22 tools and a confirmation step before orders and transfers", "Rate limits published as weight buckets per IP and UID, with Retry-After on 429 and 418", "A dated changelog of 72 spot and 26 futures entries, the newest 23 October 2026", "Fees published on MEXC's own pages, with the API futures schedule stated separately" ], "weaknesses": [ "No sandbox or testnet; only an order-validation endpoint", "No status page, incident history or SLA", "The MCP server is local only, not in the official MCP registry, and the CLI is UNLICENSED with no public source", "API futures orders pay 0.06 per cent maker and 0.08 per cent taker, and zero-fee campaigns exclude API trading", "The user agreement bars users in the United States, the United Kingdom, Mainland China, Singapore, Hong Kong, Canada, France and other jurisdictions" ], "agentNotes": [ "Use a key limited to SPOT_ACCOUNT_READ and SPOT_DEAL_WRITE, the pairs you trade and your IP addresses; keys without a linked IP expire after 90 days", "Start the MCP server as `mexc mcp spot --read-only` unless the task trades, and never pass `--yes`; orders and transfers wait for the person's confirmation", "Call POST /api/v3/order/test before a live order, since there is no sandbox", "On 429 or 418 wait for Retry-After; order placement and cancellation share 12 requests a second per UID, and repeated breaches ban the IP for up to 3 days", "Treat a 5xx on an order as unknown, not failed, and query the order before retrying; set newClientOrderId so the order can be found" ], "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": 56.3 } ], "editorialScores": { "ergonomics": 64, "maintenance": 75, "payments": 31, "reliability": 43, "schema": 64, "security": 65, "transparency": 38 }, "provenanceScore": 78, "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 @mexc-ai/cli", "http": "curl 'https://api.mexc.com/api/v3/ticker/price?symbol=BTCUSDT'", "config": { "mcpServers": { "mexc-spot": { "args": [ "mcp", "spot", "--read-only" ], "command": "mexc" } } } }, "letme": { "capability": "https://letme.dev/exchange.market-data", "tool": "https://letme.dev/mexc" }, "area": "payments", "unitPrices": [ { "item": "Spot taker fee", "unit": "pct", "usd": 0.05, "note": "maker 0 per cent; 0.04 per cent with MX deduction, not for API trading" }, { "item": "API futures taker fee", "unit": "pct", "usd": 0.08, "note": "maker 0.06 per cent, since 1 June 2026, outside the Innovation Zone" } ], "provenance": { "legalEntity": "MEXC (Comoros) Ltd", "domain": "mexc.com", "domainRegistered": "2000-02-27", "endpointOnVendorDomain": true, "terms": "https://www.mexc.com/terms", "privacy": "https://www.mexc.com/privacypolicy", "statusPage": "", "changelog": "https://www.mexc.com/api-docs/spot-v3/change-log", "securityTxt": "none", "checked": "2026-11-03", "notes": [ "MEXC (Comoros) Ltd is named in the user agreement, last updated 13 October 2026, with a registered address in Mutsamudu, Anjouan. The privacy policy, last updated 1 June 2026, names no entity.", "RDAP gives mexc.com a registration date of 27 February 2000; the exchange says it began in 2018, so the domain predates it.", "www.mexc.com/robots.txt allows the root and disallows /user/, /orders/ and some locale paths; it lists llms.txt as a sitemap. mexcdevelop.github.io has no robots.txt.", "https://www.mexc.com/.well-known/security.txt answered 404. status.mexc.com does not resolve; no status page was found.", "The fee page at mexc.com/fee is drawn by script; the fee figures come from MEXC's own fee guide and a 2024 announcement." ], "score": 78 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/mexc.json", "live": { "slug": "mexc", "securityTxt": { "url": "https://mexc.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-04T15:54:36.213483882Z" }, "updatedAt": "2026-11-04T15:54:36.213483882Z" } }, "edges": [ { "by": 42, "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; status.mexc.com does not resolve and llms.txt points to a maintenance-updates feed (0). No readable incident history (5). Rate limits documented with numbers, 300 weight per 10 seconds per IP, 500 per UID, 12 order requests a second per UID, 100 WebSocket messages a second (15). 429 and 418 carry Retry-After with ban lengths stated, a 5xx is to be treated as unknown rather than failed, an order-test endpoint exists, and newClientOrderId is optional with no idempotency promise (13 of 15). No SLA found (0). Spot and futures are generally available, futures order placement having reopened on 31 March 2026 after being closed since July 2022 (10). 0 + 5 + 15 + 13 + 0 + 10 = 43." }, "scores": { "a": 85, "b": 43 } }, { "by": 34, "category": "maintenance", "leads": "mexc", "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. Last dated change 23 October 2026 in both the spot and futures logs (30). Spot entries on 14 August, 24 August, 11 September and 23 October 2026, futures on 1 September, 11 September, 19 October and 23 October (20). An API support Telegram group, a ticket form and dated changelogs; GitHub issues not read (10 of 15). The official SDK repository was last pushed in February 2024 while the CLI is current (10 of 15). The CLI ships platform binaries with no dependencies and no public repository or CI; the SDK is stale (5 of 10). 30 + 20 + 10 + 10 + 5 = 75." }, "scores": { "a": 41, "b": 75 } }, { "by": 16, "category": "schema", "leads": "mexc", "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; a Postman collection and the CLI's 25 capability reference files are the nearest machine-readable contract (5 of 25). llms.txt on mexc.com, written for assistants and pointing at the API docs and legal pages (7 of 10). Per-endpoint pages with purpose, parameters and permissions, without when-not-to-use guidance (13 of 20). Typed parameters with enums for order types, statuses and intervals (11 of 15). Examples on each endpoint and a separate error-code page with numeric codes and messages (13 of 15). Versioned API (v3) with a dated changelog of 72 entries to 23 October 2026 (15). 5 + 7 + 13 + 11 + 13 + 15 = 64." }, "scores": { "a": 48, "b": 64 } }, { "by": 9, "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). Fees published without login on MEXC's own fee guide (20 October 2026) and a 2024 announcement, with a separate API futures schedule; the fee page itself is drawn by script (16 of 20). Public market data needs no key or card; trading needs a verified and funded account. Judgement call (15 of 20). A person must sign up in a browser, and futures need identity verification (0). 0 + 16 + 15 + 0 = 31." }, "scores": { "a": 40, "b": 31 } }, { "by": 9, "category": "transparency", "leads": "mexc", "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 with a dated user agreement naming MEXC (Comoros) Ltd; the CLI is UNLICENSED on npm (15 of 30). The privacy policy names no entity, states no retention periods and relies on standard contractual clauses for transfers (10 of 30). The changelog flags endpoints as \"will be discontinued soon\" without dates and the futures log records removals (8 of 20). Third parties are named by category only, with no subprocessor list or data locations (5 of 20). 15 + 10 + 8 + 5 = 38." }, "scores": { "a": 49, "b": 58 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "iFinex Inc.", "b": "MEXC (Comoros) Ltd", "name": "Vendor" }, { "a": "no (local only)", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "", "b": "stdio", "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": "299", "name": "Tools exposed" }, { "a": "no", "b": "yes", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-07-18", "b": "2026-10-23", "name": "Last release" }, { "a": "couldn't be read", "b": "2026-10-13", "name": "Terms last updated" }, { "a": "couldn't be read", "b": "2026-06-01", "name": "Privacy policy last updated" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "couldn't be read", "b": "yes", "name": "Terms restrict automated access" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "couldn't be read", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "couldn't be read", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "480 stars", "b": "315 stars", "name": "Popularity" } ], "faq": [ { "answer": "Bitfinex API scores 58.4 (C) on agent readiness against MEXC API's 56.3 (C), and leads in 2 of 7 scored categories. MEXC API leads on schema \u0026 documentation, maintenance \u0026 community and transparency \u0026 trust.", "question": "Which is better for AI agents, Bitfinex API or MEXC API?" }, { "answer": "Both need an API key.", "question": "Do Bitfinex API and MEXC API need an API key?" }, { "answer": "No hosted endpoint is listed for Bitfinex API. MEXC API runs on your own machine, with no hosted endpoint listed.", "question": "Can an agent call Bitfinex API and MEXC API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 85 against 43", "Payments \u0026 pricing, 40 against 31" ], "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, 64 against 48", "Maintenance \u0026 community, 75 against 41", "Transparency \u0026 trust, 58 against 49" ], "also": [ "Runs on your own machine" ], "goodFor": "Spot and futures for agents in served countries that want a vendor-built MCP server with read-only and confirmation modes.", "slug": "mexc", "watchFor": "No sandbox or testnet; only an order-validation endpoint" } ], "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-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/bitfinex-vs-upbit.json", "title": "Bitfinex API vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/bitfinex-vs-upbit" }, { "json": "https://www.anchorterminal.com/compare/bitget-vs-mexc.json", "title": "Bitget vs MEXC API", "url": "https://www.anchorterminal.com/compare/bitget-vs-mexc" }, { "json": "https://www.anchorterminal.com/compare/bithumb-vs-mexc.json", "title": "Bithumb Open API vs MEXC API", "url": "https://www.anchorterminal.com/compare/bithumb-vs-mexc" }, { "json": "https://www.anchorterminal.com/compare/bitstamp-vs-mexc.json", "title": "Bitstamp API vs MEXC API", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-mexc" }, { "json": "https://www.anchorterminal.com/compare/bybit-vs-mexc.json", "title": "Bybit vs MEXC API", "url": "https://www.anchorterminal.com/compare/bybit-vs-mexc" }, { "json": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-mexc.json", "title": "Crypto.com Exchange API vs MEXC API", "url": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-mexc" }, { "json": "https://www.anchorterminal.com/compare/gate-io-vs-mexc.json", "title": "Gate vs MEXC API", "url": "https://www.anchorterminal.com/compare/gate-io-vs-mexc" }, { "json": "https://www.anchorterminal.com/compare/gemini-exchange-vs-mexc.json", "title": "Gemini Exchange API vs MEXC API", "url": "https://www.anchorterminal.com/compare/gemini-exchange-vs-mexc" }, { "json": "https://www.anchorterminal.com/compare/htx-vs-mexc.json", "title": "HTX trading API vs MEXC API", "url": "https://www.anchorterminal.com/compare/htx-vs-mexc" }, { "json": "https://www.anchorterminal.com/compare/kucoin-vs-mexc.json", "title": "KuCoin vs MEXC API", "url": "https://www.anchorterminal.com/compare/kucoin-vs-mexc" }, { "json": "https://www.anchorterminal.com/compare/mexc-vs-okx.json", "title": "MEXC API vs OKX API", "url": "https://www.anchorterminal.com/compare/mexc-vs-okx" }, { "json": "https://www.anchorterminal.com/compare/mexc-vs-uniswap.json", "title": "MEXC API vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/mexc-vs-uniswap" }, { "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-mexc.json", "title": "Binance API vs MEXC API", "url": "https://www.anchorterminal.com/compare/binance-vs-mexc" }, { "json": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-mexc.json", "title": "Coinbase Advanced Trade API vs MEXC API", "url": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-mexc" }, { "json": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-mexc.json", "title": "Coinbase MCP server (Coinbase for Agents) vs MEXC API", "url": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-mexc" }, { "json": "https://www.anchorterminal.com/compare/kraken-vs-mexc.json", "title": "Kraken API vs MEXC API", "url": "https://www.anchorterminal.com/compare/kraken-vs-mexc" }, { "json": "https://www.anchorterminal.com/compare/deribit-vs-mexc.json", "title": "Deribit vs MEXC API", "url": "https://www.anchorterminal.com/compare/deribit-vs-mexc" }, { "json": "https://www.anchorterminal.com/compare/dydx-vs-mexc.json", "title": "dYdX vs MEXC API", "url": "https://www.anchorterminal.com/compare/dydx-vs-mexc" }, { "json": "https://www.anchorterminal.com/compare/hyperliquid-vs-mexc.json", "title": "Hyperliquid vs MEXC API", "url": "https://www.anchorterminal.com/compare/hyperliquid-vs-mexc" } ], "panel": null, "scores": [ { "bitfinex": 85, "by": 42, "edge": "bitfinex", "key": "reliability", "mexc": 43, "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "bitfinex": 48, "by": 16, "edge": "mexc", "key": "schema", "mexc": 64, "name": "Schema \u0026 documentation", "weight": 13 }, { "bitfinex": 61, "by": 3, "edge": "mexc", "key": "ergonomics", "mexc": 64, "name": "Agent ergonomics", "weight": 13 }, { "bitfinex": 62, "by": 3, "edge": "mexc", "key": "security", "mexc": 65, "name": "Security \u0026 auth", "weight": 14 }, { "bitfinex": 40, "by": 9, "edge": "bitfinex", "key": "payments", "mexc": 31, "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "bitfinex": 41, "by": 34, "edge": "mexc", "key": "maintenance", "mexc": 75, "name": "Maintenance \u0026 community", "weight": 7 }, { "bitfinex": 49, "by": 9, "edge": "mexc", "key": "transparency", "mexc": 58, "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Bitfinex API scores 58.4 (C) on agent readiness against MEXC API's 56.3 (C), and leads in 2 of 7 scored categories. MEXC API leads on schema \u0026 documentation, 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.", "mexc": "MEXC publishes granular key permissions, per-pair key limits, weighted rate limits with Retry-After and a dated changelog, and its official CLI runs a read-only-capable MCP server with confirmation before any fund movement. There is no sandbox or status page, API futures orders pay a higher fee schedule, and the user agreement excludes the US, UK, EU members and others." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/bitfinex-vs-mexc", "json": "https://www.anchorterminal.com/compare/bitfinex-vs-mexc.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/bitfinex-vs-mexc.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/bitfinex-vs-mexc.min.md" }, "markdown": "Bitfinex API scores 58.4 (C) on agent readiness against MEXC API's 56.3 (C), and leads in 2 of 7 scored categories. MEXC API leads on schema \u0026 documentation, maintenance \u0026 community and transparency \u0026 trust. Both do exchange market data.\n\n- Bitfinex API: grade C, 58.4/100, rank #687 of 1349. Markdown https://www.anchorterminal.com/tools/bitfinex.md · JSON https://www.anchorterminal.com/api/v1/tools/bitfinex.json\n- MEXC API: grade C, 56.3/100, rank #791 of 1349. Markdown https://www.anchorterminal.com/tools/mexc.md · JSON https://www.anchorterminal.com/api/v1/tools/mexc.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 43\n- Payments \u0026 pricing, 40 against 31\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### MEXC API (C)\n\nGood for: Spot and futures for agents in served countries that want a vendor-built MCP server with read-only and confirmation modes.\n\nAhead on:\n- Schema \u0026 documentation, 64 against 48\n- Maintenance \u0026 community, 75 against 41\n- Transparency \u0026 trust, 58 against 49\n\nAlso in its favour:\n- Runs on your own machine\n\nWatch for: No sandbox or testnet; only an order-validation endpoint\n\n\n## Why the edge\n\n### Reliability: Bitfinex API +42\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- MEXC API (43): Read with the hosted lines. No status page found; status.mexc.com does not resolve and llms.txt points to a maintenance-updates feed (0). No readable incident history (5). Rate limits documented with numbers, 300 weight per 10 seconds per IP, 500 per UID, 12 order requests a second per UID, 100 WebSocket messages a second (15). 429 and 418 carry Retry-After with ban lengths stated, a 5xx is to be treated as unknown rather than failed, an order-test endpoint exists, and newClientOrderId is optional with no idempotency promise (13 of 15). No SLA found (0). Spot and futures are generally available, futures order placement having reopened on 31 March 2026 after being closed since July 2022 (10). 0 + 5 + 15 + 13 + 0 + 10 = 43.\n\n### Maintenance \u0026 community: MEXC API +34\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- MEXC API (75): Read as a closed service. Last dated change 23 October 2026 in both the spot and futures logs (30). Spot entries on 14 August, 24 August, 11 September and 23 October 2026, futures on 1 September, 11 September, 19 October and 23 October (20). An API support Telegram group, a ticket form and dated changelogs; GitHub issues not read (10 of 15). The official SDK repository was last pushed in February 2024 while the CLI is current (10 of 15). The CLI ships platform binaries with no dependencies and no public repository or CI; the SDK is stale (5 of 10). 30 + 20 + 10 + 10 + 5 = 75.\n\n### Schema \u0026 documentation: MEXC API +16\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- MEXC API (64): No OpenAPI found; a Postman collection and the CLI's 25 capability reference files are the nearest machine-readable contract (5 of 25). llms.txt on mexc.com, written for assistants and pointing at the API docs and legal pages (7 of 10). Per-endpoint pages with purpose, parameters and permissions, without when-not-to-use guidance (13 of 20). Typed parameters with enums for order types, statuses and intervals (11 of 15). Examples on each endpoint and a separate error-code page with numeric codes and messages (13 of 15). Versioned API (v3) with a dated changelog of 72 entries to 23 October 2026 (15). 5 + 7 + 13 + 11 + 13 + 15 = 64.\n\n### Payments \u0026 pricing: Bitfinex API +9\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- MEXC API (31): No machine payment protocol (0). Fees published without login on MEXC's own fee guide (20 October 2026) and a 2024 announcement, with a separate API futures schedule; the fee page itself is drawn by script (16 of 20). Public market data needs no key or card; trading needs a verified and funded account. Judgement call (15 of 20). A person must sign up in a browser, and futures need identity verification (0). 0 + 16 + 15 + 0 = 31.\n\n### Transparency \u0026 trust: MEXC API +9\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- MEXC API (58): The editorial half. A closed service with a dated user agreement naming MEXC (Comoros) Ltd; the CLI is UNLICENSED on npm (15 of 30). The privacy policy names no entity, states no retention periods and relies on standard contractual clauses for transfers (10 of 30). The changelog flags endpoints as \"will be discontinued soon\" without dates and the futures log records removals (8 of 20). Third parties are named by category only, with no subprocessor list or data locations (5 of 20). 15 + 10 + 8 + 5 = 38.\n\n## Score by category\n\n| Category | Weight | Bitfinex API | MEXC API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 85 | 43 | Bitfinex API +42 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 48 | 64 | MEXC API +16 |\n| Agent ergonomics | 13% (16.2 this run) | 61 | 64 | MEXC API +3 |\n| Security \u0026 auth | 14% (17.5 this run) | 62 | 65 | MEXC API +3 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 31 | Bitfinex API +9 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 41 | 75 | MEXC API +34 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 49 | 58 | MEXC API +9 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **58.4 · C** | **56.3 · C** | |\n\n## Facts side by side\n\n| Fact | Bitfinex API | MEXC API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | iFinex Inc. | MEXC (Comoros) Ltd |\n| Hosted endpoint | no (local only) | no (local only) |\n| Transports | | stdio |\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 | 299 |\n| Read-only variant documented | no | yes |\n| llms.txt | yes | yes |\n| Last release | 2026-07-18 | 2026-10-23 |\n| Terms last updated | couldn't be read | 2026-10-13 |\n| Privacy policy last updated | couldn't be read | 2026-06-01 |\n| Customer content may train models | couldn't be read | not found in the text |\n| Terms restrict automated access | couldn't be read | yes |\n| Terms restrict benchmarking | couldn't be read | not found in the text |\n| Terms or service can change without notice | couldn't be read | yes |\n| Arbitration or class-action waiver | couldn't be read | yes |\n| Popularity | 480 stars | 315 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**MEXC API.** MEXC publishes granular key permissions, per-pair key limits, weighted rate limits with Retry-After and a dated changelog, and its official CLI runs a read-only-capable MCP server with confirmation before any fund movement. There is no sandbox or status page, API futures orders pay a higher fee schedule, and the user agreement excludes the US, UK, EU members and others.\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### MEXC API\n\n1. Use a key limited to SPOT_ACCOUNT_READ and SPOT_DEAL_WRITE, the pairs you trade and your IP addresses; keys without a linked IP expire after 90 days\n2. Start the MCP server as `mexc mcp spot --read-only` unless the task trades, and never pass `--yes`; orders and transfers wait for the person's confirmation\n3. Call POST /api/v3/order/test before a live order, since there is no sandbox\n4. On 429 or 418 wait for Retry-After; order placement and cancellation share 12 requests a second per UID, and repeated breaches ban the IP for up to 3 days\n5. Treat a 5xx on an order as unknown, not failed, and query the order before retrying; set newClientOrderId so the order can be found\n\n## Questions\n\n### Which is better for AI agents, Bitfinex API or MEXC API?\n\nBitfinex API scores 58.4 (C) on agent readiness against MEXC API's 56.3 (C), and leads in 2 of 7 scored categories. MEXC API leads on schema \u0026 documentation, maintenance \u0026 community and transparency \u0026 trust.\n\n### Do Bitfinex API and MEXC API need an API key?\n\nBoth need an API key.\n\n### Can an agent call Bitfinex API and MEXC API without installing anything?\n\nNo hosted endpoint is listed for Bitfinex API. MEXC API runs on your own machine, with no hosted endpoint listed.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/bitfinex-vs-mexc.json, and with the fewest tokens: https://www.anchorterminal.com/compare/bitfinex-vs-mexc.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"bitfinex\", \"b\": \"mexc\"}`. From a terminal: `anchor compare bitfinex mexc`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/bitfinex.json and https://www.anchorterminal.com/api/v1/tools/mexc.json\n\n## Other comparisons with Bitfinex API or MEXC 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 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- [Bitfinex API vs Upbit Open API](https://www.anchorterminal.com/compare/bitfinex-vs-upbit.md)\n- [Bitget vs MEXC API](https://www.anchorterminal.com/compare/bitget-vs-mexc.md)\n- [Bithumb Open API vs MEXC API](https://www.anchorterminal.com/compare/bithumb-vs-mexc.md)\n- [Bitstamp API vs MEXC API](https://www.anchorterminal.com/compare/bitstamp-vs-mexc.md)\n- [Bybit vs MEXC API](https://www.anchorterminal.com/compare/bybit-vs-mexc.md)\n- [Crypto.com Exchange API vs MEXC API](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-mexc.md)\n- [Gate vs MEXC API](https://www.anchorterminal.com/compare/gate-io-vs-mexc.md)\n- [Gemini Exchange API vs MEXC API](https://www.anchorterminal.com/compare/gemini-exchange-vs-mexc.md)\n- [HTX trading API vs MEXC API](https://www.anchorterminal.com/compare/htx-vs-mexc.md)\n- [KuCoin vs MEXC API](https://www.anchorterminal.com/compare/kucoin-vs-mexc.md)\n- [MEXC API vs OKX API](https://www.anchorterminal.com/compare/mexc-vs-okx.md)\n- [MEXC API vs Uniswap Trading API](https://www.anchorterminal.com/compare/mexc-vs-uniswap.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 MEXC API](https://www.anchorterminal.com/compare/binance-vs-mexc.md)\n- [Coinbase Advanced Trade API vs MEXC API](https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-mexc.md)\n- [Coinbase MCP server (Coinbase for Agents) vs MEXC API](https://www.anchorterminal.com/compare/coinbase-mcp-vs-mexc.md)\n- [Kraken API vs MEXC API](https://www.anchorterminal.com/compare/kraken-vs-mexc.md)\n- [Deribit vs MEXC API](https://www.anchorterminal.com/compare/deribit-vs-mexc.md)\n- [dYdX vs MEXC API](https://www.anchorterminal.com/compare/dydx-vs-mexc.md)\n- [Hyperliquid vs MEXC API](https://www.anchorterminal.com/compare/hyperliquid-vs-mexc.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 MEXC API", "url": "" } ], "description": "Bitfinex scores 58.4 (C) to MEXC's 56.3 (C) for exchange market data. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Bitfinex API C 58.4", "MEXC API C 56.3", "scores" ], "h1": "Bitfinex API vs MEXC API", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/bitfinex-vs-mexc", "published": "2026-10-01", "section": "tools", "title": "Bitfinex vs MEXC for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-03", "url": "https://www.anchorterminal.com/compare/bitfinex-vs-mexc" }, "tokens": { "markdown": 4450, "slim": 2330 }, "version": 1 }