> ## Documentation Index > Fetch the complete documentation index at: https://docs.chainstream.io/llms.txt > Use this file to discover all available pages before exploring further. # Data Products > Every dataset ChainStream publishes — what it contains, how fresh it is, and how to access it. ChainStream is organized as a catalog of **data products**. Each product is a normalized, multi-chain dataset with a defined shape, refresh cadence and delivery surface. Pick a product below to see its fields, coverage, SLAs and which access method fits best. ## Catalog Metadata, market data, prices, holders, security info, creation events. DEX swaps normalized across chains — price, size, maker/taker, router. Balances, PnL, net-worth curves, transfer history, first-tx timing. Pool state, reserves, fee tiers, liquidity snapshots over time. Curated lists — hot, new, migrated, final-stretch, stock-like tokens. Multi-interval OHLC for token, pair and pool addresses. Top holders, distribution, concentration and change over time. Curated wallet cohorts with labels, win-rate and flow aggregates. Raw blocks, transactions, gas metrics and chain-level state. 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: What is in the dataset, in plain English — with the canonical schema. Which chains the dataset is available on, and any per-chain caveats. Real-time tick, near-real-time (seconds), or snapshot (minutes/hours). Which interfaces expose it — REST, GraphQL, WebSocket, Kafka, SDK, CLI, MCP. Expected throughput per chain — useful for sizing consumers. 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 `tokenAddress` in **Tokens** is the same one used in **Trades**, **Candles**, **Holders** and **Pools**. * A `walletAddress` in **Wallets** flows through **Trades**, **Transfers** and **Smart Money**. * A `poolAddress` in **DEX Pools** is the source of its own **Candles** and **Trades** slice. This lets you join across products without reconciling IDs by hand. ## Pick your entry point Jump into Tokens / Trades / Wallets / Pools directly. Pick the right access method — REST / GraphQL / WebSocket / Kafka. Follow a tutorial that touches several products end-to-end. Go straight to the API Reference.