> For the complete documentation index, see [llms.txt](https://docs.nerox.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nerox.ai/readme.md). # Welcome to NeroX Web3 doesn’t wait. Narratives flip in 6–12 hours, and on Solana alone 1,000+ tokens launch daily. Yet fewer than 10% survive beyond their first week, while most traders are left chasing hype and holding losses. At the same time, the market is shaped by influence. A single KOL post on X can spark tens of thousands of mentions within minutes, instantly redirecting liquidity. With over 50M+ crypto-related posts every month, finding clarity in the noise is nearly impossible. In this chaos: * Promising projects disappear before they’re noticed. * Talented teams lose visibility beneath shills and scams. * Traders miss early entries that could have yielded 10–50x gains. #### NeroX is built to change that. By combining AI-powered narrative analysis, KOL credibility ranking, and real-time market mapping, NeroX transforms scattered noise into structured, actionable intelligence. With NeroX, worthy projects get the spotlight, and traders gain the tools to uncover alpha before it goes mainstream. --- # 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.nerox.ai/readme.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.