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

# 5.2 MDXL Token Distribution Structure

To ensure the initial stability and long-term viability of the ecosystem, MDXL tokens are allocated as follows:

* **Platform Rewards (25% - 750,000,000 MDXL)**:\
  Used for rewarding data contributions, verifications, and participation incentive programs.
* **Research & Development (20% - 600,000,000 MDXL)**:\
  Allocated for platform development, including AI and DePIN infrastructure.
* **Sales (20% - 600,000,000 MDXL)**:\
  Reserved for business development and sales activities.
* **Team & Advisors (15% - 450,000,000 MDXL)**:\
  Used to reward the project development team and advisors.
* **Liquidity (10% - 300,000,000 MDXL)**:\
  Ensures sufficient liquidity for exchange listings and token transactions.
* **Reserves (10% - 300,000,000 MDXL)**:\
  Maintains ecosystem stability and supports contingency measures.


---

# 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://mdxl.gitbook.io/mediaccel/5.2-mdxl-token-distribution-structure.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.