{
  "data": {
    "a": {
      "slug": "bitfinex",
      "name": "Bitfinex API",
      "vendor": "iFinex Inc.",
      "vendorUrl": "https://www.bitfinex.com",
      "company": "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",
      "cardUrl": "https://www.anchorterminal.com/tools/bitfinex.card.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": 60.9,
        "grade": "C",
        "agentReady": false,
        "rank": 758,
        "ranked": true,
        "rankOf": 1563,
        "categoryRank": 9,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 61,
          "maintenance": 41,
          "payments": 60,
          "reliability": 85,
          "schema": 48,
          "security": 62,
          "transparency": 49
        },
        "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": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 60.9
          }
        ],
        "editorialScores": {
          "ergonomics": 61,
          "maintenance": 41,
          "payments": 60,
          "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",
          "lastMoved": "2026-11-13",
          "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-20T21:51:03.372436227Z"
        },
        "versions": [
          {
            "registry": "github",
            "name": "bitfinexcom/bitfinex-api-node",
            "version": "4.0.15",
            "released": "2020-07-02",
            "seenAt": "2026-11-20T20:16:40.02539205Z"
          },
          {
            "registry": "npm",
            "name": "bitfinex-api-node",
            "version": "10.0.1",
            "seenAt": "2026-11-20T20:16:36.871711516Z"
          },
          {
            "registry": "pypi",
            "name": "bitfinex-api-py",
            "version": "4.0.0",
            "released": "2025-10-18",
            "seenAt": "2026-11-20T20:16:39.836492877Z"
          }
        ],
        "githubStars": 479,
        "npmWeekly": 8607,
        "pypiWeekly": 1246,
        "securityTxt": {
          "url": "https://bitfinex.com/.well-known/security.txt",
          "state": "none",
          "checkedAt": "2026-11-20T16:34:50.360285388Z"
        },
        "llmsTxt": {
          "url": "https://docs.bitfinex.com/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-11-20T16:21:43.956880993Z"
        },
        "domain": {
          "domain": "bitfinex.com",
          "registered": "2012-10-11",
          "source": "https://rdap.verisign.com/com/v1/domain/bitfinex.com",
          "checkedAt": "2026-11-15T15:31:43.088408282Z"
        },
        "pages": [
          {
            "url": "https://docs.bitfinex.com/docs/changelog",
            "kind": "changelog",
            "status": 200,
            "checkedAt": "2026-11-19T22:20:04.485024747Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "8cecd82545bb"
          },
          {
            "url": "https://www.bitfinex.com/legal/privacy/",
            "kind": "privacy",
            "status": 200,
            "checkedAt": "2026-11-19T22:41:08.800422804Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "dfcbffa257c7"
          },
          {
            "url": "https://www.bitfinex.com/legal/exchange/terms/",
            "kind": "terms",
            "status": 200,
            "checkedAt": "2026-11-19T22:41:06.639174167Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "29f5cd271205"
          }
        ],
        "github": {
          "repo": "bitfinexcom/bitfinex-api-node",
          "checkedAt": "2026-11-16T11:18:49.308686975Z",
          "stars": 480,
          "archived": false,
          "issuesEnabled": true,
          "pushedAt": "2026-11-11T11:38:39Z",
          "openIssues": 55,
          "openPRs": 12,
          "issuesOpened90d": 0,
          "issuesClosed90d": 0,
          "prsMerged90d": 1,
          "replies": {
            "sampled": 25,
            "unanswered": 21,
            "medianDays": 164.5
          }
        },
        "updatedAt": "2026-11-20T21:51:03.372436227Z"
      }
    },
    "answer": "Bitpont API and MCP scores 62.9 (B) on agent readiness against Bitfinex API's 60.9 (C), and leads in 5 of 7 scored categories. Bitfinex API leads on reliability and maintenance \u0026 community.",
    "b": {
      "slug": "bitpont",
      "name": "Bitpont API and MCP",
      "vendor": "Bitpont (LiMiT)",
      "vendorUrl": "https://www.bitpont.com/developers/",
      "company": "bitpont.com",
      "kind": "http-api",
      "category": "crypto-exchanges",
      "summary": "Bitpont is a wallet-connected DeFi front end for swaps, bridges, lending, liquidity and perpetuals on EVM networks and Solana. Its REST API and hosted MCP server quote, read positions and prepare transactions the owner's wallet signs.",
      "url": "https://www.anchorterminal.com/tools/bitpont",
      "markdownUrl": "https://www.anchorterminal.com/tools/bitpont.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/bitpont.min.md",
      "cardUrl": "https://www.anchorterminal.com/tools/bitpont.card.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/bitpont.json",
      "dns": "bitpont.grade.anchorterminal.com",
      "repo": "https://github.com/bitpont",
      "license": "A proprietary hosted service under the Bitpont Terms of Use (LIMIT SRL). The terms licence the published SDK, declarations, examples and API documentation for building integrations, with no copyright fee; the backend is closed",
      "transports": [
        "streamable-http"
      ],
      "remoteUrl": "https://www.bitpont.com/api/v1/mcp",
      "packages": [],
      "auth": "mixed",
      "authNotes": "Standard access needs no key. A client-created private workspace, sent as the `X-Bitpont-Workspace` header, keeps tickets and receipts together. Optional partner bearer keys are issued by the operator on request, with scopes (`discovery:read`, `positions:read`, `transactions:prepare`, `transactions:submit`), expiry and revocation. The owner's wallet signs every trade locally (https://www.bitpont.com/developers/authentication/, checked 2026-11-20).",
      "pricing": "usage",
      "pricingNotes": "The API is free under a shared budget of 30 request units a minute per IP; partner keys default to 60 units a minute. Bitpont takes a 0.40% interface fee on supported swaps, limit orders and direct deBridge bridges, and none on lending, Earn or liquidity actions. A verified fee lifts request quotas for an hour. No card or account is needed (https://www.bitpont.com/fees/, checked 2026-11-20).",
      "priceSummary": "0.4% fee",
      "where": "hosted",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the OpenAPI file, llms.txt or developer pages read on 20 November 2026. A finalised Bitpont trading fee, verified through `feeAccess`, unlocks an hour without standard quotas, which is not a machine payment protocol.",
        "endpoints": []
      },
      "toolCount": 1148,
      "popularity": {
        "githubStars": null,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-11-20"
      },
      "docsUrl": "https://www.bitpont.com/developers/",
      "llmsTxt": "https://www.bitpont.com/llms.txt",
      "openapi": "https://www.bitpont.com/assets/docs/bitpont-openapi.json",
      "capabilities": [
        "exchange.market-data",
        "exchange.spot-trading",
        "exchange.derivatives",
        "exchange.balances",
        "exchange.transfers",
        "exchange.staking",
        "market.crypto",
        "wallet.onchain"
      ],
      "tags": [
        "official",
        "hosted",
        "closed-source",
        "openapi",
        "llms-txt",
        "no-key",
        "no-card",
        "usage-priced",
        "typescript",
        "mcp",
        "rest",
        "no-status-page"
      ],
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 62.9,
        "grade": "B",
        "agentReady": false,
        "rank": 659,
        "ranked": true,
        "rankOf": 1563,
        "categoryRank": 8,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 74,
          "maintenance": 14,
          "payments": 90,
          "reliability": 45,
          "schema": 82,
          "security": 63,
          "transparency": 58
        },
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-20"
        },
        "negative": 0,
        "verdict": "Public market reads, quotes and unsigned transaction drafts work without an account, every trade is signed in the owner's wallet, and an OpenAPI 3.1 file covers all 1,148 operations. There is no status page, the changelog carries no dates, and the hosted MCP server exposes the same 1,148 tools, narrowed by product filters and a search tool.",
        "bestFor": "An aggregator over DeFi venues (Jupiter, KyberSwap, LI.FI, deBridge, Aave, Morpho, Hyperliquid, GMX, Derive) rather than an exchange with its own order book.",
        "strengths": [
          "Market reads, quotes and transaction drafts work with no account, key or card",
          "Every value transfer needs the owner's wallet signature; partner keys carry scopes such as `positions:read` and `transactions:submit`",
          "OpenAPI 3.1, llms.txt, Markdown guides, a Postman collection and OpenAI function definitions, with typed inputs and patterns on amounts and addresses",
          "Every error carries `code`, `requestId` and `retryable`, and `checkInputs` returns JSON Pointer paths before a provider is called",
          "Stable request IDs and saved tasks let an agent recover an order after a lost response without resubmitting"
        ],
        "weaknesses": [
          "No status page, no SLA and no sandbox or testnet in the reviewed documentation",
          "The changelog lists versions with no dates, and its latest API version (1.9) differs from the OpenAPI file's 1.33.0",
          "1,148 tools behind one MCP endpoint, a 5.4 MB OpenAPI file and a 1.7 MB tools catalogue",
          "No security.txt, bug bounty or certification; the security page says Bitpont itself has no independent audit",
          "A DeFi interface that takes 0.40% on swaps and bridges; funds sit in third-party protocols with their own risks"
        ],
        "agentNotes": [
          "Connect with `?product=swap` or another product ID, then call `bitpont_findTools` and `bitpont_describeTool` rather than loading all 1,148 tools",
          "Create a private workspace before the first ticket and store its secret and your `requestId`; reuse both to recover an order",
          "Call `bitpont_checkInputs` before preparing a transaction; amounts are base-unit decimal strings",
          "If a request returns 429, wait for the `Retry-After` value. The free budget is 30 units a minute per IP and a batch costs one unit per item",
          "Never repeat a submission whose outcome is unknown; read the execution receipt first"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "B",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 62.9
          }
        ],
        "editorialScores": {
          "ergonomics": 74,
          "maintenance": 14,
          "payments": 90,
          "reliability": 45,
          "schema": 82,
          "security": 63,
          "transparency": 48
        },
        "provenanceScore": 68,
        "checked": {
          "categories": {
            "ergonomics": "2026-11-20",
            "maintenance": "2026-11-20",
            "payments": "2026-11-20",
            "reliability": "2026-11-20",
            "schema": "2026-11-20",
            "security": "2026-11-20",
            "transparency": "2026-11-20"
          },
          "last": "2026-11-20",
          "oldest": "2026-11-20",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "http": "curl -fsS https://www.bitpont.com/api/v1/agent/tools -H 'Content-Type: application/json' -d '{\"product\":\"bridge\",\"q\":\"quote\",\"limit\":5}'",
        "claudeCode": "claude mcp add --transport http bitpont \"https://www.bitpont.com/api/v1/mcp?product=swap\""
      },
      "letme": {
        "capability": "https://letme.dev/exchange.market-data",
        "tool": "https://letme.dev/bitpont"
      },
      "area": "payments",
      "unitPrices": [
        {
          "item": "Swap and bridge interface fee",
          "unit": "pct",
          "usd": 0.4,
          "note": "0.40% of input on supported swaps, limit orders and direct deBridge routes; network and protocol fees extra"
        }
      ],
      "provenance": {
        "legalEntity": "LIMIT SRL",
        "domain": "bitpont.com",
        "domainRegistered": "2020-08-15",
        "endpointOnVendorDomain": true,
        "terms": "https://www.bitpont.com/terms/",
        "privacy": "https://www.bitpont.com/privacy/",
        "statusPage": "",
        "changelog": "https://www.bitpont.com/developers/changelog/",
        "securityTxt": "none",
        "checked": "2026-11-20",
        "notes": [
          "The terms, privacy notice and about page say Bitpont is a LiMiT product operated by LIMIT SRL, published identifiers RO21411289 and J05/751/2007. limit.ro gives the same identifiers, an Oradea address and EUID ROONRC.J05/751/2007, and lists bitpont.com as an owned project.",
          "The terms permit search engines and AI retrieval services to crawl and render public pages.",
          "www.bitpont.com/robots.txt allows all agents and disallows /api/ apart from nine named paths; the MCP endpoint and /api/v1/usage are among the closed paths.",
          "RDAP (Verisign) gives bitpont.com a registration date of 15 August 2020.",
          "/.well-known/security.txt answered 404. No status page was linked from any page read."
        ],
        "score": 68
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/bitpont.json",
      "live": {
        "slug": "bitpont",
        "probe": {
          "target": "https://www.bitpont.com/api/v1/mcp",
          "method": "get",
          "lastAt": "2026-11-20T21:48:32.606649764Z",
          "lastOk": true,
          "lastStatus": 405,
          "lastMs": 146,
          "authRequired": false,
          "uptime24h": 98.36,
          "uptime30d": 98.36,
          "p50ms24h": 129,
          "p95ms24h": 422,
          "samples24h": 61,
          "samples30d": 61,
          "days": [
            {
              "date": "2026-11-20",
              "probes": 61,
              "ok": 60
            }
          ],
          "since": "2026-11-20T15:54:23.354107122Z"
        },
        "securityTxt": {
          "url": "https://bitpont.com/.well-known/security.txt",
          "state": "none",
          "checkedAt": "2026-11-20T16:36:59.418435314Z"
        },
        "llmsTxt": {
          "url": "https://www.bitpont.com/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-11-20T16:21:44.038986512Z"
        },
        "updatedAt": "2026-11-20T21:48:32.606649764Z"
      },
      "streak": {
        "days": 0,
        "from": "2026-11-20",
        "sinceWatching": true,
        "best": 0
      }
    },
    "edges": [
      {
        "by": 40,
        "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 REST API and hosted MCP server. No status page linked from any page read (0). No readable incident history (5). Rate limits with numbers, 30 request units a minute per IP for free access, 60 for partner keys, six items a batch (15). RateLimit and Retry-After headers documented, a `retryable` flag on every error, and stable request IDs and saved tasks for recovering a write after a lost response (15). No SLA (0). Nothing in the reviewed pages marks the API as beta or preview (10). 0 + 5 + 15 + 15 + 0 + 10 = 45."
        },
        "scores": {
          "a": 85,
          "b": 45
        }
      },
      {
        "by": 34,
        "category": "schema",
        "leads": "bitpont",
        "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": "OpenAPI 3.1 file `Bitpont Developer API` 1.33.0 with 1,149 operations, read once as the reference viewer's source (25). llms.txt, Markdown downloads of the developer pages and Markdown agent guides (10). Every operation has a description and most a summary that states its job, and the guides say which tool to use for which task, though few say when not to (14 of 20). Enums, regex patterns and length limits on addresses and base-unit amounts, required fields; some inputs still allow free-form objects and the MCP operation takes a generic `params` object (12 of 15). Code examples in the guides and a shared error schema with `code`, `requestId` and `retryable` on 400 to 504 (13 of 15). A versioned changelog, but its entries carry no dates and its latest API version (1.9) doesn't match the file's 1.33.0 (8 of 15). Total 82."
        },
        "scores": {
          "a": 48,
          "b": 82
        }
      },
      {
        "by": 30,
        "category": "payments",
        "leads": "bitpont",
        "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. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.",
          "b": "No x402, MPP or L402; a verified trading fee lifting quotas for an hour is not a payment protocol (0). The API is free under published limits and the 0.40% interface fee is published per route without a login (30). Free access with no card (30). An agent starts with no signup by creating a private workspace through the API (30). Total 90."
        },
        "scores": {
          "a": 60,
          "b": 90
        }
      },
      {
        "by": 27,
        "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 hosted service. The changelog names versions (Bitpont 5.102.20, API 1.9) with no dates, so the time since the last release can't be established (0) and there are no dated entries (0). A public changelog and a support email; no answer observed and the GitHub organisation is closed to our reader (6 of 15). A first-party JavaScript client and TypeScript declarations as downloads, not on a package registry, and no MCP registry entry (8 of 15). No package or public CI seen (0). The public announcement was on 20 November 2026, so the record is days old. Total 14."
        },
        "scores": {
          "a": 41,
          "b": 14
        }
      },
      {
        "by": 13,
        "category": "ergonomics",
        "leads": "bitpont",
        "name": "Agent ergonomics",
        "reasons": {
          "a": "Graded on the REST API. Limits on trades, candles and book depth, and `pub:list` config endpoints keep responses small, but positional arrays make every field a lookup (14 of 25). `start`, `end`, `limit` and `sort` on history endpoints and per-symbol variants (16 of 20). `ERR_RATE_LIMIT` is actionable; authenticated 400s return `{}` and withdrawal status strings may change, so an agent cannot branch on causes (8 of 20). A client id on orders, order multi-op and cancel-multiple, but no idempotency key and no retry contract (8 of 20). Few required parameters and official clients in Node, Python, Go and Ruby (15). 14 + 16 + 8 + 8 + 15 = 61.",
          "b": "Read for the hosted MCP server, whose catalogue has 1,148 tools (5), with 10 added back for `?product=` profiles, `bitpont_findTools` and `bitpont_describeTool` and paginated `tools/list` (15 of 25). Cursors, limits, product and network filters and read batches (18 of 20). Errors carry `code`, `retryable` and `requestId`, and `checkInputs` returns JSON Pointer paths before any provider is called (19 of 20). Idempotent tasks and stable request IDs, with a documented rule never to repeat an unknown submission; readOnlyHint and destructiveHint unchecked because `tools/list` was not sent, and the catalogue carries no annotations (14 of 20). A JavaScript client with TypeScript declarations, OpenAI function definitions and a Postman collection, one language (8 of 15). Total 74."
        },
        "scores": {
          "a": 61,
          "b": 74
        }
      },
      {
        "by": 9,
        "category": "transparency",
        "leads": "bitpont",
        "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. Closed source under readable terms, which licence the published SDK and documentation for integrations (15 of 30). A detailed privacy notice naming the operator, bases, recipients and browser storage, but it promises no deletion period for server logs and support records and no DPA was found (18 of 30). No deprecation policy or dated notices; the changelog only says changes are additive (5 of 20). Integration providers named by function (Jupiter, deBridge, Velocity, Jito, Kamino, KyberSwap, LI.FI, 1inch); the hosting provider and data locations are given only on request (10 of 20). Total 48."
        },
        "scores": {
          "a": 49,
          "b": 58
        }
      }
    ],
    "facts": [
      {
        "a": "HTTP API",
        "b": "HTTP API",
        "name": "Kind"
      },
      {
        "a": "iFinex Inc.",
        "b": "Bitpont (LiMiT)",
        "name": "Vendor"
      },
      {
        "a": "no (local only)",
        "b": "https://www.bitpont.com/api/v1/mcp",
        "name": "Hosted endpoint"
      },
      {
        "a": "",
        "b": "Streamable HTTP",
        "name": "Transports"
      },
      {
        "a": "API key",
        "b": "OAuth or 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": "A proprietary hosted service under the Bitpont Terms of Use (LIMIT SRL). The terms licence the published SDK, declarations, examples and API documentation for building integrations, with no copyright fee; the backend is closed",
        "name": "Licence"
      },
      {
        "a": "none",
        "b": "1148",
        "name": "Tools exposed"
      },
      {
        "a": "no",
        "b": "no",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "llms.txt"
      },
      {
        "a": "2026-07-18",
        "b": "none",
        "name": "Last release"
      },
      {
        "a": "couldn't be read",
        "b": "no date given",
        "name": "Terms last updated"
      },
      {
        "a": "couldn't be read",
        "b": "2026-11-11",
        "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": "not found in the text",
        "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": "not found in the text",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "couldn't be read",
        "b": "not found in the text",
        "name": "Arbitration or class-action waiver"
      },
      {
        "a": "480 stars",
        "b": "none",
        "name": "Popularity"
      }
    ],
    "faq": [
      {
        "answer": "Bitpont API and MCP scores 62.9 (B) on agent readiness against Bitfinex API's 60.9 (C), and leads in 5 of 7 scored categories. Bitfinex API leads on reliability and maintenance \u0026 community.",
        "question": "Which is better for AI agents, Bitfinex API or Bitpont API and MCP?"
      },
      {
        "answer": "Bitfinex API needs an API key. Bitpont API and MCP takes an API key or an OAuth sign-in.",
        "question": "Do Bitfinex API and Bitpont API and MCP need an API key?"
      },
      {
        "answer": "No hosted endpoint is listed for Bitfinex API. Bitpont API and MCP has a hosted endpoint at https://www.bitpont.com/api/v1/mcp.",
        "question": "Can an agent call Bitfinex API and Bitpont API and MCP without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Reliability, 85 against 45",
          "Maintenance \u0026 community, 41 against 14"
        ],
        "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, 82 against 48",
          "Agent ergonomics, 74 against 61",
          "Payments \u0026 pricing, 90 against 60",
          "Transparency \u0026 trust, 58 against 49"
        ],
        "also": [
          "A hosted endpoint, with nothing to install",
          "Free to start without a card"
        ],
        "goodFor": "An aggregator over DeFi venues (Jupiter, KyberSwap, LI.FI, deBridge, Aave, Morpho, Hyperliquid, GMX, Derive) rather than an exchange with its own order book.",
        "slug": "bitpont",
        "watchFor": "No status page, no SLA and no sandbox or testnet in the reviewed documentation"
      }
    ],
    "history": {
      "bitfinex": [
        {
          "causes": [
            "method"
          ],
          "date": "2026-11-13",
          "delta": 2.5,
          "from": 58.4,
          "fromGrade": "C",
          "to": 60.9,
          "toGrade": "C"
        }
      ],
      "bitpont": null
    },
    "job": {
      "capability": "exchange.market-data",
      "name": "Exchange market data"
    },
    "others": [
      {
        "json": "https://www.anchorterminal.com/compare/bitfinex-vs-bitget.json",
        "title": "Bitfinex API vs Bitget",
        "url": "https://www.anchorterminal.com/compare/bitfinex-vs-bitget"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitfinex-vs-bithumb.json",
        "title": "Bitfinex API vs Bithumb Open API",
        "url": "https://www.anchorterminal.com/compare/bitfinex-vs-bithumb"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitfinex-vs-bitstamp.json",
        "title": "Bitfinex API vs Bitstamp API",
        "url": "https://www.anchorterminal.com/compare/bitfinex-vs-bitstamp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitfinex-vs-bybit.json",
        "title": "Bitfinex API vs Bybit",
        "url": "https://www.anchorterminal.com/compare/bitfinex-vs-bybit"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitfinex-vs-coinbase-advanced-trade.json",
        "title": "Bitfinex API vs Coinbase Advanced Trade API",
        "url": "https://www.anchorterminal.com/compare/bitfinex-vs-coinbase-advanced-trade"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitfinex-vs-coinbase-mcp.json",
        "title": "Bitfinex API vs Coinbase MCP server (Coinbase for Agents)",
        "url": "https://www.anchorterminal.com/compare/bitfinex-vs-coinbase-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitfinex-vs-crypto-com-exchange.json",
        "title": "Bitfinex API vs Crypto.com Exchange API",
        "url": "https://www.anchorterminal.com/compare/bitfinex-vs-crypto-com-exchange"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitfinex-vs-deribit.json",
        "title": "Bitfinex API vs Deribit",
        "url": "https://www.anchorterminal.com/compare/bitfinex-vs-deribit"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitfinex-vs-dydx.json",
        "title": "Bitfinex API vs dYdX",
        "url": "https://www.anchorterminal.com/compare/bitfinex-vs-dydx"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitfinex-vs-gate-io.json",
        "title": "Bitfinex API vs Gate",
        "url": "https://www.anchorterminal.com/compare/bitfinex-vs-gate-io"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitfinex-vs-gemini-exchange.json",
        "title": "Bitfinex API vs Gemini Exchange API",
        "url": "https://www.anchorterminal.com/compare/bitfinex-vs-gemini-exchange"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitfinex-vs-htx.json",
        "title": "Bitfinex API vs HTX trading API",
        "url": "https://www.anchorterminal.com/compare/bitfinex-vs-htx"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitfinex-vs-hyperliquid.json",
        "title": "Bitfinex API vs Hyperliquid",
        "url": "https://www.anchorterminal.com/compare/bitfinex-vs-hyperliquid"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitfinex-vs-kraken.json",
        "title": "Bitfinex API vs Kraken API",
        "url": "https://www.anchorterminal.com/compare/bitfinex-vs-kraken"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitfinex-vs-kucoin.json",
        "title": "Bitfinex API vs KuCoin",
        "url": "https://www.anchorterminal.com/compare/bitfinex-vs-kucoin"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitfinex-vs-mexc.json",
        "title": "Bitfinex API vs MEXC API",
        "url": "https://www.anchorterminal.com/compare/bitfinex-vs-mexc"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitfinex-vs-okx.json",
        "title": "Bitfinex API vs OKX API",
        "url": "https://www.anchorterminal.com/compare/bitfinex-vs-okx"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitfinex-vs-uniswap.json",
        "title": "Bitfinex API vs Uniswap Trading API",
        "url": "https://www.anchorterminal.com/compare/bitfinex-vs-uniswap"
      },
      {
        "json": "https://www.anchorterminal.com/compare/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-bitpont.json",
        "title": "Bitget vs Bitpont API and MCP",
        "url": "https://www.anchorterminal.com/compare/bitget-vs-bitpont"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bithumb-vs-bitpont.json",
        "title": "Bithumb Open API vs Bitpont API and MCP",
        "url": "https://www.anchorterminal.com/compare/bithumb-vs-bitpont"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitpont-vs-bitstamp.json",
        "title": "Bitpont API and MCP vs Bitstamp API",
        "url": "https://www.anchorterminal.com/compare/bitpont-vs-bitstamp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitpont-vs-bybit.json",
        "title": "Bitpont API and MCP vs Bybit",
        "url": "https://www.anchorterminal.com/compare/bitpont-vs-bybit"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitpont-vs-coinbase-advanced-trade.json",
        "title": "Bitpont API and MCP vs Coinbase Advanced Trade API",
        "url": "https://www.anchorterminal.com/compare/bitpont-vs-coinbase-advanced-trade"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitpont-vs-coinbase-mcp.json",
        "title": "Bitpont API and MCP vs Coinbase MCP server (Coinbase for Agents)",
        "url": "https://www.anchorterminal.com/compare/bitpont-vs-coinbase-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitpont-vs-crypto-com-exchange.json",
        "title": "Bitpont API and MCP vs Crypto.com Exchange API",
        "url": "https://www.anchorterminal.com/compare/bitpont-vs-crypto-com-exchange"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitpont-vs-deribit.json",
        "title": "Bitpont API and MCP vs Deribit",
        "url": "https://www.anchorterminal.com/compare/bitpont-vs-deribit"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitpont-vs-dydx.json",
        "title": "Bitpont API and MCP vs dYdX",
        "url": "https://www.anchorterminal.com/compare/bitpont-vs-dydx"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitpont-vs-gate-io.json",
        "title": "Bitpont API and MCP vs Gate",
        "url": "https://www.anchorterminal.com/compare/bitpont-vs-gate-io"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitpont-vs-gemini-exchange.json",
        "title": "Bitpont API and MCP vs Gemini Exchange API",
        "url": "https://www.anchorterminal.com/compare/bitpont-vs-gemini-exchange"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitpont-vs-htx.json",
        "title": "Bitpont API and MCP vs HTX trading API",
        "url": "https://www.anchorterminal.com/compare/bitpont-vs-htx"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitpont-vs-hyperliquid.json",
        "title": "Bitpont API and MCP vs Hyperliquid",
        "url": "https://www.anchorterminal.com/compare/bitpont-vs-hyperliquid"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitpont-vs-kraken.json",
        "title": "Bitpont API and MCP vs Kraken API",
        "url": "https://www.anchorterminal.com/compare/bitpont-vs-kraken"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitpont-vs-kucoin.json",
        "title": "Bitpont API and MCP vs KuCoin",
        "url": "https://www.anchorterminal.com/compare/bitpont-vs-kucoin"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitpont-vs-mexc.json",
        "title": "Bitpont API and MCP vs MEXC API",
        "url": "https://www.anchorterminal.com/compare/bitpont-vs-mexc"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitpont-vs-okx.json",
        "title": "Bitpont API and MCP vs OKX API",
        "url": "https://www.anchorterminal.com/compare/bitpont-vs-okx"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitpont-vs-uniswap.json",
        "title": "Bitpont API and MCP vs Uniswap Trading API",
        "url": "https://www.anchorterminal.com/compare/bitpont-vs-uniswap"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitpont-vs-upbit.json",
        "title": "Bitpont API and MCP vs Upbit Open API",
        "url": "https://www.anchorterminal.com/compare/bitpont-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-bitpont.json",
        "title": "Binance API vs Bitpont API and MCP",
        "url": "https://www.anchorterminal.com/compare/binance-vs-bitpont"
      }
    ],
    "panel": null,
    "scores": [
      {
        "bitfinex": 85,
        "bitpont": 45,
        "by": 40,
        "edge": "bitfinex",
        "key": "reliability",
        "name": "Reliability",
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "bitfinex": 48,
        "bitpont": 82,
        "by": 34,
        "edge": "bitpont",
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "weight": 13
      },
      {
        "bitfinex": 61,
        "bitpont": 74,
        "by": 13,
        "edge": "bitpont",
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "weight": 13
      },
      {
        "bitfinex": 62,
        "bitpont": 63,
        "by": 1,
        "edge": "bitpont",
        "key": "security",
        "name": "Security \u0026 auth",
        "weight": 14
      },
      {
        "bitfinex": 60,
        "bitpont": 90,
        "by": 30,
        "edge": "bitpont",
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "bitfinex": 41,
        "bitpont": 14,
        "by": 27,
        "edge": "bitfinex",
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "weight": 7
      },
      {
        "bitfinex": 49,
        "bitpont": 58,
        "by": 9,
        "edge": "bitpont",
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "weight": 7
      }
    ],
    "summary": "Bitpont API and MCP scores 62.9 (B) on agent readiness against Bitfinex API's 60.9 (C), and leads in 5 of 7 scored categories. Bitfinex API leads on reliability and maintenance \u0026 community. 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.",
      "bitpont": "Public market reads, quotes and unsigned transaction drafts work without an account, every trade is signed in the owner's wallet, and an OpenAPI 3.1 file covers all 1,148 operations. There is no status page, the changelog carries no dates, and the hosted MCP server exposes the same 1,148 tools, narrowed by product filters and a search tool."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/bitfinex-vs-bitpont",
    "json": "https://www.anchorterminal.com/compare/bitfinex-vs-bitpont.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/bitfinex-vs-bitpont.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/compare/bitfinex-vs-bitpont.min.md"
  },
  "markdown": "Bitpont API and MCP scores 62.9 (B) on agent readiness against Bitfinex API's 60.9 (C), and leads in 5 of 7 scored categories. Bitfinex API leads on reliability and maintenance \u0026 community. Both do exchange market data.\n\n- Bitfinex API: grade C, 60.9/100, rank #758 of 1563. Markdown https://www.anchorterminal.com/tools/bitfinex.md · JSON https://www.anchorterminal.com/api/v1/tools/bitfinex.json\n- Bitpont API and MCP: grade B, 62.9/100, rank #659 of 1563. Markdown https://www.anchorterminal.com/tools/bitpont.md · JSON https://www.anchorterminal.com/api/v1/tools/bitpont.json\n- Best crypto exchange APIs and MCP servers for AI agents: https://www.anchorterminal.com/best/crypto-exchanges/index.md\n- All 231 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 45\n- Maintenance \u0026 community, 41 against 14\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### Bitpont API and MCP (B)\n\nGood for: An aggregator over DeFi venues (Jupiter, KyberSwap, LI.FI, deBridge, Aave, Morpho, Hyperliquid, GMX, Derive) rather than an exchange with its own order book.\n\nAhead on:\n- Schema \u0026 documentation, 82 against 48\n- Agent ergonomics, 74 against 61\n- Payments \u0026 pricing, 90 against 60\n- Transparency \u0026 trust, 58 against 49\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n- Free to start without a card\n\nWatch for: No status page, no SLA and no sandbox or testnet in the reviewed documentation\n\n\n## Why the edge\n\n### Reliability: Bitfinex API +40\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- Bitpont API and MCP (45): Read with the hosted lines on the REST API and hosted MCP server. No status page linked from any page read (0). No readable incident history (5). Rate limits with numbers, 30 request units a minute per IP for free access, 60 for partner keys, six items a batch (15). RateLimit and Retry-After headers documented, a `retryable` flag on every error, and stable request IDs and saved tasks for recovering a write after a lost response (15). No SLA (0). Nothing in the reviewed pages marks the API as beta or preview (10). 0 + 5 + 15 + 15 + 0 + 10 = 45.\n\n### Schema \u0026 documentation: Bitpont API and MCP +34\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- Bitpont API and MCP (82): OpenAPI 3.1 file `Bitpont Developer API` 1.33.0 with 1,149 operations, read once as the reference viewer's source (25). llms.txt, Markdown downloads of the developer pages and Markdown agent guides (10). Every operation has a description and most a summary that states its job, and the guides say which tool to use for which task, though few say when not to (14 of 20). Enums, regex patterns and length limits on addresses and base-unit amounts, required fields; some inputs still allow free-form objects and the MCP operation takes a generic `params` object (12 of 15). Code examples in the guides and a shared error schema with `code`, `requestId` and `retryable` on 400 to 504 (13 of 15). A versioned changelog, but its entries carry no dates and its latest API version (1.9) doesn't match the file's 1.33.0 (8 of 15). Total 82.\n\n### Payments \u0026 pricing: Bitpont API and MCP +30\n\n- Bitfinex API (60): No machine payment protocol (0). The fees page is public without login (20), though it shows zero maker and taker with no tiers or date. The API is free, public endpoints need no account, and paper trading needs no money (20). A person must sign up in a browser with identity checks and mint the key (0). 0 + 20 + 20 + 0 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.\n- Bitpont API and MCP (90): No x402, MPP or L402; a verified trading fee lifting quotas for an hour is not a payment protocol (0). The API is free under published limits and the 0.40% interface fee is published per route without a login (30). Free access with no card (30). An agent starts with no signup by creating a private workspace through the API (30). Total 90.\n\n### Maintenance \u0026 community: Bitfinex API +27\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- Bitpont API and MCP (14): Read as a closed hosted service. The changelog names versions (Bitpont 5.102.20, API 1.9) with no dates, so the time since the last release can't be established (0) and there are no dated entries (0). A public changelog and a support email; no answer observed and the GitHub organisation is closed to our reader (6 of 15). A first-party JavaScript client and TypeScript declarations as downloads, not on a package registry, and no MCP registry entry (8 of 15). No package or public CI seen (0). The public announcement was on 20 November 2026, so the record is days old. Total 14.\n\n### Agent ergonomics: Bitpont API and MCP +13\n\n- Bitfinex API (61): Graded on the REST API. Limits on trades, candles and book depth, and `pub:list` config endpoints keep responses small, but positional arrays make every field a lookup (14 of 25). `start`, `end`, `limit` and `sort` on history endpoints and per-symbol variants (16 of 20). `ERR_RATE_LIMIT` is actionable; authenticated 400s return `{}` and withdrawal status strings may change, so an agent cannot branch on causes (8 of 20). A client id on orders, order multi-op and cancel-multiple, but no idempotency key and no retry contract (8 of 20). Few required parameters and official clients in Node, Python, Go and Ruby (15). 14 + 16 + 8 + 8 + 15 = 61.\n- Bitpont API and MCP (74): Read for the hosted MCP server, whose catalogue has 1,148 tools (5), with 10 added back for `?product=` profiles, `bitpont_findTools` and `bitpont_describeTool` and paginated `tools/list` (15 of 25). Cursors, limits, product and network filters and read batches (18 of 20). Errors carry `code`, `retryable` and `requestId`, and `checkInputs` returns JSON Pointer paths before any provider is called (19 of 20). Idempotent tasks and stable request IDs, with a documented rule never to repeat an unknown submission; readOnlyHint and destructiveHint unchecked because `tools/list` was not sent, and the catalogue carries no annotations (14 of 20). A JavaScript client with TypeScript declarations, OpenAI function definitions and a Postman collection, one language (8 of 15). Total 74.\n\n### Transparency \u0026 trust: Bitpont API and MCP +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- Bitpont API and MCP (58): The editorial half. Closed source under readable terms, which licence the published SDK and documentation for integrations (15 of 30). A detailed privacy notice naming the operator, bases, recipients and browser storage, but it promises no deletion period for server logs and support records and no DPA was found (18 of 30). No deprecation policy or dated notices; the changelog only says changes are additive (5 of 20). Integration providers named by function (Jupiter, deBridge, Velocity, Jito, Kamino, KyberSwap, LI.FI, 1inch); the hosting provider and data locations are given only on request (10 of 20). Total 48.\n\n## Score by category\n\n| Category | Weight | Bitfinex API | Bitpont API and MCP | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 85 | 45 | Bitfinex API +40 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% | 48 | 82 | Bitpont API and MCP +34 |\n| Agent ergonomics | 13% | 61 | 74 | Bitpont API and MCP +13 |\n| Security \u0026 auth | 14% | 62 | 63 | Bitpont API and MCP +1 |\n| Payments \u0026 pricing | 10% | 60 | 90 | Bitpont API and MCP +30 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% | 41 | 14 | Bitfinex API +27 |\n| Transparency \u0026 trust | 7% | 49 | 58 | Bitpont API and MCP +9 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **60.9 · C** | **62.9 · B** | |\n\n## Facts side by side\n\n| Fact | Bitfinex API | Bitpont API and MCP |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | iFinex Inc. | Bitpont (LiMiT) |\n| Hosted endpoint | no (local only) | `https://www.bitpont.com/api/v1/mcp` |\n| Transports |  | Streamable HTTP |\n| Auth | API key | OAuth or 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 | A proprietary hosted service under the Bitpont Terms of Use (LIMIT SRL). The terms licence the published SDK, declarations, examples and API documentation for building integrations, with no copyright fee; the backend is closed |\n| Tools exposed | none | 1148 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-07-18 | none |\n| Terms last updated | couldn't be read | no date given |\n| Privacy policy last updated | couldn't be read | 2026-11-11 |\n| Customer content may train models | couldn't be read | not found in the text |\n| Terms restrict automated access | couldn't be read | not found in the text |\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 | not found in the text |\n| Arbitration or class-action waiver | couldn't be read | not found in the text |\n| Popularity | 480 stars | none |\n\n## How the scores have moved\n\n### Bitfinex API\n\n- +2.5 on 13 November 2026: checklist\n\n### Bitpont API and MCP\n\nNo score change since it was listed.\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**Bitpont API and MCP.** Public market reads, quotes and unsigned transaction drafts work without an account, every trade is signed in the owner's wallet, and an OpenAPI 3.1 file covers all 1,148 operations. There is no status page, the changelog carries no dates, and the hosted MCP server exposes the same 1,148 tools, narrowed by product filters and a search tool.\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### Bitpont API and MCP\n\n1. Connect with `?product=swap` or another product ID, then call `bitpont_findTools` and `bitpont_describeTool` rather than loading all 1,148 tools\n2. Create a private workspace before the first ticket and store its secret and your `requestId`; reuse both to recover an order\n3. Call `bitpont_checkInputs` before preparing a transaction; amounts are base-unit decimal strings\n4. If a request returns 429, wait for the `Retry-After` value. The free budget is 30 units a minute per IP and a batch costs one unit per item\n5. Never repeat a submission whose outcome is unknown; read the execution receipt first\n\n## Questions\n\n### Which is better for AI agents, Bitfinex API or Bitpont API and MCP?\n\nBitpont API and MCP scores 62.9 (B) on agent readiness against Bitfinex API's 60.9 (C), and leads in 5 of 7 scored categories. Bitfinex API leads on reliability and maintenance \u0026 community.\n\n### Do Bitfinex API and Bitpont API and MCP need an API key?\n\nBitfinex API needs an API key. Bitpont API and MCP takes an API key or an OAuth sign-in.\n\n### Can an agent call Bitfinex API and Bitpont API and MCP without installing anything?\n\nNo hosted endpoint is listed for Bitfinex API. Bitpont API and MCP has a hosted endpoint at https://www.bitpont.com/api/v1/mcp.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/bitfinex-vs-bitpont.json, and with the fewest tokens: https://www.anchorterminal.com/compare/bitfinex-vs-bitpont.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"bitfinex\", \"b\": \"bitpont\"}`. From a terminal: `anchor compare bitfinex bitpont`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/bitfinex.json and https://www.anchorterminal.com/api/v1/tools/bitpont.json\n\n## Other comparisons with Bitfinex API or Bitpont API and MCP\n\n- [Bitfinex API vs Bitget](https://www.anchorterminal.com/compare/bitfinex-vs-bitget.md)\n- [Bitfinex API vs Bithumb Open API](https://www.anchorterminal.com/compare/bitfinex-vs-bithumb.md)\n- [Bitfinex API vs Bitstamp API](https://www.anchorterminal.com/compare/bitfinex-vs-bitstamp.md)\n- [Bitfinex API vs Bybit](https://www.anchorterminal.com/compare/bitfinex-vs-bybit.md)\n- [Bitfinex API vs Coinbase Advanced Trade API](https://www.anchorterminal.com/compare/bitfinex-vs-coinbase-advanced-trade.md)\n- [Bitfinex API vs Coinbase MCP server (Coinbase for Agents)](https://www.anchorterminal.com/compare/bitfinex-vs-coinbase-mcp.md)\n- [Bitfinex API vs Crypto.com Exchange API](https://www.anchorterminal.com/compare/bitfinex-vs-crypto-com-exchange.md)\n- [Bitfinex API vs Deribit](https://www.anchorterminal.com/compare/bitfinex-vs-deribit.md)\n- [Bitfinex API vs dYdX](https://www.anchorterminal.com/compare/bitfinex-vs-dydx.md)\n- [Bitfinex API vs Gate](https://www.anchorterminal.com/compare/bitfinex-vs-gate-io.md)\n- [Bitfinex API vs Gemini Exchange API](https://www.anchorterminal.com/compare/bitfinex-vs-gemini-exchange.md)\n- [Bitfinex API vs HTX trading API](https://www.anchorterminal.com/compare/bitfinex-vs-htx.md)\n- [Bitfinex API vs Hyperliquid](https://www.anchorterminal.com/compare/bitfinex-vs-hyperliquid.md)\n- [Bitfinex API vs Kraken API](https://www.anchorterminal.com/compare/bitfinex-vs-kraken.md)\n- [Bitfinex API vs KuCoin](https://www.anchorterminal.com/compare/bitfinex-vs-kucoin.md)\n- [Bitfinex API vs MEXC API](https://www.anchorterminal.com/compare/bitfinex-vs-mexc.md)\n- [Bitfinex API vs OKX API](https://www.anchorterminal.com/compare/bitfinex-vs-okx.md)\n- [Bitfinex API vs Uniswap Trading API](https://www.anchorterminal.com/compare/bitfinex-vs-uniswap.md)\n- [Bitfinex API vs Upbit Open API](https://www.anchorterminal.com/compare/bitfinex-vs-upbit.md)\n- [Bitget vs Bitpont API and MCP](https://www.anchorterminal.com/compare/bitget-vs-bitpont.md)\n- [Bithumb Open API vs Bitpont API and MCP](https://www.anchorterminal.com/compare/bithumb-vs-bitpont.md)\n- [Bitpont API and MCP vs Bitstamp API](https://www.anchorterminal.com/compare/bitpont-vs-bitstamp.md)\n- [Bitpont API and MCP vs Bybit](https://www.anchorterminal.com/compare/bitpont-vs-bybit.md)\n- [Bitpont API and MCP vs Coinbase Advanced Trade API](https://www.anchorterminal.com/compare/bitpont-vs-coinbase-advanced-trade.md)\n- [Bitpont API and MCP vs Coinbase MCP server (Coinbase for Agents)](https://www.anchorterminal.com/compare/bitpont-vs-coinbase-mcp.md)\n- [Bitpont API and MCP vs Crypto.com Exchange API](https://www.anchorterminal.com/compare/bitpont-vs-crypto-com-exchange.md)\n- [Bitpont API and MCP vs Deribit](https://www.anchorterminal.com/compare/bitpont-vs-deribit.md)\n- [Bitpont API and MCP vs dYdX](https://www.anchorterminal.com/compare/bitpont-vs-dydx.md)\n- [Bitpont API and MCP vs Gate](https://www.anchorterminal.com/compare/bitpont-vs-gate-io.md)\n- [Bitpont API and MCP vs Gemini Exchange API](https://www.anchorterminal.com/compare/bitpont-vs-gemini-exchange.md)\n- [Bitpont API and MCP vs HTX trading API](https://www.anchorterminal.com/compare/bitpont-vs-htx.md)\n- [Bitpont API and MCP vs Hyperliquid](https://www.anchorterminal.com/compare/bitpont-vs-hyperliquid.md)\n- [Bitpont API and MCP vs Kraken API](https://www.anchorterminal.com/compare/bitpont-vs-kraken.md)\n- [Bitpont API and MCP vs KuCoin](https://www.anchorterminal.com/compare/bitpont-vs-kucoin.md)\n- [Bitpont API and MCP vs MEXC API](https://www.anchorterminal.com/compare/bitpont-vs-mexc.md)\n- [Bitpont API and MCP vs OKX API](https://www.anchorterminal.com/compare/bitpont-vs-okx.md)\n- [Bitpont API and MCP vs Uniswap Trading API](https://www.anchorterminal.com/compare/bitpont-vs-uniswap.md)\n- [Bitpont API and MCP vs Upbit Open API](https://www.anchorterminal.com/compare/bitpont-vs-upbit.md)\n- [Binance API vs Bitfinex API](https://www.anchorterminal.com/compare/binance-vs-bitfinex.md)\n- [Binance API vs Bitpont API and MCP](https://www.anchorterminal.com/compare/binance-vs-bitpont.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-20",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "1.0",
    "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 Bitpont API and MCP",
        "url": ""
      }
    ],
    "description": "Bitpont scores 62.9 (B) to Bitfinex's 60.9 (C) for exchange market data. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "Bitfinex API C 60.9",
      "Bitpont API and MCP B 62.9",
      "scores"
    ],
    "h1": "Bitfinex API vs Bitpont API and MCP",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/compare/bitfinex-vs-bitpont",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Bitfinex vs Bitpont for AI agents in 2026: scores and prices",
    "toc": null,
    "updated": "2026-11-20",
    "url": "https://www.anchorterminal.com/compare/bitfinex-vs-bitpont"
  },
  "tokens": {
    "markdown": 5150,
    "slim": 1130
  },
  "version": 1
}
