> 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/visionmove/welcoming-a-new-partner.md). # Welcoming a new Partner To ensure the success of VisionMove’s global network of gyms, we’re excited to bring on a seasoned partner with decades of expertise in the fitness industry. While VisionMove brings cutting-edge web3 technology to the table, this new partnership fills any initial gaps in gym management and operations, providing the foundational knowledge and experience needed to bring our vision to life. This soon-to-be-announced partner has over 30 years of experience running gyms and has collaborated with major brands like Kellogg's to offer insights into fitness-related products. Together, we’re building an ecosystem that combines the best of fitness and technology, backed by industry-leading knowledge and a commitment to excellence. With this partnership, VisionMove is poised to deliver a truly unique, expertly managed fitness experience for members worldwide. --- # 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/visionmove/welcoming-a-new-partner.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.