{ "data": { "a": { "slug": "htx", "name": "HTX trading API", "vendor": "HTX", "vendorUrl": "https://www.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", "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": 43.3, "grade": "E", "agentReady": false, "rank": 1156, "ranked": true, "rankOf": 1349, "categoryRank": 21, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 69, "maintenance": 57, "payments": 15, "reliability": 38, "schema": 40, "security": 51, "transparency": 25 }, "pending": [ "performance", "tasks" ], "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": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 43.3 } ], "editorialScores": { "ergonomics": 69, "maintenance": 57, "payments": 15, "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", "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-04T15:54:20.226147452Z" }, "updatedAt": "2026-11-04T15:54:20.226147452Z" } }, "answer": "Uniswap Trading API scores 63.3 (B) on agent readiness against HTX trading API's 43.3 (E), and leads in every scored category.", "b": { "slug": "uniswap", "name": "Uniswap Trading API", "vendor": "Uniswap Labs", "vendorUrl": "https://developers.uniswap.org", "kind": "http-api", "category": "crypto-exchanges", "summary": "Uniswap Labs' Trading API quotes and builds swap, bridge and liquidity transactions across Uniswap v2, v3, v4 and UniswapX on 21 chains. The caller signs with its own wallet and broadcasts; the API is free behind an API key.", "url": "https://www.anchorterminal.com/tools/uniswap", "markdownUrl": "https://www.anchorterminal.com/tools/uniswap.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/uniswap.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/uniswap.json", "dns": "uniswap.grade.anchorterminal.com", "repo": "https://github.com/Uniswap/uniswap-ai", "license": "The Trading API is a proprietary hosted service under Uniswap Labs' API Terms of Use, which we couldn't read; the SDKs and the uniswap-ai skills are MIT. Swaps execute on the open-source Uniswap protocol contracts on chain", "transports": [], "packages": [ { "registry": "npm", "name": "@uniswap/v4-sdk" } ], "auth": "api-key", "authNotes": "An API key from the Uniswap Developer Platform dashboard, sent as `x-api-key` on every request; the docs say to keep it server-side. The API never holds funds or keys. `/quote` returns `permitData` the user signs as EIP-712 typed data, `/swap` returns calldata the caller signs and broadcasts, and `/order` takes a signed UniswapX order. An optional `X-Agent-Info` header with `decision_origin` of `autonomous` or `human_mediated` attributes agent traffic (https://developers.uniswap.org/docs/trading/swapping-api/start-building/integration-guide, checked 2026-11-03).", "pricing": "free", "pricingNotes": "The API is free, with no subscription or per-call charge, per the FAQ and the Developer Platform post of 16 April 2026. Swaps pay the pool fee and gas on chain; UniswapX orders are gasless for the swapper. Integrators may add up to 4 fee entries totalling at most 500 bips. Each key is limited to 6 requests a second (https://developers.uniswap.org/docs/trading/swapping-api/faqs, checked 2026-11-03).", "priceSummary": "Free", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 on the API's endpoints (checked 2026-11-03). The uniswap-ai repository's `pay-with-any-token` skill helps an agent pay HTTP 402 challenges (MPP or x402) by swapping tokens through Uniswap, which is a buyer-side skill, not a paid endpoint.", "endpoints": [] }, "toolCount": 0, "popularity": { "githubStars": 236, "npmWeekly": 153782, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://developers.uniswap.org/docs/trading/overview", "llmsTxt": "https://developers.uniswap.org/llms.txt", "openapi": "https://trade-api.gateway.uniswap.org/v1/api.json", "capabilities": [ "exchange.spot-trading", "exchange.market-data", "market.crypto", "wallet.onchain" ], "tags": [ "official", "hosted", "closed-source", "openapi", "llms-txt", "api-key", "free", "no-card", "typescript", "agent-skills", "no-status-page", "security-txt", "rest" ], "lastRelease": "2026-10-22", "graded": true, "anchor": { "graded": true, "score": 63.3, "grade": "B", "agentReady": false, "rank": 470, "ranked": true, "rankOf": 1349, "categoryRank": 5, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 72, "maintenance": 88, "payments": 40, "reliability": 42, "schema": 90, "security": 63, "transparency": 55 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-03" }, "negative": 0, "verdict": "The Trading API is free, documented by an OpenAPI file with stable error codes, holds no keys since the caller signs every swap, and posts sunset notices 30 days ahead. There is no official MCP server, status page or sandbox, the key is a plain header secret at 6 requests a second, and the API terms refused our reader.", "bestFor": "An agent swapping or bridging tokens from its own wallet on 21 EVM chains, or managing liquidity positions, with routing done for it.", "strengths": [ "OpenAPI 3.0 file, llms.txt, llms-full.txt and Markdown twins, with 400, 401, 404 and 429 schemas and a stable `errorCode` enum", "The API builds calldata and never holds funds or keys; the caller signs `permitData` and the transaction with its own wallet", "Free with no per-call charge, 21 chains for classic swaps and UniswapX on 10 of them", "Dated changelog notices with a 30-day minimum sunset policy, and the uniswap-ai skills (MIT) for coding agents", "A documented `X-Agent-Info` header for autonomous and human-mediated traffic, and retry guidance per error code" ], "weaknesses": [ "No official MCP server; the registry's Uniswap entries are third parties", "No status page, no SLA and no sandbox; tests use production endpoints on testnets", "A single `x-api-key` per key with 6 requests a second and no scopes; the dashboard is disallowed by robots.txt so key management is unchecked", "The API Terms of Use and Uniswap Labs' terms and privacy policy are on a help centre that answered 403 or draw by script, so restricted countries and data handling are unchecked", "No official client library for the API; the TypeScript SDKs cover the protocol and quoting, not the API" ], "agentNotes": [ "Call `/check_approval` first, then `/quote`; if `permitData` is non-null sign it as EIP-712 and send `signature` and `permitData` together to `/swap` or `/order`, never one without the other", "Route on the quote's `routing`: `CLASSIC`, `WRAP`, `UNWRAP` and `BRIDGE` go to `/swap`, `DUTCH_V2`, `DUTCH_V3` and `PRIORITY` to `/order`, `CHAINED` to `/plan`", "Refresh any quote older than 30 seconds before broadcasting, and on 429 pause every request from the key before retrying", "Retry unchanged only on `UpstreamTimeoutError`; `NoRouteFoundError` and `QuoteAmountTooLowError` need a different amount, token or `protocols` list", "Send `X-Agent-Info` with `decision_origin: autonomous` and keep `x-api-key` server-side" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 63.3 } ], "editorialScores": { "ergonomics": 72, "maintenance": 88, "payments": 40, "reliability": 42, "schema": 90, "security": 63, "transparency": 35 }, "provenanceScore": 74, "checked": { "categories": { "ergonomics": "2026-11-03", "maintenance": "2026-11-03", "payments": "2026-11-03", "reliability": "2026-11-03", "schema": "2026-11-03", "security": "2026-11-03", "transparency": "2026-11-03" }, "last": "2026-11-03", "oldest": "2026-11-03", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "npx skills add Uniswap/uniswap-ai", "http": "curl -X POST https://trade-api.gateway.uniswap.org/v1/quote -H 'x-api-key: YOUR_UNISWAP_API_KEY' -H 'Content-Type: application/json' -d '{\"tokenIn\":\"0x0000000000000000000000000000000000000000\",\"tokenOut\":\"0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48\",\"tokenInChainId\":1,\"tokenOutChainId\":1,\"type\":\"EXACT_INPUT\",\"amount\":\"1000000000000000000\",\"swapper\":\"0xYourWallet\"}'" }, "letme": { "capability": "https://letme.dev/exchange.spot-trading", "tool": "https://letme.dev/uniswap" }, "area": "payments", "provenance": { "legalEntity": "Uniswap Labs", "domain": "uniswap.org", "domainRegistered": "2018-11-26", "endpointOnVendorDomain": true, "terms": "https://support.uniswap.org/hc/en-us/articles/43018872248589-API-Terms-of-Use", "privacy": "", "statusPage": "", "changelog": "https://developers.uniswap.org/docs/changelog", "securityTxt": "valid", "checked": "2026-11-03", "notes": [ "Uniswap Labs is the name on the uniswap-ai licence and the blog; the API Terms of Use (support.uniswap.org, answered 403) are said in a search snippet to name Universal Navigation, Inc., which was not read first-hand.", "RDAP gives uniswap.org a registration date of 26 November 2018, registrar Cloudflare.", "app.uniswap.org/.well-known/security.txt lists a Cantina bounty and security@uniswap.org with no Expires field; uniswap.org redirects to the app.", "status.uniswap.org redirects to app.uniswap.org/swap, so no status page is recorded.", "The privacy policy at app.uniswap.org draws by script and was not read. developers.uniswap.org/robots.txt disallows /dashboard, /api/ and /oauth/, so the key dashboard was not fetched; trade-api.gateway.uniswap.org has no robots.txt (404)." ], "score": 74 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/uniswap.json", "live": { "slug": "uniswap", "securityTxt": { "url": "https://uniswap.org/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-04T15:53:09.573484239Z" }, "updatedAt": "2026-11-04T15:53:09.573484239Z" } }, "edges": [ { "by": 50, "category": "schema", "leads": "uniswap", "name": "Schema \u0026 documentation", "reasons": { "a": "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.", "b": "OpenAPI 3.0 file (Token Trading 1.0.0) for the Trading and LP APIs, about 33 paths with `x-internal` markers on the margin and 4337 operations (25). llms.txt, llms-full.txt and a Markdown twin of every docs page (10). Operation summaries are one line, but the guides say which routing types go to `/swap`, `/order` and `/plan`, when UniswapX quotes are returned and when a 404 means change the request (14 of 20). Enums for routing types, urgency and position statuses, required fields and bounded integers such as `limit` 1 to 20 (12 of 15). Examples on every guide page and error schemas for 400, 401, 404 and 429 with a stable `errorCode` enum and per-code retry advice (14 of 15). A /v1 path, a changelog with posted and effective dates and a 30-day minimum sunset policy (15). Total 90." }, "scores": { "a": 40, "b": 90 } }, { "by": 31, "category": "maintenance", "leads": "uniswap", "name": "Maintenance \u0026 community", "reasons": { "a": "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.", "b": "Read as a closed hosted service. The newest changelog notice is dated 22 October 2026 (30). Notices of 20 August, 21 September and 22 October 2026, three in 90 days (20). A help form for developer support that says it won't debug integrators' code, and uniswap-ai with 6 open issues and a push on 26 October (14 of 25). Official TypeScript SDKs current (@uniswap/v4-sdk 2.4.4 with provenance) and the uniswap-ai skills, though no client for the API itself; no MCP registry entry (15). Trusted publishing with provenance on npm, CI and lint hooks on uniswap-ai (9 of 10). Total 88." }, "scores": { "a": 57, "b": 88 } }, { "by": 30, "category": "transparency", "leads": "uniswap", "name": "Transparency \u0026 trust", "reasons": { "a": "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.", "b": "The editorial half. The API is closed under API Terms of Use that answered 403; the SDKs and uniswap-ai are MIT and the protocol contracts are open source (15 of 30). No privacy policy read (app.uniswap.org draws by script) and nothing in the docs on retention of quotes or wallet addresses (0 of 30). A published sunset policy of at least 30 days, ideally 60, with dated notices such as the Universal Router 2.0 and 2.1.1 sunset of 21 October 2026 (20). No subprocessors or data locations (0 of 20). Total 35." }, "scores": { "a": 25, "b": 55 } }, { "by": 25, "category": "payments", "leads": "uniswap", "name": "Payments \u0026 pricing", "reasons": { "a": "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.", "b": "No machine payment protocol on the API's endpoints; the `pay-with-any-token` skill lets an agent pay other services' 402 challenges by swapping, which earns nothing here (0). The API is free, stated in the FAQ and the 16 April 2026 post, and integrator fees are capped at 500 bips (20). No card and no plan (20). A person creates an account in the dashboard to get a key (0). Total 40." }, "scores": { "a": 15, "b": 40 } }, { "by": 12, "category": "security", "leads": "uniswap", "name": "Security \u0026 auth", "reasons": { "a": "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.", "b": "A single `x-api-key` header, no scopes, no IP allow-list; revocation and rotation happen in a dashboard robots.txt disallows, so unchecked; nothing in a URL (18 of 30). The API never holds keys or funds, every value transfer needs the caller's signature on `permitData` and the transaction, and the swapper sets slippage (16 of 20). The API returns routes and token lists, not untrusted content (10). The dashboard presumably shows key usage; not read, and no per-call log is documented (5 of 15). security.txt on app.uniswap.org with a Cantina bounty and security@uniswap.org, protocol audits in the docs; no SOC 2 or disclosure timeline read (14 of 20). Total 63." }, "scores": { "a": 51, "b": 63 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "HTX", "b": "Uniswap Labs", "name": "Vendor" }, { "a": "no (local only)", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "", "b": "", "name": "Transports" }, { "a": "API key", "b": "API key", "name": "Auth" }, { "a": "Pay per use", "b": "Free", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "none", "b": "The Trading API is a proprietary hosted service under Uniswap Labs' API Terms of Use, which we couldn't read; the SDKs and the uniswap-ai skills are MIT. Swaps execute on the open-source Uniswap protocol contracts on chain", "name": "Licence" }, { "a": "0", "b": "0", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-21", "b": "2026-10-22", "name": "Last release" }, { "a": "no date given", "b": "couldn't be read", "name": "Terms last updated" }, { "a": "no document linked", "b": "no document linked", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "couldn't be read", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "couldn't be read", "name": "Arbitration or class-action waiver" }, { "a": "684 stars", "b": "236 stars, 154k npm/wk", "name": "Popularity" } ], "faq": [ { "answer": "Uniswap Trading API scores 63.3 (B) on agent readiness against HTX trading API's 43.3 (E), and leads in every scored category.", "question": "Which is better for AI agents, HTX trading API or Uniswap Trading API?" }, { "answer": "Both need an API key.", "question": "Do HTX trading API and Uniswap Trading API need an API key?" }, { "answer": "No hosted endpoint is listed for HTX trading API. No hosted endpoint is listed for Uniswap Trading API.", "question": "Can an agent call HTX trading API and Uniswap Trading API without installing anything?" } ], "goodFor": [ { "aheadOn": null, "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" }, { "aheadOn": [ "Schema \u0026 documentation, 90 against 40", "Security \u0026 auth, 63 against 51", "Payments \u0026 pricing, 40 against 15", "Maintenance \u0026 community, 88 against 57", "Transparency \u0026 trust, 55 against 25" ], "also": [ "Free to start without a card" ], "goodFor": "An agent swapping or bridging tokens from its own wallet on 21 EVM chains, or managing liquidity positions, with routing done for it.", "slug": "uniswap", "watchFor": "No official MCP server; the registry's Uniswap entries are third parties" } ], "history": null, "job": { "capability": "exchange.market-data", "name": "Exchange market data" }, "others": [ { "json": "https://www.anchorterminal.com/compare/bitfinex-vs-htx.json", "title": "Bitfinex API vs HTX trading API", "url": "https://www.anchorterminal.com/compare/bitfinex-vs-htx" }, { "json": "https://www.anchorterminal.com/compare/bitfinex-vs-uniswap.json", "title": "Bitfinex API vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/bitfinex-vs-uniswap" }, { "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-uniswap.json", "title": "Bitget vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/bitget-vs-uniswap" }, { "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/bithumb-vs-uniswap.json", "title": "Bithumb Open API vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/bithumb-vs-uniswap" }, { "json": "https://www.anchorterminal.com/compare/bitstamp-vs-htx.json", "title": "Bitstamp API vs HTX trading API", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-htx" }, { "json": "https://www.anchorterminal.com/compare/bitstamp-vs-uniswap.json", "title": "Bitstamp API vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-uniswap" }, { "json": "https://www.anchorterminal.com/compare/bybit-vs-htx.json", "title": "Bybit vs HTX trading API", "url": "https://www.anchorterminal.com/compare/bybit-vs-htx" }, { "json": "https://www.anchorterminal.com/compare/bybit-vs-uniswap.json", "title": "Bybit vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/bybit-vs-uniswap" }, { "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/crypto-com-exchange-vs-uniswap.json", "title": "Crypto.com Exchange API vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-uniswap" }, { "json": "https://www.anchorterminal.com/compare/dydx-vs-uniswap.json", "title": "dYdX vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/dydx-vs-uniswap" }, { "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/gate-io-vs-uniswap.json", "title": "Gate vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/gate-io-vs-uniswap" }, { "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/gemini-exchange-vs-uniswap.json", "title": "Gemini Exchange API vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/gemini-exchange-vs-uniswap" }, { "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-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/kucoin-vs-uniswap.json", "title": "KuCoin vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/kucoin-vs-uniswap" }, { "json": "https://www.anchorterminal.com/compare/mexc-vs-uniswap.json", "title": "MEXC API vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/mexc-vs-uniswap" }, { "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/binance-vs-uniswap.json", "title": "Binance API vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/binance-vs-uniswap" }, { "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-advanced-trade-vs-uniswap.json", "title": "Coinbase Advanced Trade API vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-uniswap" }, { "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/coinbase-mcp-vs-uniswap.json", "title": "Coinbase MCP server (Coinbase for Agents) vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-uniswap" }, { "json": "https://www.anchorterminal.com/compare/deribit-vs-uniswap.json", "title": "Deribit vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/deribit-vs-uniswap" }, { "json": "https://www.anchorterminal.com/compare/hyperliquid-vs-uniswap.json", "title": "Hyperliquid vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/hyperliquid-vs-uniswap" }, { "json": "https://www.anchorterminal.com/compare/kraken-vs-uniswap.json", "title": "Kraken API vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/kraken-vs-uniswap" }, { "json": "https://www.anchorterminal.com/compare/okx-vs-uniswap.json", "title": "OKX API vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/okx-vs-uniswap" }, { "json": "https://www.anchorterminal.com/compare/uniswap-vs-upbit.json", "title": "Uniswap Trading API vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/uniswap-vs-upbit" }, { "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": [ { "by": 4, "edge": "uniswap", "htx": 38, "key": "reliability", "name": "Reliability", "uniswap": 42, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 50, "edge": "uniswap", "htx": 40, "key": "schema", "name": "Schema \u0026 documentation", "uniswap": 90, "weight": 13 }, { "by": 3, "edge": "uniswap", "htx": 69, "key": "ergonomics", "name": "Agent ergonomics", "uniswap": 72, "weight": 13 }, { "by": 12, "edge": "uniswap", "htx": 51, "key": "security", "name": "Security \u0026 auth", "uniswap": 63, "weight": 14 }, { "by": 25, "edge": "uniswap", "htx": 15, "key": "payments", "name": "Payments \u0026 pricing", "uniswap": 40, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 31, "edge": "uniswap", "htx": 57, "key": "maintenance", "name": "Maintenance \u0026 community", "uniswap": 88, "weight": 7 }, { "by": 30, "edge": "uniswap", "htx": 25, "key": "transparency", "name": "Transparency \u0026 trust", "uniswap": 55, "weight": 7 } ], "summary": "Uniswap Trading API scores 63.3 (B) on agent readiness against HTX trading API's 43.3 (E), and leads in every scored category. Both do exchange market data.", "tasks": null, "tutorials": [], "verdicts": { "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.", "uniswap": "The Trading API is free, documented by an OpenAPI file with stable error codes, holds no keys since the caller signs every swap, and posts sunset notices 30 days ahead. There is no official MCP server, status page or sandbox, the key is a plain header secret at 6 requests a second, and the API terms refused our reader." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/htx-vs-uniswap", "json": "https://www.anchorterminal.com/compare/htx-vs-uniswap.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/htx-vs-uniswap.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/htx-vs-uniswap.min.md" }, "markdown": "Uniswap Trading API scores 63.3 (B) on agent readiness against HTX trading API's 43.3 (E), and leads in every scored category. Both do exchange market data.\n\n- HTX trading API: grade E, 43.3/100, rank #1156 of 1349. Markdown https://www.anchorterminal.com/tools/htx.md · JSON https://www.anchorterminal.com/api/v1/tools/htx.json\n- Uniswap Trading API: grade B, 63.3/100, rank #470 of 1349. Markdown https://www.anchorterminal.com/tools/uniswap.md · JSON https://www.anchorterminal.com/api/v1/tools/uniswap.json\n- Best crypto exchange APIs and MCP servers for AI agents: https://www.anchorterminal.com/best/crypto-exchanges/index.md\n- All 210 exchanges comparisons: https://www.anchorterminal.com/compare/crypto-exchanges/index.md\n\n## Which one, for what\n\n### 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\nWatch for: No official MCP server; the only one in the MCP registry is a third party's read-only ticker server\n\n### Uniswap Trading API (B)\n\nGood for: An agent swapping or bridging tokens from its own wallet on 21 EVM chains, or managing liquidity positions, with routing done for it.\n\nAhead on:\n- Schema \u0026 documentation, 90 against 40\n- Security \u0026 auth, 63 against 51\n- Payments \u0026 pricing, 40 against 15\n- Maintenance \u0026 community, 88 against 57\n- Transparency \u0026 trust, 55 against 25\n\nAlso in its favour:\n- Free to start without a card\n\nWatch for: No official MCP server; the registry's Uniswap entries are third parties\n\n\n## Why the edge\n\n### Schema \u0026 documentation: Uniswap Trading API +50\n\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- Uniswap Trading API (90): OpenAPI 3.0 file (Token Trading 1.0.0) for the Trading and LP APIs, about 33 paths with `x-internal` markers on the margin and 4337 operations (25). llms.txt, llms-full.txt and a Markdown twin of every docs page (10). Operation summaries are one line, but the guides say which routing types go to `/swap`, `/order` and `/plan`, when UniswapX quotes are returned and when a 404 means change the request (14 of 20). Enums for routing types, urgency and position statuses, required fields and bounded integers such as `limit` 1 to 20 (12 of 15). Examples on every guide page and error schemas for 400, 401, 404 and 429 with a stable `errorCode` enum and per-code retry advice (14 of 15). A /v1 path, a changelog with posted and effective dates and a 30-day minimum sunset policy (15). Total 90.\n\n### Maintenance \u0026 community: Uniswap Trading API +31\n\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- Uniswap Trading API (88): Read as a closed hosted service. The newest changelog notice is dated 22 October 2026 (30). Notices of 20 August, 21 September and 22 October 2026, three in 90 days (20). A help form for developer support that says it won't debug integrators' code, and uniswap-ai with 6 open issues and a push on 26 October (14 of 25). Official TypeScript SDKs current (@uniswap/v4-sdk 2.4.4 with provenance) and the uniswap-ai skills, though no client for the API itself; no MCP registry entry (15). Trusted publishing with provenance on npm, CI and lint hooks on uniswap-ai (9 of 10). Total 88.\n\n### Transparency \u0026 trust: Uniswap Trading API +30\n\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- Uniswap Trading API (55): The editorial half. The API is closed under API Terms of Use that answered 403; the SDKs and uniswap-ai are MIT and the protocol contracts are open source (15 of 30). No privacy policy read (app.uniswap.org draws by script) and nothing in the docs on retention of quotes or wallet addresses (0 of 30). A published sunset policy of at least 30 days, ideally 60, with dated notices such as the Universal Router 2.0 and 2.1.1 sunset of 21 October 2026 (20). No subprocessors or data locations (0 of 20). Total 35.\n\n### Payments \u0026 pricing: Uniswap Trading API +25\n\n- HTX trading API (15): 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.\n- Uniswap Trading API (40): No machine payment protocol on the API's endpoints; the `pay-with-any-token` skill lets an agent pay other services' 402 challenges by swapping, which earns nothing here (0). The API is free, stated in the FAQ and the 16 April 2026 post, and integrator fees are capped at 500 bips (20). No card and no plan (20). A person creates an account in the dashboard to get a key (0). Total 40.\n\n### Security \u0026 auth: Uniswap Trading API +12\n\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- Uniswap Trading API (63): A single `x-api-key` header, no scopes, no IP allow-list; revocation and rotation happen in a dashboard robots.txt disallows, so unchecked; nothing in a URL (18 of 30). The API never holds keys or funds, every value transfer needs the caller's signature on `permitData` and the transaction, and the swapper sets slippage (16 of 20). The API returns routes and token lists, not untrusted content (10). The dashboard presumably shows key usage; not read, and no per-call log is documented (5 of 15). security.txt on app.uniswap.org with a Cantina bounty and security@uniswap.org, protocol audits in the docs; no SOC 2 or disclosure timeline read (14 of 20). Total 63.\n\n## Score by category\n\n| Category | Weight | HTX trading API | Uniswap Trading API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 38 | 42 | Uniswap Trading API +4 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 40 | 90 | Uniswap Trading API +50 |\n| Agent ergonomics | 13% (16.2 this run) | 69 | 72 | Uniswap Trading API +3 |\n| Security \u0026 auth | 14% (17.5 this run) | 51 | 63 | Uniswap Trading API +12 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 15 | 40 | Uniswap Trading API +25 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 57 | 88 | Uniswap Trading API +31 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 25 | 55 | Uniswap Trading API +30 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **43.3 · E** | **63.3 · B** | |\n\n## Facts side by side\n\n| Fact | HTX trading API | Uniswap Trading API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | HTX | Uniswap Labs |\n| Hosted endpoint | no (local only) | no (local only) |\n| Transports | | |\n| Auth | API key | API key |\n| Pricing | Pay per use | Free |\n| x402 | no | no |\n| Licence | none | The Trading API is a proprietary hosted service under Uniswap Labs' API Terms of Use, which we couldn't read; the SDKs and the uniswap-ai skills are MIT. Swaps execute on the open-source Uniswap protocol contracts on chain |\n| Tools exposed | 0 | 0 |\n| Read-only variant documented | no | no |\n| llms.txt | no | yes |\n| Last release | 2026-10-21 | 2026-10-22 |\n| Terms last updated | no date given | couldn't be read |\n| Privacy policy last updated | no document linked | no document linked |\n| Customer content may train models | not found in the text | couldn't be read |\n| Terms restrict automated access | not found in the text | couldn't be read |\n| Terms restrict benchmarking | not found in the text | couldn't be read |\n| Terms or service can change without notice | yes | couldn't be read |\n| Arbitration or class-action waiver | yes | couldn't be read |\n| Popularity | 684 stars | 236 stars, 154k npm/wk |\n\n## Verdicts\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**Uniswap Trading API.** The Trading API is free, documented by an OpenAPI file with stable error codes, holds no keys since the caller signs every swap, and posts sunset notices 30 days ahead. There is no official MCP server, status page or sandbox, the key is a plain header secret at 6 requests a second, and the API terms refused our reader.\n\n## Before you call either\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### Uniswap Trading API\n\n1. Call `/check_approval` first, then `/quote`; if `permitData` is non-null sign it as EIP-712 and send `signature` and `permitData` together to `/swap` or `/order`, never one without the other\n2. Route on the quote's `routing`: `CLASSIC`, `WRAP`, `UNWRAP` and `BRIDGE` go to `/swap`, `DUTCH_V2`, `DUTCH_V3` and `PRIORITY` to `/order`, `CHAINED` to `/plan`\n3. Refresh any quote older than 30 seconds before broadcasting, and on 429 pause every request from the key before retrying\n4. Retry unchanged only on `UpstreamTimeoutError`; `NoRouteFoundError` and `QuoteAmountTooLowError` need a different amount, token or `protocols` list\n5. Send `X-Agent-Info` with `decision_origin: autonomous` and keep `x-api-key` server-side\n\n## Questions\n\n### Which is better for AI agents, HTX trading API or Uniswap Trading API?\n\nUniswap Trading API scores 63.3 (B) on agent readiness against HTX trading API's 43.3 (E), and leads in every scored category.\n\n### Do HTX trading API and Uniswap Trading API need an API key?\n\nBoth need an API key.\n\n### Can an agent call HTX trading API and Uniswap Trading API without installing anything?\n\nNo hosted endpoint is listed for HTX trading API. No hosted endpoint is listed for Uniswap Trading API.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/htx-vs-uniswap.json, and with the fewest tokens: https://www.anchorterminal.com/compare/htx-vs-uniswap.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"htx\", \"b\": \"uniswap\"}`. From a terminal: `anchor compare htx uniswap`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/htx.json and https://www.anchorterminal.com/api/v1/tools/uniswap.json\n\n## Other comparisons with HTX trading API or Uniswap Trading API\n\n- [Bitfinex API vs HTX trading API](https://www.anchorterminal.com/compare/bitfinex-vs-htx.md)\n- [Bitfinex API vs Uniswap Trading API](https://www.anchorterminal.com/compare/bitfinex-vs-uniswap.md)\n- [Bitget vs HTX trading API](https://www.anchorterminal.com/compare/bitget-vs-htx.md)\n- [Bitget vs Uniswap Trading API](https://www.anchorterminal.com/compare/bitget-vs-uniswap.md)\n- [Bithumb Open API vs HTX trading API](https://www.anchorterminal.com/compare/bithumb-vs-htx.md)\n- [Bithumb Open API vs Uniswap Trading API](https://www.anchorterminal.com/compare/bithumb-vs-uniswap.md)\n- [Bitstamp API vs HTX trading API](https://www.anchorterminal.com/compare/bitstamp-vs-htx.md)\n- [Bitstamp API vs Uniswap Trading API](https://www.anchorterminal.com/compare/bitstamp-vs-uniswap.md)\n- [Bybit vs HTX trading API](https://www.anchorterminal.com/compare/bybit-vs-htx.md)\n- [Bybit vs Uniswap Trading API](https://www.anchorterminal.com/compare/bybit-vs-uniswap.md)\n- [Crypto.com Exchange API vs HTX trading API](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-htx.md)\n- [Crypto.com Exchange API vs Uniswap Trading API](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-uniswap.md)\n- [dYdX vs Uniswap Trading API](https://www.anchorterminal.com/compare/dydx-vs-uniswap.md)\n- [Gate vs HTX trading API](https://www.anchorterminal.com/compare/gate-io-vs-htx.md)\n- [Gate vs Uniswap Trading API](https://www.anchorterminal.com/compare/gate-io-vs-uniswap.md)\n- [Gemini Exchange API vs HTX trading API](https://www.anchorterminal.com/compare/gemini-exchange-vs-htx.md)\n- [Gemini Exchange API vs Uniswap Trading API](https://www.anchorterminal.com/compare/gemini-exchange-vs-uniswap.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 Upbit Open API](https://www.anchorterminal.com/compare/htx-vs-upbit.md)\n- [KuCoin vs Uniswap Trading API](https://www.anchorterminal.com/compare/kucoin-vs-uniswap.md)\n- [MEXC API vs Uniswap Trading API](https://www.anchorterminal.com/compare/mexc-vs-uniswap.md)\n- [Binance API vs HTX trading API](https://www.anchorterminal.com/compare/binance-vs-htx.md)\n- [Binance API vs Uniswap Trading API](https://www.anchorterminal.com/compare/binance-vs-uniswap.md)\n- [Coinbase Advanced Trade API vs HTX trading API](https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-htx.md)\n- [Coinbase Advanced Trade API vs Uniswap Trading API](https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-uniswap.md)\n- [Coinbase MCP server (Coinbase for Agents) vs HTX trading API](https://www.anchorterminal.com/compare/coinbase-mcp-vs-htx.md)\n- [Coinbase MCP server (Coinbase for Agents) vs Uniswap Trading API](https://www.anchorterminal.com/compare/coinbase-mcp-vs-uniswap.md)\n- [Deribit vs Uniswap Trading API](https://www.anchorterminal.com/compare/deribit-vs-uniswap.md)\n- [Hyperliquid vs Uniswap Trading API](https://www.anchorterminal.com/compare/hyperliquid-vs-uniswap.md)\n- [Kraken API vs Uniswap Trading API](https://www.anchorterminal.com/compare/kraken-vs-uniswap.md)\n- [OKX API vs Uniswap Trading API](https://www.anchorterminal.com/compare/okx-vs-uniswap.md)\n- [Uniswap Trading API vs Upbit Open API](https://www.anchorterminal.com/compare/uniswap-vs-upbit.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-04", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "HTX trading API vs Uniswap Trading API", "url": "" } ], "description": "Uniswap Trading scores 63.3 (B) to HTX trading's 43.3 (E) for exchange market data. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "HTX trading API E 43.3", "Uniswap Trading API B 63.3", "scores" ], "h1": "HTX trading API vs Uniswap Trading API", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/htx-vs-uniswap", "published": "2026-10-01", "section": "tools", "title": "HTX trading vs Uniswap Trading for AI agents (2026) | Anchor Terminal", "toc": null, "updated": "2026-11-04", "url": "https://www.anchorterminal.com/compare/htx-vs-uniswap" }, "tokens": { "markdown": 4400, "slim": 2180 }, "version": 1 }