> 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/access-and-discord.md). # Access and Discord Holding a Mythic is what unlocks the magic. #### Getting in Once you hold a Mythic, you get access to a **closed environment inside the Discord server**. This isn't a public channel — it's a private space that only holders can enter. #### What happens there Everything covered in [How It Works](/mythics-world-docs/how-it-works.md) — the monitoring, the signals, the alerts, the ranked opportunities — is delivered right there, inside that Discord channel. That's where the magic actually happens: * Signals and alerts get posted as they're detected * Analytics and scoring are shared in real time * Updates on tokens, narratives, and market activity all flow through this one space > You don't need to check multiple tools or dashboards. Your Mythic unlocks the features, and the closed Discord channel is where they show up for you. *** **Next:** [Technical Foundation](/mythics-world-docs/technical-foundation.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/access-and-discord.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.