> For the complete documentation index, see [llms.txt](https://catonbnb.gitbook.io/catonbnb-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://catonbnb.gitbook.io/catonbnb-docs/vision-and-mission.md). # Vision & Mission Our Vision & Mission is designed with a long-term vision ## 🎯 CatonBNB Vision **To build a future where artificial intelligence doesn’t just exist in the digital world — but lives among us, physically, through customizable, ownable, and user-controlled robots.** We believe AGI (Artificial General Intelligence) should not be controlled solely by large corporations. CatonBNB is here to create a secure, open infrastructure where anyone can build, connect, and live alongside their own intelligent creations. ## 🧭 Mission * **Provide a decentralized infrastructure** for creating and managing customizable AI Agents. * **Bridge digital AI with physical robots**, allowing AGI to interact directly with the real world. * **Empower users** to design the brain of their robots using simple, modular prompt-based systems. * **Promote the adoption of Web3 and AI together**, ensuring every agent and interaction is securely and transparently recorded on-chain. * **Build a community of AI creators and users** who collaborate, share skills, and contribute to an open intelligence network for the future. --- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://catonbnb.gitbook.io/catonbnb-docs/vision-and-mission.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 `build a script that syncs our docs to a CMS` 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.