Buildix speaks the Model Context Protocol, so an AI assistant can read Hyperliquid orderflow analytics while you talk to it. There are two modes. Free needs no account and no key and answers with short readings. API uses your Buildix API key and returns the raw values the REST API returns, including what the free mode does not have.
Both modes are read-only: no tool places an order, moves funds or changes anything in your account.
https://www.buildix.trade/api/mcp/public
Every tool accepts detail: "brief" (the default) returns labels and the key numbers in a few hundred tokens, "full" adds the underlying values, the age of each source and a short note on method. Every answer states the time of the market data it was computed from and ends with the line Informational orderflow analytics, not financial advice.
get_orderflow_snapshotOrderflow snapshotReturns a compact orderflow reading for one Hyperliquid perpetual market, computed by Buildix from recent fills, the order book and market context: direction of recent buy and sell flow (CVD), order book imbalance (OBI) and flow toxicity (VPIN) as categories, funding rate and open interest. Use it when the user asks about buying or selling pressure, order book balance, flow toxicity, funding or open interest for one coin or HIP-3 market.
input: symbol (e.g. "BTC", "kPEPE", "xyz:NVDA"), detail?: "brief" | "full"
try: "Is there more buying or selling pressure on SOL right now?"
get_liquidation_levelsLiquidation levelsReturns the main liquidation levels above and below the current price for one Hyperliquid perpetual market, estimated from the whole open interest with an assumed leverage mix: price, distance and size of each cluster, and in detail "full" a wider range and the amount liquidated on moves of 5, 10 and 15%. A model, not a record of positions. Use it when the user asks where liquidations sit around the price or how much could be liquidated on a move of a given size.
input: symbol, detail?: "brief" | "full"
try: "Where are the liquidation levels for BTC on Hyperliquid?"
get_whale_positioningWhale positioningReturns the aggregated long versus short positioning of the large Hyperliquid accounts Buildix tracks for one market: long and short notional, the number of accounts on each side and the resulting bias. No account addresses are returned. Use it when the user asks whether whales or large traders are long or short a coin.
input: symbol, detail?: "brief" | "full"
try: "Are whales long or short ETH right now?"
get_funding_ratesFunding ratesReturns Hyperliquid perpetual funding rates ranked from highest to most negative, annualized, with a market-wide summary (median, open-interest-weighted average, count of positive and negative markets). Markets under $1M of open interest are left out of the rankings. Use it when the user asks which markets pay the highest or most negative funding, or how funding looks across Hyperliquid.
input: detail?: "brief" | "full"
try: "Which Hyperliquid markets have the highest funding?"
get_market_screenerMarket screenerReturns a snapshot of the Hyperliquid perpetual market: number of markets, total open interest and 24h volume, breadth, open-interest-weighted funding, the top markets by 24h volume, price change, open interest or funding, and the largest 24h gainers and losers. Use it for market overviews, top movers or the most active markets.
input: detail?: "brief" | "full", sort_by?: "volume" | "change" | "open_interest" | "funding"
try: "Give me an overview of the Hyperliquid market today."
https://www.buildix.trade/api/mcp
Each tool sits at the same plan as its REST equivalent and spends from the same daily quota, so a plan includes the same data whichever protocol you use. API keys are issued on the Whale and API plans, in Dashboard, API Keys.
get_screenerNO KEY NEEDEDEvery tradable Hyperliquid perpetual with mark price, 24h change, 24h volume, open interest in USD and funding, raw and annualized.
input: none
get_pairNO KEY NEEDEDOne pair in detail: mark and oracle price, 24h change and volume, open interest, funding raw and annualized, margin limits, size decimals and a link to its Deep View.
input: symbol, for example "BTC"
get_signalsWHALE / APICurrent signals of the Buildix V5 and V6 orderflow engines across all pairs: direction, signed score, confidence 0 to 100, regime, the components that passed their gate and up to six reasons.
input: none
get_smart_moneyWHALE / APITracked whale wallets ranked by account value, their largest open positions and the long or short bias per coin, from the tracker snapshot refreshed every 10 minutes.
input: none
get_liquidation_mapWHALE / APILiquidation clusters around the mark with the estimated size in USD at each price level, plus cascade scenarios for moves of N percent. HIP-3 markets as "dex:COIN".
input: symbol, price_range_pct? 1 to 20, scenarios? number[]
get_hip4_edgeWHALE / APIActive HIP-4 outcome markets ranked by the gap between model and market: implied and model probability, divergence, edge_score blended with the V5 signal on the underlying, edge_flag and a consistency flag.
input: underlying?, min_abs_divergence? 0 to 1, edge_flag?, limit?
get_cvdWHALE / APICumulative volume delta as a time series: buy_usd, sell_usd, delta, running cvd and trade count per bucket. Computed on a sample of the tape, so it is a directional measure, not absolute traded volume.
input: symbol, interval? "5m" | "15m" | "1h", lookback?
A key is bx_ followed by 32 hex characters. Send it on every request, in either header:
Authorization: Bearer bx_0123456789abcdef0123456789abcdef x-api-key: bx_0123456789abcdef0123456789abcdef
Assistants whose connector form takes only a URL (Claude, ChatGPT, Le Chat, Perplexity, Grok) accept the key on the URL instead:
https://www.buildix.trade/api/mcp?api_key=bx_0123456789abcdef0123456789abcdef
Headers are read first; the query parameter is the fallback. A key in a URL can end up in client logs and browser history, so give that connector its own key and revoke it from the dashboard if it is ever exposed. Revocation applies to the next request.
A tool your plan does not cover answers inside the JSON-RPC envelope, not with an HTTP error, so the assistant can read the reason out to you:
Buildix MCP: "get_signals" requires the trader plan or above. This request resolved to "anonymous". Pass a Buildix API key with every MCP request, as a header: Authorization: Bearer bx_xxxxxxxx or x-api-key: bx_xxxxxxxx
A key keeps working if its owner moves to another plan, and then follows that plan: get_signals answers from Trader, get_smart_money from Pro, the other gated tools from Whale.
Short readings the assistant can quote: pressure, liquidation levels, whale bias, funding, a market overview. No account, nothing to configure beyond the URL.
Raw values in the same shape as the REST API, the CVD history as a time series, the signal engine, the HIP-4 edge ranking and the liquidation map with cascade scenarios.
Menu names move between app versions; the steps below are the current ones. Use the free URL or the API URL depending on the mode.
https://www.buildix.trade/api/mcp/public
https://www.buildix.trade/api/mcp?api_key=bx_0123456789abcdef0123456789abcdef
Custom connectors take a URL, not a header, so API mode uses the key on the URL.
claude mcp add --transport http buildix https://www.buildix.trade/api/mcp/public
claude mcp add --transport http buildix-api https://www.buildix.trade/api/mcp \ --header "Authorization: Bearer bx_0123456789abcdef0123456789abcdef"
https://www.buildix.trade/api/mcp/public
https://www.buildix.trade/api/mcp?api_key=bx_0123456789abcdef0123456789abcdef
Developer mode is offered on paid ChatGPT plans, on the web.
https://www.buildix.trade/api/mcp/public
https://www.buildix.trade/api/mcp?api_key=bx_0123456789abcdef0123456789abcdef
Adding a connector needs the administrator role, which an individual account owner has.
https://www.buildix.trade/api/mcp/public
https://www.buildix.trade/api/mcp?api_key=bx_0123456789abcdef0123456789abcdef
Custom connectors are a paid Perplexity feature.
https://www.buildix.trade/api/mcp/public
https://www.buildix.trade/api/mcp?api_key=bx_0123456789abcdef0123456789abcdef
{
"mcpServers": {
"buildix": { "url": "https://www.buildix.trade/api/mcp/public" }
}
}{
"mcpServers": {
"buildix-api": {
"url": "https://www.buildix.trade/api/mcp",
"headers": { "Authorization": "Bearer bx_0123456789abcdef0123456789abcdef" }
}
}
}{
"servers": {
"buildix": { "type": "http", "url": "https://www.buildix.trade/api/mcp/public" }
}
}{
"inputs": [
{ "type": "promptString", "id": "buildix-key", "description": "Buildix API key", "password": true }
],
"servers": {
"buildix-api": {
"type": "http",
"url": "https://www.buildix.trade/api/mcp",
"headers": { "Authorization": "Bearer ${input:buildix-key}" }
}
}
}Free mode, one tool call:
curl -X POST https://www.buildix.trade/api/mcp/public \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_funding_rates","arguments":{}}}'API mode, the tool list with your key:
curl -X POST https://www.buildix.trade/api/mcp \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-H "Authorization: Bearer bx_0123456789abcdef0123456789abcdef" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'The free mode is published in these MCP directories:
Claude Connectors Directory: pending review.
Both modes read analytics Buildix computes from Hyperliquid market data that its own pipeline collects. Neither queries Hyperliquid while answering you, which is why an answer arrives in well under a second and why it states the time of the data it used.
All Hyperliquid perpetuals on the default dex, plus HIP-3 builder markets such as xyz:NVDA.
CVD reads the last captured fills: a sample of the tape, so it shows direction, not total traded volume. OBI uses the top 10 levels on each side.
Computed for the most active default-dex markets. Other markets report it as unavailable.
The free mode returns aggregates only, never an address. The API mode tool get_smart_money lists the tracked wallets.
Each tool returns exactly what its REST equivalent returns at /api/v1.
Liquidation levels are an estimate over the whole open interest of a market: aggregated clusters, not a record of individual positions.
Full policy: Privacy Policy.
One shared daily capacity of 20,000 tool calls across all users, reset at 00:00 UTC. Connecting and listing the tools does not count. There is no per-address limit, because assistants call from shared networks. An identical question is answered from a short cache (30 seconds to 2 minutes, depending on how often the data changes).
The daily quota of the key, shared with the REST API, reset at Europe/Rome midnight. Past it the server answers HTTP 429 with Retry-After. Every caller also has a burst guard of 60 requests per minute per IP address. Read the limit applied to your key at /api/v1/usage.
Quotas of every plan, and the legacy Whale allowance: REST API docs.
Check the URL: https://www.buildix.trade/api/mcp/public for free mode, https://www.buildix.trade/api/mcp for API mode. Choose no authentication when the assistant asks: neither mode uses OAuth. Both speak Streamable HTTP, so a client that only supports the older SSE transport cannot connect. Run the curl command of the mode you use: a JSON answer means the server is up and the problem is in the client setup.
Use the Hyperliquid ticker: BTC, ETH, SOL. Contracts quoted per thousand units carry a lowercase k (kPEPE, kBONK); PEPE also resolves to kPEPE. HIP-3 markets are written dex:COIN, for example xyz:NVDA.
Both modes answer only from data Buildix collected in the last few minutes and never fill a gap with an older figure. Retry after a few minutes.
Free capacity is shared by everyone and resets at 00:00 UTC. A pause is a maintenance switch. Neither depends on your account or your prompt; API mode is not affected.
The key decides which tools answer. The message names the tool, the plan it needs and the plan your request resolved to. A request without a key resolves to "anonymous" and only reaches get_screener and get_pair.
A 401 means the key is not valid or was revoked. A 429 means the daily quota of the key is used up; the Retry-After header carries the seconds until the reset at Europe/Rome midnight.
Disclaimer. Informational orderflow analytics, not financial advice. The tools describe market conditions; they do not recommend trades, and figures can be estimates (each answer says which). Trading perpetual futures carries a high risk of loss. Read the risk disclosure.
Support and security reports: hello@buildix.trade