Data

Data categories

Nine categories, one asset identity. Every page below states what the data is, where it conceptually comes from, how often it changes, which fields exist and where it stops being reliable.

How to read the coverage figures

Coverage is not uniform across categories, and we do not present it as if it were. Market, social and sentiment cover a broad hourly snapshot of 1,000 assets. Ecosystem and developer activity are daily series for a curated set of 69 assets. News and narratives are market-wide rather than per-asset. All figures on this site were measured on 2026-08-31.

The path a value takes

Nothing reaches an application straight from a provider. Each value passes through identity resolution, unit and schema normalization, validation, and then storage as an immutable observation with the timestamp it belongs to. That is what makes two different categories comparable on the same asset at the same hour.

Provider payload
provider idsprovider field namesprovider unitsprovider cadence
Resolution
match to canonical assetcreate asset if unseenattach provider id
Normalization
field mappingnumeric typesUTC timestampssnapshot alignment
Validation
required fieldsrange checksnullabilityreject or flag
Storage
immutable observationasset + observedAtappend only

Each stage is documented in infrastructure.