> For the complete documentation index, see [llms.txt](https://userguide.cryptoquant.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://userguide.cryptoquant.com/what-is-cryptoquant/introduction/how-we-process-data.md).

# How We Process Data

## How We Process Data

<figure><img src="https://downloads.intercomcdn.com/i/o/759063131/aa6eae99cc3a115ae1e258d2/a139c109-5dd0-4afc-924f-95e8be9aedd5" alt=""><figcaption></figcaption></figure>

CryptoQuant collects raw data from both on-chain and off-chain sources including comprehensive data from 10+ blockchains, wallet labels, market data from exchanges, as well as log data from web2 companies entering the blockchain space.&#x20;

The collected raw data is then processed by decoding smart-contracts, identifying transactions, and creating structured data tables by web3 category. CryptoQuant develops pre-built metrics and indicators to value decentralized blockchain applications, track capital flows (including exchange and miner flows), analyze market and network activity, and metrics related to DeFi, NFTs, and GameFi, to name a few.&#x20;

Our solutions provide data at various levels of resolution and frequency, as well as via multiple delivery mechanisms, for custom and flexible analysis.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://userguide.cryptoquant.com/what-is-cryptoquant/introduction/how-we-process-data.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.