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

# Incentives

In the XYO Layer One ecosystem, incentives are designed to reward meaningful contributions to data integrity, availability, and processing. Whether collecting, validating, or storing data, participants are economically compensated through the network’s dual-token model using [**$XYO**](/xyo-layer-one/dual-token-model/xyo-token.md) and [**$XL1**](/xyo-layer-one/dual-token-model/xl1-token.md).

### Token-Based Compensation

While XL1 is often the choice of compensation for on-chain services, off-chain services can also use XYO. For example, XYO’s DePIN ecosystem utilizes XYO as an incentive and redeem item to encourage accurate and valid data production by contributors.

* **Data collectors** – Individuals or devices that gather real-world data
* **Data processors** – Nodes or applications that transform or enrich data
* **Data storers** – Participants who ensure long-term data availability and access

This flexibility allows for a wide range of decentralized services to operate within the network and be appropriately rewarded.


---

# 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.xyo.network/xyo-layer-one/tokenomics/incentives.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.