> For the complete documentation index, see [llms.txt](https://whitepaper.virtuals.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.virtuals.io/about-virtuals/capital-formation-layer/launch-radar.md). # Launch Radar Launch Radar is an optional module that surfaces your upcoming token to the Virtuals community before the official launch window opens. Activating Launch Radar requires a 100 $VIRTUAL fee. *** ### How It Works When activated, your project appears in the Launch Radar feed on the Virtuals platform. This gives potential supporters the opportunity to review your project, team, and agent details before trading begins. Launch Radar enables founders to: * Build awareness and buzz before a single token is traded * Pre-qualify a holder base of genuinely interested participants * Receive community feedback before launch * Enter launch day with existing visibility rather than starting cold *** #### Configuration Launch Radar is toggled on during the creation phase. No additional parameters are required. The project will be surfaced automatically once the Agent Launch Page is published. --- # 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.virtuals.io/about-virtuals/capital-formation-layer/launch-radar.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.