> For the complete documentation index, see [llms.txt](https://pepelon.gitbook.io/pepelon/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://pepelon.gitbook.io/pepelon/about-usdpepelon/utility.md). # Utility Pepelon is a multi-faceted memecoin which offers the next generation blah blah. We will be blunt and honest. This is a pure memecoin which will strive to focus on ensuring maximum exposure. More memes and viral marketing is the only focus our team has at the moment. We realised the market at the moment favours tokens with high memeability and that is exactly what we aspire to do. We do however have the resources to build a utility for Pepelon down the road, something which hasn't been done before :) Stick around as we start with mass exposure then proceed to utility creation. Just wait till we trend this worldwide across every social media/crypto platform. You heard it here first $PEPELON will be the next talked about token. --- # 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://pepelon.gitbook.io/pepelon/about-usdpepelon/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.