- Pairs (Trading, DWM) — per-minute candlestick / K-line data (OHLC, volume, trade count)
- Tokens (Trading, DWM) — per-minute trade statistics with buy/sell breakdown and unique traders
- TokenSupplyUpdates (Solana / EVM, DWD) — mint/burn events with supply, price, market cap, and FDV fields
- Token metadata — there is no separate TokenSearch cube; use Token (and related) dimensions on Pairs / Tokens, or other cubes such as DEXPools, TokenHolders, and DEXTradeByTokens for discovery and screening
Trading has no
network argument. Filter by chain with where: { Market: { Network: { is: "sol" } } } (or eth, bsc, polygon). Solana and EVM groups use their usual wrappers (Solana { ... }, EVM(network: eth) { ... }).How do I get K-line (OHLC) candlestick data?
Fetch candlestick data for a token — open, high, low, close prices per minute, plus USD volume and trade count. Use the Pairs cube inside Trading.Key fields
Key fields
| Field | Description |
|---|---|
Interval.Time.Start | Minute-bucket start (same as candle time) |
Token.Address | Token address |
Market.Network | Chain identifier (sol, eth, bsc, …) |
Price.Ohlc.Open | Opening price for the interval |
Price.Ohlc.High | Highest price during the interval |
Price.Ohlc.Low | Lowest price during the interval |
Price.Ohlc.Close | Closing price for the interval |
Volume.Usd | Total USD volume in this interval |
Stats.TradeCount | Number of trades in this interval |
Customization tips
Customization tips
- Longer timeframes: Request more rows with
limit, or aggregate client-side; candles are stored at minute granularity - Volume filter: e.g.
where: { Volume: { Usd: { gt: 100 } }, Market: { Network: { is: "sol" } } }to skip low-volume intervals - Time range: e.g.
where: { Block: { Time: { since: "2026-03-27T00:00:00Z" } }, Market: { Network: { is: "sol" } } }
The Pairs cube is a DWM (aggregated) model — data is pre-computed per minute. It is much faster than scanning raw trades for chart data.
How do I get trade statistics for a token?
Get per-minute trade statistics with buy/sell counts, unique buyer/seller counts, and volume. Use the Tokens cube inside Trading.Key fields
Key fields
| Field | Description |
|---|---|
Interval.Time.Start | Minute-bucket start (same as candle time) |
Stats.TradeCount | Total trades in this interval |
Stats.BuyCount | Buy-side trades |
Stats.SellCount | Sell-side trades |
Volume.Usd | Total USD volume |
Stats.UniqueBuyers | Distinct buyer wallets |
Stats.UniqueSellers | Distinct seller wallets |
Customization tips
Customization tips
- Buy/sell pressure: Compare
Stats.BuyCountvsStats.SellCount - Unique traders:
Stats.UniqueBuyersandStats.UniqueSellersshow whether volume is broad or concentrated - Activity heatmap: Query a full day (
count: 1440) and chart byInterval.Time.Start(orBlock.Time) - Buy/sell volume: The Tokens record also exposes
Volume.BuyVolumeUSDandVolume.SellVolumeUSDwhen you need USD split
How do I get market cap, price, and supply over time?
The legacy TokenMarketCap summary cube is not used in the current schema. Use TokenSupplyUpdates (Solana or EVM): each row reflects a supply-affecting event with TokenSupplyUpdate metrics including price, market cap, FDV, and total supply.Solana
EVM (Ethereum example)
Key fields
Key fields
| Field | Description |
|---|---|
Block.Time | Event time |
TokenSupplyUpdate.Currency.* | Token identity (mint/contract, decimals, symbol, name) |
TokenSupplyUpdate.PriceInUSD | Price in USD at this update |
TokenSupplyUpdate.MarketCapInUSD | Market capitalization |
TokenSupplyUpdate.TotalSupply | Total supply |
TokenSupplyUpdate.FDVInUSD | Fully diluted valuation |
TokenSupplyUpdate.PostBalance | Supply-related balance after the event |
Customization tips
Customization tips
- Latest snapshot:
limit: { count: 1 }withorderBy: { descending: Block_Time } - Compare chains: Run the same shape under
SolanaandEVM(network: bsc)(or other supported networks) - More context: See also Pools & Liquidity for supply and pool-related examples
TokenSupplyUpdates is DWD (event-level). It is the right place for historical valuation and supply changes tied to mint/burn activity, rather than a single static “market cap” summary row.
Where is token search / metadata?
The TokenSearch cube is not part of the current API. For token context:- Pairs and Tokens expose Token dimensions (e.g. Token.Address) alongside OHLC and stats — use them when you already know the address and want aggregated trading data.
- For richer metadata, holder counts, pools, or discovery, use cubes such as DEXPools, TokenHolders, or DEXTradeByTokens under Solana or EVM, depending on your chain.
Multi-Chain Examples
- Solana (Trading)
- Ethereum (Trading)
- BSC (Trading)
Next Steps
DEX Trades
Query DEX trading data — token trades, wallet activity, and top traders.
Transfers
Track on-chain token transfers between wallets.
Balances & Holders
Look up wallet balances, balance history, and top holders.
Pools & Liquidity
Explore DEX pool and liquidity data.

