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

# Annual Incentives

To guarantee platform growth and community engagement, a fixed amount of 85M SWAP tokens in annual incentives are emitted and allocated to various stakeholders within the ecosystem.

### Breakdown of Annual Incentives

<figure><img src="/files/MZs5X7BZBQY9ZBQ7Xrwh" alt=""><figcaption></figcaption></figure>

1. Platform Incentives: 65,000,000 SWAP tokens allocated annually.
   * 5% (3,250,000 SWAP ): Incentives for node validators to secure the metagraph.
   * 20% (13,000,000 SWAP): Support for the SWAP DAO to cover operating costs.
   * 75% (48,750,000 SWAP ): Allocated based on community voting power.
2. Governance Incentives: 20,000,000 SWAP tokens


---

# 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://docs.pacaswap.com/tokenomics/emissions-and-incentives/annual-incentives.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.
