Data sources

Every displayed figure comes from the table below and is rendered on the server before the page is sent, so it is present for readers, search crawlers and answer engines alike.

The source that was withdrawn

Until 19 August 2026 the coin pages carried a spot price, 24-hour statistics and spot candle charts from Coinbase Exchange, plus the basis between that price and the perpetual. All of it has been removed and none of it is served anywhere, including through this site's JSON endpoint.

Coinbase's Market Data Terms of Use (last updated 7 August 2026) were read in full on that date. Quoting that document, https://www.coinbase.com/legal/market_data: they bind on access alone — "By accessing or using Coinbase Market Data, you agree to be bound by these Market Data Terms of Use" — grant a licence only for "personal or research purposes" that "may not be used to build an application intended for use by end users", and provide that, absent prior express written consent, you may not "Redistribute, display, or disseminate the Market Data—or any data, charts, analytics, research, or other works based on, referring to, or derived from the Market Data" to any third party outside your organisation. This site is a public website; that is the whole of the question.

So the coin pages are now perpetual pages, drawn from the same Hyperliquid feed as the rest of the site. The basis went with the spot price, because computing it requires one. Nothing here substitutes Hyperliquid's oracle index for a spot price: the oracle is a validator median across venues rather than a traded market, and using it under the old label would be a different number wearing the old one's name.

The two venues we never contact

Binance and Bybit funding rates appear on this site, and no request is ever made to either. They arrive inside Hyperliquid's predictedFundings response — one query, to one venue — and that is checkable: there is no Binance or Bybit hostname anywhere in this codebase. Both venues' terms bind on accessing their service, and we do not.

That is the whole of the position, and it is worth being exact about its shape rather than comfortable about it. We rely on not being party to those venues' terms — not on any permission from them. Neither has granted this site anything, neither has been asked, and nothing here should be read as a claim that they permit the display. It is an argument about who a contract reaches, and a lawyer has not tested it. Bybit's API terms were read on 19 August 2026; they bar providing access to Bybit's platform to a third party and bar automated retrieval, which is why this site does neither.

Which Ethereum endpoints

The on-chain figures are read from three interchangeable public JSON-RPC endpoints — ethereum-rpc.publicnode.com, eth.drpc.org and 1rpc.io — whichever answers first. The table calls that "Ethereum JSON-RPC" because the reader's question is which chain and which method, not which mirror. They are named here anyway, for the narrower question that only a hostname can answer: whose terms apply, and where to read them.

Coverage

A contract gets a page when its perpetual holds $5.00M of open interest and ranks among the largest 50 by open interest. Once published it keeps the page while its open interest stays above $3.50M, even if larger contracts outrank it — up to 5 pages beyond the 50. 76 of the 178 perpetuals the venue lists clear the $5.00M floor today and 55 have pages — 21 clear the floor but rank below the largest 50 and have no page yet; 5 keep their pages although outranked.

Outbound, and behind no figure

Five hosts are contacted that supply nothing you see. When a contract crosses the coverage floor or a coin reaches its publication date, a URL exists that did not exist before, and the ingest worker announces that one URL through the IndexNow protocol — to api.indexnow.org and, separately, to www.bing.com, yandex.com, search.seznam.cz and searchadvisor.naver.com. The protocol says one endpoint shares a submission with the others, and until 19 August only the shared one was called; the five were measured answering independently that day — one of them returns a different status code for the same request — so a success from the aggregator is not evidence that any particular index received anything. These are server-to-server calls: nothing about you is sent, because nothing about you is known — see Privacy. They fire on new URLs only, never on the prices moving. The fastest figures in the table above refresh every minute; announcing each refresh would be announcing nothing, up to 60 times an hour, which is the behaviour the protocol exists to be distinguished from.

What is deliberately absent

• Liquidation totals. Exchange feeds are throttled and any total would be understated — the full explanation.
• Market capitalisation and circulating supply. Every source that carries these restricts their display — CoinGecko's free tier is non-commercial, and the paid feeds are a purchase decision rather than an engineering one. So they are absent rather than quietly borrowed, and the coin pages are ordered by measured traded volume rather than by a market cap this site cannot cite.
• Binance and Bybit spot. Both are unreachable from this site's servers. Their funding rates appear because Hyperliquid publishes them in its own predicted-funding feed; their order books do not.
• OKX. Not called at all. There is no OKX request anywhere in this codebase and nothing here is derived from it, directly or as a cross-check — that half is checkable and is the part that matters. It was ruled out on a reading of its API Agreement recorded in July 2026; that reading is uncited and unverified, so it is given as our reason for a decision rather than as a statement about what OKX's terms say.
• Predicted or forecast rates. Only the venues' own published next-interval rates appear; nothing here is a model output.

Where to go next