> 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/how-it-works.md). # How it works Your Mythic unlocks magical trading features that help you watch the market, so you don't have to. #### What gets watched for you * **New launches** — spotting fresh memecoins as they appear * **Volume** — tracking spikes and shifts in activity * **Narratives** — following the trends and stories driving the market * **Liquidity** — keeping an eye on what's moving and what's not * **Market activity** — monitoring the overall pulse of the trenches While these features are watching all of this for you, you're free to do literally anything else. #### Why this matters Memecoin trading usually means: * Endless chart watching * Chasing every new meme before it's too late * Trying to track dozens of signals at once, manually Mythics removes that grind. Instead of doing the digging yourself, your Mythic gives you magical access to features that do it for you — watching the trenches, staying alert, and working in the background while you live your life. *** **Next:** [Access & Where It Lives](/mythics-world-docs/access-and-discord.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/how-it-works.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.