Native portfolio-margin data

Hyperliquid Native Reserve Health

Inspect reserve balances, rates, and history.

Official public reserve stateNo address or signature

What does Hyperliquid's native borrow/lend reserve show?

The public API currently reports reserve-level supplied, borrowed, available-balance, utilization, yearly-rate, oracle-price, and LTV fields. HypeBasis maps each reserve index through official spot metadata and keeps the API's balance field separate instead of reconstructing it. This is Hyperliquid's native portfolio-margin system—not the separate HyperLend protocol.

Hyperliquid labels portfolio margin pre-alpha

Eligible assets, caps, parameters, rate behavior, and liquidation mechanics may change. Reported yearly rates are point-in-time protocol fields—not promised returns, realized account yield, or a recommendation to supply or borrow.

Current read

Reserve ledger

Live · Sep 5, 04:17
Reported assets
5
Mapped reserve rows
Total supplied
$1.34B
Calculated at reported oracle prices
Total borrowed
$244.71M
Calculated at reported oracle prices
Aggregate utilization
18.2%
Borrowed USD ÷ supplied USD

HYPE

Token index 150 · oracle 83.829

0.0% used
Supplied
9.32M · $781.67M
Borrowed
0 · $0
Reported balance
9.32M · $781.67M
Reported LTV
65%
Supply rate
0.00% / yr
Borrow rate
5.00% / yr

USDC

Token index 0 · oracle 1

58.8% used
Supplied
414.87M · $414.87M
Borrowed
244.04M · $244.04M
Reported balance
170.83M · $170.83M
Reported LTV
0%
Supply rate
2.65% / yr
Borrow rate
5.00% / yr

UBTC

Token index 197 · oracle 79,583

0.0% used
Supplied
1.81K · $144.41M
Borrowed
0 · $0
Reported balance
1.81K · $144.41M
Reported LTV
50%
Supply rate
0.00% / yr
Borrow rate
5.00% / yr

USDT0

Token index 268 · oracle 1.0003

30.7% used
Supplied
2.12M · $2.12M
Borrowed
649.8K · $650K
Reported balance
1.47M · $1.47M
Reported LTV
0%
Supply rate
1.38% / yr
Borrow rate
5.00% / yr

USDH

Token index 360 · oracle 1

11.0% used
Supplied
172.27K · $172K
Borrowed
18.87K · $19K
Reported balance
153.4K · $153K
Reported LTV
0%
Supply rate
0.49% / yr
Borrow rate
5.00% / yr

Reported available balance totals $1.1B across current rows. USD totals are calculated with each row's reported oracle price and can move with that price.

Hourly public dataset

Seven-day reserve history

History Building
Reserve history is building

2 valid hourly captures are saved. The utilization chart stays hidden until a reserve has at least 24 fresh observations spanning 18 hours without a gap above 90 minutes.

Newest saved capture · Sep 5, 04:17

Download stored reserve observations

2 captures · 5 mapped or indexed assets · CSV never makes a new upstream request.

Download CSV

Calculation boundary

What HypeBasis calculates

  • USD supplied, borrowed, and balance values multiply the reported native-unit amount by the same row's oracle price.
  • Aggregate utilization divides summed borrowed USD by summed supplied USD. It is a cross-asset overview, not an account risk metric.
  • Percent displays multiply the API's utilization, yearly-rate, and LTV decimals by 100. No compounding or yield projection is added.
  • History requires 24 observations, 18 observed hours, no gap above 90 minutes, and a newest capture no older than 90 minutes.
CSV columns and units20 fields
Native reserve history CSV columns, units, and meanings
ColumnUnitMeaning
captured_at_utcISO 8601 UTCScheduled observation time.
capture_statuslabelWhether the saved capture was live or partial.
asset_indexintegerOfficial spot token index in the reserve tuple.
assetsymbolOfficial spotMeta token name, when mapped.
token_idhex identifierOfficial spot token identifier, when mapped.
oracle_price_usdUSD per assetReported reserve oracle price.
total_suppliedasset unitsReported total supplied balance.
total_supplied_usdUSDTotal supplied multiplied by oracle price.
total_borrowedasset unitsReported total borrowed balance.
total_borrowed_usdUSDTotal borrowed multiplied by oracle price.
reported_balanceasset unitsThe API's balance field; not reconstructed.
reported_balance_usdUSDReported balance multiplied by oracle price.
utilization_decimaldecimalReported utilization ratio.
utilization_percent%Reported utilization multiplied by 100.
supply_yearly_rate_decimaldecimalReported yearly supply rate.
supply_yearly_rate_percent% yearlySupply yearly rate multiplied by 100.
borrow_yearly_rate_decimaldecimalReported yearly borrow rate.
borrow_yearly_rate_percent% yearlyBorrow yearly rate multiplied by 100.
ltv_decimaldecimalReported loan-to-value parameter.
ltv_percent%Reported LTV multiplied by 100.

Risk and interpretation limits

Borrowing, lending, portfolio margin, liquidations, oracle changes, smart-contract behavior, and protocol changes can cause loss. A reserve-level utilization or LTV value does not describe a specific account, guarantee future liquidity, or establish that supplying or borrowing is suitable. Test pre-alpha behavior cautiously through official interfaces and documentation.

How to read this dataReviewed 2026-09-04 · Expand
Where this comes from
Official Hyperliquid allBorrowLendReserveStates and spotMeta info requests.
How fresh it is
Current state refreshes through a one-minute server cache. Saved history uses the existing hourly schedule. Latest live read: Sep 5, 04:17.
Last reviewed
2026-09-04
How to use it
The page preserves reported reserve fields, labels every display calculation, withholds incomplete trends, and does not request user account data.
Last updated: 2026-09-04Last reviewed: 2026-09-04

Sources

4 references · Expand
  • Supports: Public info endpoint families used for market, book, candle, account, portfolio, native borrow/lend reserve, vaultDetails, userFees account-rate, and maxBuilderFee approval reads.
  • Supports: The pre-alpha status of portfolio margin, eligible quote-asset supplying and borrowing, utilization definition, hourly interest indexing, the documented pre-alpha stablecoin rate model, protocol interest buffer, LTV context, and liquidation mechanics.
  • Supports: Public spot token and pair metadata, rolling dayNtlVlm market contexts, outcomeMeta request and response fields, asset-context price and supply fields, tokenDetails maximum-supply definitions, and spotClearinghouseState balances.
  • Supports: Current REST request-weight, WebSocket, and user-limit constraints for public-data tooling.