{
  "data": {
    "a": {
      "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
      }
    },
    "answer": "Bitpont API and MCP scores 62.9 (B) on agent readiness against Bybit's 59.8 (C), and leads in 5 of 7 scored categories. Bybit leads on maintenance \u0026 community.",
    "b": {
      "slug": "bybit",
      "name": "Bybit",
      "vendor": "Bybit",
      "vendorUrl": "https://www.bybit.com",
      "company": "bybit.com",
      "kind": "http-api",
      "category": "crypto-exchanges",
      "summary": "Bybit is a centralised crypto exchange for spot, perpetual and futures contracts, options and earn products, reached through its V5 REST and WebSocket API, a FIX order-entry gateway and an official stdio MCP server published from its GitHub organisation.",
      "url": "https://www.anchorterminal.com/tools/bybit",
      "markdownUrl": "https://www.anchorterminal.com/tools/bybit.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/bybit.min.md",
      "cardUrl": "https://www.anchorterminal.com/tools/bybit.card.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/bybit.json",
      "dns": "bybit.grade.anchorterminal.com",
      "repo": "https://github.com/bybit-exchange/trading-mcp",
      "transports": [
        "stdio"
      ],
      "packages": [
        {
          "registry": "npm",
          "name": "bybit-official-trading-server"
        },
        {
          "registry": "pypi",
          "name": "pybit"
        }
      ],
      "auth": "api-key",
      "authNotes": "API key minted on the API management page after a browser sign-up and identity verification, signed per request with HMAC-SHA256 (system-generated secret) or RSA-SHA256 (self-generated key pair) in the X-BAPI-API-KEY, X-BAPI-TIMESTAMP, X-BAPI-SIGN and X-BAPI-RECV-WINDOW headers. Permissions are granted per group (ContractTrade, Spot, Wallet with a separate Withdraw value, Options, Derivatives, Exchange, Earn, Affiliate, BlockTrade) with a readOnly flag, and keys can be bound to IP addresses. A key with no IP binding expires 90 days after creation and can be extended on the management page with email and 2FA codes. Keys for testnet come from testnet.bybit.com and keys for demo trading from the production account in demo mode (https://bybit-exchange.github.io/docs/v5/user/apikey-info and https://bybit-exchange.github.io/docs/faq, checked 2026-11-03).",
      "pricing": "usage",
      "pricingNotes": "The API and the MCP server cost nothing; trades carry Bybit's fees. At VIP 0 the spot fee is 0.1 per cent maker and taker, perpetual and futures contracts 0.02 per cent maker and 0.055 per cent taker, options 0.02 per cent maker and 0.03 per cent taker, with lower tiers by 30-day volume or asset balance and a note that rates vary by region. Fiat pairs, the Adventure Zone, xStocks and pre-market perpetuals have their own tables (https://www.bybit.com/en/help-center/article/Trading-Fee-Structure, last updated 2 September 2026, read 2026-11-03).",
      "priceSummary": "0.1% fee",
      "where": "local",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the V5 docs, the MCP server's README or source, or the fee schedule (checked 2026-11-03). Trading fees are taken from the account balance.",
        "endpoints": []
      },
      "toolCount": 398,
      "popularity": {
        "githubStars": 43,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-11-03"
      },
      "docsUrl": "https://bybit-exchange.github.io/docs/v5/intro",
      "capabilities": [
        "exchange.market-data",
        "exchange.spot-trading",
        "exchange.derivatives",
        "exchange.balances",
        "exchange.transfers",
        "exchange.staking",
        "market.crypto"
      ],
      "tags": [
        "hosted",
        "closed-source",
        "api-key",
        "usage-priced",
        "sandbox",
        "no-status-page",
        "mcp",
        "official",
        "python",
        "typescript",
        "go",
        "java",
        "dotnet"
      ],
      "lastRelease": "2026-10-30",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 59.8,
        "grade": "C",
        "agentReady": false,
        "rank": 805,
        "ranked": true,
        "rankOf": 1563,
        "categoryRank": 11,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 66,
          "maintenance": 66,
          "payments": 60,
          "reliability": 45,
          "schema": 73,
          "security": 60,
          "transparency": 51
        },
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-03"
        },
        "negative": 0,
        "verdict": "Bybit publishes per-endpoint rate limits, a demo environment, scoped keys with a read-only flag and IP binding, and an official stdio MCP server whose 398 tools carry read-only and destructive annotations. There is no status page, no OpenAPI file, no SLA, the MCP server has no toolsets, and the global terms and privacy pages are drawn by script.",
        "bestFor": "An agent trading spot, perpetuals, futures and options in a person's Bybit account outside the excluded jurisdictions, with a demo environment to rehearse on.",
        "strengths": [
          "Official MCP server from Bybit's GitHub organisation with 398 generated tools, each annotated readOnlyHint, destructiveHint and openWorldHint, and market data tools that need no key",
          "Rate limits published per endpoint and per UID with limit, remaining and reset headers on every response, and a documented 403 ban rule for the IP limit",
          "API keys scoped by product group with a read-only flag, a separate Withdraw permission, IP binding and a 90-day expiry for unbound keys",
          "Demo trading at api-demo.bybit.com with self-served demo funds, plus a testnet with its own keys",
          "VIP 0 fees published without login, 0.1 per cent spot and 0.02 per cent maker and 0.055 per cent taker on contracts"
        ],
        "weaknesses": [
          "No status page, incident history or SLA was found; the terms say the API is not guaranteed to be available",
          "No OpenAPI or llms.txt for the V5 API, and the MCP server exposes all 398 tools with no toolset, module or read-only switch",
          "Not in the official MCP registry; the hosted `bybit` entry there is a third party's server, not Bybit's",
          "The global terms, privacy policy and about pages on bybit.com render by script and were not read; the terms read are the UAE-regulated entity's PDF",
          "Changelog entries change response shapes and remove fields without a notice period, such as the Asset Overview restructure of 18 August 2026"
        ],
        "agentNotes": [
          "Create a key with only the permission groups the task needs, set readOnly for research keys, leave Withdraw off and bind an IP, or the key expires after 90 days",
          "Send a unique orderLinkId on every order and reuse it when amending or cancelling, since create-order is asynchronous and confirmed over WebSocket",
          "Read X-Bapi-Limit-Status before bursts and wait until X-Bapi-Limit-Reset-Timestamp on retCode 10006; on HTTP 403 stop all sessions for at least 10 minutes",
          "Test on api-demo.bybit.com with a demo key from the production account, not on testnet demo mode, which the docs call meaningless",
          "Run the MCP server with BYBIT_TESTNET=true first, and only in a client that shows a per-call approval, because the server has no read-only mode of its own"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "C",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 59.8
          }
        ],
        "editorialScores": {
          "ergonomics": 66,
          "maintenance": 66,
          "payments": 60,
          "reliability": 45,
          "schema": 73,
          "security": 60,
          "transparency": 27
        },
        "provenanceScore": 75,
        "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 -g bybit-official-trading-server",
        "http": "curl https://api.bybit.com/v5/market/tickers?category=spot\u0026symbol=BTCUSDT",
        "claudeCode": "claude mcp add bybit -- npx -y bybit-official-trading-server@latest",
        "config": {
          "mcpServers": {
            "bybit": {
              "args": [
                "-y",
                "bybit-official-trading-server@latest"
              ],
              "command": "npx",
              "env": {
                "BYBIT_API_KEY": "YOUR_API_KEY",
                "BYBIT_API_SECRET": "YOUR_API_SECRET",
                "BYBIT_TESTNET": "true"
              }
            }
          }
        }
      },
      "letme": {
        "capability": "https://letme.dev/exchange.market-data",
        "tool": "https://letme.dev/bybit"
      },
      "area": "payments",
      "unitPrices": [
        {
          "item": "Spot trade, VIP 0 maker or taker",
          "unit": "pct",
          "usd": 0.1,
          "note": "crypto-crypto pairs"
        },
        {
          "item": "Perpetual or futures trade, VIP 0 taker",
          "unit": "pct",
          "usd": 0.055,
          "note": "maker 0.02 per cent"
        },
        {
          "item": "Options trade, VIP 0 taker",
          "unit": "pct",
          "usd": 0.03,
          "note": "maker 0.02 per cent"
        }
      ],
      "provenance": {
        "legalEntity": "Bybit Virtual Asset Platform Operator L.L.C. S.P.C",
        "domain": "bybit.com",
        "domainRegistered": "1999-08-05",
        "endpointOnVendorDomain": true,
        "terms": "https://www.bybit.com/en/terms-service",
        "privacy": "https://www.bybit.com/en/privacy-policy",
        "statusPage": "",
        "changelog": "https://bybit-exchange.github.io/docs/changelog/v5",
        "securityTxt": "none",
        "checked": "2026-11-03",
        "notes": [
          "www.bybit.com answers WebFetch with a timeout; its robots.txt (read with curl) allows the help centre, legal and static paths and disallows query-string URLs and x-api endpoints. The terms and privacy pages render by script, so the terms read are the PDF at /common-static/compliance/legal/BYBIT/b2e1c94c53ee5e12e165919de919337e.pdf (Bybit Virtual Asset Platform Operator L.L.C. S.P.C, last updated 23 January 2026, English and Welsh law, SIAC arbitration). The privacy policy was not read.",
          "RDAP gives bybit.com a registration date of 5 August 1999 (CSC Corporate Domains), earlier than the company, so the domain was bought.",
          "https://www.bybit.com/.well-known/security.txt answers 404. bybit-exchange.github.io has no robots.txt and no security.txt.",
          "No status page found; status.bybit.com does not resolve, the docs link none, and a search found only third-party monitors.",
          "The V5 changelog is dated by day; the MCP server's versions are on npm. The P2P service terms on bybit.com name Bybit Technology Limited as the company."
        ],
        "score": 75
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/bybit.json",
      "live": {
        "slug": "bybit",
        "versions": [
          {
            "registry": "github",
            "name": "bybit-exchange/trading-mcp",
            "version": "2.1.28",
            "released": "2026-11-13",
            "seenAt": "2026-11-20T20:18:36.405358017Z"
          },
          {
            "registry": "npm",
            "name": "bybit-official-trading-server",
            "version": "2.1.28",
            "seenAt": "2026-11-20T20:18:35.82359205Z"
          },
          {
            "registry": "pypi",
            "name": "pybit",
            "version": "5.17.2",
            "released": "2026-11-10",
            "seenAt": "2026-11-20T20:18:36.211488295Z"
          }
        ],
        "githubStars": 45,
        "npmWeekly": 1625,
        "pypiWeekly": 88330,
        "securityTxt": {
          "url": "https://bybit.com/.well-known/security.txt",
          "state": "none",
          "checkedAt": "2026-11-20T16:35:23.439738959Z"
        },
        "domain": {
          "domain": "bybit.com",
          "registered": "1999-08-05",
          "source": "https://rdap.verisign.com/com/v1/domain/bybit.com",
          "checkedAt": "2026-11-15T15:23:53.033806563Z"
        },
        "pages": [
          {
            "url": "https://bybit-exchange.github.io/docs/changelog/v5",
            "kind": "changelog",
            "status": 304,
            "checkedAt": "2026-11-19T22:15:33.522097851Z",
            "changedAt": "2026-11-17T20:53:28.442870997Z",
            "fingerprint": "7b446bbb80d6"
          }
        ],
        "github": {
          "repo": "bybit-exchange/trading-mcp",
          "checkedAt": "2026-11-16T11:19:19.302933761Z",
          "stars": 44,
          "archived": false,
          "issuesEnabled": true,
          "pushedAt": "2026-11-13T08:30:20Z",
          "openIssues": 4,
          "openPRs": 0,
          "issuesOpened90d": 7,
          "issuesClosed90d": 4,
          "prsMerged90d": 13,
          "replies": {
            "sampled": 8,
            "unanswered": 2,
            "medianDays": 10.2
          }
        },
        "updatedAt": "2026-11-20T20:18:36.405358017Z"
      }
    },
    "edges": [
      {
        "by": 52,
        "category": "maintenance",
        "leads": "bybit",
        "name": "Maintenance \u0026 community",
        "reasons": {
          "a": "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.",
          "b": "Read as a hosted service with an open-source MCP server. The MCP package shipped 2.1.26 on 30 October 2026 and the V5 changelog's latest entry is 29 October (30). 31 npm versions since 16 April 2026, 11 of them in the last 90 days, and 24 changelog entries in the same window (20). The trading-mcp repository has 4 open issues and 18 forks; whether issues get answers was not checked, and the API has no public forum we could read (10 of 25). Not in the official MCP registry (0). The package has four dependencies, no install scripts, a publish workflow and no test workflow (6 of 10). 66."
        },
        "scores": {
          "a": 14,
          "b": 66
        }
      },
      {
        "by": 30,
        "category": "payments",
        "leads": "bitpont",
        "name": "Payments \u0026 pricing",
        "reasons": {
          "a": "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.",
          "b": "No machine payment protocol (0). The fee schedule is public without login, with VIP 0 maker and taker rates per product and the tier criteria (20). Reading market data needs no key and the demo environment costs nothing, no card is asked for at sign-up (20). A person must register, pass identity verification and mint the key in a browser (0). 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60."
        },
        "scores": {
          "a": 90,
          "b": 60
        }
      },
      {
        "by": 9,
        "category": "schema",
        "leads": "bitpont",
        "name": "Schema \u0026 documentation",
        "reasons": {
          "a": "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.",
          "b": "No OpenAPI or other machine-readable contract for the REST API; the MCP server's 398 tools have zod schemas turned into JSON Schema, so the contract exists for the MCP surface only (12 of 25). No llms.txt; the docs are a public Docusaurus repository (bybit-exchange/docs) whose MDX source an agent can read (5 of 10). The MCP tool descriptions state purpose, rules and an agent hint per tool, and the API reference gives one page per endpoint (15 of 20). Parameters are typed with enums such as category and orderType and required flags (12 of 15). Request and response examples on each endpoint page and an error code page of about 750 codes with text (14 of 15). A dated changelog with 24 entries in the last 90 days, versioned V3 to V5 (15). 73."
        },
        "scores": {
          "a": 82,
          "b": 73
        }
      },
      {
        "by": 8,
        "category": "ergonomics",
        "leads": "bitpont",
        "name": "Agent ergonomics",
        "reasons": {
          "a": "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.",
          "b": "Read for the API with the MCP server beside it. The MCP server has 398 tools in one list with no toolset, module or read-only switch (5 of 25, nothing added back). V5 reads take limit and cursor and category filters (15 of 20). retCode and retMsg on every response with a code list an agent can branch on, though create-order answers before the order is final and the docs say to confirm over WebSocket (14 of 20). orderLinkId makes order retries safe and every MCP tool carries readOnlyHint and destructiveHint (17 of 20). Five required fields on an order, official SDKs in Python, Go, Java and .NET (15). 66."
        },
        "scores": {
          "a": 74,
          "b": 66
        }
      },
      {
        "by": 7,
        "category": "transparency",
        "leads": "bitpont",
        "name": "Transparency \u0026 trust",
        "reasons": {
          "a": "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.",
          "b": "The editorial half. A closed hosted service. The terms read are the UAE entity's PDF served from bybit.com, clear on API use and availability, but the global terms page renders by script and was not read; the MCP server is MIT (12 of 30). The privacy policy was not read, so data handling is unscored (5 of 30). The changelog dates removals and response changes but gives no notice period or deprecation policy (10 of 20). No subprocessor list or data location statement was read (0 of 20). 27."
        },
        "scores": {
          "a": 58,
          "b": 51
        }
      }
    ],
    "facts": [
      {
        "a": "HTTP API",
        "b": "HTTP API",
        "name": "Kind"
      },
      {
        "a": "Bitpont (LiMiT)",
        "b": "Bybit",
        "name": "Vendor"
      },
      {
        "a": "https://www.bitpont.com/api/v1/mcp",
        "b": "no (local only)",
        "name": "Hosted endpoint"
      },
      {
        "a": "Streamable HTTP",
        "b": "stdio",
        "name": "Transports"
      },
      {
        "a": "OAuth or key",
        "b": "API key",
        "name": "Auth"
      },
      {
        "a": "Pay per use",
        "b": "Pay per use",
        "name": "Pricing"
      },
      {
        "a": "no",
        "b": "no",
        "name": "x402"
      },
      {
        "a": "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",
        "b": "none",
        "name": "Licence"
      },
      {
        "a": "1148",
        "b": "398",
        "name": "Tools exposed"
      },
      {
        "a": "no",
        "b": "yes",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "no",
        "name": "llms.txt"
      },
      {
        "a": "none",
        "b": "2026-10-30",
        "name": "Last release"
      },
      {
        "a": "no date given",
        "b": "couldn't be read",
        "name": "Terms last updated"
      },
      {
        "a": "2026-11-11",
        "b": "couldn't be read",
        "name": "Privacy policy last updated"
      },
      {
        "a": "not found in the text",
        "b": "couldn't be read",
        "name": "Customer content may train models"
      },
      {
        "a": "not found in the text",
        "b": "couldn't be read",
        "name": "Terms restrict automated access"
      },
      {
        "a": "not found in the text",
        "b": "couldn't be read",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "not found in the text",
        "b": "couldn't be read",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "not found in the text",
        "b": "couldn't be read",
        "name": "Arbitration or class-action waiver"
      },
      {
        "a": "none",
        "b": "43 stars",
        "name": "Popularity"
      }
    ],
    "faq": [
      {
        "answer": "Bitpont API and MCP scores 62.9 (B) on agent readiness against Bybit's 59.8 (C), and leads in 5 of 7 scored categories. Bybit leads on maintenance \u0026 community.",
        "question": "Which is better for AI agents, Bitpont API and MCP or Bybit?"
      },
      {
        "answer": "Bitpont API and MCP takes an API key or an OAuth sign-in. Bybit needs an API key.",
        "question": "Do Bitpont API and MCP and Bybit need an API key?"
      },
      {
        "answer": "Bitpont API and MCP has a hosted endpoint at https://www.bitpont.com/api/v1/mcp. Bybit runs on your own machine, with no hosted endpoint listed.",
        "question": "Can an agent call Bitpont API and MCP and Bybit without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Schema \u0026 documentation, 82 against 73",
          "Agent ergonomics, 74 against 66",
          "Payments \u0026 pricing, 90 against 60",
          "Transparency \u0026 trust, 58 against 51"
        ],
        "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"
      },
      {
        "aheadOn": [
          "Maintenance \u0026 community, 66 against 14"
        ],
        "also": [
          "Runs on your own machine"
        ],
        "goodFor": "An agent trading spot, perpetuals, futures and options in a person's Bybit account outside the excluded jurisdictions, with a demo environment to rehearse on.",
        "slug": "bybit",
        "watchFor": "No status page, incident history or SLA was found; the terms say the API is not guaranteed to be available"
      }
    ],
    "history": {
      "bitpont": null,
      "bybit": [
        {
          "causes": [
            "method"
          ],
          "date": "2026-11-13",
          "delta": 2.5,
          "from": 57.3,
          "fromGrade": "C",
          "to": 59.8,
          "toGrade": "C"
        }
      ]
    },
    "job": {
      "capability": "exchange.market-data",
      "name": "Exchange market data"
    },
    "others": [
      {
        "json": "https://www.anchorterminal.com/compare/bitfinex-vs-bitpont.json",
        "title": "Bitfinex API vs Bitpont API and MCP",
        "url": "https://www.anchorterminal.com/compare/bitfinex-vs-bitpont"
      },
      {
        "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/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/bitget-vs-bybit.json",
        "title": "Bitget vs Bybit",
        "url": "https://www.anchorterminal.com/compare/bitget-vs-bybit"
      },
      {
        "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/bithumb-vs-bybit.json",
        "title": "Bithumb Open API vs Bybit",
        "url": "https://www.anchorterminal.com/compare/bithumb-vs-bybit"
      },
      {
        "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-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/bitstamp-vs-bybit.json",
        "title": "Bitstamp API vs Bybit",
        "url": "https://www.anchorterminal.com/compare/bitstamp-vs-bybit"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bybit-vs-coinbase-advanced-trade.json",
        "title": "Bybit vs Coinbase Advanced Trade API",
        "url": "https://www.anchorterminal.com/compare/bybit-vs-coinbase-advanced-trade"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bybit-vs-coinbase-mcp.json",
        "title": "Bybit vs Coinbase MCP server (Coinbase for Agents)",
        "url": "https://www.anchorterminal.com/compare/bybit-vs-coinbase-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bybit-vs-crypto-com-exchange.json",
        "title": "Bybit vs Crypto.com Exchange API",
        "url": "https://www.anchorterminal.com/compare/bybit-vs-crypto-com-exchange"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bybit-vs-deribit.json",
        "title": "Bybit vs Deribit",
        "url": "https://www.anchorterminal.com/compare/bybit-vs-deribit"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bybit-vs-dydx.json",
        "title": "Bybit vs dYdX",
        "url": "https://www.anchorterminal.com/compare/bybit-vs-dydx"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bybit-vs-gate-io.json",
        "title": "Bybit vs Gate",
        "url": "https://www.anchorterminal.com/compare/bybit-vs-gate-io"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bybit-vs-gemini-exchange.json",
        "title": "Bybit vs Gemini Exchange API",
        "url": "https://www.anchorterminal.com/compare/bybit-vs-gemini-exchange"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bybit-vs-htx.json",
        "title": "Bybit vs HTX trading API",
        "url": "https://www.anchorterminal.com/compare/bybit-vs-htx"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bybit-vs-hyperliquid.json",
        "title": "Bybit vs Hyperliquid",
        "url": "https://www.anchorterminal.com/compare/bybit-vs-hyperliquid"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bybit-vs-kraken.json",
        "title": "Bybit vs Kraken API",
        "url": "https://www.anchorterminal.com/compare/bybit-vs-kraken"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bybit-vs-kucoin.json",
        "title": "Bybit vs KuCoin",
        "url": "https://www.anchorterminal.com/compare/bybit-vs-kucoin"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bybit-vs-mexc.json",
        "title": "Bybit vs MEXC API",
        "url": "https://www.anchorterminal.com/compare/bybit-vs-mexc"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bybit-vs-okx.json",
        "title": "Bybit vs OKX API",
        "url": "https://www.anchorterminal.com/compare/bybit-vs-okx"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bybit-vs-uniswap.json",
        "title": "Bybit vs Uniswap Trading API",
        "url": "https://www.anchorterminal.com/compare/bybit-vs-uniswap"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bybit-vs-upbit.json",
        "title": "Bybit vs Upbit Open API",
        "url": "https://www.anchorterminal.com/compare/bybit-vs-upbit"
      },
      {
        "json": "https://www.anchorterminal.com/compare/binance-vs-bitpont.json",
        "title": "Binance API vs Bitpont API and MCP",
        "url": "https://www.anchorterminal.com/compare/binance-vs-bitpont"
      },
      {
        "json": "https://www.anchorterminal.com/compare/binance-vs-bybit.json",
        "title": "Binance API vs Bybit",
        "url": "https://www.anchorterminal.com/compare/binance-vs-bybit"
      }
    ],
    "panel": null,
    "scores": [
      {
        "bitpont": 45,
        "by": 0,
        "bybit": 45,
        "edge": "",
        "key": "reliability",
        "name": "Reliability",
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "bitpont": 82,
        "by": 9,
        "bybit": 73,
        "edge": "bitpont",
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "weight": 13
      },
      {
        "bitpont": 74,
        "by": 8,
        "bybit": 66,
        "edge": "bitpont",
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "weight": 13
      },
      {
        "bitpont": 63,
        "by": 3,
        "bybit": 60,
        "edge": "bitpont",
        "key": "security",
        "name": "Security \u0026 auth",
        "weight": 14
      },
      {
        "bitpont": 90,
        "by": 30,
        "bybit": 60,
        "edge": "bitpont",
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "bitpont": 14,
        "by": 52,
        "bybit": 66,
        "edge": "bybit",
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "weight": 7
      },
      {
        "bitpont": 58,
        "by": 7,
        "bybit": 51,
        "edge": "bitpont",
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "weight": 7
      }
    ],
    "summary": "Bitpont API and MCP scores 62.9 (B) on agent readiness against Bybit's 59.8 (C), and leads in 5 of 7 scored categories. Bybit leads on maintenance \u0026 community. Both do exchange market data.",
    "tasks": null,
    "tutorials": [],
    "verdicts": {
      "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.",
      "bybit": "Bybit publishes per-endpoint rate limits, a demo environment, scoped keys with a read-only flag and IP binding, and an official stdio MCP server whose 398 tools carry read-only and destructive annotations. There is no status page, no OpenAPI file, no SLA, the MCP server has no toolsets, and the global terms and privacy pages are drawn by script."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/bitpont-vs-bybit",
    "json": "https://www.anchorterminal.com/compare/bitpont-vs-bybit.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/bitpont-vs-bybit.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/compare/bitpont-vs-bybit.min.md"
  },
  "markdown": "Bitpont API and MCP scores 62.9 (B) on agent readiness against Bybit's 59.8 (C), and leads in 5 of 7 scored categories. Bybit leads on maintenance \u0026 community. Both do exchange market data.\n\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- Bybit: grade C, 59.8/100, rank #805 of 1563. Markdown https://www.anchorterminal.com/tools/bybit.md · JSON https://www.anchorterminal.com/api/v1/tools/bybit.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### 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 73\n- Agent ergonomics, 74 against 66\n- Payments \u0026 pricing, 90 against 60\n- Transparency \u0026 trust, 58 against 51\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### Bybit (C)\n\nGood for: An agent trading spot, perpetuals, futures and options in a person's Bybit account outside the excluded jurisdictions, with a demo environment to rehearse on.\n\nAhead on:\n- Maintenance \u0026 community, 66 against 14\n\nAlso in its favour:\n- Runs on your own machine\n\nWatch for: No status page, incident history or SLA was found; the terms say the API is not guaranteed to be available\n\n\n## Why the edge\n\n### Maintenance \u0026 community: Bybit +52\n\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- Bybit (66): Read as a hosted service with an open-source MCP server. The MCP package shipped 2.1.26 on 30 October 2026 and the V5 changelog's latest entry is 29 October (30). 31 npm versions since 16 April 2026, 11 of them in the last 90 days, and 24 changelog entries in the same window (20). The trading-mcp repository has 4 open issues and 18 forks; whether issues get answers was not checked, and the API has no public forum we could read (10 of 25). Not in the official MCP registry (0). The package has four dependencies, no install scripts, a publish workflow and no test workflow (6 of 10). 66.\n\n### Payments \u0026 pricing: Bitpont API and MCP +30\n\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- Bybit (60): No machine payment protocol (0). The fee schedule is public without login, with VIP 0 maker and taker rates per product and the tier criteria (20). Reading market data needs no key and the demo environment costs nothing, no card is asked for at sign-up (20). A person must register, pass identity verification and mint the key in a browser (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\n### Schema \u0026 documentation: Bitpont API and MCP +9\n\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- Bybit (73): No OpenAPI or other machine-readable contract for the REST API; the MCP server's 398 tools have zod schemas turned into JSON Schema, so the contract exists for the MCP surface only (12 of 25). No llms.txt; the docs are a public Docusaurus repository (bybit-exchange/docs) whose MDX source an agent can read (5 of 10). The MCP tool descriptions state purpose, rules and an agent hint per tool, and the API reference gives one page per endpoint (15 of 20). Parameters are typed with enums such as category and orderType and required flags (12 of 15). Request and response examples on each endpoint page and an error code page of about 750 codes with text (14 of 15). A dated changelog with 24 entries in the last 90 days, versioned V3 to V5 (15). 73.\n\n### Agent ergonomics: Bitpont API and MCP +8\n\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- Bybit (66): Read for the API with the MCP server beside it. The MCP server has 398 tools in one list with no toolset, module or read-only switch (5 of 25, nothing added back). V5 reads take limit and cursor and category filters (15 of 20). retCode and retMsg on every response with a code list an agent can branch on, though create-order answers before the order is final and the docs say to confirm over WebSocket (14 of 20). orderLinkId makes order retries safe and every MCP tool carries readOnlyHint and destructiveHint (17 of 20). Five required fields on an order, official SDKs in Python, Go, Java and .NET (15). 66.\n\n### Transparency \u0026 trust: Bitpont API and MCP +7\n\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- Bybit (51): The editorial half. A closed hosted service. The terms read are the UAE entity's PDF served from bybit.com, clear on API use and availability, but the global terms page renders by script and was not read; the MCP server is MIT (12 of 30). The privacy policy was not read, so data handling is unscored (5 of 30). The changelog dates removals and response changes but gives no notice period or deprecation policy (10 of 20). No subprocessor list or data location statement was read (0 of 20). 27.\n\n## Score by category\n\n| Category | Weight | Bitpont API and MCP | Bybit | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 45 | 45 | even |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% | 82 | 73 | Bitpont API and MCP +9 |\n| Agent ergonomics | 13% | 74 | 66 | Bitpont API and MCP +8 |\n| Security \u0026 auth | 14% | 63 | 60 | Bitpont API and MCP +3 |\n| Payments \u0026 pricing | 10% | 90 | 60 | Bitpont API and MCP +30 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% | 14 | 66 | Bybit +52 |\n| Transparency \u0026 trust | 7% | 58 | 51 | Bitpont API and MCP +7 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **62.9 · B** | **59.8 · C** | |\n\n## Facts side by side\n\n| Fact | Bitpont API and MCP | Bybit |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Bitpont (LiMiT) | Bybit |\n| Hosted endpoint | `https://www.bitpont.com/api/v1/mcp` | no (local only) |\n| Transports | Streamable HTTP | stdio |\n| Auth | OAuth or key | API key |\n| Pricing | Pay per use | Pay per use |\n| x402 | no | no |\n| Licence | 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 | none |\n| Tools exposed | 1148 | 398 |\n| Read-only variant documented | no | yes |\n| llms.txt | yes | no |\n| Last release | none | 2026-10-30 |\n| Terms last updated | no date given | couldn't be read |\n| Privacy policy last updated | 2026-11-11 | couldn't be read |\n| Customer content may train models | not found in the text | couldn't be read |\n| Terms restrict automated access | not found in the text | couldn't be read |\n| Terms restrict benchmarking | not found in the text | couldn't be read |\n| Terms or service can change without notice | not found in the text | couldn't be read |\n| Arbitration or class-action waiver | not found in the text | couldn't be read |\n| Popularity | none | 43 stars |\n\n## How the scores have moved\n\n### Bitpont API and MCP\n\nNo score change since it was listed.\n\n### Bybit\n\n- +2.5 on 13 November 2026: checklist\n\n## Verdicts\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**Bybit.** Bybit publishes per-endpoint rate limits, a demo environment, scoped keys with a read-only flag and IP binding, and an official stdio MCP server whose 398 tools carry read-only and destructive annotations. There is no status page, no OpenAPI file, no SLA, the MCP server has no toolsets, and the global terms and privacy pages are drawn by script.\n\n## Before you call either\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### Bybit\n\n1. Create a key with only the permission groups the task needs, set readOnly for research keys, leave Withdraw off and bind an IP, or the key expires after 90 days\n2. Send a unique orderLinkId on every order and reuse it when amending or cancelling, since create-order is asynchronous and confirmed over WebSocket\n3. Read X-Bapi-Limit-Status before bursts and wait until X-Bapi-Limit-Reset-Timestamp on retCode 10006; on HTTP 403 stop all sessions for at least 10 minutes\n4. Test on api-demo.bybit.com with a demo key from the production account, not on testnet demo mode, which the docs call meaningless\n5. Run the MCP server with BYBIT_TESTNET=true first, and only in a client that shows a per-call approval, because the server has no read-only mode of its own\n\n## Questions\n\n### Which is better for AI agents, Bitpont API and MCP or Bybit?\n\nBitpont API and MCP scores 62.9 (B) on agent readiness against Bybit's 59.8 (C), and leads in 5 of 7 scored categories. Bybit leads on maintenance \u0026 community.\n\n### Do Bitpont API and MCP and Bybit need an API key?\n\nBitpont API and MCP takes an API key or an OAuth sign-in. Bybit needs an API key.\n\n### Can an agent call Bitpont API and MCP and Bybit without installing anything?\n\nBitpont API and MCP has a hosted endpoint at https://www.bitpont.com/api/v1/mcp. Bybit runs on your own machine, with no hosted endpoint listed.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/bitpont-vs-bybit.json, and with the fewest tokens: https://www.anchorterminal.com/compare/bitpont-vs-bybit.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"bitpont\", \"b\": \"bybit\"}`. From a terminal: `anchor compare bitpont bybit`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/bitpont.json and https://www.anchorterminal.com/api/v1/tools/bybit.json\n\n## Other comparisons with Bitpont API and MCP or Bybit\n\n- [Bitfinex API vs Bitpont API and MCP](https://www.anchorterminal.com/compare/bitfinex-vs-bitpont.md)\n- [Bitfinex API vs Bybit](https://www.anchorterminal.com/compare/bitfinex-vs-bybit.md)\n- [Bitget vs Bitpont API and MCP](https://www.anchorterminal.com/compare/bitget-vs-bitpont.md)\n- [Bitget vs Bybit](https://www.anchorterminal.com/compare/bitget-vs-bybit.md)\n- [Bithumb Open API vs Bitpont API and MCP](https://www.anchorterminal.com/compare/bithumb-vs-bitpont.md)\n- [Bithumb Open API vs Bybit](https://www.anchorterminal.com/compare/bithumb-vs-bybit.md)\n- [Bitpont API and MCP vs Bitstamp API](https://www.anchorterminal.com/compare/bitpont-vs-bitstamp.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- [Bitstamp API vs Bybit](https://www.anchorterminal.com/compare/bitstamp-vs-bybit.md)\n- [Bybit vs Coinbase Advanced Trade API](https://www.anchorterminal.com/compare/bybit-vs-coinbase-advanced-trade.md)\n- [Bybit vs Coinbase MCP server (Coinbase for Agents)](https://www.anchorterminal.com/compare/bybit-vs-coinbase-mcp.md)\n- [Bybit vs Crypto.com Exchange API](https://www.anchorterminal.com/compare/bybit-vs-crypto-com-exchange.md)\n- [Bybit vs Deribit](https://www.anchorterminal.com/compare/bybit-vs-deribit.md)\n- [Bybit vs dYdX](https://www.anchorterminal.com/compare/bybit-vs-dydx.md)\n- [Bybit vs Gate](https://www.anchorterminal.com/compare/bybit-vs-gate-io.md)\n- [Bybit vs Gemini Exchange API](https://www.anchorterminal.com/compare/bybit-vs-gemini-exchange.md)\n- [Bybit vs HTX trading API](https://www.anchorterminal.com/compare/bybit-vs-htx.md)\n- [Bybit vs Hyperliquid](https://www.anchorterminal.com/compare/bybit-vs-hyperliquid.md)\n- [Bybit vs Kraken API](https://www.anchorterminal.com/compare/bybit-vs-kraken.md)\n- [Bybit vs KuCoin](https://www.anchorterminal.com/compare/bybit-vs-kucoin.md)\n- [Bybit vs MEXC API](https://www.anchorterminal.com/compare/bybit-vs-mexc.md)\n- [Bybit vs OKX API](https://www.anchorterminal.com/compare/bybit-vs-okx.md)\n- [Bybit vs Uniswap Trading API](https://www.anchorterminal.com/compare/bybit-vs-uniswap.md)\n- [Bybit vs Upbit Open API](https://www.anchorterminal.com/compare/bybit-vs-upbit.md)\n- [Binance API vs Bitpont API and MCP](https://www.anchorterminal.com/compare/binance-vs-bitpont.md)\n- [Binance API vs Bybit](https://www.anchorterminal.com/compare/binance-vs-bybit.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": "Bitpont API and MCP vs Bybit",
        "url": ""
      }
    ],
    "description": "Bitpont scores 62.9 (B) to Bybit's 59.8 (C) for exchange market data. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "Bitpont API and MCP B 62.9",
      "Bybit C 59.8",
      "scores"
    ],
    "h1": "Bitpont API and MCP vs Bybit",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/compare/bitpont-vs-bybit",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Bitpont vs Bybit for AI agents in 2026: scores and prices",
    "toc": null,
    "updated": "2026-11-20",
    "url": "https://www.anchorterminal.com/compare/bitpont-vs-bybit"
  },
  "tokens": {
    "markdown": 4600,
    "slim": 1080
  },
  "version": 1
}
