> For the complete documentation index, see [llms.txt](https://mythics-world.gitbook.io/mythics-world-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mythics-world.gitbook.io/mythics-world-docs/what-is-mythics.md). # What is Mythics? Mythics is a world of myths, where imagination meets trading. Each Mythic is a unique character with its own identity and story. But every Mythic is more than just a character — holding one gives you **magical access to a set of trading features** built for the memecoin trenches. #### The core idea Trading memecoins is chaotic — new tokens appear every minute, trends shift overnight, and it's nearly impossible to watch everything yourself. Mythics turns that chaos into something you don't have to face alone. Instead of a bot trading *for* you, your Mythic unlocks a set of features that help *you* see the market more clearly — the signals, the timing, the noise, all filtered down into something usable. > Think of it less like "a trading bot" and more like being handed a set of tools that only holders get to use. *** **Next:** [How It Works](/mythics-world-docs/how-it-works.md) → --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://mythics-world.gitbook.io/mythics-world-docs/what-is-mythics.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.