Docs
    Guide · Preview

    Perp Exchanges

    Hyperliquid markets, OHLCV at multiple resolutions, open interest, funding, and per-account activity — query everything you need to analyze a venue without standing up your own indexer.

    What you get

    • Market metadata (asset, contract, leverage, fees, status)
    • OHLCV candles per market across multiple resolutions
    • Open-interest time-series
    • Funding-rate history
    • Per-account positions and trade activity
    • Venue-level aggregates (volume, OI, fees)

    Coverage is currently Hyperliquid. More venues are tracked under support@pinax.network — let us know which perp DEX you need next.

    Use cases

    Market microstructure

    OHLCV at multiple resolutions plus funding-rate history lets you reconstruct the carry side of each market, model basis between perps and spot, and benchmark execution venues.

    Open-interest tracking

    Watch /markets/open-interest across the venue to detect coordinated positioning, unwinds, and squeeze setups before they show up in price.

    Account activity feeds

    Per-account trade and position feeds make it easy to follow whales, attribute PnL, or run compliance-style scans for related-party flow.

    AI-assisted research

    Wire the endpoints into a Custom GPT or MCP client — see the Custom GPT guide — to summarize funding regimes, surface unusual OI moves, or draft trade theses from market data.

    Frequently asked

    Why is this marked Preview?
    The endpoint surface is still settling — shapes can change without a deprecation period. Pin to a JWT and the canonical endpoint catalog before relying on it in production.
    Which perp venues are supported?
    Hyperliquid is live. Additional venues are added based on demand — request one via support.
    How fresh is the data?
    Up to the latest finalized state on the underlying chain. Sub-second latency requires Firehose / Substreams, not the REST endpoints.
    Can I get funding-rate predictions?
    No — only realized funding history. Predictions are venue-specific and outside the scope of an indexed-data API.
    Authentication and quotas?
    Same as the rest of the Token API — Bearer JWT in Authorization, shared quota across products. Check /usage for current spend.

    Related