Candles (data API)

OHLCV for any token Chord indexes on Arc, Robinhood Chain, Avalanche, Base, BNB Chain, Arbitrum, Ethereum or Monad, built only from Chord's own index — never a third-party feed, so source is always index. 1m / 5m / 15m come from a 1-minute rollup that keeps history after raw trades are retired; 1h and above from the hourly rollup; the newest minutes straight from the tape. Each candle carries n, the trades in the bucket. Buckets without a trade are absent unless fill=1, which carries the previous close through them.

Paging: the default window ends with the still-open bucket (forming: true) and holds limit buckets. A from–to range wider than limit keeps the newest buckets; ask for the previous page with to = this page's from. The token must trade on the chain you name — 404 UNKNOWN_TOKEN says which chain it trades on when it is another one. The zero address stands for the chain's native asset (its wrapped twin, or the USDC predeploy on Arc). For live candles subscribe on /v1/ws/live (see Streaming).

Avalanche, Base, BNB Chain (43114, 8453, 56): candles come from chain-keyed tables, so one address on two chains is two tokens, and 404 UNKNOWN_TOKEN means no indexed trades on the chain you named. These chains answer once their tape runs and, until the chain is public, only to requests with an X-API-Key (400 UNSUPPORTED_CHAIN otherwise; all three are public today). Where the tape runs with an ingest floor (BNB Chain, $100 today) the response carries ingestFloor, and v and n count only trades at or above it.