> For the complete documentation index, see [llms.txt](https://fomos-bonding-paper.gitbook.io/fomobond-1/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fomos-bonding-paper.gitbook.io/fomobond-1/revenue/editor.md).

# Fees

There are no fees once a project's bonding curve is complete and it's live on **UNISWAP-V2**, plus our platform has no control of the contract, or anything that happens with the coin. This process is fully **automated**, therefore once the token is live, it becomes just another renounced, burned liquidity, coin.\
\
Within our platform however, we have the following fees:\
\
-> **1%** for traders **ONLY** inside our platform.\
-> An extra **25%** on covered costs besides liquidity\
\
The first one is self-explanatory. Focusing on the second one, this means that if a contract and its airdrops costed **$100**, the platform earns **$25**. Remember that this does only affect volatility of the coin, but does not inflict a difference on the value of tokens for holders of such.\
\
Keep in mind that these values can be changed and edited at anytime, albeit **with** further notice, and are likely to decrease among adoption, not otherwise.


---

# 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://fomos-bonding-paper.gitbook.io/fomobond-1/revenue/editor.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.