> For the complete documentation index, see [llms.txt](https://grimoire.mytho.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://grimoire.mytho.io/getting-started/fees-and-revenue-sources.md).
# Fees and Revenue Sources
Mytho makes money through fees tied to its core features, ensuring the platform grows while supporting totems and users.
* How Mytho Earns Revenue:
* Fee for Community Tokens Purchases in the Initial Liquidity Pool: When you buy a new token in its initial sale (at $0.00005 per token), Mytho takes a 2.5% fee on the total MYTHO spent. This fee kicks in once the pool fully sells out—not during the sale itself.
* Fee on Donations to Posts: When you send tokens as a donation to a post’s author, Mytho takes a 20% fee.
* Payment for Premium Merit Boost (equivalent to $0.10 per transaction)
* What Happens to the Revenue:\
\
Mytho splits its profits to keep the ecosystem strong:
* 50% to Communities: Half of all revenue goes to communities through the Merit system. The more Merit points a community earns from activity (like posts or boosts), the bigger its share of this MYTHO pool.
* 50% to MYTHO Stakers: The other half rewards users who stake MYTHO with the platform. This gives you a direct return for supporting Mytho.\
\
This 50/50 split ensures both communities and token holders benefit as the platform grows.
* How It Ties to MYTHO:\
\
The fees are paid in MYTHO (e.g., from community token purchases or swaps), and the revenue gets redistributed in MYTHO. As more people use Mytho—buying community tokens, trading, or donating—the fees pile up, increasing the MYTHO flowing to communities and stakers. This makes MYTHO more valuable as the platform scales.
---
# 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://grimoire.mytho.io/getting-started/fees-and-revenue-sources.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.