> 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/vi/what-is-cryptoquant/gioi-thieu/how-we-process-data.md).
# How We Process Data
## How We Process Data
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.
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.
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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://userguide.cryptoquant.com/vi/what-is-cryptoquant/gioi-thieu/how-we-process-data.md?ask=&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.