> For the complete documentation index, see [llms.txt](https://the-merry-aigents-of-maia.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://the-merry-aigents-of-maia.gitbook.io/docs/readme.md). # Welcome **The Merry AIgents of Maia · $MAiA on Robinhood Chain** > Living document. Figures are expressed as **percentages and stages, not fixed amounts or dates**, on purpose — nothing here is a promise of returns. Experimental project, not investment advice. See *Risk & Disclaimers*. Merry AIgents is a collection of **4,444 dynamic NFTs** on **Robinhood Chain**. Each NFT is not a static picture — it is an **autonomous on-chain trading agent** (an ERC-6551 token-bound account) dressed as an archer-automaton of Sherwood. You **burn $MAiA** to wake your AIgent and to level it up. As it ascends, three things grow together: the **art** (from a dormant chassis to a fully-equipped elite archer), the **DeFi tooling** it can run (DCA → GRID → autonomous market scanning), and the **rewards** it earns. A community treasury — **The Major Oak Treasury** — is seeded from the sale and put to work in diversified, audited yield. Only the *yield* funds prizes and buy-back-and-burn; the principal is preserved. In the Robin Hood spirit, the value the machines generate is redistributed to the community that holds them. *** --- # 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://the-merry-aigents-of-maia.gitbook.io/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.