onchain data bank

market data for AI agents

A decision-ready market state
for AI agents

A coherent, minute-by-minute view of ETH and BTC across spot, derivatives, options, on-chain, ETF and macro data – structured for agents that need to analyse the market, not reconstruct it.

We consolidate public exchange feeds and commercial data providers, including on-chain, ETF and macro data, into a single versioned snapshot per market, delivered over MCP. It captures the flows, positioning, leverage, volatility and event context shaping that market now – and how it stands against its neighbour.

Every snapshot carries its own reading contract: definitions, units, windows, baselines, freshness and completeness. Missing data stays explicit, aggregate quality remains visible, and stale snapshots are never served as current.

Consistent, auditable context for agentic research and decision support.

Ask your agent

This is the whole point of connecting: you ask about the market in your own words, and the agent picks the tool. Nobody types a tool name.

ether
bitcoin
the two together

Each snapshot already carries the neighbouring market differenced against its own, so the last two answers come from one call, not from stitching two.

Connect

  1. Get an access token from the service operator. Use a separate token for each AI client. Holding one means accepting the terms of use, and how the numbers behind it are made is written in the methodology.
  2. Paste the token below, choose your client, and copy the generated setup.
  3. Ask any of the questions above. An answer that names the minute it describes and the code of the snapshot it read means you are connected – and that the numbers in it can be traced back.
access token

Used only to generate the setup in this tab. It is not uploaded or saved and is cleared when you close or reload the page.

manual test

Interface

Read-only tools, one per market and horizon. The market is part of the name, so an agent never has to guess which instrument it just received – and the two never arrive mixed. The server exposes no write surface of any kind.

every response carries

Fields within data may be added or removed between builds. The contract defines which fields are authoritative, and an absent field denotes unavailable, not zero.

What comes back

One snapshot of one market, taken on a completed UTC minute, in a frame that never changes shape. The frame states what you are holding – the market, the schema, the exact minute, the age in seconds and the reading contract. Inside it sits the market itself.

the picture inside

The exact field names, units and gating rules are not documented here: they travel with the data, in the reading contract of that very snapshot. An agent reads the rules it was given, never the ones it remembers.

What this is not