{
  "data": {
    "a": {
      "slug": "bitget",
      "name": "Bitget",
      "vendor": "BTG Technology Holdings Limited",
      "vendorUrl": "https://www.bitget.com",
      "company": "bitget.com",
      "kind": "http-api",
      "category": "crypto-exchanges",
      "summary": "Bitget is a centralised crypto exchange for spot, margin, futures, earn and tokenised stocks, reached through its Unified Trading Account v3 REST and WebSocket API and an Agent Hub toolkit with a stdio MCP server, CLI and agent skills.",
      "url": "https://www.anchorterminal.com/tools/bitget",
      "markdownUrl": "https://www.anchorterminal.com/tools/bitget.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/bitget.min.md",
      "cardUrl": "https://www.anchorterminal.com/tools/bitget.card.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/bitget.json",
      "dns": "bitget.grade.anchorterminal.com",
      "repo": "https://github.com/Bitget-AI/agent-mcp",
      "transports": [
        "stdio"
      ],
      "packages": [
        {
          "registry": "npm",
          "name": "@bitget-ai/bitget-agent-mcp"
        },
        {
          "registry": "npm",
          "name": "bitget-mcp-server"
        }
      ],
      "auth": "api-key",
      "authNotes": "API key, system-generated secret and user-set passphrase minted under API Key Management after a browser sign-up and identity verification, up to 50 keys per UID, each with read or read-and-write permission, signed per request with HMAC-SHA256 or RSA over timestamp, method, path and body in the ACCESS-KEY, ACCESS-SIGN, ACCESS-TIMESTAMP and ACCESS-PASSPHRASE headers. Binding an IP is recommended, not required. Sub-account keys carry trade or management permission, read-only or read-write, once the main account enables key management for them. Demo keys are minted in demo mode and sent with the paptrading header set to 1 (https://www.bitget.com/legacy-docs/uta/guide, checked 2026-11-03).",
      "pricing": "usage",
      "pricingNotes": "The API and the Agent Hub packages cost nothing; trades carry Bitget's fees. Base rates are 0.1 per cent maker and taker on spot and 0.02 per cent maker and 0.06 per cent taker on futures before VIP tiers or the BGB discount, which applies to spot only at a rate the article says to read on the live schedule. The fee page draws its table by script (https://www.bitget.com/support/articles/12560603892734, 20 August 2026, checked 2026-11-03).",
      "priceSummary": "0.1% fee",
      "where": "local",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the UTA docs, the Agent Hub READMEs, the SDK's openapi.yaml or the fee article (checked 2026-11-03).",
        "endpoints": []
      },
      "toolCount": 14,
      "popularity": {
        "githubStars": 234,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-11-03"
      },
      "docsUrl": "https://www.bitget.com/api-doc/uta/intro",
      "registryName": "io.github.Bitget-AI/bitget-agent-mcp",
      "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",
        "mcp-registry",
        "official",
        "read-only-mode",
        "agent-skills",
        "cli",
        "python",
        "typescript",
        "go",
        "java",
        "php"
      ],
      "lastRelease": "2026-10-30",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 56.4,
        "grade": "C",
        "agentReady": false,
        "rank": 945,
        "ranked": true,
        "rankOf": 1563,
        "categoryRank": 15,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 83,
          "maintenance": 78,
          "payments": 60,
          "reliability": 40,
          "schema": 74,
          "security": 62,
          "transparency": 65
        },
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-03"
        },
        "negative": -8,
        "negativeNotes": [
          "Security incident of 24 September 2026. An attacker who had obtained high-level internal credentials through a vulnerability in a third-party security product injected forged withdrawal commands into Bitget's wallet back end and moved about 388 million dollars in 13 assets on 11 chains from hot and warm wallets. Withdrawals, fiat and C2C were paused from 24 September and restored in phases from 28 September to 2 October 2026; trading, deposits and the API kept running. Bitget says user balances were unaffected, the Protection Fund covered the loss and was topped above 300 million dollars, private keys and cold wallets were untouched, and Mandiant and SlowMist reports of 30 September agree with its account. A fixed, documented incident with a public root cause, so below the top of the range. Sources https://www.bitget.com/academy/12560603896113 (updated 20 October 2026) and https://www.bitget.com/support/articles/12560603896110 (26 September 2026), read 2026-11-03."
        ],
        "verdict": "Bitget's official MCP server keeps the default surface to 14 intent tools with discovery, read-only and paper-trading switches, dry runs and a confirmation gate on withdrawals, over an API with demo trading. A 388 million dollar wallet breach in September 2026 paused withdrawals for eight days, and there is no status page, SLA or readable fee table.",
        "bestFor": "An agent trading spot, futures and earn products in a person's Bitget account outside the prohibited list, with the smallest default MCP surface of the exchanges graded and a paper-trading switch.",
        "strengths": [
          "Official stdio MCP server with 14 intent tools by default, progressive discovery, `--read-only`, `--paper-trading`, `dryRun: true` on writes and `confirm: true` required for withdrawals and cancel-all",
          "Demo trading on the production host with demo keys and a paptrading header, and a TypeScript agent SDK whose openapi.yaml types all 109 UTA v3 operations",
          "Terms name BTG Technology Holdings Limited with Hong Kong law, and the privacy notice gives retention periods of 7 and up to 10 years",
          "Changelog with 58 dated entries since 5 August 2026, including preview notices with demo and live dates for WebSocket changes",
          "Base fees public in a help article, 0.1 per cent spot and 0.02 per cent maker and 0.06 per cent taker on futures"
        ],
        "weaknesses": [
          "Hot and warm wallets lost about 388 million dollars on 24 September 2026 to forged withdrawal commands, and withdrawals were paused until 2 October",
          "No status page, incident history or SLA; the terms disclaim uninterrupted access",
          "Two official MCP servers coexist, the V2-based bitget-mcp-server on Bitget's own Agent Hub page and the v3 bitget-agent-mcp on GitHub and npm, with different tool counts",
          "The current api-doc site renders every page as the UTA overview for a reader without script; the legacy docs were used instead",
          "Keys have read or read-and-write only, with no separate withdrawal permission in the docs read, and IP binding is recommended rather than required"
        ],
        "agentNotes": [
          "Run `npx -y @bitget-ai/bitget-agent-mcp --read-only` for research and `--paper-trading` with a demo key before any live order; the two flags cannot be combined",
          "Call discover({}) first, then the intent verbs; add `dryRun: true` to any write to preview it, and pass `confirm: true` only after the person has agreed to a withdraw or cancelAll",
          "Send a unique clientOid of at most 64 characters on every order and reuse it on retry; orderId wins when both are sent",
          "Stay under 10 requests a second per endpoint on a new account and 6,000 a minute per IP; the SDK retries on 429, so do not add a second retry loop",
          "Bind the key to an IP and keep write permission off a research key; the docs read show no separate withdrawal scope"
        ],
        "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": 56.4
          }
        ],
        "editorialScores": {
          "ergonomics": 83,
          "maintenance": 78,
          "payments": 60,
          "reliability": 40,
          "schema": 74,
          "security": 62,
          "transparency": 53
        },
        "provenanceScore": 76,
        "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": "npx -y @bitget-ai/bitget-agent-mcp",
        "http": "curl https://api.bitget.com/api/v3/market/tickers?category=SPOT\u0026symbol=BTCUSDT",
        "claudeCode": "claude mcp add bitget -- npx -y @bitget-ai/bitget-agent-mcp --read-only",
        "config": {
          "mcpServers": {
            "bitget": {
              "args": [
                "-y",
                "@bitget-ai/bitget-agent-mcp",
                "--read-only"
              ],
              "command": "npx",
              "env": {
                "BITGET_API_KEY": "YOUR_API_KEY",
                "BITGET_PASSPHRASE": "YOUR_PASSPHRASE",
                "BITGET_SECRET_KEY": "YOUR_SECRET_KEY"
              }
            }
          }
        }
      },
      "letme": {
        "capability": "https://letme.dev/exchange.market-data",
        "tool": "https://letme.dev/bitget"
      },
      "area": "payments",
      "unitPrices": [
        {
          "item": "Spot trade, base maker or taker",
          "unit": "pct",
          "usd": 0.1,
          "note": "before VIP tiers and the BGB discount"
        },
        {
          "item": "Futures trade, base taker",
          "unit": "pct",
          "usd": 0.06,
          "note": "maker 0.02 per cent"
        }
      ],
      "provenance": {
        "legalEntity": "BTG Technology Holdings Limited",
        "domain": "bitget.com",
        "domainRegistered": "2003-02-03",
        "endpointOnVendorDomain": true,
        "terms": "https://www.bitget.com/support/articles/360014944032-terms-of-use",
        "privacy": "https://www.bitget.com/support/articles/360015150651",
        "statusPage": "",
        "changelog": "https://www.bitget.com/legacy-docs/uta/changelog",
        "securityTxt": "none",
        "checked": "2026-11-03",
        "notes": [
          "Terms of Use last updated 20 October 2026 name BTG Technology Holdings Limited under Hong Kong law with HKIAC arbitration; the privacy notice (5 December 2025) names the same company as controller under the Seychelles Data Protection Act 2023 with BTGT Europe Limited, UAB as EEA representative. /user-agreement and /privacy-policy answer 404; the documents live in the support centre.",
          "www.bitget.com/robots.txt disallows internal, search, calendar, wiki and register paths; the api-doc, legacy-docs, support, academy, blog and activity-hub paths are allowed.",
          "RDAP gives bitget.com a registration date of 3 February 2003 (MarkMonitor), earlier than the exchange, so the domain was bought.",
          "https://www.bitget.com/.well-known/security.txt answers 404; the Agent Hub README gives security@bitget.com for reports. No status page found; status.bitget.com does not resolve and the docs link none.",
          "The current api-doc site answers every path with the UTA overview for a reader without script; the legacy docs at /legacy-docs/uta/ were read for the guide, rate limits and changelog."
        ],
        "score": 76
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/bitget.json",
      "live": {
        "slug": "bitget",
        "versions": [
          {
            "registry": "mcp-registry",
            "name": "io.github.Bitget-AI/bitget-agent-mcp",
            "version": "3.0.2",
            "seenAt": "2026-11-19T23:10:32.423145357Z"
          },
          {
            "registry": "npm",
            "name": "@bitget-ai/bitget-agent-mcp",
            "version": "3.3.1",
            "seenAt": "2026-11-20T20:16:42.450612679Z"
          },
          {
            "registry": "npm",
            "name": "bitget-mcp-server",
            "version": "1.1.0",
            "seenAt": "2026-11-20T20:16:42.932651262Z"
          }
        ],
        "githubStars": 2,
        "npmWeekly": 270,
        "securityTxt": {
          "url": "https://bitget.com/.well-known/security.txt",
          "state": "none",
          "checkedAt": "2026-11-20T16:36:57.334557659Z"
        },
        "domain": {
          "domain": "bitget.com",
          "registered": "2003-02-03",
          "source": "https://rdap.verisign.com/com/v1/domain/bitget.com",
          "checkedAt": "2026-11-15T15:24:35.411747649Z"
        },
        "pages": [
          {
            "url": "https://www.bitget.com/legacy-docs/uta/changelog",
            "kind": "changelog",
            "status": 304,
            "checkedAt": "2026-11-19T22:41:09.281796723Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "3b27e82e7d79"
          },
          {
            "url": "https://www.bitget.com/support/articles/360015150651",
            "kind": "privacy",
            "status": 200,
            "checkedAt": "2026-11-19T22:41:14.402728657Z",
            "changedAt": "2026-11-11T17:16:43.431244098Z",
            "fingerprint": "fe42b857fbc2"
          },
          {
            "url": "https://www.bitget.com/support/articles/360014944032-terms-of-use",
            "kind": "terms",
            "status": 200,
            "checkedAt": "2026-11-19T22:41:11.895739785Z",
            "changedAt": "2026-11-11T17:16:40.565375553Z",
            "fingerprint": "8ba72aa23554"
          }
        ],
        "github": {
          "repo": "bitget-ai/agent-mcp",
          "checkedAt": "2026-11-16T11:18:55.360670189Z",
          "stars": 1,
          "archived": false,
          "issuesEnabled": true,
          "pushedAt": "2026-09-01T10:12:14Z",
          "openIssues": 0,
          "openPRs": 1,
          "issuesOpened90d": 0,
          "issuesClosed90d": 0,
          "prsMerged90d": 1,
          "ci": {
            "branch": "main",
            "runs": 3,
            "success": 1,
            "failure": 2,
            "other": 0,
            "latest": "success",
            "latestAt": "2026-09-01T10:12:47Z"
          }
        },
        "updatedAt": "2026-11-20T20:16:44.718506958Z"
      }
    },
    "answer": "Bitpont API and MCP scores 62.9 (B) on agent readiness against Bitget's 56.4 (C), and leads in 4 of 7 scored categories. Bitget leads on agent ergonomics, maintenance \u0026 community and transparency \u0026 trust.",
    "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": 64,
        "category": "maintenance",
        "leads": "bitget",
        "name": "Maintenance \u0026 community",
        "reasons": {
          "a": "Read as a hosted service with an open-source toolkit. The UTA changelog's latest launched entry is 30 October 2026 and a preview entry 3 November; the MCP package shipped 3.3.1 on 20 September and agent-skill was pushed 30 October (30). 58 dated changelog entries since 5 August 2026 and six MCP versions since June (20). Issue trackers on the Bitget-AI repositories (11 open on agent_hub) and a support centre; replies were not checked (10 of 25). In the official MCP registry under io.github.Bitget-AI, a GitHub namespace, with official SDKs in five languages (10 of 15). CI workflow with coverage, npm provenance attestations, two runtime dependencies, no install scripts (8 of 10). 78.",
          "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": 78,
          "b": 14
        }
      },
      {
        "by": 30,
        "category": "payments",
        "leads": "bitpont",
        "name": "Payments \u0026 pricing",
        "reasons": {
          "a": "No machine payment protocol (0). Base spot and futures rates are stated in a help article without login, the tier table draws by script (20). Market data needs no key, demo trading costs nothing and no card is asked for at sign-up (20). A person registers, verifies identity and mints 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.",
          "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": 9,
        "category": "ergonomics",
        "leads": "bitget",
        "name": "Agent ergonomics",
        "reasons": {
          "a": "Read for the API with the MCP server as the agent route. 14 compact tools by default, module filters, a full surface on request and progressive discovery (25). Cursor pagination on CFD order history since 15 October 2026 and limit parameters on lists (15 of 20). Uniform ok or error result shape from the SDK with typed error classes and compact JSON in the text channel (13 of 20). clientOid on orders, `dryRun: true` on every write, `confirm: true` gating cancelAll and withdraw, annotations derived from risk level including readOnlyHint, destructiveHint and idempotentHint (18 of 20). Few required fields, official SDKs in five languages plus the TypeScript agent SDK and a CLI (12 of 15). 83.",
          "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": 83,
          "b": 74
        }
      },
      {
        "by": 8,
        "category": "schema",
        "leads": "bitpont",
        "name": "Schema \u0026 documentation",
        "reasons": {
          "a": "The agent SDK ships openapi.yaml with 109 typed UTA v3 operations from which the tools are generated, a machine-readable contract from the vendor's own organisation though not on the docs site (20 of 25). llms.txt in the SDK and MCP repositories; the docs site has none (6 of 10). Intent tools with a discover tool that explains each verb, action and its risk level, and the server's initialize instructions state surface, modules and read-only posture (15 of 20). Typed inputs with enums and required fields from the OpenAPI source (12 of 15). Examples in the quick start and READMEs, a REST error code page in the legacy docs that we did not read in full (9 of 15). Changelog by day with preview notices and effective dates (12 of 15). 74.",
          "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": 74,
          "b": 82
        }
      },
      {
        "by": 7,
        "category": "transparency",
        "leads": "bitget",
        "name": "Transparency \u0026 trust",
        "reasons": {
          "a": "The editorial half. A closed hosted service with clear terms naming BTG Technology Holdings Limited; the toolkit is MIT (15 of 30). The privacy notice names the controller and EEA representative, gives 7-year and up to 10-year retention for compliance and litigation, and names recipients by category only (18 of 30). Deprecations and parameter changes carry effective dates (delta mode deprecated 27 August, symbol and category required from 30 September, snapshot changes with demo and live dates) but no written policy (15 of 20). Recipients by category, transfers under Seychelles law with no locations or provider names (5 of 20). 53.",
          "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": 65,
          "b": 58
        }
      },
      {
        "by": 5,
        "category": "reliability",
        "leads": "bitpont",
        "name": "Reliability",
        "reasons": {
          "a": "Graded with the hosted lines on the UTA v3 API at api.bitget.com. No status page found (status.bitget.com does not resolve, the docs link none), so 0 for the page and 5 for no readable history; the September 2026 breach is in the deduction, not here. Rate limits are published as 6,000 per IP per minute and per-endpoint UID limits by VIP level (15). An x-mbx-used-remain-limit header is documented and the agent SDK backs off on 429, orders take a clientOid of up to 64 characters, but the breach error code and a Retry-After rule were not read (10 of 15). No SLA (0). UTA v3 is the production API (10). 40.",
          "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": 40,
          "b": 45
        }
      }
    ],
    "facts": [
      {
        "a": "HTTP API",
        "b": "HTTP API",
        "name": "Kind"
      },
      {
        "a": "BTG Technology Holdings Limited",
        "b": "Bitpont (LiMiT)",
        "name": "Vendor"
      },
      {
        "a": "no (local only)",
        "b": "https://www.bitpont.com/api/v1/mcp",
        "name": "Hosted endpoint"
      },
      {
        "a": "stdio",
        "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": "none",
        "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": "14",
        "b": "1148",
        "name": "Tools exposed"
      },
      {
        "a": "yes",
        "b": "no",
        "name": "Read-only variant documented"
      },
      {
        "a": "no",
        "b": "yes",
        "name": "llms.txt"
      },
      {
        "a": "io.github.Bitget-AI/bitget-agent-mcp",
        "b": "not listed",
        "name": "MCP registry"
      },
      {
        "a": "2026-10-30",
        "b": "none",
        "name": "Last release"
      },
      {
        "a": "2026-10-20",
        "b": "no date given",
        "name": "Terms last updated"
      },
      {
        "a": "2025-12-05",
        "b": "2026-11-11",
        "name": "Privacy policy last updated"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Customer content may train models"
      },
      {
        "a": "yes",
        "b": "not found in the text",
        "name": "Terms restrict automated access"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "yes",
        "b": "not found in the text",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "yes",
        "b": "not found in the text",
        "name": "Arbitration or class-action waiver"
      },
      {
        "a": "234 stars",
        "b": "none",
        "name": "Popularity"
      }
    ],
    "faq": [
      {
        "answer": "Bitpont API and MCP scores 62.9 (B) on agent readiness against Bitget's 56.4 (C), and leads in 4 of 7 scored categories. Bitget leads on agent ergonomics, maintenance \u0026 community and transparency \u0026 trust.",
        "question": "Which is better for AI agents, Bitget or Bitpont API and MCP?"
      },
      {
        "answer": "Bitget needs an API key. Bitpont API and MCP takes an API key or an OAuth sign-in.",
        "question": "Do Bitget and Bitpont API and MCP need an API key?"
      },
      {
        "answer": "Bitget runs on your own machine, with no hosted endpoint listed. Bitpont API and MCP has a hosted endpoint at https://www.bitpont.com/api/v1/mcp.",
        "question": "Can an agent call Bitget and Bitpont API and MCP without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Agent ergonomics, 83 against 74",
          "Maintenance \u0026 community, 78 against 14",
          "Transparency \u0026 trust, 65 against 58"
        ],
        "also": [
          "Runs on your own machine"
        ],
        "goodFor": "An agent trading spot, futures and earn products in a person's Bitget account outside the prohibited list, with the smallest default MCP surface of the exchanges graded and a paper-trading switch.",
        "slug": "bitget",
        "watchFor": "Hot and warm wallets lost about 388 million dollars on 24 September 2026 to forged withdrawal commands, and withdrawals were paused until 2 October"
      },
      {
        "aheadOn": [
          "Reliability, 45 against 40",
          "Schema \u0026 documentation, 82 against 74",
          "Payments \u0026 pricing, 90 against 60"
        ],
        "also": [
          "A hosted endpoint, with nothing to install",
          "Free to start without a card",
          "No incidents deducted, where Bitget loses 8 points for them"
        ],
        "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": {
      "bitget": [
        {
          "causes": [
            "method"
          ],
          "date": "2026-11-13",
          "delta": 2.5,
          "from": 53.9,
          "fromGrade": "D",
          "to": 56.4,
          "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-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/bitget-vs-bithumb.json",
        "title": "Bitget vs Bithumb Open API",
        "url": "https://www.anchorterminal.com/compare/bitget-vs-bithumb"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitget-vs-bitstamp.json",
        "title": "Bitget vs Bitstamp API",
        "url": "https://www.anchorterminal.com/compare/bitget-vs-bitstamp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitget-vs-bybit.json",
        "title": "Bitget vs Bybit",
        "url": "https://www.anchorterminal.com/compare/bitget-vs-bybit"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitget-vs-coinbase-advanced-trade.json",
        "title": "Bitget vs Coinbase Advanced Trade API",
        "url": "https://www.anchorterminal.com/compare/bitget-vs-coinbase-advanced-trade"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitget-vs-coinbase-mcp.json",
        "title": "Bitget vs Coinbase MCP server (Coinbase for Agents)",
        "url": "https://www.anchorterminal.com/compare/bitget-vs-coinbase-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitget-vs-crypto-com-exchange.json",
        "title": "Bitget vs Crypto.com Exchange API",
        "url": "https://www.anchorterminal.com/compare/bitget-vs-crypto-com-exchange"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitget-vs-deribit.json",
        "title": "Bitget vs Deribit",
        "url": "https://www.anchorterminal.com/compare/bitget-vs-deribit"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitget-vs-dydx.json",
        "title": "Bitget vs dYdX",
        "url": "https://www.anchorterminal.com/compare/bitget-vs-dydx"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitget-vs-gate-io.json",
        "title": "Bitget vs Gate",
        "url": "https://www.anchorterminal.com/compare/bitget-vs-gate-io"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitget-vs-gemini-exchange.json",
        "title": "Bitget vs Gemini Exchange API",
        "url": "https://www.anchorterminal.com/compare/bitget-vs-gemini-exchange"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitget-vs-htx.json",
        "title": "Bitget vs HTX trading API",
        "url": "https://www.anchorterminal.com/compare/bitget-vs-htx"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitget-vs-hyperliquid.json",
        "title": "Bitget vs Hyperliquid",
        "url": "https://www.anchorterminal.com/compare/bitget-vs-hyperliquid"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitget-vs-kraken.json",
        "title": "Bitget vs Kraken API",
        "url": "https://www.anchorterminal.com/compare/bitget-vs-kraken"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitget-vs-kucoin.json",
        "title": "Bitget vs KuCoin",
        "url": "https://www.anchorterminal.com/compare/bitget-vs-kucoin"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitget-vs-mexc.json",
        "title": "Bitget vs MEXC API",
        "url": "https://www.anchorterminal.com/compare/bitget-vs-mexc"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitget-vs-okx.json",
        "title": "Bitget vs OKX API",
        "url": "https://www.anchorterminal.com/compare/bitget-vs-okx"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitget-vs-uniswap.json",
        "title": "Bitget vs Uniswap Trading API",
        "url": "https://www.anchorterminal.com/compare/bitget-vs-uniswap"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bitget-vs-upbit.json",
        "title": "Bitget vs Upbit Open API",
        "url": "https://www.anchorterminal.com/compare/bitget-vs-upbit"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bithumb-vs-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-bitget.json",
        "title": "Binance API vs Bitget",
        "url": "https://www.anchorterminal.com/compare/binance-vs-bitget"
      },
      {
        "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": [
      {
        "bitget": 40,
        "bitpont": 45,
        "by": 5,
        "edge": "bitpont",
        "key": "reliability",
        "name": "Reliability",
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "bitget": 74,
        "bitpont": 82,
        "by": 8,
        "edge": "bitpont",
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "weight": 13
      },
      {
        "bitget": 83,
        "bitpont": 74,
        "by": 9,
        "edge": "bitget",
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "weight": 13
      },
      {
        "bitget": 62,
        "bitpont": 63,
        "by": 1,
        "edge": "bitpont",
        "key": "security",
        "name": "Security \u0026 auth",
        "weight": 14
      },
      {
        "bitget": 60,
        "bitpont": 90,
        "by": 30,
        "edge": "bitpont",
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "bitget": 78,
        "bitpont": 14,
        "by": 64,
        "edge": "bitget",
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "weight": 7
      },
      {
        "bitget": 65,
        "bitpont": 58,
        "by": 7,
        "edge": "bitget",
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "weight": 7
      }
    ],
    "summary": "Bitpont API and MCP scores 62.9 (B) on agent readiness against Bitget's 56.4 (C), and leads in 4 of 7 scored categories. Bitget leads on agent ergonomics, maintenance \u0026 community and transparency \u0026 trust. Both do exchange market data.",
    "tasks": null,
    "tutorials": [],
    "verdicts": {
      "bitget": "Bitget's official MCP server keeps the default surface to 14 intent tools with discovery, read-only and paper-trading switches, dry runs and a confirmation gate on withdrawals, over an API with demo trading. A 388 million dollar wallet breach in September 2026 paused withdrawals for eight days, and there is no status page, SLA or readable fee table.",
      "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/bitget-vs-bitpont",
    "json": "https://www.anchorterminal.com/compare/bitget-vs-bitpont.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/bitget-vs-bitpont.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/compare/bitget-vs-bitpont.min.md"
  },
  "markdown": "Bitpont API and MCP scores 62.9 (B) on agent readiness against Bitget's 56.4 (C), and leads in 4 of 7 scored categories. Bitget leads on agent ergonomics, maintenance \u0026 community and transparency \u0026 trust. Both do exchange market data.\n\n- Bitget: grade C, 56.4/100, rank #945 of 1563. Markdown https://www.anchorterminal.com/tools/bitget.md · JSON https://www.anchorterminal.com/api/v1/tools/bitget.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### Bitget (C)\n\nGood for: An agent trading spot, futures and earn products in a person's Bitget account outside the prohibited list, with the smallest default MCP surface of the exchanges graded and a paper-trading switch.\n\nAhead on:\n- Agent ergonomics, 83 against 74\n- Maintenance \u0026 community, 78 against 14\n- Transparency \u0026 trust, 65 against 58\n\nAlso in its favour:\n- Runs on your own machine\n\nWatch for: Hot and warm wallets lost about 388 million dollars on 24 September 2026 to forged withdrawal commands, and withdrawals were paused until 2 October\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- Reliability, 45 against 40\n- Schema \u0026 documentation, 82 against 74\n- Payments \u0026 pricing, 90 against 60\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n- Free to start without a card\n- No incidents deducted, where Bitget loses 8 points for them\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### Maintenance \u0026 community: Bitget +64\n\n- Bitget (78): Read as a hosted service with an open-source toolkit. The UTA changelog's latest launched entry is 30 October 2026 and a preview entry 3 November; the MCP package shipped 3.3.1 on 20 September and agent-skill was pushed 30 October (30). 58 dated changelog entries since 5 August 2026 and six MCP versions since June (20). Issue trackers on the Bitget-AI repositories (11 open on agent_hub) and a support centre; replies were not checked (10 of 25). In the official MCP registry under io.github.Bitget-AI, a GitHub namespace, with official SDKs in five languages (10 of 15). CI workflow with coverage, npm provenance attestations, two runtime dependencies, no install scripts (8 of 10). 78.\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### Payments \u0026 pricing: Bitpont API and MCP +30\n\n- Bitget (60): No machine payment protocol (0). Base spot and futures rates are stated in a help article without login, the tier table draws by script (20). Market data needs no key, demo trading costs nothing and no card is asked for at sign-up (20). A person registers, verifies identity and mints 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- 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### Agent ergonomics: Bitget +9\n\n- Bitget (83): Read for the API with the MCP server as the agent route. 14 compact tools by default, module filters, a full surface on request and progressive discovery (25). Cursor pagination on CFD order history since 15 October 2026 and limit parameters on lists (15 of 20). Uniform ok or error result shape from the SDK with typed error classes and compact JSON in the text channel (13 of 20). clientOid on orders, `dryRun: true` on every write, `confirm: true` gating cancelAll and withdraw, annotations derived from risk level including readOnlyHint, destructiveHint and idempotentHint (18 of 20). Few required fields, official SDKs in five languages plus the TypeScript agent SDK and a CLI (12 of 15). 83.\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### Schema \u0026 documentation: Bitpont API and MCP +8\n\n- Bitget (74): The agent SDK ships openapi.yaml with 109 typed UTA v3 operations from which the tools are generated, a machine-readable contract from the vendor's own organisation though not on the docs site (20 of 25). llms.txt in the SDK and MCP repositories; the docs site has none (6 of 10). Intent tools with a discover tool that explains each verb, action and its risk level, and the server's initialize instructions state surface, modules and read-only posture (15 of 20). Typed inputs with enums and required fields from the OpenAPI source (12 of 15). Examples in the quick start and READMEs, a REST error code page in the legacy docs that we did not read in full (9 of 15). Changelog by day with preview notices and effective dates (12 of 15). 74.\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### Transparency \u0026 trust: Bitget +7\n\n- Bitget (65): The editorial half. A closed hosted service with clear terms naming BTG Technology Holdings Limited; the toolkit is MIT (15 of 30). The privacy notice names the controller and EEA representative, gives 7-year and up to 10-year retention for compliance and litigation, and names recipients by category only (18 of 30). Deprecations and parameter changes carry effective dates (delta mode deprecated 27 August, symbol and category required from 30 September, snapshot changes with demo and live dates) but no written policy (15 of 20). Recipients by category, transfers under Seychelles law with no locations or provider names (5 of 20). 53.\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### Reliability: Bitpont API and MCP +5\n\n- Bitget (40): Graded with the hosted lines on the UTA v3 API at api.bitget.com. No status page found (status.bitget.com does not resolve, the docs link none), so 0 for the page and 5 for no readable history; the September 2026 breach is in the deduction, not here. Rate limits are published as 6,000 per IP per minute and per-endpoint UID limits by VIP level (15). An x-mbx-used-remain-limit header is documented and the agent SDK backs off on 429, orders take a clientOid of up to 64 characters, but the breach error code and a Retry-After rule were not read (10 of 15). No SLA (0). UTA v3 is the production API (10). 40.\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## Score by category\n\n| Category | Weight | Bitget | Bitpont API and MCP | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 40 | 45 | Bitpont API and MCP +5 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% | 74 | 82 | Bitpont API and MCP +8 |\n| Agent ergonomics | 13% | 83 | 74 | Bitget +9 |\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% | 78 | 14 | Bitget +64 |\n| Transparency \u0026 trust | 7% | 65 | 58 | Bitget +7 |\n| Negative events | ≤15 | -8 | 0 | |\n| **Total** | | **56.4 · C** | **62.9 · B** | |\n\n## Facts side by side\n\n| Fact | Bitget | Bitpont API and MCP |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | BTG Technology Holdings Limited | Bitpont (LiMiT) |\n| Hosted endpoint | no (local only) | `https://www.bitpont.com/api/v1/mcp` |\n| Transports | stdio | Streamable HTTP |\n| Auth | API key | OAuth or key |\n| Pricing | Pay per use | Pay per use |\n| x402 | no | no |\n| Licence | none | 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 | 14 | 1148 |\n| Read-only variant documented | yes | no |\n| llms.txt | no | yes |\n| MCP registry | `io.github.Bitget-AI/bitget-agent-mcp` | not listed |\n| Last release | 2026-10-30 | none |\n| Terms last updated | 2026-10-20 | no date given |\n| Privacy policy last updated | 2025-12-05 | 2026-11-11 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | yes | not found in the text |\n| Terms restrict benchmarking | not found in the text | not found in the text |\n| Terms or service can change without notice | yes | not found in the text |\n| Arbitration or class-action waiver | yes | not found in the text |\n| Popularity | 234 stars | none |\n\n## How the scores have moved\n\n### Bitget\n\n- +2.5 on 13 November 2026 (D to C): checklist\n\n### Bitpont API and MCP\n\nNo score change since it was listed.\n\n## Verdicts\n\n**Bitget.** Bitget's official MCP server keeps the default surface to 14 intent tools with discovery, read-only and paper-trading switches, dry runs and a confirmation gate on withdrawals, over an API with demo trading. A 388 million dollar wallet breach in September 2026 paused withdrawals for eight days, and there is no status page, SLA or readable fee table.\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### Bitget\n\n1. Run `npx -y @bitget-ai/bitget-agent-mcp --read-only` for research and `--paper-trading` with a demo key before any live order; the two flags cannot be combined\n2. Call discover({}) first, then the intent verbs; add `dryRun: true` to any write to preview it, and pass `confirm: true` only after the person has agreed to a withdraw or cancelAll\n3. Send a unique clientOid of at most 64 characters on every order and reuse it on retry; orderId wins when both are sent\n4. Stay under 10 requests a second per endpoint on a new account and 6,000 a minute per IP; the SDK retries on 429, so do not add a second retry loop\n5. Bind the key to an IP and keep write permission off a research key; the docs read show no separate withdrawal scope\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, Bitget or Bitpont API and MCP?\n\nBitpont API and MCP scores 62.9 (B) on agent readiness against Bitget's 56.4 (C), and leads in 4 of 7 scored categories. Bitget leads on agent ergonomics, maintenance \u0026 community and transparency \u0026 trust.\n\n### Do Bitget and Bitpont API and MCP need an API key?\n\nBitget needs an API key. Bitpont API and MCP takes an API key or an OAuth sign-in.\n\n### Can an agent call Bitget and Bitpont API and MCP without installing anything?\n\nBitget runs on your own machine, with no hosted endpoint listed. 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/bitget-vs-bitpont.json, and with the fewest tokens: https://www.anchorterminal.com/compare/bitget-vs-bitpont.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"bitget\", \"b\": \"bitpont\"}`. From a terminal: `anchor compare bitget bitpont`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/bitget.json and https://www.anchorterminal.com/api/v1/tools/bitpont.json\n\n## Other comparisons with Bitget or Bitpont API and MCP\n\n- [Bitfinex API vs Bitget](https://www.anchorterminal.com/compare/bitfinex-vs-bitget.md)\n- [Bitfinex API vs Bitpont API and MCP](https://www.anchorterminal.com/compare/bitfinex-vs-bitpont.md)\n- [Bitget vs Bithumb Open API](https://www.anchorterminal.com/compare/bitget-vs-bithumb.md)\n- [Bitget vs Bitstamp API](https://www.anchorterminal.com/compare/bitget-vs-bitstamp.md)\n- [Bitget vs Bybit](https://www.anchorterminal.com/compare/bitget-vs-bybit.md)\n- [Bitget vs Coinbase Advanced Trade API](https://www.anchorterminal.com/compare/bitget-vs-coinbase-advanced-trade.md)\n- [Bitget vs Coinbase MCP server (Coinbase for Agents)](https://www.anchorterminal.com/compare/bitget-vs-coinbase-mcp.md)\n- [Bitget vs Crypto.com Exchange API](https://www.anchorterminal.com/compare/bitget-vs-crypto-com-exchange.md)\n- [Bitget vs Deribit](https://www.anchorterminal.com/compare/bitget-vs-deribit.md)\n- [Bitget vs dYdX](https://www.anchorterminal.com/compare/bitget-vs-dydx.md)\n- [Bitget vs Gate](https://www.anchorterminal.com/compare/bitget-vs-gate-io.md)\n- [Bitget vs Gemini Exchange API](https://www.anchorterminal.com/compare/bitget-vs-gemini-exchange.md)\n- [Bitget vs HTX trading API](https://www.anchorterminal.com/compare/bitget-vs-htx.md)\n- [Bitget vs Hyperliquid](https://www.anchorterminal.com/compare/bitget-vs-hyperliquid.md)\n- [Bitget vs Kraken API](https://www.anchorterminal.com/compare/bitget-vs-kraken.md)\n- [Bitget vs KuCoin](https://www.anchorterminal.com/compare/bitget-vs-kucoin.md)\n- [Bitget vs MEXC API](https://www.anchorterminal.com/compare/bitget-vs-mexc.md)\n- [Bitget vs OKX API](https://www.anchorterminal.com/compare/bitget-vs-okx.md)\n- [Bitget vs Uniswap Trading API](https://www.anchorterminal.com/compare/bitget-vs-uniswap.md)\n- [Bitget vs Upbit Open API](https://www.anchorterminal.com/compare/bitget-vs-upbit.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 Bitget](https://www.anchorterminal.com/compare/binance-vs-bitget.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": "Bitget vs Bitpont API and MCP",
        "url": ""
      }
    ],
    "description": "Bitpont scores 62.9 (B) to Bitget's 56.4 (C) for exchange market data. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "Bitget C 56.4",
      "Bitpont API and MCP B 62.9",
      "scores"
    ],
    "h1": "Bitget vs Bitpont API and MCP",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/compare/bitget-vs-bitpont",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Bitget vs Bitpont for AI agents in 2026: scores and prices",
    "toc": null,
    "updated": "2026-11-20",
    "url": "https://www.anchorterminal.com/compare/bitget-vs-bitpont"
  },
  "tokens": {
    "markdown": 5050,
    "slim": 1130
  },
  "version": 1
}
