IN DEVELOPMENT
The data behind these dashboards, as an API.
Entropy builds and operates the dashboards listed on this site. Behind each one is a set of maintained datasets: chain economics, blockspace, onchain liquidity, tokenized equities, perpetuals markets, treasury flows. The charts are one view of them.
We are building an API so the same data can be read programmatically, by people who want to work with the numbers rather than look at them.
It is not open yet, and this page is not a specification. It describes what the data covers, and how to ask for access.
What the data covers
Everything below is published on a dashboard today, on Robinhood Chain or Variational. More dashboards mean more datasets.
- Chain economics
- Fee revenue and gross profit margin, the cost of settling to Ethereum broken down by component, and annualized revenue run-rates.
- Blockspace
- Transactions, active addresses, contract creations, throughput, transaction failure rates, average and median gas fees, and which contracts consume the block.
- Liquidity and spot markets
- Protocol TVL and its split by protocol type, stablecoin market cap, canonical bridge balances and flows, AMM liquidity, DEX volume by venue, and launchpad token deployments.
- Tokenized equities
- Total tokenized value and its split by asset type, daily mint and burn volume, holders, and DEX volume — in aggregate and per ticker.
- Lending markets
- Total market size and TVL by vault.
- Perpetuals
- Volume, open interest, long/short skew, annualized funding rates, OI turnover, and quoted spreads at size, per market and across the venue.
- Treasury
- Balances and cumulative flow over time.
What you could build with it
Research and analysis: pull a series into a notebook or a spreadsheet, extend it further back than a chart shows, or join it against data of your own.
Product: back a feature, an internal dashboard, or a monitor with figures that agree with what we publish, instead of reimplementing the pipeline that produces them.
Writing and reporting: quote a number in a post, a report, or a governance thread and have it match the dashboard it came from, including the day it was computed.
Engineering: alerting on a threshold, a bot that reacts to a change, a model that takes one of these series as an input.
If your use is not on that list, it is still worth telling us. What gets exposed first will follow from what people say they need.
What we have not decided
The shape of it is open: which datasets go out first, how a series is addressed, what a response looks like, and what an access grant covers. We would rather decide that with a few real uses in front of us than publish a specification and discover afterwards that it fits nobody.
So there are no endpoints, formats, or dates on this page. When there are, they will be documented rather than announced here.
Access, and why it works this way
The data is not free to take. What is on these dashboards is compiled, derived, and maintained work, and our terms reserve it: retrieving it systematically, or republishing it, needs our permission, and programmatic access runs through an API we provide rather than around it.
The API is how that permission is given. Getting access and being allowed to use the data are the same conversation, which is the point of having one — nobody has to guess where the line is.
Quoting an individual figure or chart in non-commercial research, commentary, journalism, or governance discussion does not need any of this, as long as it is attributed to Entropy Advisors and not presented misleadingly. The full terms cover the rest.