> For the complete documentation index, see [llms.txt](https://felixinu.gitbook.io/felixinu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://felixinu.gitbook.io/felixinu/utility.md). # Utility We are not only building the most hard-charging bullish community platform leading the charge towards the next bull run but also building an ecosystem with economically sustainable revenue-sharing components. Our objective is to build a Felix Academy, Felix Bot, staking, game, and merchandise to continue to expand our use cases and revenue generation points to sustain our ecosystem. We will continue to update our whitepaper to showcase all planned utilities in detail as we evolve the project. Our approach is to maximize the potential of Felix Inu ecosystem by leveraging the power of our community expansion and growth to revolutionize the crypto space and further develop more utilities and future investment asset infrastructure designed to sustain the ecosystem economy and increase the native token value at the same time. {% content-ref url="/pages/0XG25ZHA9A9zbeedKW7U" %} [Team](/felixinu/team.md) {% endcontent-ref %} --- # 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://felixinu.gitbook.io/felixinu/utility.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.