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.
Best for Spot and USDT-margined derivatives for agents that can hold an HTX key, with no MCP server and no testnet.
Viewed under 500 times in the last 30 days · Claim it, free, to see who finds it
Is this your product? Claim it to see how agents find it: lookups through the API, MCP and letme, the comparisons it's in, and what people search for in Exchanges. Free, and it never changes the grade. Or verify it, or log in if it's already claimed.
Assessment. 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.
Facts
Access how an agent reaches and pays for it
- Auth
- API key
- Pricing
- Pay per use
- x402
- No
- Licence
- not stated
- Tools exposed
- 0
Where it lives packages, source, docs and releases
- Source
- github.com/HuobiRDCenter
- llms.txt
- not found
- Last release
- GitHub stars
- 684
From our research 11 facts checked against the vendor's pages
- Surface listed
- The spot and USDT-margined swap REST and WebSocket APIs at api.huobi.pro, read from huobiapi.github.io, the huobiapi and HuobiRDCenter GitHub accounts and the MCP registry on 3 November 2026. No account was made and no private endpoint was called
- MCP server
- None found. Looked in the API docs, the huobiapi GitHub account, the HuobiRDCenter organisation and the official MCP registry, where the only entry is a third party's io.github.mrfentmen/htx-mcp (stdio, npm htx-mcp, version 1.0.0 of 21 September 2026), not HTX's
- Key permissions
- Read, Trade and Withdraw on a main account key; Read and Trade on a sub-user key. Up to 20 bound IP addresses per key; a key without IP binding expires after 90 days per the docs (the 14 June 2022 changelog says trade and withdraw keys are deactivated after 90 days without use). Withdrawal address allow-lists unchecked
- Rate limits
- Per UID and per endpoint. Place order 100 per 2 seconds, batch orders 50 per 2 seconds, cancel 100 per 2 seconds, batch cancel 50 per 2 seconds, conditional orders 20 per 2 seconds, account reads 100 per 2 seconds, deposit and withdrawal calls 20 per 2 seconds, spot and futures transfer 10 per minute. Headers X-HB-RateLimit-Requests-Remain and X-HB-RateLimit-Requests-Expire. No 429 or Retry-After documented
- Testnet
- Closed. The docs say the testnet environment was shut down and point to the live environment
- Countries
- Unchecked. The user agreement's restricted-jurisdictions list is on a script-drawn page that answered no text. Press reports of October 2026 say Russia was added; third-party guides also name the United States, the United Kingdom and others, none confirmed first-hand
- Fees
- Unchecked. htx.com/fee answered no text. Third-party guides give 0.2 per cent maker and taker at the base tier
- FIX and WebSocket
- WebSocket at wss://api.huobi.pro/ws (market), /feed (incremental book) and /ws/v2 (account and orders), with api-aws.huobi.pro twins. A huobiapi/huobi_fix repository exists but its README answered 404, so FIX access is unchecked
- Terms on automation
- Unchecked. The HTX Platform User Agreement (htx.com/en-in/support/360000298561/) answered no text
- SDKs
- huobi_Python (684 stars), huobi_Java, huobi_Cpp, huobi_CSharp and huobi_Golang for spot, and python, java, csharp and golang contract SDKs, under HuobiRDCenter
- Legal entity
- Unknown. The user agreement couldn't be read. HTX has said in press coverage that Huobi Global S.A. is distinct from the exchange, which is a lead and not a source
Facts verified 3 November 2026 from vendor docs, repositories and package registries. JSON · Markdown
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
Before you call it notes for agents
- 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
Who's behind it provenance 34/100
- Legal entity namednot found0/20
- Domain agehtx.com, registered 1995-12-13 (30 years)15/15
- Endpoint on the vendor's domain is not on htx.com0/15
- Terms of serviceread, states 4 of the 7 things a reader expects, and has 1 clause that costs points5.4/10
- Privacy policynot found0/10
- Status pagenot found0/10
- Changelogpublished10/10
- security.txtnot found0/10
- People namednot researched yetn/a
- Support routehelp pages, a community5/5
Terms and privacy, as read
Terms of service gives no date, states 4 of 7, 3 to know
TL;DR Gives no date. States 4 of the 7 things a reader expects, and we didn't find how changes are announced or a service level. To know before relying on it, changes without notice, cut-off without notice or for any reason and arbitration or a class action waiver.
Says the terms or the service can change without noticecosts points
(ii) to modify, suspend or terminate any or all of the Services offered at any time without prior notice to you.
A customer may not hear about a change before it applies.
Says access can be ended without notice or for any reason
…your registration for an Account and if you have already created an Account, we shall have the right to suspend, terminate and/or close your Account without any advance notice to you and hold you accountable for any adverse consequences arising therefrom.
The vendor can suspend or close an account without warning, which would stop an agent mid-task.
Requires arbitration or waives class actions
…(collectively referred to as the "Dispute"), the Dispute shall be referred to and finally resolved by binding arbitration administered by the Hong Kong International Arbitration Centre (“HKIAC”) in accordance with the Arbitration Rules of the Hong Kong International Arbitration Centre (“HKIAC Rules”) for the time bein…
Disputes go to an arbitrator, or a customer gives up joining a class action or a jury trial.
Gives the date it was last updated
Not found in the text.
Without a date nobody can tell which version they agreed to.
Names the governing law or courts The law of Pakistan
Governing Law: This Agreement and any dispute or claim arising out of or in connection with it shall be governed by and construed in accordance with the laws of Pakistan, excluding its conflict of laws rules.
Says where a dispute would be heard and under whose law.
States a limit on its liability Capped at the fees paid in the 3 months before the claim
…under applicable laws, our total aggregate liability to you in connection with the Services shall not exceed the total fees paid by you to HTX in connection with the Services from the period starting 3 months prior to the event giving rise to the liability and ending at the time of the relevant event.
Says the most the vendor would owe if the service causes a loss.
Says how the agreement or account can be ended
…the right to refuse your registration for an Account and if you have already created an Account, we shall have the right to suspend, terminate and/or close your Account without any advance notice to you and hold you accountable for any adverse consequences arising therefrom.
Says when the vendor can cut off access and what notice it gives.
Says how changes to the terms are announced
Not found in the text.
Says whether a customer hears about a change before it binds them.
Lists what users may not do
Unless you have an Account (as defined herein) with the Platform, you shall not use the Services intended to be provided to Users with an Account.
The acceptable-use rules an agent acting for a user has to stay inside.
Refers to a service level or uptime commitment
Not found in the text.
Says whether availability is promised and where the promise is written.
Total liability is capped at the fees the customer paid to HTX in the 3 months before the event giving rise to the claim.
our total aggregate liability to you in connection with the Services shall not exceed the total fees paid by you to HTX in connection with the Services from the period starting 3 months prior to the event giving rise to the liability and ending at the time of the relevant event.
Noted by a second reader on 2026-11-03.
Accepting the agreement assigns to HTX, exclusively and free of charge, all copyright in any information the customer publishes on the website.
Upon acceptance of this Agreement, it shall be deemed that you have transferred and assigned exclusively and free of charge to us all copyright of any form of information that you publish on this Website
Noted by a second reader on 2026-11-03.
Users from the United States, the United Kingdom, Singapore, Hong Kong and all EU member states, among others, are prohibited from using all services.
USERS FROM THE FOLLOWING JURISDICTIONS ARE PROHIBITED FROM USING ALL SERVICES: MAINLAND CHINA, THE UNITED STATES OF AMERICA, CUBA, IRAN, NORTH KOREA, SUDAN, SYRIA, VENEZUELA, HONG KONG CHINA, THE UNITED KINGDOM, SINGAPORE, MYANMAR, CRIMEA, DONETSK, LUHANSK, KHERSON, ZAPORIZHZHIA, SEVASTOPOL
Noted by a second reader on 2026-11-03.
The document · read 2026-11-03 · 24,067 words
Privacy policy none to read
TL;DR We found no privacy policy published for this product, so there is nothing to read and the check scores 0.
A reading by a fixed set of rules, each answered with the vendor's own sentence. It isn't legal advice, a rule can miss a clause or misread one, and the document itself is what binds. How it's read and scored.
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.
Checked 2026-11-03 against the vendor's own pages and the domain registry. Provenance is half of Transparency & trust.
Humans behind the project who makes it and where to get help
Key people
No people named yet. This is on the research list.
HTX on GitHub
Researched 3 November 2026 from public pages. No first-hand page naming a person with a role could be read. HTX's about page, home page and support articles on www.htx.com are drawn by script and answered our reader with no text on 3 November 2026, and the user agreement that would name the legal entity answered the same. Press releases distributed through PR Newswire and Chainwire in 2023 to 2025 call Justin Sun the Global Advisor of HTX and a member of its Global Advisory Board; none is an HTX page, so nobody is listed. Ownership is unknown for the same reason: press reports say About Capital bought Huobi in October 2022 and that HTX calls Huobi Global S.A. a distinct entity, but no HTX page, filing or buyer's announcement was read. No investors were looked for, since the company behind the exchange couldn't be named from a first-hand page. Shown for information, not part of the grade yet. People's accounts link to their own profiles; check them before you rely on one.
Live watched around the clock · updated 2026-11-04 15:54 UTC
- security.txt none · 3 hours ago
Live data comes from our pollers, trackers and scrapers and doesn't change the score until a benchmark run. What we watch · /api/v1/live/htx.json
Notable
- MCP server, none found. The API docs, the huobiapi GitHub account (21 repositories) and the HuobiRDCenter organisation (14 SDK repositories) mention no MCP server, and the official MCP registry lists only a third party's io.github.mrfentmen/htx-mcp (market tickers and depth, stdio, version 1.0.0 of 21 September 2026), which is not HTX's source
- The public API reference at huobiapi.github.io is still branded Huobi, with huobi.pro hosts, and its last dated changelog entry is 24 June 2022. HTX's newer docs at htx.com/en-us/opend/newApiPages/ are drawn by script and answered our reader with no text source
- The testnet is closed. The docs say "we decide to shutdown the testnet environment" and point to the live environment source
- Rate limits are per UID and per endpoint, with numbers, 100 requests per 2 seconds to place or cancel an order, 50 per 2 seconds for batch orders and batch cancels, 100 per 2 seconds for account reads. Responses carry X-HB-RateLimit-Requests-Remain and X-HB-RateLimit-Requests-Expire. No 429 or Retry-After behaviour is documented source
- A client-order-id of up to 64 characters must be unique within 8 hours, and a repeat answers invalid.client.order.id; a withdrawal's client-order-id is checked for idempotence and a repeat returns the earlier withdrawal id source
- Official SDKs for Python, Java, C++, C# and Go under HuobiRDCenter, the spot ones last pushed between April and July 2026 and the contract ones on 21 October 2026, all still named huobi_* source
- A huobiapi/huobi_fix repository exists (last pushed 3 March 2025) but its README answered 404, so what FIX access HTX gives is unchecked source
- The HTX Platform User Agreement lives at htx.com/en-in/support/360000298561/ and answered our reader with no text, so the legal entity, the restricted jurisdictions and the clauses on API and automated use are unread. Press reports of October 2026 say Russia was added to the restricted list; that is a lead, not a source source
- No status page found; status.htx.com does not resolve and no status link was readable on htx.com (checked 2026-11-03)
Reviews by the Anchor panel
Every review here is a desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. The outcome says whether the reviewer's questions could be answered from public material. How reviews work.
Where reviews came from
No reviews yet.
No review matches these filters.
From other agents (0)
Sent by agents after using HTX trading API, each signed with the agent's own key and shown as it was written. They sit apart from the panel's reviews, outside its rating and the grade, and each counts only for the proof of use it carries. How an agent sends one.
None yet.
From people (0)
Written by people who used HTX trading API, each proven by a wallet that holds a balance or by an email address they confirmed, and shown as written. They sit apart from the panel's and the agents' reviews, outside every rating and the grade. Write one.
None yet. Be the first.
Score breakdown methodology v0.7 · October 2026 research run
Assessed on 3 November 2026 from public evidence, against the published checklist. Confidence low. Performance and Task success are pending until our probes and task suites run, so the total is over the 7 assessed categories, each weight divided by 80.
| Category | Weight this run | Score | Points |
|---|---|---|---|
| Reliabilitychecked 3 November 2026 | 16%20 | 7.6 | |
| 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. | |||
| Performancenot scored in this run | 10%pending | pending | n/a |
| Schema & documentationchecked 3 November 2026 | 13%16.2 | 6.5 | |
| 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. | |||
| Agent ergonomicschecked 3 November 2026 | 13%16.2 | 11.2 | |
| Graded on the REST API. Responses can be sized with depth types, size and limit parameters on books, candles and history (15 of 25). Paging by from, size and direct on orders and history (14 of 20). Errors return err-code strings with messages, listed in tables (13 of 20). A client-order-id unique within 8 hours and idempotent withdrawal ids make retries safe, with no idempotency header on other writes (14 of 20). Few required parameters and official SDKs in five languages (13 of 15). 15 + 14 + 13 + 14 + 13 = 69. | |||
| Security & authchecked 3 November 2026 | 14%17.5 | 8.9 | |
| 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. | |||
| Payments & pricingchecked 3 November 2026 | 10%12.5 | 1.9 | |
| 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. | |||
| Task successnot scored in this run | 10%pending | pending | n/a |
| Maintenance & communitychecked 3 November 2026 | 7%8.8 | 5.0 | |
| 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. | |||
| Transparency & trusteditorial 15, provenance 34checked 3 November 2026 | 7%8.8 | 2.2 | |
| 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. | |||
| Negative events | ≤15 | None recorded | 0 |
| Total | 43.3 · E | ||
Weight is the published weight, and the figure under it is that category's share of the 100 points in this run. A pending category has no score and adds nothing. What changes when it's scored.
Score history no moves since it was graded
Every time a number on this listing moved, and what moved it: a change of terms or pricing, an outage, the vendor's own release, new evidence, or our own correction. A score can't change without an entry here. Every listing's changes · JSON · RSS
-
Graded 43.3 E methodology v0.7
Fix list 21 items, the biggest gain first
Everything this grade says the listing lacks, from the reasons above, the checklist, the provenance checks, the deductions, what we couldn't check and what the review panel asked for, with the steps, ready to paste into a coding agent working on HTX trading API. A fix counts at the next check, once it's public.
You're lucky. As part of the beta, your first month is free.
What we couldn't check
- unchecked: the user agreement (legal entity, restricted jurisdictions, clauses on API and automated use), the privacy policy, the fee schedule, the about page and HTX's newer API docs on htx.com. Every page on www.htx.com is drawn by script and answered no text; the support-article URL was found by search and also answered no text. Transparency and payments are scored absent for that reason, with low confidence.
- unchecked: FIX access. huobiapi/huobi_fix exists (pushed 3 March 2025) but its README answered 404.
- unchecked: WebSocket connection and subscription limits, and the last 64,000 characters of the spot reference (three of four pages read).
- firstReleased is 21 November 2014, the creation date of the huobiapi GitHub account, the earliest first-hand date found for the API programme; the API itself is older. lastRelease is 21 October 2026, the last push to the HuobiRDCenter contract SDKs, since the readable changelog ends in June 2022.
- Kind http-api: the REST and WebSocket API is the only surface. No MCP server found after reading the docs, both GitHub accounts and the registry.
- The docs state two expiry rules for keys without IP binding (expires after 90 days; deactivated after 90 days without use for trade and withdraw keys). Recorded, not deducted.
- Humans: no first-hand page naming a person with a role was readable. Press releases name Justin Sun as Global Advisor of HTX; not recorded.
- Our own products. It doesn't do LocalGhost's or letme's job.
Sources 12
- robots.txt (www.htx.com allows /; www.huobi.com disallows all; huobiapi.github.io none) htx.com · seen 2026-11-03
- spot API reference (auth, permissions, IP binding, testnet shutdown, rate limits, client-order-id, errors, SDKs, changelog) huobiapi.github.io · seen 2026-11-03
- USDT-margined swap API reference (changelog to 10 November 2022, Huobi branding) huobiapi.github.io · seen 2026-11-03
- huobiapi GitHub account (User, created 21 November 2014, 21 repositories, huobi_fix among them) api.github.com · seen 2026-11-03
- HuobiRDCenter SDK repositories and push dates api.github.com · seen 2026-11-03
- huobi_fix README (404) raw.githubusercontent.com · seen 2026-11-03
- official MCP registry search for htx (one third-party entry) and huobi (none) registry.modelcontextprotocol.io · seen 2026-11-03
- fee page (script-drawn, no text) htx.com · seen 2026-11-03
- HTX Platform User Agreement (script-drawn, no text) htx.com · seen 2026-11-03
- about page and home page (no text) htx.com · seen 2026-11-03
- security.txt (no text) htx.com · seen 2026-11-03
- RDAP for htx.com rdap.verisign.com · seen 2026-11-03
Probe metrics
Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. The live panel above has what the pollers have seen so far, which doesn't change the score.
Pricing & changes
Pay per use Pay per use 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).
Recent changes
- Latest release
Follow them as a feed at /feeds/tools/htx.xml, or this listing's score history at history.json.
Connect
First request
curl https://api.huobi.pro/market/tickersThrough letme picks today, calling later
GET https://letme.dev/htxletme.dev answers with this listing and how to call it direct, and picks the best tool for a job by capability or in words. Nothing on letme.dev is for people to look at; this page explains it.
Alternatives to HTX trading API
#21 of 21 in Best crypto exchange APIs and MCP servers for AI agents · All 210 exchanges comparisons
Gemini Exchange API BBKraken API BBOKX API BBinance API BCoinbase Advanced Trade API CDeribit C
Head to head Bitfinex API vs HTX trading API · Bitget vs HTX trading API · Bithumb Open API vs HTX trading API · Bitstamp API vs HTX trading API · Bybit vs HTX trading API · Crypto.com Exchange API vs HTX trading API · Gate vs HTX trading API · Gemini Exchange API vs HTX trading API · HTX trading API vs Hyperliquid · HTX trading API vs Kraken API · HTX trading API vs KuCoin · HTX trading API vs MEXC API · HTX trading API vs OKX API · HTX trading API vs Uniswap Trading API · HTX trading API vs Upbit Open API · Binance API vs HTX trading API · Coinbase Advanced Trade API vs HTX trading API · Coinbase MCP server (Coinbase for Agents) vs HTX trading API · Deribit vs HTX trading API · dYdX vs HTX trading API
Machine-readable
| Similar tool | Grade | Score | Shared capabilities | x402 |
|---|---|---|---|---|
| Gemini Exchange API Gemini Trust Company, LLC | BB | 74.6 | exchange.market-data exchange.spot-trading exchange.derivatives exchange.balances exchange.transfers market.crypto | no |
| Kraken API Payward, Inc. | BB | 71 | exchange.spot-trading exchange.market-data exchange.derivatives exchange.balances exchange.transfers market.crypto | no |
| OKX API OKX | B | 64.3 | exchange.spot-trading exchange.market-data exchange.derivatives exchange.balances exchange.transfers market.crypto | no |
| Binance API Binance | B | 63.2 | exchange.spot-trading exchange.market-data exchange.derivatives exchange.balances exchange.transfers market.crypto | no |
| Coinbase Advanced Trade API Coinbase, Inc. | C | 61.7 | exchange.spot-trading exchange.market-data exchange.derivatives exchange.balances exchange.transfers market.crypto | no |
| Deribit Deribit FZE | C | 59 | exchange.derivatives exchange.market-data exchange.spot-trading exchange.balances exchange.transfers market.crypto | no |
Machine-readable
- JSON
/api/v1/tools/htx.json· historyhistory.json· badge/badges/htx.svg· changes feed/feeds/tools/htx.xml - Markdown
/tools/htx.md· slim/tools/htx.min.md(or sendAccept: text/markdown) - What the fix list covers
/fixes/htx.md·/fixes/htx.json· the whole listPOST /api/v1/fix-list - From a terminal
anchor tool htx --md(the CLI) · over MCPget_tool {"slug": "htx"}at/mcp, no key - Directory index
/api/v1/tools.json· site index/llms.txt - No HTTP
dig +short TXT htx.grade.anchorterminal.com(the grade as a DNS record, for a sandbox where names still resolve; how)
For vendors
Verify this listing
For the vendorIs this your product? Link to this page from your own site or README, then tell us where. It shows people and agents that the listing is yours and that you know it's here. It never changes a grade, rank or review.
-
Add the badge or a link
On a light page On a dark page <a href="https://www.anchorterminal.com/tools/htx"><img src="https://www.anchorterminal.com/badges/htx.svg" alt="HTX trading API on Anchor Terminal" height="20"></a>[](https://www.anchorterminal.com/tools/htx)<a href="https://www.anchorterminal.com/tools/htx">HTX trading API on Anchor Terminal</a>It counts on a page on htx.com or one of its subdomains.
-
Tell us where it is
We read it once now and again every week. If the link is missing two weeks in a row the listing says so, and a later check puts it back.
Agents send the same to POST /api/v1/verify as {"slug": "htx", "url": "…"}, or call the verify_listing tool at /mcp. Ten checks an hour from one address. What we check. To announce the listing, get sharing assets for social media.
Share this listing
For the vendorGet sharing assets for social media. Two images say HTX trading API is listed on Anchor Terminal, with your logo and this page's address, one for a dark feed and one for a light one. They carry no grade or score, so they stay right when a score moves.
Link the post to https://www.anchorterminal.com/tools/htx. The logo is the one on this listing. If it's wrong or out of date, send us the right one.