> For the complete documentation index, see [llms.txt](https://docs.visiongame.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.visiongame.io/visiongame-ecosystem/visionarcade/visionboy.md). # VisionBoy VisionBoy is our innovative portable gaming device that bridges the gap between traditional businesses and web3, much like VisionMove. Designed to create a seamless entry point for both web3 companies and web2 mobile developers, VisionBoy opens up new revenue and engagement channels by rewarding players simply for playing and interacting with its games and features. With VisionBoy, we’re building a platform that appeals to a broad audience, from web3 enthusiasts to mobile game developers seeking alternative monetization paths. It’s a device we’ve been developing for some time, carefully aligning it with VisionArcade’s ecosystem. Once VisionArcade has fully matured, VisionBoy will be launched, starting with a selection of games for the TON blockchain, our mobile offerings, and social platform. This approach ensures that VisionBoy enters a well-established ecosystem, ready to support and enhance player engagement across both web3 and traditional gaming landscapes. --- # 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.visiongame.io/visiongame-ecosystem/visionarcade/visionboy.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.