> For the complete documentation index, see [llms.txt](https://docs.w.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.w.ai/w.ai-guide/vision.md). # Vision ### Liberating Intelligence from Centralized Control At w\.ai, we’re creating a decentralized future where artificial general intelligence (AGI) belongs to everyone—not centralized gatekeepers. Imagine hundreds of millions of idle devices—consumer laptops, gaming PCs, and smartphones—awakened and united into a single decentralized AI supercomputer. This global network, owned and operated by its contributors, will democratize access to intelligence, preventing centralized entities from monopolizing humanity’s most transformative technology.
Our mission is clear: liberate intelligence, make superintelligence universally accessible, and empower creators, researchers, and builders worldwide to freely innovate, collaborate, and thrive outside the constraints of proprietary control. --- # 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.w.ai/w.ai-guide/vision.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.