Liquidity adds and removes

Liquidity added to and removed from the token's busiest V2 / V3-style pools of the day (up to 8), newest first, read live from the chain's Mint and Burn logs: no LP indexer runs for these chains. A V4 pool's log carries no amounts, so V4 pools are not read, nor pools paired with no reference asset of the chain; poolsLeftOut counts the day's pools not read (past the 8 busiest, V4, or with no reference asset). The reads stop at 300 events or one day: on a token whose pools churn (just-in-time liquidity bots on majors) the list is the newest events, since says how far back it reaches and summary is null; summary holds the day's figures only when the reads covered the whole day. wallet is the transaction's sender (the pool's own owner field is the position manager). Cached 60 seconds per token.

Chain-keyed data for Avalanche C-Chain, Base and BNB Chain, served from Chord's rollup tables for the chain (every swap summed by hour, token and venue). Only the trade tape, the prints ticker and the wallet read raw rows, scoped to one token or one wallet and bounded.

• Access. No key needed while the chain is public (all three are today). A chain whose tape is off, or that is not public yet, answers 400 UNSUPPORTED_CHAIN ("chain N is not served yet") unless the request carries an X-API-Key; those answers are sent Cache-Control: private.
• Ingest floor. Every count, volume and print covers trades at or above the chain's floor, returned as ingestFloor. BNB Chain runs at $100 today; Avalanche and Base at 0.
• Readiness. 503 NOT_READY until the chain's rollup has run on this deployment; 503 CHAIN_DATA_UNAVAILABLE when the store cannot be read. Never treat either as "no trades".