| note | No | One line saying what the numbers cover, or why there are none. Read it before reporting any zero as a market reading. | |
| count | No | How many rows this reply carries. | |
| capped | No | Present only when an argument was cut down to a ceiling. Absent means nothing was clamped, so a smaller number than you asked for is the data and not a limit. | |
| window | No | The period the returned rows actually span: from, to and hours. | |
| matched | No | How many rows matched the chain filter before the row cap. | |
| available | No | False when this lane could not answer: a producer is dark, the pair sits outside this plan, or the argument named something we do not carry. Absent or true means the numbers are a real reading, not a guess. | |
| total_usd | No | Dollars across exactly the rows returned. A page sum, not a fixed 24h total: the window field says what period those rows span. | |
| truncated | No | True when more rows matched than were returned, so what you have is a page and not the whole set. | |
| access_note | No | What this connection could not return and what lifts it. Always pass this on to the user: it is the only place that information appears. | |
| liquidations | No | The events, each naming BOTH wallets: the one liquidated and the one that repaid the debt and took the collateral. | |
| unknown_chain | No | Set when a chain was named that this lane does not index. Nothing was searched, so this is not no liquidations there. | |
| chains_covered | No | The chains this lane indexes. | |
| protocols_covered | No | The lending protocols behind these rows. | |
| duplicates_dropped | No | How many repeat rows for the same event were removed before counting, so the dollars are not doubled. | |