{ "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 Bitstamp API's 50.4 (D), and leads in 5 of 7 scored categories.", "b": { "slug": "bitstamp", "name": "Bitstamp API", "vendor": "Bitstamp Ltd.", "vendorUrl": "https://www.bitstamp.net", "kind": "http-api", "category": "crypto-exchanges", "summary": "Bitstamp's HTTP API v2 for spot and derivatives trading, balances, deposits and withdrawals, with WebSocket and FIX feeds and a sandbox at sandbox.bitstamp.net. Bitstamp is a Robinhood company since June 2025.", "url": "https://www.anchorterminal.com/tools/bitstamp", "markdownUrl": "https://www.anchorterminal.com/tools/bitstamp.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/bitstamp.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/bitstamp.json", "dns": "bitstamp.grade.anchorterminal.com", "license": "Proprietary hosted API under Bitstamp's terms of use, which our reader couldn't load", "transports": [], "packages": [], "auth": "api-key", "authNotes": "API key and secret made in the Bitstamp account after a browser signup, sent as `X-Auth: BITSTAMP {key}` with an HMAC-SHA256 `X-Auth-Signature` over the verb, host, path, query, nonce, timestamp and body, a 36-character single-use nonce and a timestamp within 150 seconds. Keys carry per-endpoint permissions (error API0003 names a missing permission) and an IP allow-list (API0002), and `X-Auth-Subaccount-Id` targets a sub-account. `POST /api/v2/revoke_all_api_keys/` is a kill switch for every key. Responses carry an `X-Server-Auth-Signature` to verify (https://www.bitstamp.net/api/, checked 2026-11-03).", "pricing": "usage", "pricingNotes": "The API itself costs nothing. Trading fees are maker and taker by 30-day volume per the API's fees endpoints, but the fee schedule page at bitstamp.net/fee-schedule/ draws its table by script and loaded empty for our reader, so the rates are unchecked. Commercial use of exchange data needs a Data License Agreement through partners@bitstamp.net. The sandbox at sandbox.bitstamp.net needs no money (https://www.bitstamp.net/api/, checked 2026-11-03).", "priceSummary": "Pay per use", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the API documentation (checked 2026-11-03). Fees are taken from the account; onboarding is a browser signup.", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://www.bitstamp.net/api/", "capabilities": [ "exchange.market-data", "exchange.spot-trading", "exchange.derivatives", "exchange.balances", "exchange.transfers", "exchange.staking", "market.crypto" ], "tags": [ "official", "hosted", "api-key", "sandbox", "status-page", "usage-priced", "eu", "uk" ], "lastRelease": "2026-08-28", "graded": true, "anchor": { "graded": true, "score": 50.4, "grade": "D", "agentReady": false, "rank": 942, "ranked": true, "rankOf": 1349, "categoryRank": 18, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 58, "maintenance": 28, "payments": 20, "reliability": 63, "schema": 51, "security": 60, "transparency": 53 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "low", "date": "2026-11-03" }, "negative": 0, "verdict": "Bitstamp documents its v2 API on one static page with numeric rate limits, per-endpoint key permissions, an IP allow-list, a kill switch and a sandbox. There is no official MCP server, duplicate client order ids are allowed, and the fee schedule, terms, privacy policy and country list render by script and could not be read.", "bestFor": "An agent that needs a long-running regulated spot venue in the EU, UK and US with a sandbox and per-endpoint key permissions, and can do its own signing.", "strengths": [ "Rate limits with numbers (400 requests a second, 10,000 per 10 minutes) and named error codes for client and market limits", "Keys carry per-endpoint permissions and an IP allow-list, and one call revokes every key on the account", "A sandbox at sandbox.bitstamp.net with the same v2 paths, plus order-data endpoints to recover gaps after a dropped WebSocket", "A dated API changelog from 2023 to 28 August 2026 and a Statuspage feed with per-market incidents", "Signed responses (`X-Server-Auth-Signature`) let a client verify what the server returned" ], "weaknesses": [ "No official MCP server, SDK, llms.txt or OpenAPI file; the registry's Bitstamp servers are third parties proxying public market data", "Duplicate client order ids are allowed since November 2023, so a retried order can execute twice", "The fee schedule, terms of use, privacy policy, about page and FAQ load empty without a browser, so fees, retention and the bot clauses are unchecked", "A 3-hour withdrawal failure across 14 networks on 21 August 2026 and a 39-minute halt of all markets on 5 August 2026", "security.txt expired on 12 July 2026, and no SLA was found" ], "agentNotes": [ "Mint a key with only the endpoint permissions the task needs and an IP allow-list; keep `revoke_all_api_keys` in reach as a kill switch", "Treat `client_order_id` as a label, not a guard. On a timeout (500.016) fetch the order by client id before resending, because duplicates are accepted", "Use a fresh 36-character nonce and a timestamp within 150 seconds of server time on every request, or expect API0004 and API0017", "Stay under 400 requests a second and 10,000 per 10 minutes; 400.002 and 400.067 mean back off, and open-orders answers are cached for 10 seconds", "Start on sandbox.bitstamp.net with the same paths, and read the fee schedule in a browser before quoting costs, since it is unreadable to a plain fetch" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "low", "grade": "D", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 50.4 } ], "editorialScores": { "ergonomics": 58, "maintenance": 28, "payments": 20, "reliability": 63, "schema": 51, "security": 60, "transparency": 16 }, "provenanceScore": 90, "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": { "http": "curl https://www.bitstamp.net/api/v2/ticker/btcusd/" }, "letme": { "capability": "https://letme.dev/exchange.market-data", "tool": "https://letme.dev/bitstamp" }, "area": "payments", "provenance": { "legalEntity": "Bitstamp Ltd.", "domain": "bitstamp.net", "domainRegistered": "2011-07-04", "endpointOnVendorDomain": true, "terms": "https://www.bitstamp.net/terms-of-use/", "privacy": "https://www.bitstamp.net/privacy-policy/", "statusPage": "https://status.bitstamp.net", "changelog": "https://www.bitstamp.net/api/", "securityTxt": "expired", "checked": "2026-11-03", "notes": [ "Bitstamp Ltd. is named in Robinhood's newsroom post of 2 June 2025 on closing the acquisition; the terms of use and privacy policy pages loaded empty for our reader, so the entities they name are unconfirmed.", "RDAP gives bitstamp.net a registration date of 4 July 2011.", "https://www.bitstamp.net/.well-known/security.txt names HackerOne's Robinhood programme as Contact and Policy and expired on 12 July 2026.", "www.bitstamp.net/robots.txt allows /api/ itself and disallows /api/*, /account/, /trade/ and others; only /api/ was read under it. status.bitstamp.net disallows /api/ and /embed/, so the history feed was read. support.bitstamp.net did not resolve.", "The API changelog is a section of the API documentation page; there is no separate changelog URL." ], "score": 90 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/bitstamp.json", "live": { "slug": "bitstamp", "vendorStatus": { "page": "https://status.bitstamp.net", "indicator": "minor", "summary": "Partially Degraded Service", "checkedAt": "2026-11-04T21:25:16.463949619Z" }, "securityTxt": { "url": "https://bitstamp.net/.well-known/security.txt", "state": "expired", "expires": "2026-07-12T11:59:00.000Z", "checkedAt": "2026-11-04T15:53:31.314157297Z" }, "updatedAt": "2026-11-04T21:25:16.463949619Z" } }, "edges": [ { "by": 22, "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 on the HTTP API v2 at www.bitstamp.net/api/v2/. status.bitstamp.net is a Statuspage site with component history (20). Its feed for 5 August to 3 November 2026 has 17 entries, among them withdrawals failing on 14 networks for about 3 hours on 21 August, database maintenance with login failures and intermittent trading interruptions for about 1 hour 44 minutes on 23 September, a 39-minute halt of all markets on 5 August, and delistings and single-asset suspensions. One major (10). Rate limits with numbers, 400 a second and 10,000 per 10 minutes (15). Limit errors are named (400.002, 400.067, 400.068) but there is no Retry-After or backoff guidance, duplicate client order ids are allowed, and the only retry guidance is to check the order after a 500.016 timeout (8 of 15). No SLA found (0). Generally available (10). 20 + 10 + 15 + 8 + 0 + 10 = 63." }, "scores": { "a": 85, "b": 63 } }, { "by": 20, "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 page loaded empty, the API's fee endpoints need a key, and no rate could be read, so fees are scored as not published (0, unchecked). The API is free, public endpoints need no key and the sandbox needs no money (20). A person must sign up in a browser with identity checks and mint the key (0). 0 + 0 + 20 + 0 = 20." }, "scores": { "a": 40, "b": 20 } }, { "by": 13, "category": "maintenance", "leads": "bitfinex", "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. The last dated API change is 28 August 2026, 67 days before the check (20). Only one dated entry in the last 90 days, after 1 July and 12 June (0). No public repository or issue tracker, support pages did not load and support.bitstamp.net did not resolve; a changelog exists (8 of 25). No official SDKs and no MCP registry presence of Bitstamp's own (0). No package to assess (0). 20 + 0 + 8 + 0 + 0 = 28." }, "scores": { "a": 41, "b": 28 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "iFinex Inc.", "b": "Bitstamp Ltd.", "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": "Proprietary hosted API under Bitstamp's terms of use, which our reader couldn't load", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "no", "name": "llms.txt" }, { "a": "2026-07-18", "b": "2026-08-28", "name": "Last release" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Terms last updated" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Privacy policy last updated" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Customer content may train models" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Terms restrict automated access" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Terms restrict benchmarking" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Terms or service can change without notice" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Arbitration or class-action waiver" }, { "a": "480 stars", "b": "none", "name": "Popularity" } ], "faq": [ { "answer": "Bitfinex API scores 58.4 (C) on agent readiness against Bitstamp API's 50.4 (D), and leads in 5 of 7 scored categories.", "question": "Which is better for AI agents, Bitfinex API or Bitstamp API?" }, { "answer": "Both need an API key.", "question": "Do Bitfinex API and Bitstamp API need an API key?" }, { "answer": "No hosted endpoint is listed for Bitfinex API. No hosted endpoint is listed for Bitstamp API.", "question": "Can an agent call Bitfinex API and Bitstamp API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 85 against 63", "Payments \u0026 pricing, 40 against 20", "Maintenance \u0026 community, 41 against 28" ], "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": null, "also": null, "goodFor": "An agent that needs a long-running regulated spot venue in the EU, UK and US with a sandbox and per-endpoint key permissions, and can do its own signing.", "slug": "bitstamp", "watchFor": "No official MCP server, SDK, llms.txt or OpenAPI file; the registry's Bitstamp servers are third parties proxying public market data" } ], "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-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/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-bitstamp.json", "title": "Bitget vs Bitstamp API", "url": "https://www.anchorterminal.com/compare/bitget-vs-bitstamp" }, { "json": "https://www.anchorterminal.com/compare/bithumb-vs-bitstamp.json", "title": "Bithumb Open API vs Bitstamp API", "url": "https://www.anchorterminal.com/compare/bithumb-vs-bitstamp" }, { "json": "https://www.anchorterminal.com/compare/bitstamp-vs-bybit.json", "title": "Bitstamp API vs Bybit", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-bybit" }, { "json": "https://www.anchorterminal.com/compare/bitstamp-vs-coinbase-advanced-trade.json", "title": "Bitstamp API vs Coinbase Advanced Trade API", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-coinbase-advanced-trade" }, { "json": "https://www.anchorterminal.com/compare/bitstamp-vs-coinbase-mcp.json", "title": "Bitstamp API vs Coinbase MCP server (Coinbase for Agents)", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-coinbase-mcp" }, { "json": "https://www.anchorterminal.com/compare/bitstamp-vs-crypto-com-exchange.json", "title": "Bitstamp API vs Crypto.com Exchange API", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-crypto-com-exchange" }, { "json": "https://www.anchorterminal.com/compare/bitstamp-vs-deribit.json", "title": "Bitstamp API vs Deribit", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-deribit" }, { "json": "https://www.anchorterminal.com/compare/bitstamp-vs-dydx.json", "title": "Bitstamp API vs dYdX", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-dydx" }, { "json": "https://www.anchorterminal.com/compare/bitstamp-vs-gate-io.json", "title": "Bitstamp API vs Gate", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-gate-io" }, { "json": "https://www.anchorterminal.com/compare/bitstamp-vs-gemini-exchange.json", "title": "Bitstamp API vs Gemini Exchange API", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-gemini-exchange" }, { "json": "https://www.anchorterminal.com/compare/bitstamp-vs-htx.json", "title": "Bitstamp API vs HTX trading API", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-htx" }, { "json": "https://www.anchorterminal.com/compare/bitstamp-vs-hyperliquid.json", "title": "Bitstamp API vs Hyperliquid", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-hyperliquid" }, { "json": "https://www.anchorterminal.com/compare/bitstamp-vs-kraken.json", "title": "Bitstamp API vs Kraken API", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-kraken" }, { "json": "https://www.anchorterminal.com/compare/bitstamp-vs-kucoin.json", "title": "Bitstamp API vs KuCoin", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-kucoin" }, { "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/bitstamp-vs-okx.json", "title": "Bitstamp API vs OKX API", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-okx" }, { "json": "https://www.anchorterminal.com/compare/bitstamp-vs-uniswap.json", "title": "Bitstamp API vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-uniswap" }, { "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/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-bitstamp.json", "title": "Binance API vs Bitstamp API", "url": "https://www.anchorterminal.com/compare/binance-vs-bitstamp" } ], "panel": null, "scores": [ { "bitfinex": 85, "bitstamp": 63, "by": 22, "edge": "bitfinex", "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "bitfinex": 48, "bitstamp": 51, "by": 3, "edge": "bitstamp", "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "bitfinex": 61, "bitstamp": 58, "by": 3, "edge": "bitfinex", "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "bitfinex": 62, "bitstamp": 60, "by": 2, "edge": "bitfinex", "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "bitfinex": 40, "bitstamp": 20, "by": 20, "edge": "bitfinex", "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "bitfinex": 41, "bitstamp": 28, "by": 13, "edge": "bitfinex", "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "bitfinex": 49, "bitstamp": 53, "by": 4, "edge": "bitstamp", "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Bitfinex API scores 58.4 (C) on agent readiness against Bitstamp API's 50.4 (D), and leads in 5 of 7 scored categories. 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.", "bitstamp": "Bitstamp documents its v2 API on one static page with numeric rate limits, per-endpoint key permissions, an IP allow-list, a kill switch and a sandbox. There is no official MCP server, duplicate client order ids are allowed, and the fee schedule, terms, privacy policy and country list render by script and could not be read." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/bitfinex-vs-bitstamp", "json": "https://www.anchorterminal.com/compare/bitfinex-vs-bitstamp.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/bitfinex-vs-bitstamp.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/bitfinex-vs-bitstamp.min.md" }, "markdown": "Bitfinex API scores 58.4 (C) on agent readiness against Bitstamp API's 50.4 (D), and leads in 5 of 7 scored categories. 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- Bitstamp API: grade D, 50.4/100, rank #942 of 1349. Markdown https://www.anchorterminal.com/tools/bitstamp.md · JSON https://www.anchorterminal.com/api/v1/tools/bitstamp.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 63\n- Payments \u0026 pricing, 40 against 20\n- Maintenance \u0026 community, 41 against 28\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### Bitstamp API (D)\n\nGood for: An agent that needs a long-running regulated spot venue in the EU, UK and US with a sandbox and per-endpoint key permissions, and can do its own signing.\n\nWatch for: No official MCP server, SDK, llms.txt or OpenAPI file; the registry's Bitstamp servers are third parties proxying public market data\n\n\n## Why the edge\n\n### Reliability: Bitfinex API +22\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- Bitstamp API (63): Read with the hosted lines on the HTTP API v2 at www.bitstamp.net/api/v2/. status.bitstamp.net is a Statuspage site with component history (20). Its feed for 5 August to 3 November 2026 has 17 entries, among them withdrawals failing on 14 networks for about 3 hours on 21 August, database maintenance with login failures and intermittent trading interruptions for about 1 hour 44 minutes on 23 September, a 39-minute halt of all markets on 5 August, and delistings and single-asset suspensions. One major (10). Rate limits with numbers, 400 a second and 10,000 per 10 minutes (15). Limit errors are named (400.002, 400.067, 400.068) but there is no Retry-After or backoff guidance, duplicate client order ids are allowed, and the only retry guidance is to check the order after a 500.016 timeout (8 of 15). No SLA found (0). Generally available (10). 20 + 10 + 15 + 8 + 0 + 10 = 63.\n\n### Payments \u0026 pricing: Bitfinex API +20\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- Bitstamp API (20): No machine payment protocol (0). The fee schedule page loaded empty, the API's fee endpoints need a key, and no rate could be read, so fees are scored as not published (0, unchecked). The API is free, public endpoints need no key and the sandbox needs no money (20). A person must sign up in a browser with identity checks and mint the key (0). 0 + 0 + 20 + 0 = 20.\n\n### Maintenance \u0026 community: Bitfinex API +13\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- Bitstamp API (28): Read as a closed service. The last dated API change is 28 August 2026, 67 days before the check (20). Only one dated entry in the last 90 days, after 1 July and 12 June (0). No public repository or issue tracker, support pages did not load and support.bitstamp.net did not resolve; a changelog exists (8 of 25). No official SDKs and no MCP registry presence of Bitstamp's own (0). No package to assess (0). 20 + 0 + 8 + 0 + 0 = 28.\n\n## Score by category\n\n| Category | Weight | Bitfinex API | Bitstamp API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 85 | 63 | Bitfinex API +22 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 48 | 51 | Bitstamp API +3 |\n| Agent ergonomics | 13% (16.2 this run) | 61 | 58 | Bitfinex API +3 |\n| Security \u0026 auth | 14% (17.5 this run) | 62 | 60 | Bitfinex API +2 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 20 | Bitfinex API +20 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 41 | 28 | Bitfinex API +13 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 49 | 53 | Bitstamp API +4 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **58.4 · C** | **50.4 · D** | |\n\n## Facts side by side\n\n| Fact | Bitfinex API | Bitstamp API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | iFinex Inc. | Bitstamp Ltd. |\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 | Proprietary hosted API under Bitstamp's terms of use, which our reader couldn't load |\n| Read-only variant documented | no | no |\n| llms.txt | yes | no |\n| Last release | 2026-07-18 | 2026-08-28 |\n| Terms last updated | couldn't be read | couldn't be read |\n| Privacy policy last updated | couldn't be read | couldn't be read |\n| Customer content may train models | couldn't be read | couldn't be read |\n| Terms restrict automated access | couldn't be read | couldn't be read |\n| Terms restrict benchmarking | couldn't be read | couldn't be read |\n| Terms or service can change without notice | couldn't be read | couldn't be read |\n| Arbitration or class-action waiver | couldn't be read | couldn't be read |\n| Popularity | 480 stars | none |\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**Bitstamp API.** Bitstamp documents its v2 API on one static page with numeric rate limits, per-endpoint key permissions, an IP allow-list, a kill switch and a sandbox. There is no official MCP server, duplicate client order ids are allowed, and the fee schedule, terms, privacy policy and country list render by script and could not be 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### Bitstamp API\n\n1. Mint a key with only the endpoint permissions the task needs and an IP allow-list; keep `revoke_all_api_keys` in reach as a kill switch\n2. Treat `client_order_id` as a label, not a guard. On a timeout (500.016) fetch the order by client id before resending, because duplicates are accepted\n3. Use a fresh 36-character nonce and a timestamp within 150 seconds of server time on every request, or expect API0004 and API0017\n4. Stay under 400 requests a second and 10,000 per 10 minutes; 400.002 and 400.067 mean back off, and open-orders answers are cached for 10 seconds\n5. Start on sandbox.bitstamp.net with the same paths, and read the fee schedule in a browser before quoting costs, since it is unreadable to a plain fetch\n\n## Questions\n\n### Which is better for AI agents, Bitfinex API or Bitstamp API?\n\nBitfinex API scores 58.4 (C) on agent readiness against Bitstamp API's 50.4 (D), and leads in 5 of 7 scored categories.\n\n### Do Bitfinex API and Bitstamp API need an API key?\n\nBoth need an API key.\n\n### Can an agent call Bitfinex API and Bitstamp API without installing anything?\n\nNo hosted endpoint is listed for Bitfinex API. No hosted endpoint is listed for Bitstamp API.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/bitfinex-vs-bitstamp.json, and with the fewest tokens: https://www.anchorterminal.com/compare/bitfinex-vs-bitstamp.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"bitfinex\", \"b\": \"bitstamp\"}`. From a terminal: `anchor compare bitfinex bitstamp`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/bitfinex.json and https://www.anchorterminal.com/api/v1/tools/bitstamp.json\n\n## Other comparisons with Bitfinex API or Bitstamp 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 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- [Bitfinex API vs Upbit Open API](https://www.anchorterminal.com/compare/bitfinex-vs-upbit.md)\n- [Bitget vs Bitstamp API](https://www.anchorterminal.com/compare/bitget-vs-bitstamp.md)\n- [Bithumb Open API vs Bitstamp API](https://www.anchorterminal.com/compare/bithumb-vs-bitstamp.md)\n- [Bitstamp API vs Bybit](https://www.anchorterminal.com/compare/bitstamp-vs-bybit.md)\n- [Bitstamp API vs Coinbase Advanced Trade API](https://www.anchorterminal.com/compare/bitstamp-vs-coinbase-advanced-trade.md)\n- [Bitstamp API vs Coinbase MCP server (Coinbase for Agents)](https://www.anchorterminal.com/compare/bitstamp-vs-coinbase-mcp.md)\n- [Bitstamp API vs Crypto.com Exchange API](https://www.anchorterminal.com/compare/bitstamp-vs-crypto-com-exchange.md)\n- [Bitstamp API vs Deribit](https://www.anchorterminal.com/compare/bitstamp-vs-deribit.md)\n- [Bitstamp API vs dYdX](https://www.anchorterminal.com/compare/bitstamp-vs-dydx.md)\n- [Bitstamp API vs Gate](https://www.anchorterminal.com/compare/bitstamp-vs-gate-io.md)\n- [Bitstamp API vs Gemini Exchange API](https://www.anchorterminal.com/compare/bitstamp-vs-gemini-exchange.md)\n- [Bitstamp API vs HTX trading API](https://www.anchorterminal.com/compare/bitstamp-vs-htx.md)\n- [Bitstamp API vs Hyperliquid](https://www.anchorterminal.com/compare/bitstamp-vs-hyperliquid.md)\n- [Bitstamp API vs Kraken API](https://www.anchorterminal.com/compare/bitstamp-vs-kraken.md)\n- [Bitstamp API vs KuCoin](https://www.anchorterminal.com/compare/bitstamp-vs-kucoin.md)\n- [Bitstamp API vs MEXC API](https://www.anchorterminal.com/compare/bitstamp-vs-mexc.md)\n- [Bitstamp API vs OKX API](https://www.anchorterminal.com/compare/bitstamp-vs-okx.md)\n- [Bitstamp API vs Uniswap Trading API](https://www.anchorterminal.com/compare/bitstamp-vs-uniswap.md)\n- [Bitstamp API vs Upbit Open API](https://www.anchorterminal.com/compare/bitstamp-vs-upbit.md)\n- [Binance API vs Bitfinex API](https://www.anchorterminal.com/compare/binance-vs-bitfinex.md)\n- [Binance API vs Bitstamp API](https://www.anchorterminal.com/compare/binance-vs-bitstamp.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 Bitstamp API", "url": "" } ], "description": "Bitfinex scores 58.4 (C) to Bitstamp's 50.4 (D) for exchange market data. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Bitfinex API C 58.4", "Bitstamp API D 50.4", "scores" ], "h1": "Bitfinex API vs Bitstamp API", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/bitfinex-vs-bitstamp", "published": "2026-10-01", "section": "tools", "title": "Bitfinex vs Bitstamp for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-04", "url": "https://www.anchorterminal.com/compare/bitfinex-vs-bitstamp" }, "tokens": { "markdown": 3750, "slim": 1480 }, "version": 1 }