Buildix is an institutional-grade orderflow analytics platform for DEX and CEX perpetual trading. Access real-time CVD, VPIN, OBI, whale tracking and signal data over a REST API from Python, JavaScript or cURL. All endpoints are documented below. There is no WebSocket: the platform is serverless and holds no connections, so consumers poll, and the feed endpoints report their producer cadence so you know how often that is worth doing.
The same data is exposed to AI agents over the Model Context Protocol. Seven read-only tools, one endpoint, the same API keys and the same daily quota. Buildix MCP server.
Counted per API key, reset at Europe/Rome midnight (not UTC). Exhausting it returns HTTP 429 with a Retry-After header holding the seconds until the reset. Whale moved from 50,000 to 2,000 requests per day in September 2026 and the 50,000 allowance moved to the API plan; a Whale subscription that started before 8 September 2026 keeps 50,000 per day for 60 days from that date. Read /api/v1/usage for the limit actually applied to your key.
The burst guard runs at the edge and does not depend on your plan. It is keyed by identity: your IP address, or your IP plus the public prefix of the key when you send one, so a shared office address is not punished for one noisy key. Going over returns HTTP 429 with the window in the body and an accurate Retry-After.
Every tradable Hyperliquid perpetual with mark price, 24h change, 24h volume, open interest in USD and funding (raw + annualized). No API key required; a key only raises the daily quota.
curl "https://www.buildix.trade/api/v1/screener" # A key is optional here, and raises the daily quota: curl "https://www.buildix.trade/api/v1/screener" \ -H "Authorization: Bearer YOUR_API_KEY"
Generate an API key from your Dashboard → API Keys. Include it in every request as a Bearer token. Keys look like bx_ followed by 32 hex characters — there is no bx_live_ / bx_test_ split.
Authorization: Bearer bx_0123456789abcdef0123456789abcdef
Two other spellings are accepted, in this order of priority: the header x-api-key: bx_..., and, only where a client cannot set a custom header at all, the query parameter ?api_key=bx_.... A key in a URL can be captured by your own client logs and by any proxy in between, so keep the query form for connectors that leave you no choice and give those a dedicated key.
/api/v1/screener and /api/v1/pair/{symbol} answer without a key; a key on those only raises the daily quota. Every other endpoint requires one. An invalid or revoked key returns 401, a plan below the endpoint returns 403 naming the tier required, and an exhausted daily quota returns 429.
Need API access?
The screener and pair endpoints are open, so you can build against them before you pick a plan. A key raises the daily quota and unlocks the gated endpoints; the burst limit per minute is the same on every plan.