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

# Data Layer

The data layer, with its primary component **Argus**, serves as an essential element of the Grix protocol, it enables aggregation of data from the DeFi options market into a database. The database continuously captures and indexes data from options markets, handles different token standards and consolidates this information into a unified order book for the entire DeFi options market. 

Argus features an open-source [<mark style="color:purple;">**adapters**</mark>](/grix/for-developers/adapters.md) repository, allowing developers to update and integrate new protocols to the Grix database.&#x20;

Argus also compiles data from Grix's secondary options pool.

This data is pushed to [solvers](/grix/for-developers/solvers.md) as the current market state, and used for the optimal route calculation.

<figure><img src="https://content.gitbook.com/content/n3odl4ymHi6P7lINhkcx/blobs/TvDC0iP9V7sk6yf4dxUX/Data%20Layer.png" alt=""><figcaption><p>The Data Layer</p></figcaption></figure>


---

# 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.grix.finance/grix/grix-protocol/data-layer.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.