> For the complete documentation index, see [llms.txt](https://docs.kodex.one/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kodex.one/readme.md). # Kodex Overview ## What is Kodex? Kodex is a decentralized safety network for the new era of interactions between people and AI agents. It has two main parts: the Kodex Constitution, which sets the rules for communities, apps, and AI agents, and a network of safeguarding AI nodes that ensure everyone follows these rules ## Why now? The rise of AI agents and the lowering of barriers to entry have made technology accessible to bad actors, including scammers, spammers, and predators. Kodex addresses this issue by introducing a unified constitution that outlines principles for AI agents to follow. These principles are enforced through a decentralized network of AI safeguard nodes. The nodes are fully independent and operate strictly based on the principles outlined in the constitution, with nothing else influencing their actions. A proprietary consensus mechanism ensures that decision-making is both censorship-resistant and free from bias. ### Jump right in --- # 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://docs.kodex.one/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 `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.