Ordinals and Runes data terms: using our data

Using our data

0.9.53

What you may quote and cite from this dashboard, how to attribute it, what isn't allowed, and what is and isn't ours to share.

The short version

Quote it, cite it, link to it. Please don't copy it wholesale or resell it.

Most of what the dashboard shows is worked out from the Bitcoin blockchain by our own node: sales and their prices, mints, blocks and the mempool, holdings, wash-trade flags, which venue a trade went through, the Runes index, rune prices and Greeks, fee times and pool filtering. Each has a methodology page that says exactly how.

Some figures come from other services under their own terms, such as the BTC/USD price. Those are shown with their source named, and they are not covered by these terms: ask the source. The table at the end of this page lists every source and which is which.

You may

Quote any figure, chart or finding in an article, report, post, research note or answer, including AI-generated answers.
Link to any page, and to a specific rune or collection page.
Use screenshots with the dashboard visible as the source.

Please attribute it as "Atrium XBT" with a link to the page you took it from. The date matters too: these numbers change with every block.

Please don't

Copy the data in bulk, mirror the site, or republish it as a feed or dataset of your own.
Resell it, or put it behind a paywall of your own.
Scrape the internal /api/ endpoints. They exist for the dashboard's own pages, change without notice, and are not a public interface. A documented, stable data API is planned.

No warranty

Everything here is provided as is, without any promise that it is complete, current or correct. It is not financial advice. See the terms.

Questions

Use the feedback form on the about page.

These terms are a plain-language draft and may change after legal review.

Where each figure comes from

Source	What it supplies here	Covered by these terms?
Our Bitcoin node and ord index	Blocks, the mempool, fees, sales, mints, rune and inscription data, holdings of any address a visitor looks up, venue attribution, wash-trade flags, Greeks, the BTC/USD price (estimated from the round-dollar payments in our node's blocks, since 2026-10-13) and every other figure we compute from them.	Yes, under these terms
ordinals.com (inscription content)	Inscription content, as a fallback when our own ord index hasn't reached it.	Yes, under these terms
Wizards of Ord collection registry	Collection names, membership and curator flags.	Yes: it's public domain (CC0)
Magic Eden archive (via Wizards of Ord)	Names and membership of former Magic Eden collections. Descriptions stay off the public pages.	No: ask the source
Bitcoin Magazine and CoinDesk RSS	Headline, publisher, time and a link to the article. Never article text.	No: ask the source
RichSwap (Omnity REE)	Rune AMM pool prices and depth from its public ticker list.	No: ask the source
European Central Bank reference rates (via Frankfurter)	One number a day: US dollars to Chinese yuan, for showing prices in CNY.	No: ask the source
OFAC SDN Bitcoin-address list (via 0xB10C's extraction)	Nothing public: the membership test result (address screened, hit or not) is logged internally for compliance review only -- never shown on any page, public or private.	No: ask the source
A BRC-20 ledger indexer (OPI, the community reference implementation, or a vendor's)	Nothing public: whether a transfer inscription paying an ORDI invoice was actually valid (did the sender have the balance when it was inscribed) is used only to decide whether to credit an ORDI payment -- never shown on any page, public or private.	No: ask the source
Public EVM JSON-RPC endpoints (Ethereum/Base/Arbitrum/Optimism)	Whether a payment arrived at an EVM invoice address, and the confirmed block and transaction data needed to credit it -- used only to decide whether to credit that payment, never displayed as general chain data the way our Bitcoin node's data is.	No: ask the source

Last updated 2026-10-10