> For the complete documentation index, see [llms.txt](https://docs.neurochain.ai/nc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.neurochain.ai/nc/overview/our-vision.md). # Our Vision Our vision is to lead the market in network-based artificial intelligence implementation by providing the most accessible and user-friendly gateway to Web3 AI. To do so we simplify the integration of Web2 and Web3 applications with advanced gRPC and HTTP messaging protocols. Our commitment extends to empowering a decentralized network of miners and AI validators, driven by a Proof-of-Work through Proof-of-Stake (PoWtS) consensus and fuelled by a robust, community-driven open-source technology. We're setting a new standard in AI implementation, making it more efficient, accessible, and collaborative for everyone. ***Important Notice:** Please read the entire document, including all legal disclaimers and other important statements herein, carefully. NeurochainAI shall not be held liable for any damages, losses, or liabilities arising from the use of this website and/or the information provided herein.* --- # 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.neurochain.ai/nc/overview/our-vision.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.