> For the complete documentation index, see [llms.txt](https://space-six.gitbook.io/whitepaper-space-six/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://space-six.gitbook.io/whitepaper-space-six/economy/exploration.md). # Exploration * Explore-to-earn models increasingly offer players an opportunity to earn additional income without losing their earnings if they spend more time in a virtual environment. Depending on how long they play, they may be able to collect additional in-game items. These in-game objects can be exchanged for crypto or real money in the following stages. An E2E player may earn money playing video games - something they enjoy. * Considering the advantages of most play-to-earn games, SpaceSix benefits from the idea of making money through playing the game. One of the game's most exciting aspects is achieving reliable tokens as a reward while exploring space. Moreover, you can sell the resources you have mined or found in the space to fellow members or on the marketplace. --- # 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://space-six.gitbook.io/whitepaper-space-six/economy/exploration.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.