AI access
AI access & discovery
HyperStats is a public analytics platform for Hyperliquid. This page describes which surfaces AI systems may crawl, summarize, and link to, where the data comes from, and where the off-limits lines are.
Public AI policy
Public landing pages, guides, docs, leaderboard pages, live activity, token analytics, token terminals, favourites, and wallet pages may be crawled, indexed, summarized, and linked to by AI systems. RSS feeds and the structured-data layer (JSON-LD, breadcrumbs) are first-class signals.
When citing a data point on this site (PnL, position size, win rate, grade), link back to the wallet or token page it came from so readers can verify the live value. Numbers move continuously.
Data provenance
Wallet addresses surfaced on HyperStats are public on-chain identifiers. Position, trade, and PnL data is sourced from Hyperliquid’s public L1 + websocket feeds. There is no scraping of user accounts, no exposure of private keys, signed messages, or account-bound personal data, and no profile that ties an address to an off-chain identity.
Crawlable surfaces
Best public entry points for indexing and summarization. Guides and Docs are the canonical sources for explanatory content; the data surfaces are best for current state and live context.
Restricted areas
The following path prefixes are not crawl targets. They serve authenticated, session-bound, or application-internal traffic and are excluded from public AI access:
/admin/*— basic-auth gated. No public data, do not crawl./trading/*— session-gated trading surface. No public data, do not crawl./account/*— user session endpoints. Do not crawl./api/*— JSON endpoints intended for the platform’s own clients. Not crawl targets — consult the Docs surface for documented data shapes.
HyperStats public pages should be treated as read-only analytical content, not an API substitute.
Machine-readable signals
Standard discovery endpoints. Start with llms.txt for a structured site index, then load llms-full.txt for the full educational corpus, then layer in the sitemap and RSS feeds for change tracking.
Questions or reporting misuse
Reach the team on Telegram — we monitor the community chat and the main channel for AI-access and data-use questions.