> For the complete documentation index, see [llms.txt](https://docs.nemus.earth/nemus-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nemus.earth/nemus-docs/nemus-litepaper/defi-and-game-mechanics/experience-xp-and-levels.md). # Experience (XP) & Levels As time draws closer to activating game mechanics within the Nemus ecosystem, there will be a clear description provided for the various activities, quests and adventures that will unlock XP points and leveling up. The idea behind these game elements inside of Nemus is to allow Guardians to express their unique interests in the ecosystem and biodiversity. Through XP and levels, a Guardian will be able to earn specific titles within the application (and Discord,) as well as additional rewards for having achieved specific collections. There are many benefits to introducing XP into Nemus. For example, it could be used to impact a Guardian’s weight and status inside of the DAO. Active participants -- who have taken the time to educate themselves on the biodiversity and potential economic activities within Nemus -- should have a stronger voice after all. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.nemus.earth/nemus-docs/nemus-litepaper/defi-and-game-mechanics/experience-xp-and-levels.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.