> For the complete documentation index, see [llms.txt](https://docs.kaiko.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kaiko.com/coverage/data-infrastructure-coverage.md).

# Data infrastructure coverage

Explore Kaiko’s supported networks and available Data On-Ramp, Data Off-Ramp, and Tokenized Indices coverage.

Kaiko delivers institutional-grade market data directly onchain across public, permissioned, EVM-compatible, and non-EVM networks.

Our [Data On-Ramp](https://www.kaiko.com/data-infrastructure/data-on-ramp) infrastructure enables blockchain applications to access independently sourced market data for pricing, valuation, risk management, settlement, and trade execution.\
\
Our [Data Off-Ramp](https://www.kaiko.com/data-infrastructure/data-off-ramp) connects onchain data with off-chain systems, making blockchain activity accessible through APIs, reporting tools, business intelligence platforms, and other enterprise workflows.\
\
Our [Tokenized Indices](https://www.kaiko.com/data-infrastructure/tokenized-indices) infrastructure enables benchmark and index data to be used within blockchain-based financial products and onchain workflows.

Coverage varies by network and deployment. Some datasets are live today, while additional data products can be made available on supported networks based on client requirements.

<table><thead><tr><th width="178.12109375">Network</th><th>Data On-Ramp</th><th>Data Off-Ramp</th><th>Tokenized Indices</th></tr></thead><tbody><tr><td>Canton</td><td><ul><li>Kaiko Reference Rates (Crypto)</li><li>Kaiko Reference Rates (Capital Markets)</li><li>NCFX FX rates</li><li>Bloomberg data</li></ul></td><td>Broadridge Distributed Ledger Repo data, via the Bloomberg terminal (and RWA.xyz)</td><td>iBoxx U.S. Treasuries Index (S&#x26;P Dow Jones Indices)</td></tr><tr><td>Arbitrum</td><td><ul><li>Kaiko Reference Rates (Crypto)</li><li>Kaiko Reference Rates (Capital Markets)</li><li>Kaiko FX Rates</li></ul></td><td></td><td></td></tr><tr><td>Stellar</td><td><ul><li>Kaiko Reference Rates (Crypto)</li></ul></td><td></td><td></td></tr><tr><td>Ethereum</td><td><ul><li>Kaiko Reference Rates (Crypto)</li><li>Kaiko Reference Rates (Capital Markets)</li><li>Kaiko FX Rates Available on Request</li></ul></td><td></td><td></td></tr><tr><td>Besu</td><td><ul><li>Kaiko Reference Rates (Crypto)</li><li>Kaiko Reference Rates (Capital Markets)</li><li>Kaiko FX Rates Available on Request</li></ul></td><td></td><td></td></tr><tr><td>Hyperliquid</td><td><ul><li>Kaiko Reference Rates (Crypto)</li><li>Kaiko Reference Rates (Capital Markets</li></ul></td><td></td><td></td></tr><tr><td>Additional Networks</td><td>Support for EVM-compatible environments and additional non-EVM networks on request</td><td></td><td></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.kaiko.com/coverage/data-infrastructure-coverage.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
