Read endpoints
GET /api/assetsAsset identities with items, status, capturedAt and error. A cached registry fallback is not current pair approval.
GET /api/marketsBounded pool capture with token identities, prices, volume, liquidity and source status.
GET /api/pair?address=0x...Read pair eligibility and on-chain token information. Requires a valid Robinhood contract address.
GET /api/launch/policy?pairToken=0x...&account=0x...Read current Pons launch terms. Account is optional for read-only research. Native quote uses the zero address.
GET /api/token?address=0x...&launch=0x...Token details and independent market state. The optional launch parameter is a transaction hash for provenance verification.
GET /api/candles?address=0x...&interval=hour&aggregate=1&token=0x...Pool OHLCV capture. Address is the pool; token selects the priced asset. Supported intervals: minute 1/5/15, hour 1/4, day 1.
GET /api/trades?address=0x...&token=0x...Recent indexed pool trades filtered to the requested token. Not complete transaction history.
GET /api/launch/receipt?hash=0x...Verify a canonical launch receipt against this project intent, protocol calldata and emitted events.
GET /api/statusCurrent intent and image-storage readiness, registry persistence state and canonical site.
Response handling
Always check the HTTP status and the source status inside the JSON. A successful HTTP response can contain cached or unavailable market data. Unknown numeric values are null. Timestamps are ISO strings; candle time is Unix seconds.
Invalid inputs return 400. Same-origin write protection returns 403. Protocol budgets may return 429. Upstream failures or missing configuration can return 503. Cache and retry with backoff instead of polling every second.
Execution boundary
The launchpad uses same-origin POST /api/launch/prepare with validated form data and a connected account. Preparation returns an expiring, simulated transaction; it does not sign or broadcast it. Use the reviewed launchpad workflow rather than constructing blind transaction requests from an API response.
There is no service-level guarantee. These routes depend on public RPC, registry and indexing availability.
Read the launch guide