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

# Tokenomics

The CREPE Token issued by Crepe Foundation is designed to be issued in a limited amount of 1 billion tokens. Of this, 350 million tokens (35%) can be mined as a reward through various staking methods, and 150 million tokens (15%) are paid for community expansion. Among team quantities, 50 million tokens (5%) for founders will be paid in a lump sum in February 2025 after the 3-year vesting period from February 2022 and 30 million tokens (3%) for early contributors will be paid in a sliding way for 12 months from November 1, 2023 after the lock-up period from February 2022. The remaining 120 million tokens (12%) for teams are paid for the salary and compensation of the development team and management team, development expenses and marketing expenses, etc.

<figure><img src="/files/HxaglAZHAeU6oI1HyIIr" alt=""><figcaption><p> CREPE Token Distribution Plan</p></figcaption></figure>


---

# 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://crepe.gitbook.io/paam/crepe-token/tokenomics.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.