Developers > API reference
API reference
Everything the app shows comes from these JSON endpoints, served by the same process that indexes the chain. No key needed.
| Endpoint | Returns |
|---|---|
GET /api/config | Chain, contract addresses, live launcher settings, relay status, HYPE price |
GET /api/stats | Tokens launched, swaps rejected in launch blocks, volume, indexer head |
GET /api/tokens?tab=&sort=&mc=&vol=&age=&liq=&q=&limit=&offset= | Token list with the Discover filters |
GET /api/tokens/:address | Token detail: pool, supply split, protection, developer |
GET /api/tokens/:address/trades?side=&limit=&before= | Trades, newest first |
GET /api/tokens/:address/holders | Holders with tags |
GET /api/tokens/:address/traders | Top traders by PnL |
GET /api/tokens/:address/candles?tf=1m|5m|15m|1h|1d | OHLCV in HYPE per coin |
GET /api/tokens/:address/comments · POST | Comments; posting needs a signed message |
GET /api/feed | Server-sent events: feed, trade, token, head. ?history=1 for the last rows |
GET /api/leaderboard?board=&period=&page= | Traders, creators, tokens |
GET /api/profile/:address · POST /api/profile | Profile with created tokens, holdings and activity; update with a signed message |
GET /api/portfolio/:address | Positions, PnL, history |
GET /api/search?q= | Tokens and creators |
GET /api/verify?q= | Launch verification |
POST /api/upload | Image upload (multipart "file", ≤1 MB) → URL for token metadata |
Signed actions
Comments, profile edits and follows prove the wallet with an EIP-191 signature over:
Bedrock · <action> <JSON payload> at <unix seconds>
Payloads: comment { token, text }, profile { name, bio, visor, x }, follow { target, follow }. Signatures older than ten minutes are refused.