> For the complete documentation index, see [llms.txt](https://stackerai.gitbook.io/stacker-ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://stackerai.gitbook.io/stacker-ai/how-it-works/holder-rewards.md).

# Holder Rewards

## Treasury Profits

The StackerAI treasury is 100% community owned. Our custom AI continually trades the treasury to take advantage of opportunities in the market. These profits are then redistributed to the holders in the form of claims. 

## Platform Rewards 

This adoption based rewards program entitles holders to 50% of the net fees acquired by the StackerAI platform. The fees are fed directly into the distribution system that is operated by the claims portal. 

{% hint style="info" %}
Rewards are distributed based on the Snapshots recorded and consist of 3 factors. The amount of tokens held, the length of ownership and the profits available for distribution. Holders may choose to leave their rewards unclaimed to receive further compounded growth.
{% endhint %}


---

# 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://stackerai.gitbook.io/stacker-ai/how-it-works/holder-rewards.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.