> 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/social-opportunities.md). # Social Opportunities Play-to-earn (P2E) gaming has immense potential as a social driver, transforming engagement beyond gameplay into broader interactions and discovery. VisionArcade harnesses this power by encouraging users to connect with new games, products, and communities, all motivated by the prospect of earning rewards. Players who are eager for rewards can, for example, share games on their social channels, helping spread awareness and attracting new users to the VisionArcade ecosystem. Through these social-driven incentives, VisionArcade empowers users to try new games, explore diverse products, and discover experiences they might not have sought out otherwise. Whether it’s encouraging players to download a game or experience a new product, VisionArcade’s reward structure makes engagement and exploration an easy and rewarding experience for users, creating an interconnected community that thrives on both gameplay and social interactions. --- # 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/social-opportunities.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.