> 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.md).

# $RAAC Token

$RAAC is RAAC’s ecosystem token, managing and coordinating its various components including RWf(x), RAACLend index, as well as $RAAC distributions.

RAAC uses a ve (vote escrow) token model to align token holders with the protocol. Lockers receive a pro rata share of value captured by RAAC based on their $veRAAC token holdings. This may include:

* 80% of RAACLend revenue
* 0.5% take rate on REET NFTs and $iREET trading volume (a share of the total token tax and royalty fees)
* Voting incentives for primary and secondary gauge emissions
* Further value share from the RAAC Treasury (see section “[Protocol Economics & Fees](/learn/overview/protocol-economics-and-fees.md)”) if such allocation is deemed effective use of capital


---

# 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.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 `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.