Crypto market data: sources, APIs and MiCA rules

Crypto market data comes from two kinds of source. Exchange-reported data comes directly from a trading venue's own order book: the price and size of each trade. Aggregated data comes from a data provider that collects prices across many exchanges and publishes one figure. CoinGecko, for example, describes itself as an independent data provider that aggregates prices from thousands of exchanges and tracks tokens across more than 200 blockchain networks, publishing its aggregation method so a user can check how a figure was built.

A third source sits onchain: a blockchain oracle writes outside prices directly into a smart contract, so the contract itself can read a value without calling an external API. Oracle networks covers how that delivery works and what it changes for a lending or trading contract.

A trading desk needs live prices to quote and hedge a position. A risk team needs historical price and volatility data to mark a book or run a stress test. A custody provider needs a reliable reference price to value client holdings. Each use case sets its own requirements for how fast the data has to arrive and how many independent sources back up a single figure.

Traditional market infrastructure has started publishing onchain alongside these providers. Deutsche Börse Market Data + Services in Frankfurt announced on October 1, 2025 that it publishes real-time data from the trading venues Xetra, Eurex, 360T and Tradegate onchain through Chainlink's DataLink service, so smart contracts on more than 40 blockchains can read figures that used to reach only traditional trading systems.

Title VI of MiCA, Regulation (EU) 2023/1114, sets rules against market abuse involving crypto-assets, including insider dealing and market manipulation through price data. A crypto-asset service provider that runs a trading platform has to make its trading data public on reasonable commercial terms, a transparency duty similar to the one MiFID II sets for securities markets. A firm that reads a manipulated price, whether from an exchange feed or an oracle, can act on a wrong figure. Oracle networks covers a case where a trader manipulated an oracle's price feed to borrow far more than his collateral was worth.

Finance Loop connects people who build and use market data pipelines in traditional and crypto finance. On April 15, 2024, Finance Loop, Chainlink and TechQuartier invited guests to a Chainlink panel at TechQuartier in Frankfurt, a pre-event of the Crypto Assets Conference, where the evening opened with Chainlink's decentralized oracle networks for smart contracts. At a MarketVector Indexes panel at TechQuartier, Martin Leinweber, Digital Asset Product Strategist at MarketVector, showed a systematic method for choosing crypto assets, and Dominik Poiger of Deutsche Digital Assets explained the market for crypto ETPs. Related pages: oracle networks, European crypto exchanges and crypto in Europe.

A crypto market data API is a programming interface that returns prices, trading volumes and other market figures on request, so a trading, risk or accounting system can read them automatically. Providers such as CoinGecko publish REST and WebSocket APIs; blockchain oracles deliver the same kind of data directly into a smart contract instead of a server.

MiCA's Title VI sets market abuse rules for crypto-asset trading, including a duty for trading platforms to publish their trading data on reasonable commercial terms. A data provider that only aggregates prices from public sources, without running a trading platform itself, does not need a MiCA license for that activity alone.

It depends on the source. An exchange's own order book updates with every trade. An aggregator that pulls from many exchanges adds a small delay for collection and calculation. An onchain oracle updates on a schedule or when the price moves past a set threshold, which a lending protocol relies on to keep collateral valued correctly.