> 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/readme.md).
# Readme
## Mythics
Long before charts and candles, there were myths — stories of beings who could see what others couldn't, who moved through chaos and came out ahead.
Mythics brings that idea into the world of trading. It's an NFT collection where every character is more than art — each one is a key that unlocks magical trading features built to help you navigate the market.
> **Only 100 unique Mythics exist. No more will ever be made.**
***
#### What you'll find in these docs
| Page | What it covers |
| -------------------------------------------------------------------- | ------------------------------------------- |
| [What is Mythics?](/mythics-world-docs/what-is-mythics.md) | The core idea behind the project |
| [How It Works](/mythics-world-docs/how-it-works.md) | What your Mythic actually watches for you |
| [Access & Where It Lives](/mythics-world-docs/access-and-discord.md) | How holding a Mythic unlocks Discord access |
| [Technical Foundation](/mythics-world-docs/technical-foundation.md) | The system behind the magic |
| [Closed Alpha](/mythics-world-docs/closed-alpha.md) | Where the project stands right now |
***
**Myth and market, working for you.**
---
# 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/readme.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.
