> For the complete documentation index, see [llms.txt](https://docs.metacom.space/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.metacom.space/overview/our-pitch/competition.md). # Competition Many different NFT projects and startups are building high-quality metaverse platforms with advanced graphics and functionality but they require high-quality computers or expensive VR equipment, which can limit the number of potential users. Even though some metaverse platforms can be accessed through cheap computers or mobile devices, they must sacrifice a better user experience with limited graphics and functionality. Centralized servers are expensive to maintain and limit the number of users who can access the metaverse at the same time which can result in the virtual world appearing less populated and isolated and discouraging people from spending more time. Our competitors and big companies focus mostly on building persistent virtual spaces that are always available. Hence, people easily get bored and lonely since the initial excitement of exploring a virtual world is temporary if they’re unable to experience meaningful social interactions. That’s why most people aren’t hosting meetings or networking events in the metaverse because it’s too expensive and the experience is not practical enough to replace existing platforms or the real world. --- # 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.metacom.space/overview/our-pitch/competition.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.