> For the complete documentation index, see [llms.txt](https://whitepaper.interthedungeon.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.interthedungeon.com/community-interoperability.md). # Community/Interoperability Using our decades of experience creating enterprise-level software, we want to set the example of a solid API-based foundation that can pave the way for others to create Axie community-run applications. Our APIs will simplify moving assets between the various Axie projects. The game we create will be the showcase of what is possible. We will be actively seeking out fellow Axie Builder projects to both share our resources with and create collaborations where we can import, display, and promote their game assets in both of our games' play spaces. Our interoperability project will develop the API protocols and documentation for Axie microverse creators to easily transfer and balance NFT and fungible assets between Axie community games. In addition, we're creating a series of simple mini-games in Unity to assist with educating others for creating specification-driven web3 development and hosting APIs to allow creators to leverage the existing infrastructure for their games. In other words, help design best practices in sharing content between games. --- # 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://whitepaper.interthedungeon.com/community-interoperability.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.