> For the complete documentation index, see [llms.txt](https://docs.monaverse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.monaverse.com/create/building-spaces/submit-your-space.md). # Submit Your Space Once you have finished your Space you can submit it for QA before minting the space. The following docs are a useful guide on how to do that. ### Submitting your Space This doc covers the main aspects of what you need to do in order to submit your space for QA before being allowed to Mint your Space. ### Creating An Image & Video Preview This doc goes into the detail of how to create a Preview Image and Video for your asset. There are multiple ways to do it, and this page covers a couple of those. ### QA Process The QA Process is there in order to make sure that your space is ready to go public. The QA team will go over your space to make sure that it is ready to be minted. ### Mint Your Space Once your space has been cleared it is ready to be minted! This doc goes over any final elements before doing so. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.monaverse.com/create/building-spaces/submit-your-space.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.