Data model
Every method returns an array of data objects that share a few consistent conventions.
A data point
{
"id": 1024,
"base": "DezXAZ8z7PnrnRJjz3wXBoRgixCa6xjnB7YaB1pPB263",
"quote": "So11111111111111111111111111111111111111112",
"timestamp": "2026-06-01T02:16:22.000000000Z",
"window_duration": "PT1M",
"open": "0.00001901",
"close": "0.00001942",
"base_volume": "48210.7531",
"data_points": "37"
}A data point is one element of a response's
result. Every response - query or stream - is itself a JSON array with one entry per request.Conventions
- Types are ReifyDB value types. Each Fields table lists a column's ReifyDB type -
Utf8,Uint8,Float8,DateTime,Duration,Boolean. The points below cover how each renders in JSON. - Numbers are strings. Prices, amounts, and counts come back as decimal strings to preserve full token precision - parse them with a big-decimal library, not
Number. - Timestamps are ISO-8601. Fields like
timestamp,window_start, andwindow_endare UTC strings with nanosecond precision, ending inZ. - Booleans stay native.
is_buyand the volume-profile flags are real JSON booleans. - Every data point has an id. A stable numeric
id. When streaming, matchupdatesanddeletesto data you already hold byid. - USD fields are derived.
*_usdvalues come from anchor-token pricing; see Sources.
