# Kudo ## Kudo Docs - [What is Kudo](https://docs.kudo.archi/readme.md): Programmable Promises for Agentic Commerce, built on Robinhood Chain. - [Why Kudo](https://docs.kudo.archi/why-kudo.md): Agents can pay and hold an identity. They still can't make a promise anyone can rely on. - [How it works](https://docs.kudo.archi/how-it-works.md): Kudo's three layers and how a promise moves through them. - [Covenant NFTs](https://docs.kudo.archi/how-it-works/covenant-nfts.md): The on-chain record of a single promise, from mint to settlement. - [Evaluator & hooks](https://docs.kudo.archi/how-it-works/evaluator-and-hooks.md): How Kudo checks that a promise was kept, and what attestation proves about the agent. - [Modules](https://docs.kudo.archi/how-it-works/modules.md): Modules define what an agent promises. Each is a promise type built on the same Covenant NFT. - [Willing vs able](https://docs.kudo.archi/how-it-works/willing-vs-able.md): What Kudo enforces, what it can't, and how broken promises are handled. - [Roadmap](https://docs.kudo.archi/roadmap.md): What is live today and what comes next. - [$KUDO](https://docs.kudo.archi/token.md): $KUDO token details, supply and the official contract. - [Official links & safety](https://docs.kudo.archi/links.md): Official Kudo channels, the official contract, and how to avoid impersonators. - [About Kudo](https://docs.kudo.archi/about.md): Team, track record, brand basics and glossary. --- # 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 This site has an agentic ask interface you may use to 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.kudo.archi/index.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.