HyperCore info API

The Hyperliquid info API (read types only) with your endpoint token: POST the usual {"type": …} body.

Contents

Chains, regions and plans open one by one when enough teams ask for them. These docs describe exactly how they work. What is open

Endpoints

HTTPShttps://rpc.blockmetric.io/hypercore/YOUR_TOKENAvailable when your plan opens.

Header authhttps://rpc.blockmetric.io/hypercorewith Authorization: Bearer bmr_… Available when your plan opens.

Healthhttps://rpc.blockmetric.io/hypercore/healthPublic, no token, once this chain opens. Available when your plan opens.

Native token: HYPE
Network: Mainnet
WebSocket: No, HTTPS only

POST the Hyperliquid info request body ({"type": …}); only the read types listed in the docs.

First request

Weight per type below; the answer is passed through unchanged.

curl -s https://rpc.blockmetric.io/hypercore/$BLOCKMETRIC_RPC_TOKEN \
  -H "Content-Type: application/json" \
  -d '{"type":"clearinghouseState","user":"0x0000000000000000000000000000000000000000"}'

Info types and weights

Only these read types reach the node; unknown fields are dropped. Addresses are 0x with 40 hex characters.

HyperCore info types with weights and parameters
Type	Parameters	Weight
`activeAssetData`	`user, coin`	1
`allMids`	-	1
`clearinghouseState`	`user, dex?`	1
`delegations`	`user`	1
`delegatorSummary`	`user`	1
`exchangeStatus`	-	1
`extraAgents`	`user`	1
`frontendOpenOrders`	`user, dex?`	1
`marginTable`	`id`	1
`maxBuilderFee`	`user, builder`	1
`maxMarketOrderNtls`	-	1
`meta`	`dex?`	1
`openOrders`	`user, dex?`	1
`perpDexs`	-	1
`perpsAtOpenInterestCap`	`dex?`	1
`spotClearinghouseState`	`user`	1
`spotMeta`	-	1
`subAccounts`	`user`	1
`userFees`	`user`	1
`userRateLimit`	`user`	1
`userToMultiSigSigners`	`user`	1
`userVaultEquities`	`user`	1
`leadingVaults`	`user`	2
`metaAndAssetCtxs`	-	2
`perpDeployAuctionStatus`	-	2
`spotDeployState`	`user`	2
`userRole`	`user`	2
`validatorL1Votes`	-	2
`vaultSummaries`	-	2
`webData2`	`user`	2
`liquidatable`	-	5

"?" marks an optional parameter. Order and transaction actions are not offered: this endpoint only reads.

The info API is not JSON-RPC, so errors of the info request itself (type, parameters, rate, node) are plain JSON: {"error":{"code":"…","message":"…","doc_url":"…","request_id":"…"}}. Token, access and body-size errors come first and use the JSON-RPC error shape. Both carry the HTTP status and the codes of the error table.

Independent infrastructure, not affiliated with Hyperliquid. Answers come from the chain’s nodes as they are, without guarantee.

Code snippets in these docs are licensed under MIT-0: copy them into your own code without attribution. Use of Blockmetric RPC is governed by the terms. Independent infrastructure, not affiliated with the chains or their foundations.