Build
JSON API
Public read endpoints for launches, the feed, XP and the leaderboard.
Everything on the site is also available as JSON. There is no API key. Poll modestly and back off on errors: responses come from an index and are not a guarantee of the latest chain state.
Launches
| Endpoint | Returns |
|---|---|
GET /api/launch/list | Launches. Query: chain, sort (live, new, mcap, volume, gainers, holders), window (1h, 24h, all), limit, offset. |
GET /api/launch/feed | The latest launches and trades. |
GET /api/launch/meta/<token> | A token's image, description and links. |
POST /api/launch/meta | Register metadata before launching: {chain, launcher, salt, name, symbol, description?, image_url?, website?, x_handle?}. Returns {uri, token}. |
POST /api/launch/sync | Index a transaction you just sent. |
GET /api/health | Indexer status. |
XP and profiles
| Endpoint | Returns |
|---|---|
GET /api/xp/leaderboard | Rankings. Query: period (daily, weekly, monthly, all), sort (xp, trades, volume, launches, fees), limit, offset, wallet. |
GET /api/xp/tasks | The active XP tasks. |
GET /api/xp/me?wallet=0x... | A wallet's XP, level, streak, tasks and badges. |
GET /api/profile?wallet=0x... | A wallet's username and claimed badges. |
Reading the data
- Raw token and quote amounts are decimal integer strings. Use
quote_decimalsfor quote amounts, not a blanket 18. price_quoteandfdv_quoteare numbers in the token's quote asset.- Writes that cost XP or change a profile are wallet-signed messages, not API keys.
A machine-readable summary is at /llms.txt.