One envelope
Every response is{ data, meta }. meta.asOf is a timestamp (ms): on wallet positions and closed positions it is the moment the holdings were read on-chain, on pulse and token holders the moment the list was computed, and on wallet equity history the moment the curve was computed (the age of the data, so a cached response is visible as such); elsewhere it is the server time of the response. A field that can’t be computed is null (never a fabricated value, see null means unknown); when data is momentarily unavailable the endpoint returns a 503 with Retry-After rather than partial data.
Chain ids
evm:<EIP-155 id> (the chain’s own chain id, e.g. evm:8453 for Base, evm:999 for HyperEVM) and solana (solana:solana is accepted on input; the prefix is case-insensitive). evm:645749, HyperEVM’s former id, is still accepted on input. Responses always echo the canonical id.
camelCase fields, ms timestamps
All fields are camelCase; every timestamp is unix milliseconds and ends inAt (candle time is unix seconds, TradingView-style). Trade timestamps carry the block time: EVM blocks are second-stamped, and Solana slots are stamped at second precision too, so a trade at is a whole second; the order of trades inside a second is exact (block/logIndex on EVM, slot order and the cursor on Solana), and the live stream carries a finer at on Solana. Timestamp parameters follow the same rule: milliseconds everywhere (fromAt, toAt, beforeAt, and from / to outside candles), seconds for the candle bounds endTime and from. A value in the other unit is rejected with 400 rather than interpreted.
null means unknown
Anull field means the source is unavailable or the value fails sanity checks (e.g. marketCapUsd > $1T). A 0 is always a measured zero.
Wallet labels
Trades, top traders, token holders, wallet positions and their stream channels carrylabels: the labels of the wallet behind the row, always in this order, only those that apply ([] when none).
On a trade, the labels describe the wallet at the time of the trade (
dev and kol as known now): a trade made before a label was tracked never carries it. On top traders, holders and positions, they describe the wallet now. On Solana, the token’s creator carries dev and none of the token’s other labels (sniper, bundler, whale, freshTrader, insider); on its trades, isSniper is false. A trade tape filtered by wallet (makers, maker) serves the wallets’ current labels.
/v1/wallet/labels serves the labels of a wallet as a whole, with no token: there freshTrader is judged on the wallet’s first funding across every chain, and sniper, bundler, whale and insider on its most recently traded tokens (see that page).
The trade tapes, the token holders, the top traders (among the top 1 000 traders) and the trades channel take a labels filter (comma-separated or a list, any of them matches). A filtered response says how it was matched: meta.labelBasis is trade (the labels of each trade) or current (the wallets’ labels now), and meta.labelCoverage gives, for each requested label tracked only since a given time, that time in unix milliseconds. In the current basis on Solana, that time is the launch date of the tokens that carry the label (whale since June 3, 2026, bundler since October 29, 2026, insider since October 2, 2026); freshTrader there is tracked token by token and has no single time. insider is a token holders and top traders filter on Solana only (400 on trades and on EVM chains); locker is not served: asking for it returns 400.
Strict validation
Unknown params or invalid enums return 400 with a machine-readableerror.code - never silently-empty data. A parameter we do not know answers UNKNOWN_PARAM and names it in the message; a known parameter with a bad value answers INVALID_PARAM.
Tokens and pools
Two scopes, named the same way everywhere. A token endpoint (/v1/token/*, the token-updates channel) covers the token across all its pools: token-wide trades and stats, and the token’s main market for its price and candles. A pool endpoint (/v1/pool/*, the pool-updates channel) covers one pool, that is one market: chain + pool address identify it, stable and never reused. Lists follow the same rule on the stream: pulse and screener give one row per token, pulse-pools and screener-pools one row per pool.
Identity fields
The rows in the table below say which token and which pool they describe, by two explicit names placed right afteraddress: tokenAddress (the token) and poolAddress (the pool). address stays, with the value it has always had: the token on a token row, the pool on a pool row. Read tokenAddress and poolAddress when you need to be sure: address is the token on /v1/pulse but the pool on /v1/screener.
On input, the same names work in place of
address: tokenAddress on every /v1/token/* endpoint, poolAddress on every /v1/pool/* endpoint, in the query and in each item of a batch (POST /v1/token/sparklines takes plain addresses in tokens[]). On the streams, tokenAddress is the other name of address and poolAddress the other name of pool on trades, ohlcv, token-updates and pool-updates, lists included. Send one of the two names: two different addresses are refused with INVALID_PARAM. In filters, tokenAddress and poolAddress are aliases of address and pool.address.
The main market
Every token has one main market, the same on every endpoint and stream: thepool (and poolAddress) of /v1/token, rank 1 of /v1/token/pools, the market shown by the Screener, Pulse and search rows, and the market behind the token’s price, price change, candles and sparklines. One rule picks it, the same on every chain:
- While the token trades on its launch curve, the curve is its main market.
- Otherwise it is the market where the token trades best: real depth close to the current price, real trading, a recent last trade, and a quote asset we trust. The longer a market goes without a trade, the less it counts; a nearly empty one, or one whose price is far from the token’s other markets, gives way to the others. A token with a single market is still priced from it, however small it is: check
liquidityUsdbefore relying on the price of a token whose market holds almost nothing. - Venues that trade from a market maker’s inventory (order books, proprietary AMMs) hold no pooled depth: they lead only when the token has no market with real depth.
- A native coin and its wrapped form use their main USD market.
Which figure covers what
Majors, stablecoins, wrapped natives and native coins keep figures that cover all their markets. On token stats, trades, candles and top traders,
pools= picks the markets yourself: the figures cover the pools you list, candles merge them, and the price change follows the main market when you list it, otherwise the first pool you list. A token row of the Screener or Pulse, on the REST API and on the streams, stands for the whole token: the token is listed as soon as one of its markets belongs to the list, and the row always shows its main market. A Pulse card’s top-level counters cover the market the card shows, as its page says. Search rows, built to find a token, show the liquidity and the 1h and 24h price change of their pool: the token’s main market, or the pool you searched when the query is a pool address. Their volumes, fees and counts cover every market of the token.
Native + USD
On-chain amounts are native-denominated (priceNative, liquidityNative as strings for precision); USD fields are computed from native prices. USD figures drawn from past trades (trade tapes, wallet trades and swaps, entry and exit prices, bought and sold totals, realized PnL) are valued at the native coin’s USD price at the time of each trade. usdBasis, on the responses that carry such figures, says how USD amounts were computed: trade = each trade valued at the native coin’s USD price at that trade’s minute; spot = native amounts converted at the current native price. Current values (a position’s amountUsd, currentPriceUsd, market cap, liquidity) use the current price. Amounts are GROSS on-chain (the exact swapped amounts). Price webhook levels are set in USD (priceUsd, judged on the current native coin price) or in the native coin (priceNative). Token quantities sent as strings (amount, boughtTokens, soldTokens, openTokens) are plain decimal strings, never in exponent notation (0.00000001, not 1e-8); a wallet’s amount is its exact on-chain balance at the token’s full precision. Quantities sent as JSON numbers, such as amountToken on trades, are standard JSON numbers.
Batch twins
Hot single-GET endpoints have a POST batch twin, most on the same path takingitems[] (token sparklines take tokens[]; the pool data, pool trades and pool sparklines batches still accept markets[], the former name of their items[]); the response array is in input order with per-item {error} slots. Only the items served are billed, an {error} slot never is: most batches bill one call of the endpoint per tranche of items (25 for token details, stats, price, metadata, sparklines, pool details, pool data, pool price, pool sparklines, wallet profile and funding, assets; 10 for security; 5 for wallet PnL, pool trades and candles), wallet positions, closed positions, wallet trades and swaps bill each wallet at the endpoint’s price, and a wallet batch counts the same address on several chains as one wallet (Batches). POST /v1/token/trades is not a batch: it is the trade tape of one token with a list of makers, billed as one call.
Solana included
Every REST endpoint and stream channel also serves Solana with the same shapes: chain=solana, base58 addresses (case-sensitive; the native-coin aliases0x0000…0000 and 0xeeee…eeee are read as the SOL mint), tx identity is the signature (carried in txHash). Displayed Solana volumes and counts are the full on-chain figures; organic twins (wash-filtered) are available as separate *Organic fields where provided. Solana trades aggregate multihop legs per transaction (effective VWAP); EVM tapes serve one row per swap event, so a swap routed through several pools of a token yields several rows sharing txHash. On token stats, token details, market data and token pools, txns counts distinct transactions on every chain.