onchain data bank

what you may do with this data, and what you may not

Terms of use

onchain data bank · this edition: 17 August 2026

These terms cover onchainbank.com, app.onchainbank.com and the MCP endpoint. They are written plainly and they are short, because the product is measurement and the rules around it are few.

The short version

What you may and may not do

you mayyou may not
Read every public page, without an account Crawl the pages or the API in bulk instead of reading the published files and the endpoint we gave you
Use the data in internal research, analytics and decision-support systems of your own, including commercial ones Republish the market state, whole or in bulk, as a data feed of your own, or resell access to it
Quote a figure or a whole section with attribution Present the data as your own measurement, or strip the provenance that qualifies it – the as_of, the revision and the completeness
Connect an agent over MCP with a token issued to you, and let it answer your questions from the state Share that token, or use it on behalf of somebody who was not issued one
Cache what you received for as long as your work needs it Train or fine-tune a machine-learning model on it. The same answer stands in robots.txt – search yes, retrieval yes, training no

Crawling is not the same as collecting. Search indexing and retrieval crawling in accordance with our robots.txt are permitted, and the signal there says so in three words – index us, quote us, do not train on us. What is not permitted is automated collection intended to reconstruct or republish the dataset.

What the words mean

Four of them decide most questions, so they are defined rather than left to taste.

wordwhat it means here
Bulk Taking the published surface wholesale rather than reading it – systematic crawling of the pages, or repeated calls whose purpose is to accumulate a copy of the data rather than to answer a question of yours
Feed Any onward publication of the market state, whole or in part, on a schedule or on demand, to somebody other than yourself – an API, a file drop, a channel, a webhook, a mirror
Resale Charging anyone for access to the data as such, whether directly or as an item inside another price
Derived analytics What you compute FROM the data – a score, a signal, a chart, a conclusion in a report. Derived analytics are yours, and publishing them is allowed, as long as the underlying state is not recoverable from what you publish

Attribution

Where a figure of ours appears in something published, name the source and the minute it describes:

onchain data bank, ETH market state as of 2026-08-17T09:38Z

The minute is not decoration. Every state carries a fixed as_of and a revision, and a number quoted without them cannot be checked against anything – see how revisions work and how far back each series goes.

Tokens

Access over MCP needs a token, and tokens are issued by hand to a named holder. Using a token is acceptance of these terms. A token is yours alone – it is not transferable, and the holder answers for what is done with it.

We may suspend or revoke a token where these terms are broken, where the load threatens the service for everybody else, or where we are required to. You may ask for your own token to be revoked at any time, and it stops working the moment we do it.

Liability and what we do not promise

The data is provided as it is measured. To the extent the law allows, we are not liable for indirect or consequential loss, for lost profit, or for any trading or investment decision taken with this data or against it - the decision is yours and so is its outcome. Where liability cannot be excluded, it is limited to the amount you have paid us for the service in the twelve months before the claim.

An agreement of your own comes first

These are the public terms. Where an institutional customer holds a signed agreement with us, that agreement governs, and these terms fill only the gaps it leaves.

Governing law

These terms are governed by the laws of the Cayman Islands, and the courts of the Cayman Islands have jurisdiction over disputes arising from them.

Who publishes this

onchain data bank is the publisher of these pages and of the data behind them. A corporate entity is not named here at the date of this edition, and this page will name one on the day there is one to name.

Questions about these terms, about a use they do not cover, or about access for a team – write to [email protected].

Changes

The date at the top is the edition, and a change takes effect when it is published here. Where a change materially narrows what a token holder may do, we write to the address the token was issued to before it takes effect, and continued use after that is acceptance. Nothing published here applies backwards to work already done under an earlier edition.