> 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/on-chain/introduction.md).

# Introduction

### Welcome to the Kaiko Data Services documentation. <a href="#welcome-to-the-kaiko-csv-documentation" id="welcome-to-the-kaiko-csv-documentation"></a>

Kaiko Data Services is an ecosystem that acts as a bidirectional intermediary between various data providers and blockchains. Think of it as a data marketplace that facilitates data feeds designed for regulatory and compliance use cases to be leveraged across various blockchains.

#### **Kaiko Data Services comprises three core solutions:**

* **Data On-Ramp**: Enables off-chain providers to distribute various data products on-chain, powering use cases like NAV calculations and mark-to-market accounting for crypto or FX collateral.
* **Data Off-Ramp:** Enables network participants and dApp builders to connect their on-chain activity with off-chain facilities & systems, supporting various use cases like reporting, business intelligence, and auditing by removing technical barriers to data access.
* **Data Lifecycle Apps:** Enables any business to digitize complex, multi-party workflows that require data sharing and coordination by leveraging a blockchain network as their backend infrastructure.<br>

Learn more about Kaiko Data Services [here](https://onchain.kaiko.com/).


---

# 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/on-chain/introduction.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.