> For the complete documentation index, see [llms.txt](https://vortexai.gitbook.io/vortexai-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vortexai.gitbook.io/vortexai-docs/token-and-revenue/revenue-sharing.md).
# Revenue Sharing
While our platform is free to use, it charges a small fee between 0.1%-1% based on your tier holding on executed trades on DEX.
On top of that we also offer a subscription model to have access to our auto trading bot for the non holders who would like to benefit from it. You can access our tier solution [here](/vortexai-docs/token-and-revenue/tiers-system.md).
VIP/Token holders receive 50% of the fees and revenues generated thanks to our subscription model.
Revenues will be shared at the end of the month for all holders who held for the total month.
\*The information is subjected to change with updates being communicated in our official channels.
---
# 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://vortexai.gitbook.io/vortexai-docs/token-and-revenue/revenue-sharing.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.