Catalog
Tokens
Metadata, market data, prices, holders, security info, creation events.
Trades
DEX swaps normalized across chains — price, size, maker/taker, router.
Wallets
Balances, PnL, net-worth curves, transfer history, first-tx timing.
DEX Pools
Pool state, reserves, fee tiers, liquidity snapshots over time.
Rankings
Curated lists — hot, new, migrated, final-stretch, stock-like tokens.
Candles (OHLC)
Multi-interval OHLC for token, pair and pool addresses.
Holders
Top holders, distribution, concentration and change over time.
Smart Money
Curated wallet cohorts with labels, win-rate and flow aggregates.
Blockchain Core
Raw blocks, transactions, gas metrics and chain-level state.
Data Freshness & SLA
Latency, refresh intervals and backfill behaviour per dataset.
How data products are organized
Every dataset is described the same way, so you can assess fit quickly:Definition
What is in the dataset, in plain English — with the canonical schema.
Coverage
Which chains the dataset is available on, and any per-chain caveats.
Freshness
Real-time tick, near-real-time (seconds), or snapshot (minutes/hours).
Access
Which interfaces expose it — REST, GraphQL, WebSocket, Kafka, SDK, CLI, MCP.
Volume & rate
Expected throughput per chain — useful for sizing consumers.
Billing
Which plan tier and unit cost applies when you call it.
Relationship between products
Most products cross-reference each other by the same canonical IDs:- A
tokenAddressin Tokens is the same one used in Trades, Candles, Holders and Pools. - A
walletAddressin Wallets flows through Trades, Transfers and Smart Money. - A
poolAddressin DEX Pools is the source of its own Candles and Trades slice.
Pick your entry point
I know the entity I want
Jump into Tokens / Trades / Wallets / Pools directly.
I know the pattern I want
Pick the right access method — REST / GraphQL / WebSocket / Kafka.
I want to learn before I build
Follow a tutorial that touches several products end-to-end.
I want raw facts
Go straight to the API Reference.

