> For the complete documentation index, see [llms.txt](https://docs.looplay.gg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.looplay.gg/our-vision.md). # Our Vision We've been around Web3 gaming long enough to see the pattern. A token launches, hype rolls in, early insiders win, and everyone else walks away with nothing. The games themselves barely matter. At the same time, we kept meeting people with genuinely good game ideas who would never get to build them. They can't code, can't afford a dev team, and even if they somehow finished a game, no app store or publisher was going to give them a shot. Looplay is our answer to both problems. Describe your game, and our AI builds it with you. Publish it, and it reaches players across web, mobile, Telegram, TikTok and more instantly. No need coding, no gatekeepers, no marketing budget required from creators. And when a game succeeds, it succeeds because people actually play it. Skill and ideas wins here. For creators and players alike. --- # 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.looplay.gg/our-vision.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.