> For the complete documentation index, see [llms.txt](https://docs.abachi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.abachi.io/abi/total-supply-and-emissions.md).
# Total Supply & Emissions
**Total Supply: 1 million**
A total of 1 million ABI can ever be minted. Although the full supply has been minted, however a large portion of the supply is non-circulating and resides in the Abachi Treasury.
\
**Emissions vs Burn vs Total Supply**
In our proposal we have 10% of the treasury used to buy back and burn ABI in circulation. This rewards stakers into the system and secures the longer term viability of the system. It also rewards our lending pools, partners and other core services that rely on ABI to function.\
\
100% of partner revenue profits will be used to **buy and burn** the ABI token. This may change slightly once the DAO meets for its policy meeting, there is discussion to reduce partner profits to 90% when buying back.
---
# 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.abachi.io/abi/total-supply-and-emissions.md?ask=&goal=
```
`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.