> For the complete documentation index, see [llms.txt](https://sayve-protocol.gitbook.io/sayve-litepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sayve-protocol.gitbook.io/sayve-litepaper/tokenomics/token-supply.md).

# Token Supply

The SAYVE token supply has a hard-capped number of 100,000,000 $SAYVE, scheduled for distribution over at least four years. Beyond that, there will be no more SAYVE tokens introduced to the supply. Please see [Token Distribution](/sayve-litepaper/tokenomics/token-distribution.md) for more details on the actual emission schedule.

SAYVE is burnt for the following uses:

* Leveling up (higher levels)
* Minting the top 5% rarest NFTs
* Unlocking achievements and improvements

Burn $SAYVE to mint a new character from breeding characters 

Burn $SAYVE to improve luck in breeding

$LINGO has an unlimited supply and is earned when users learn and are destroyed through ecosystem usage, such as:

* Minting NFTs
* Restoring health
* Leveling up


---

# 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:

```
GET https://sayve-protocol.gitbook.io/sayve-litepaper/tokenomics/token-supply.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.