> For the complete documentation index, see [llms.txt](https://gitbook.raac.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook.raac.io/learn/usdraac-token/tokenomics.md).
# Tokenomics
{% hint style="info" %}
Total Supply: 21,000,000
{% endhint %}
## Allocations
41.92% of supply is allocated for the ecosystem. Ecosystem token distributions follow a fixed schedule and their destination is decided by $veRAAC holders (see section “[Ecosystem Token Distribution](/learn/usdraac-token/tokenomics/ecosystem-token-distribution.md)”).
The treasury is used to seed multiple key components of the RAAC system, including DEX LPs and leRAAC’s maturity vault. More details, such as exact allocations across LPs, will be published. For the required flexibility, the treasury has to be unlocked at day one as showcased by the vesting schedule. The RAAC team will not sell any RAAC from the treasury allocation.
***
## Emissions
As explained throughout this section and the [next section](/learn/usdraac-token/tokenomics/ecosystem-token-distribution.md), not all emitted RAAC will be liquid as emissions are making use of leRAAC and veRAAC, locked versions of RAAC.
---
# 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 following URL with the `ask` and `goal` query parameters:
```
GET https://gitbook.raac.io/learn/usdraac-token/tokenomics.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 `build a script that syncs our docs to a CMS` 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.
