femtos

HyperEVM data API

HyperEVM data API: the Hyperliquid EVM chain: DEX pools, swaps, tokens, holders, NFTs, LiquidLaunch launches. 31 REST calls and WebSocket channels, each with its latency measured live.

Base URL https://api.femtos.xyz/v1, key in Authorization: Bearer. Markdown: HyperEVM endpoints as Markdown.

Endpoints

Launches

  • Launch story
    One LiquidLaunch launch on HyperEVM told event by event from the Femtos API: launch, dev wallet, early buyers, swaps, holders, market cap over time.
  • LiquidLaunch launches GET /v1/launches
    Latest LiquidLaunch bonding-curve launches, newest first.
  • Launches stream WS hyperevm.launches
    One message per new LiquidLaunch launch, the moment its block is indexed.
  • Launch detail & signals GET /v1/launches/{token}
    Metrics, dev wallet, early buyers and risk signals of one launch.
  • Launch timeline GET /v1/launches/{token}/timeline
    The whole life of a launch as ordered events with running state.

Market data

  • Markets GET /v1/markets
    Active HyperEVM pools with 24 h stats.
  • Candles GET /v1/candles
    OHLCV of one pool in pair price, USD and market cap, ascending, UTC-aligned.
  • Forming candle WS hyperevm.candles
    The forming candle, pushed once per block where it changes.
  • Trades GET /v1/trades
    Latest swaps of one pool, newest first.
  • Trades stream WS hyperevm.trades
    The swaps of one pool, one message per block that has some.

Holders & tokens

  • Holders GET /v1/holders
    Current balances of an ERC-20, largest first, with concentration.
  • Token registry GET /v1/coins
    HyperEVM tokens with their HyperCore spot link and price.
  • Coin detail GET /v1/coins/{layer}/{id}
    One token: its links across layers, the markets it trades on, its 5 largest holders.
  • Daily token volume GET /v1/volume
    USD swap volume of a token per UTC day, both sides of every priced swap.
  • Token families GET /v1/token-families
    Tokens whose balance moves without Transfer logs: Aave aTokens and debt tokens, stHYPE, xStocks.
  • Family token holders GET /v1/token-families/{token}
    Holders of one family token with balanceOf at the indexed head.
  • Spam tokens GET /v1/tokens/spam
    Tokens the indexer flags as spam, left out of every list, and the latest flag changes.

NFTs

  • Active NFT collections GET /v1/nfts/collections
    Collections with the most transfers over the last 1 h or 24 h.
  • NFT collection GET /v1/nfts/collections/{address}
    Metadata, tokens seen and 24 h activity of one collection.
  • Collection tokens GET /v1/nfts/tokens
    Tokens of a collection by id, with their owner and metadata URI.
  • NFTs of a wallet GET /v1/nfts/owned
    ERC-721 tokens owned and ERC-1155 balances of one address.
  • NFT transfers GET /v1/nfts/transfers
    Transfers of a collection or one token, newest first. While HyperEVM syncs: the last 24 h or 7 d of indexed blocks.

Bridge & wallet

  • Bridge transfers GET /v1/bridges
    HyperCore ↔ HyperEVM transfers (core_evm) or HyperEVM ↔ Elysium movements (evm_elysium), with 24 h stats.
  • Bridge coverage GET /v1/bridges/coverage
    Every HyperCore ↔ HyperEVM leg since our data starts, paired with its other leg: matched share per direction and token, why the others are not, latency.
  • Bridge stream WS bridge.transfers
    Each HyperCore ↔ HyperEVM transfer, initiated then completed.
  • Cross-layer wallet GET /v1/wallet/{address}
    One address (or a named wallet's handle) on HyperCore, HyperEVM and Elysium, plus its latest events.

Named wallets

  • KOL leaderboard GET /v1/kols/leaderboard
    KOLs, traders and funds ranked by their HyperEVM swaps, transfers, bridge legs and holdings.
  • KOL moves GET /v1/kols/activity
    The latest HyperEVM swaps and transfers of the named wallets, with who moved.
  • KOL stream WS kol.activity
    Every HyperEVM swap, transfer and bridge leg of a named wallet, on each indexed block.

Reference

  • Freshness GET /v1/status
    Head and lag of each layer, measured now.
  • Check your key GET /v1/whoami
    Answers the name your key is registered under, its tier, billing state and the limits in force.
  • OpenAPI document GET /v1/openapi.json
    The OpenAPI 3.1 contract of every REST call, public.