{
  "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-20T22:06:01.197726895Z",
          "lastOk": true,
          "lastStatus": 405,
          "lastMs": 156,
          "authRequired": false,
          "uptime24h": 98.44,
          "uptime30d": 98.44,
          "p50ms24h": 129,
          "p95ms24h": 422,
          "samples24h": 64,
          "samples30d": 64,
          "days": [
            {
              "date": "2026-11-20",
              "probes": 64,
              "ok": 63
            }
          ],
          "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-20T22:06:01.197726895Z"
      },
      "streak": {
        "days": 0,
        "from": "2026-11-20",
        "sinceWatching": true,
        "best": 0
      }
    },
    "answer": "Bitpont API and MCP scores 62.9 (B) on agent readiness against HTX trading API's 44.3 (E), and leads in 6 of 7 scored categories. HTX trading API leads on maintenance \u0026 community.",
    "b": {
      "slug": "htx",
      "name": "HTX trading API",
      "vendor": "HTX",
      "vendorUrl": "https://www.htx.com",
      "company": "htx.com",
      "kind": "http-api",
      "category": "crypto-exchanges",
      "summary": "HTX, the exchange formerly Huobi, runs REST and WebSocket APIs for spot and derivatives trading, balances, transfers and withdrawals, authenticated with HMAC-signed API keys that carry read, trade and withdraw permissions.",
      "url": "https://www.anchorterminal.com/tools/htx",
      "markdownUrl": "https://www.anchorterminal.com/tools/htx.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/htx.min.md",
      "cardUrl": "https://www.anchorterminal.com/tools/htx.card.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/htx.json",
      "dns": "htx.grade.anchorterminal.com",
      "repo": "https://github.com/HuobiRDCenter",
      "transports": [],
      "packages": [],
      "auth": "api-key",
      "authNotes": "API keys made in the account's API Management page after a browser sign-up and identity check. Requests are signed with HMAC SHA256 (SignatureVersion 2) over the query string, with AccessKeyId, Timestamp and the Signature sent as query parameters; the secret never travels. A main account key carries Read, Trade and Withdraw permissions, a sub-user key Read and Trade only. A key can be bound to up to 20 IP addresses, and the docs say a key without IP binding expires after 90 days (https://huobiapi.github.io/docs/spot/v1/en/, checked 2026-11-03).",
      "pricing": "usage",
      "pricingNotes": "Trading fees per order. The fee schedule at htx.com/fee is drawn by script and answered our reader with no text, so no rate is recorded; third-party guides give 0.2 per cent maker and taker at the base tier, which is a lead and not a source. Public market data needs no key and no account (https://www.htx.com/fee/, checked 2026-11-03).",
      "priceSummary": "Pay per use",
      "where": "local",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the API docs or on the pages that loaded (checked 2026-11-03). Trading fees are taken from each fill.",
        "endpoints": []
      },
      "toolCount": 0,
      "popularity": {
        "githubStars": 684,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-11-03"
      },
      "docsUrl": "https://huobiapi.github.io/docs/spot/v1/en/",
      "capabilities": [
        "exchange.market-data",
        "exchange.spot-trading",
        "exchange.derivatives",
        "exchange.balances",
        "exchange.transfers",
        "market.crypto"
      ],
      "tags": [
        "hosted",
        "api-key",
        "closed-source",
        "usage-priced",
        "python",
        "java",
        "go",
        "no-status-page"
      ],
      "lastRelease": "2026-10-21",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 44.3,
        "grade": "E",
        "agentReady": false,
        "rank": 1312,
        "ranked": true,
        "rankOf": 1563,
        "categoryRank": 22,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 69,
          "maintenance": 57,
          "payments": 23,
          "reliability": 38,
          "schema": 40,
          "security": 51,
          "transparency": 25
        },
        "assessment": {
          "confidence": "low",
          "date": "2026-11-03"
        },
        "negative": 0,
        "verdict": "HTX's API has per-endpoint rate limits, read, trade and withdraw key permissions with IP binding, and SDKs in five languages. No official MCP server exists, the testnet is closed, the public reference is still Huobi's with a 2022 changelog, and the fee schedule, terms and restricted countries are on script-drawn pages we couldn't read.",
        "bestFor": "Spot and USDT-margined derivatives for agents that can hold an HTX key, with no MCP server and no testnet.",
        "strengths": [
          "Key permissions split into Read, Trade and Withdraw, sub-user keys without Withdraw, and up to 20 bound IP addresses per key",
          "Rate limits published per endpoint with numbers, and remaining-quota headers on every response",
          "A client-order-id unique within 8 hours on orders and idempotent on withdrawals, so a retry doesn't double an order",
          "Official SDKs in Python, Java, C++, C# and Go, the contract ones pushed on 21 October 2026"
        ],
        "weaknesses": [
          "No official MCP server; the only one in the MCP registry is a third party's read-only ticker server",
          "The testnet is shut down, so order logic can only be tried with real funds",
          "The public API reference is still branded Huobi with a last changelog entry of June 2022, and HTX's newer docs are drawn by script",
          "No status page, no SLA and no documented 429 or Retry-After behaviour",
          "The fee schedule, user agreement, privacy policy and restricted-country list couldn't be read, so none is recorded first-hand"
        ],
        "agentNotes": [
          "Ask the operator for a key with Read and Trade only and bound to your IP addresses; a key without IP binding expires after 90 days",
          "Send a fresh client-order-id of up to 64 characters with every order and reuse it only on retry; a repeat within 8 hours answers invalid.client.order.id",
          "Watch X-HB-RateLimit-Requests-Remain and pace at under 100 order calls per 2 seconds per UID; limits are shared by every key on the account",
          "There is no testnet; try order logic with the smallest size the market allows",
          "Confirm the person's country is served before trading; the restricted list in the user agreement couldn't be read here"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "low",
            "grade": "E",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 44.3
          }
        ],
        "editorialScores": {
          "ergonomics": 69,
          "maintenance": 57,
          "payments": 23,
          "reliability": 38,
          "schema": 40,
          "security": 51,
          "transparency": 15
        },
        "provenanceScore": 34,
        "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": {
        "http": "curl https://api.huobi.pro/market/tickers"
      },
      "letme": {
        "capability": "https://letme.dev/exchange.market-data",
        "tool": "https://letme.dev/htx"
      },
      "area": "payments",
      "provenance": {
        "legalEntity": "",
        "domain": "htx.com",
        "domainRegistered": "1995-12-13",
        "endpointOnVendorDomain": false,
        "terms": "https://www.htx.com/en-in/support/360000298561/",
        "privacy": "",
        "statusPage": "",
        "changelog": "https://huobiapi.github.io/docs/spot/v1/en/",
        "securityTxt": "none",
        "checked": "2026-11-03",
        "notes": [
          "The legal entity is unread. The HTX Platform User Agreement and every other page on www.htx.com answered our reader with no text on 3 November 2026 (the pages are drawn by script), so the terms, privacy policy, fee schedule and about page were not read. Terms URL recorded from a search result's title.",
          "RDAP gives htx.com a registration date of 13 December 1995, long before the exchange took the name in 2023; the domain was acquired, not registered, by the exchange.",
          "The API endpoint api.huobi.pro is on the old huobi.pro domain, not htx.com.",
          "www.htx.com/robots.txt allows / and disallows account paths (finance/account, user-center/security and the like). www.huobi.com/robots.txt disallows everything and was not read further. huobiapi.github.io has no robots.txt.",
          "https://www.htx.com/.well-known/security.txt answered no text; recorded as none. status.htx.com does not resolve."
        ],
        "score": 34
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/htx.json",
      "live": {
        "slug": "htx",
        "securityTxt": {
          "url": "https://htx.com/.well-known/security.txt",
          "state": "none",
          "checkedAt": "2026-11-20T16:36:42.52407375Z"
        },
        "domain": {
          "domain": "htx.com",
          "registered": "1995-12-13",
          "source": "https://rdap.verisign.com/com/v1/domain/htx.com",
          "checkedAt": "2026-11-15T15:22:18.703441703Z"
        },
        "pages": [
          {
            "url": "https://huobiapi.github.io/docs/spot/v1/en/",
            "kind": "changelog",
            "status": 304,
            "checkedAt": "2026-11-19T22:26:01.190716465Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "46357b45983f"
          },
          {
            "url": "https://www.htx.com/en-in/support/360000298561/",
            "kind": "terms",
            "status": 200,
            "checkedAt": "2026-11-19T22:45:21.015626729Z",
            "changedAt": "2026-11-13T18:40:26.380798368Z",
            "fingerprint": "c3a3ae8e8cc8"
          }
        ],
        "updatedAt": "2026-11-20T16:36:42.52407375Z"
      }
    },
    "edges": [
      {
        "by": 67,
        "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 at htx.com/fee is drawn by script and answered no text, so no price is recorded first-hand (0 of 20, unchecked). Public market data needs no key, card or account; trading needs a verified and funded account. Judgement call (15 of 20). A person must sign up in a browser and pass identity checks (0). 0 + 0 + 15 + 0 = 15. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 15 is 23."
        },
        "scores": {
          "a": 90,
          "b": 23
        }
      },
      {
        "by": 43,
        "category": "maintenance",
        "leads": "htx",
        "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 closed service. The readable changelog ends on 24 June 2022, but the official contract SDKs were pushed on 21 October 2026 and the spot SDKs in April and July 2026, so the API surface is still being maintained; judgement call (20 of 30). SDK pushes on 30 July, 23 August and 21 October 2026 are commits, not releases (10 of 20). A Telegram group for API support and a support centre, neither tested; GitHub issues not read (8 of 15). Official SDKs in five languages (15). No CI seen, dependencies not checked (4 of 10). 20 + 10 + 8 + 15 + 4 = 57."
        },
        "scores": {
          "a": 14,
          "b": 57
        }
      },
      {
        "by": 42,
        "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 found in the docs or the GitHub accounts (0). No llms.txt on htx.com, and the readable reference is a static page (0). Each endpoint states its purpose and parameters, without when-to-use guidance (12 of 20). Parameter tables carry types, required flags and enums for order types and states (10 of 15). Request and response examples throughout and error-code tables with messages (11 of 15). Versions v1 and v2 are mixed in one reference whose last changelog entry is 24 June 2022, while HTX's newer docs on htx.com couldn't be read (7 of 15). 0 + 0 + 12 + 10 + 11 + 7 = 40."
        },
        "scores": {
          "a": 82,
          "b": 40
        }
      },
      {
        "by": 33,
        "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 service whose user agreement exists but couldn't be read (script-drawn pages), so the licence clarity is unknown rather than unclear (10 of 30). The privacy policy was not read (0 of 30, unchecked). The testnet shutdown and the 2022 changelog entries are dated, with no deprecation policy (5 of 20). No subprocessor or data-location statement read (0 of 20). 10 + 0 + 5 + 0 = 15."
        },
        "scores": {
          "a": 58,
          "b": 25
        }
      },
      {
        "by": 12,
        "category": "security",
        "leads": "bitpont",
        "name": "Security \u0026 auth",
        "reasons": {
          "a": "Keyless use with a client-created workspace secret in a header; optional partner bearer keys with scopes, expiry and revocation, rotated by asking the operator; no key in a URL (22 of 30). Four scopes from read to submit, customer approval of exact trading tickets, and the owner's wallet signs every value transfer (18 of 20). The API returns third-party token and protocol data; the pages say symbols are labels and exact addresses identify assets, but nothing on prompt injection (8 of 15). Per-workspace execution receipts, a monthly settlement report and a usage endpoint (10 of 15). A private reporting email on the security page with no bounty, response time or safe harbour, no security.txt (404) and no certification; the page says Bitpont itself has no independent audit (5 of 20). Total 63.",
          "b": "HMAC-signed keys with Read, Trade and Withdraw permissions, sub-user keys without Withdraw, up to 20 bound IPs, revocation in the account and a 90-day expiry without IP binding. The AccessKeyId and the HMAC signature travel as query parameters; the secret does not, so no deduction for a secret in the URL (24 of 30). Read-only keys and withdraw-free keys exist; no server-side confirmation for orders or withdrawals (14 of 20). The API returns the exchange's own data, no untrusted content (10). No per-call log or key-use history found for the operator (3 of 15). No security.txt, disclosure policy or certification found on the pages that loaded (0 of 20). 24 + 14 + 10 + 3 + 0 = 51."
        },
        "scores": {
          "a": 63,
          "b": 51
        }
      },
      {
        "by": 7,
        "category": "reliability",
        "leads": "bitpont",
        "name": "Reliability",
        "reasons": {
          "a": "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.",
          "b": "Read with the hosted lines. No status page found; status.htx.com does not resolve and nothing on htx.com was readable (0). No readable incident history (5). Rate limits documented per endpoint with numbers, 100 order calls per 2 seconds per UID and so on, with remaining-quota headers (15). No 429 or Retry-After behaviour is documented and the only limit error named is 1006 for conditional orders; a client-order-id unique within 8 hours and an idempotent withdrawal id give safe retries on writes (8 of 15). No SLA found (0). The spot and swap APIs are generally available (10). 0 + 5 + 15 + 8 + 0 + 10 = 38."
        },
        "scores": {
          "a": 45,
          "b": 38
        }
      }
    ],
    "facts": [
      {
        "a": "HTTP API",
        "b": "HTTP API",
        "name": "Kind"
      },
      {
        "a": "Bitpont (LiMiT)",
        "b": "HTX",
        "name": "Vendor"
      },
      {
        "a": "https://www.bitpont.com/api/v1/mcp",
        "b": "no (local only)",
        "name": "Hosted endpoint"
      },
      {
        "a": "Streamable HTTP",
        "b": "",
        "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": "0",
        "name": "Tools exposed"
      },
      {
        "a": "no",
        "b": "no",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "no",
        "name": "llms.txt"
      },
      {
        "a": "none",
        "b": "2026-10-21",
        "name": "Last release"
      },
      {
        "a": "no date given",
        "b": "no date given",
        "name": "Terms last updated"
      },
      {
        "a": "2026-11-11",
        "b": "no document linked",
        "name": "Privacy policy last updated"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Customer content may train models"
      },
      {
        "a": "not found in the text",
        "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": "not found in the text",
        "b": "yes",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "not found in the text",
        "b": "yes",
        "name": "Arbitration or class-action waiver"
      },
      {
        "a": "none",
        "b": "684 stars",
        "name": "Popularity"
      }
    ],
    "faq": [
      {
        "answer": "Bitpont API and MCP scores 62.9 (B) on agent readiness against HTX trading API's 44.3 (E), and leads in 6 of 7 scored categories. HTX trading API leads on maintenance \u0026 community.",
        "question": "Which is better for AI agents, Bitpont API and MCP or HTX trading API?"
      },
      {
        "answer": "Bitpont API and MCP takes an API key or an OAuth sign-in. HTX trading API needs an API key.",
        "question": "Do Bitpont API and MCP and HTX trading API need an API key?"
      },
      {
        "answer": "Bitpont API and MCP has a hosted endpoint at https://www.bitpont.com/api/v1/mcp. No hosted endpoint is listed for HTX trading API.",
        "question": "Can an agent call Bitpont API and MCP and HTX trading API without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Reliability, 45 against 38",
          "Schema \u0026 documentation, 82 against 40",
          "Agent ergonomics, 74 against 69",
          "Security \u0026 auth, 63 against 51",
          "Payments \u0026 pricing, 90 against 23",
          "Transparency \u0026 trust, 58 against 25"
        ],
        "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, 57 against 14"
        ],
        "also": null,
        "goodFor": "Spot and USDT-margined derivatives for agents that can hold an HTX key, with no MCP server and no testnet.",
        "slug": "htx",
        "watchFor": "No official MCP server; the only one in the MCP registry is a third party's read-only ticker server"
      }
    ],
    "history": {
      "bitpont": null,
      "htx": [
        {
          "causes": [
            "method"
          ],
          "date": "2026-11-13",
          "delta": 1,
          "from": 43.3,
          "fromGrade": "E",
          "to": 44.3,
          "toGrade": "E"
        }
      ]
    },
    "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-htx.json",
        "title": "Bitfinex API vs HTX trading API",
        "url": "https://www.anchorterminal.com/compare/bitfinex-vs-htx"
      },
      {
        "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-htx.json",
        "title": "Bitget vs HTX trading API",
        "url": "https://www.anchorterminal.com/compare/bitget-vs-htx"
      },
      {
        "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-htx.json",
        "title": "Bithumb Open API vs HTX trading API",
        "url": "https://www.anchorterminal.com/compare/bithumb-vs-htx"
      },
      {
        "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-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-htx.json",
        "title": "Bitstamp API vs HTX trading API",
        "url": "https://www.anchorterminal.com/compare/bitstamp-vs-htx"
      },
      {
        "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/crypto-com-exchange-vs-htx.json",
        "title": "Crypto.com Exchange API vs HTX trading API",
        "url": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-htx"
      },
      {
        "json": "https://www.anchorterminal.com/compare/gate-io-vs-htx.json",
        "title": "Gate vs HTX trading API",
        "url": "https://www.anchorterminal.com/compare/gate-io-vs-htx"
      },
      {
        "json": "https://www.anchorterminal.com/compare/gemini-exchange-vs-htx.json",
        "title": "Gemini Exchange API vs HTX trading API",
        "url": "https://www.anchorterminal.com/compare/gemini-exchange-vs-htx"
      },
      {
        "json": "https://www.anchorterminal.com/compare/htx-vs-hyperliquid.json",
        "title": "HTX trading API vs Hyperliquid",
        "url": "https://www.anchorterminal.com/compare/htx-vs-hyperliquid"
      },
      {
        "json": "https://www.anchorterminal.com/compare/htx-vs-kraken.json",
        "title": "HTX trading API vs Kraken API",
        "url": "https://www.anchorterminal.com/compare/htx-vs-kraken"
      },
      {
        "json": "https://www.anchorterminal.com/compare/htx-vs-kucoin.json",
        "title": "HTX trading API vs KuCoin",
        "url": "https://www.anchorterminal.com/compare/htx-vs-kucoin"
      },
      {
        "json": "https://www.anchorterminal.com/compare/htx-vs-mexc.json",
        "title": "HTX trading API vs MEXC API",
        "url": "https://www.anchorterminal.com/compare/htx-vs-mexc"
      },
      {
        "json": "https://www.anchorterminal.com/compare/htx-vs-okx.json",
        "title": "HTX trading API vs OKX API",
        "url": "https://www.anchorterminal.com/compare/htx-vs-okx"
      },
      {
        "json": "https://www.anchorterminal.com/compare/htx-vs-uniswap.json",
        "title": "HTX trading API vs Uniswap Trading API",
        "url": "https://www.anchorterminal.com/compare/htx-vs-uniswap"
      },
      {
        "json": "https://www.anchorterminal.com/compare/htx-vs-upbit.json",
        "title": "HTX trading API vs Upbit Open API",
        "url": "https://www.anchorterminal.com/compare/htx-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-htx.json",
        "title": "Binance API vs HTX trading API",
        "url": "https://www.anchorterminal.com/compare/binance-vs-htx"
      },
      {
        "json": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-htx.json",
        "title": "Coinbase Advanced Trade API vs HTX trading API",
        "url": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-htx"
      },
      {
        "json": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-htx.json",
        "title": "Coinbase MCP server (Coinbase for Agents) vs HTX trading API",
        "url": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-htx"
      },
      {
        "json": "https://www.anchorterminal.com/compare/deribit-vs-htx.json",
        "title": "Deribit vs HTX trading API",
        "url": "https://www.anchorterminal.com/compare/deribit-vs-htx"
      },
      {
        "json": "https://www.anchorterminal.com/compare/dydx-vs-htx.json",
        "title": "dYdX vs HTX trading API",
        "url": "https://www.anchorterminal.com/compare/dydx-vs-htx"
      }
    ],
    "panel": null,
    "scores": [
      {
        "bitpont": 45,
        "by": 7,
        "edge": "bitpont",
        "htx": 38,
        "key": "reliability",
        "name": "Reliability",
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "bitpont": 82,
        "by": 42,
        "edge": "bitpont",
        "htx": 40,
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "weight": 13
      },
      {
        "bitpont": 74,
        "by": 5,
        "edge": "bitpont",
        "htx": 69,
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "weight": 13
      },
      {
        "bitpont": 63,
        "by": 12,
        "edge": "bitpont",
        "htx": 51,
        "key": "security",
        "name": "Security \u0026 auth",
        "weight": 14
      },
      {
        "bitpont": 90,
        "by": 67,
        "edge": "bitpont",
        "htx": 23,
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "bitpont": 14,
        "by": 43,
        "edge": "htx",
        "htx": 57,
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "weight": 7
      },
      {
        "bitpont": 58,
        "by": 33,
        "edge": "bitpont",
        "htx": 25,
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "weight": 7
      }
    ],
    "summary": "Bitpont API and MCP scores 62.9 (B) on agent readiness against HTX trading API's 44.3 (E), and leads in 6 of 7 scored categories. HTX trading API 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.",
      "htx": "HTX's API has per-endpoint rate limits, read, trade and withdraw key permissions with IP binding, and SDKs in five languages. No official MCP server exists, the testnet is closed, the public reference is still Huobi's with a 2022 changelog, and the fee schedule, terms and restricted countries are on script-drawn pages we couldn't read."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/bitpont-vs-htx",
    "json": "https://www.anchorterminal.com/compare/bitpont-vs-htx.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/bitpont-vs-htx.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/compare/bitpont-vs-htx.min.md"
  },
  "markdown": "Bitpont API and MCP scores 62.9 (B) on agent readiness against HTX trading API's 44.3 (E), and leads in 6 of 7 scored categories. HTX trading API 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- HTX trading API: grade E, 44.3/100, rank #1312 of 1563. Markdown https://www.anchorterminal.com/tools/htx.md · JSON https://www.anchorterminal.com/api/v1/tools/htx.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- Reliability, 45 against 38\n- Schema \u0026 documentation, 82 against 40\n- Agent ergonomics, 74 against 69\n- Security \u0026 auth, 63 against 51\n- Payments \u0026 pricing, 90 against 23\n- Transparency \u0026 trust, 58 against 25\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### HTX trading API (E)\n\nGood for: Spot and USDT-margined derivatives for agents that can hold an HTX key, with no MCP server and no testnet.\n\nAhead on:\n- Maintenance \u0026 community, 57 against 14\n\nWatch for: No official MCP server; the only one in the MCP registry is a third party's read-only ticker server\n\n\n## Why the edge\n\n### Payments \u0026 pricing: Bitpont API and MCP +67\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- HTX trading API (23): No machine payment protocol (0). The fee schedule at htx.com/fee is drawn by script and answered no text, so no price is recorded first-hand (0 of 20, unchecked). Public market data needs no key, card or account; trading needs a verified and funded account. Judgement call (15 of 20). A person must sign up in a browser and pass identity checks (0). 0 + 0 + 15 + 0 = 15. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 15 is 23.\n\n### Maintenance \u0026 community: HTX trading API +43\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- HTX trading API (57): Read as a closed service. The readable changelog ends on 24 June 2022, but the official contract SDKs were pushed on 21 October 2026 and the spot SDKs in April and July 2026, so the API surface is still being maintained; judgement call (20 of 30). SDK pushes on 30 July, 23 August and 21 October 2026 are commits, not releases (10 of 20). A Telegram group for API support and a support centre, neither tested; GitHub issues not read (8 of 15). Official SDKs in five languages (15). No CI seen, dependencies not checked (4 of 10). 20 + 10 + 8 + 15 + 4 = 57.\n\n### Schema \u0026 documentation: Bitpont API and MCP +42\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- HTX trading API (40): No OpenAPI or other machine-readable contract found in the docs or the GitHub accounts (0). No llms.txt on htx.com, and the readable reference is a static page (0). Each endpoint states its purpose and parameters, without when-to-use guidance (12 of 20). Parameter tables carry types, required flags and enums for order types and states (10 of 15). Request and response examples throughout and error-code tables with messages (11 of 15). Versions v1 and v2 are mixed in one reference whose last changelog entry is 24 June 2022, while HTX's newer docs on htx.com couldn't be read (7 of 15). 0 + 0 + 12 + 10 + 11 + 7 = 40.\n\n### Transparency \u0026 trust: Bitpont API and MCP +33\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- HTX trading API (25): The editorial half. A closed service whose user agreement exists but couldn't be read (script-drawn pages), so the licence clarity is unknown rather than unclear (10 of 30). The privacy policy was not read (0 of 30, unchecked). The testnet shutdown and the 2022 changelog entries are dated, with no deprecation policy (5 of 20). No subprocessor or data-location statement read (0 of 20). 10 + 0 + 5 + 0 = 15.\n\n### Security \u0026 auth: Bitpont API and MCP +12\n\n- Bitpont API and MCP (63): Keyless use with a client-created workspace secret in a header; optional partner bearer keys with scopes, expiry and revocation, rotated by asking the operator; no key in a URL (22 of 30). Four scopes from read to submit, customer approval of exact trading tickets, and the owner's wallet signs every value transfer (18 of 20). The API returns third-party token and protocol data; the pages say symbols are labels and exact addresses identify assets, but nothing on prompt injection (8 of 15). Per-workspace execution receipts, a monthly settlement report and a usage endpoint (10 of 15). A private reporting email on the security page with no bounty, response time or safe harbour, no security.txt (404) and no certification; the page says Bitpont itself has no independent audit (5 of 20). Total 63.\n- HTX trading API (51): HMAC-signed keys with Read, Trade and Withdraw permissions, sub-user keys without Withdraw, up to 20 bound IPs, revocation in the account and a 90-day expiry without IP binding. The AccessKeyId and the HMAC signature travel as query parameters; the secret does not, so no deduction for a secret in the URL (24 of 30). Read-only keys and withdraw-free keys exist; no server-side confirmation for orders or withdrawals (14 of 20). The API returns the exchange's own data, no untrusted content (10). No per-call log or key-use history found for the operator (3 of 15). No security.txt, disclosure policy or certification found on the pages that loaded (0 of 20). 24 + 14 + 10 + 3 + 0 = 51.\n\n### Reliability: Bitpont API and MCP +7\n\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- HTX trading API (38): Read with the hosted lines. No status page found; status.htx.com does not resolve and nothing on htx.com was readable (0). No readable incident history (5). Rate limits documented per endpoint with numbers, 100 order calls per 2 seconds per UID and so on, with remaining-quota headers (15). No 429 or Retry-After behaviour is documented and the only limit error named is 1006 for conditional orders; a client-order-id unique within 8 hours and an idempotent withdrawal id give safe retries on writes (8 of 15). No SLA found (0). The spot and swap APIs are generally available (10). 0 + 5 + 15 + 8 + 0 + 10 = 38.\n\n## Score by category\n\n| Category | Weight | Bitpont API and MCP | HTX trading API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 45 | 38 | Bitpont API and MCP +7 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% | 82 | 40 | Bitpont API and MCP +42 |\n| Agent ergonomics | 13% | 74 | 69 | Bitpont API and MCP +5 |\n| Security \u0026 auth | 14% | 63 | 51 | Bitpont API and MCP +12 |\n| Payments \u0026 pricing | 10% | 90 | 23 | Bitpont API and MCP +67 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% | 14 | 57 | HTX trading API +43 |\n| Transparency \u0026 trust | 7% | 58 | 25 | Bitpont API and MCP +33 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **62.9 · B** | **44.3 · E** | |\n\n## Facts side by side\n\n| Fact | Bitpont API and MCP | HTX trading API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Bitpont (LiMiT) | HTX |\n| Hosted endpoint | `https://www.bitpont.com/api/v1/mcp` | no (local only) |\n| Transports | Streamable HTTP |  |\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 | 0 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | no |\n| Last release | none | 2026-10-21 |\n| Terms last updated | no date given | no date given |\n| Privacy policy last updated | 2026-11-11 | no document linked |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | 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 | not found in the text | yes |\n| Arbitration or class-action waiver | not found in the text | yes |\n| Popularity | none | 684 stars |\n\n## How the scores have moved\n\n### Bitpont API and MCP\n\nNo score change since it was listed.\n\n### HTX trading API\n\n- +1.0 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**HTX trading API.** HTX's API has per-endpoint rate limits, read, trade and withdraw key permissions with IP binding, and SDKs in five languages. No official MCP server exists, the testnet is closed, the public reference is still Huobi's with a 2022 changelog, and the fee schedule, terms and restricted countries are on script-drawn pages we couldn't read.\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### HTX trading API\n\n1. Ask the operator for a key with Read and Trade only and bound to your IP addresses; a key without IP binding expires after 90 days\n2. Send a fresh client-order-id of up to 64 characters with every order and reuse it only on retry; a repeat within 8 hours answers invalid.client.order.id\n3. Watch X-HB-RateLimit-Requests-Remain and pace at under 100 order calls per 2 seconds per UID; limits are shared by every key on the account\n4. There is no testnet; try order logic with the smallest size the market allows\n5. Confirm the person's country is served before trading; the restricted list in the user agreement couldn't be read here\n\n## Questions\n\n### Which is better for AI agents, Bitpont API and MCP or HTX trading API?\n\nBitpont API and MCP scores 62.9 (B) on agent readiness against HTX trading API's 44.3 (E), and leads in 6 of 7 scored categories. HTX trading API leads on maintenance \u0026 community.\n\n### Do Bitpont API and MCP and HTX trading API need an API key?\n\nBitpont API and MCP takes an API key or an OAuth sign-in. HTX trading API needs an API key.\n\n### Can an agent call Bitpont API and MCP and HTX trading API without installing anything?\n\nBitpont API and MCP has a hosted endpoint at https://www.bitpont.com/api/v1/mcp. No hosted endpoint is listed for HTX trading API.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/bitpont-vs-htx.json, and with the fewest tokens: https://www.anchorterminal.com/compare/bitpont-vs-htx.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"bitpont\", \"b\": \"htx\"}`. From a terminal: `anchor compare bitpont htx`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/bitpont.json and https://www.anchorterminal.com/api/v1/tools/htx.json\n\n## Other comparisons with Bitpont API and MCP or HTX trading API\n\n- [Bitfinex API vs Bitpont API and MCP](https://www.anchorterminal.com/compare/bitfinex-vs-bitpont.md)\n- [Bitfinex API vs HTX trading API](https://www.anchorterminal.com/compare/bitfinex-vs-htx.md)\n- [Bitget vs Bitpont API and MCP](https://www.anchorterminal.com/compare/bitget-vs-bitpont.md)\n- [Bitget vs HTX trading API](https://www.anchorterminal.com/compare/bitget-vs-htx.md)\n- [Bithumb Open API vs Bitpont API and MCP](https://www.anchorterminal.com/compare/bithumb-vs-bitpont.md)\n- [Bithumb Open API vs HTX trading API](https://www.anchorterminal.com/compare/bithumb-vs-htx.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 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 HTX trading API](https://www.anchorterminal.com/compare/bitstamp-vs-htx.md)\n- [Bybit vs HTX trading API](https://www.anchorterminal.com/compare/bybit-vs-htx.md)\n- [Crypto.com Exchange API vs HTX trading API](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-htx.md)\n- [Gate vs HTX trading API](https://www.anchorterminal.com/compare/gate-io-vs-htx.md)\n- [Gemini Exchange API vs HTX trading API](https://www.anchorterminal.com/compare/gemini-exchange-vs-htx.md)\n- [HTX trading API vs Hyperliquid](https://www.anchorterminal.com/compare/htx-vs-hyperliquid.md)\n- [HTX trading API vs Kraken API](https://www.anchorterminal.com/compare/htx-vs-kraken.md)\n- [HTX trading API vs KuCoin](https://www.anchorterminal.com/compare/htx-vs-kucoin.md)\n- [HTX trading API vs MEXC API](https://www.anchorterminal.com/compare/htx-vs-mexc.md)\n- [HTX trading API vs OKX API](https://www.anchorterminal.com/compare/htx-vs-okx.md)\n- [HTX trading API vs Uniswap Trading API](https://www.anchorterminal.com/compare/htx-vs-uniswap.md)\n- [HTX trading API vs Upbit Open API](https://www.anchorterminal.com/compare/htx-vs-upbit.md)\n- [Binance API vs Bitpont API and MCP](https://www.anchorterminal.com/compare/binance-vs-bitpont.md)\n- [Binance API vs HTX trading API](https://www.anchorterminal.com/compare/binance-vs-htx.md)\n- [Coinbase Advanced Trade API vs HTX trading API](https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-htx.md)\n- [Coinbase MCP server (Coinbase for Agents) vs HTX trading API](https://www.anchorterminal.com/compare/coinbase-mcp-vs-htx.md)\n- [Deribit vs HTX trading API](https://www.anchorterminal.com/compare/deribit-vs-htx.md)\n- [dYdX vs HTX trading API](https://www.anchorterminal.com/compare/dydx-vs-htx.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 HTX trading API",
        "url": ""
      }
    ],
    "description": "Bitpont scores 62.9 (B) to HTX trading's 44.3 (E) for exchange market data. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "Bitpont API and MCP B 62.9",
      "HTX trading API E 44.3",
      "scores"
    ],
    "h1": "Bitpont API and MCP vs HTX trading API",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/compare/bitpont-vs-htx",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Bitpont vs HTX trading for AI agents in 2026: scores and prices",
    "toc": null,
    "updated": "2026-11-20",
    "url": "https://www.anchorterminal.com/compare/bitpont-vs-htx"
  },
  "tokens": {
    "markdown": 4900,
    "slim": 1080
  },
  "version": 1
}
