> For the complete documentation index, see [llms.txt](https://monopolon.gitbook.io/monopolon-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://monopolon.gitbook.io/monopolon-whitepaper/2.-about-us.md). # 2. About Us ![](/files/NXdjLRJcVlosUHzKzCfS) ### Mission Our mission is to create an accessible game to everyone with low entry costs and a variety of free NFTs that can develop real monetary value over time. We want to provide a fun opportunity for players, suppliers, and investors to generate income based on their ‘*play-formance’,* making every Monopolon stakeholder a winner. ### **Vision** We strive to create a positive-sum project with fun, attractive play-to-earn dynamics, and include NFTs that provide real-world value to our community as part of the experience. Our long-term aim is to become one of the leading projects in GameFi, the blockchain industry, and to create a metaverse that is finally worth the players’ time. ### Belief We believe in a play-to-earn gaming experience that allows you to build real-world wealth from virtual opulence. --- # 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://monopolon.gitbook.io/monopolon-whitepaper/2.-about-us.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.