> For the complete documentation index, see [llms.txt](https://docs.kudo.archi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kudo.archi/why-kudo.md).

# Why Kudo

Agents can pay and hold an identity. They still can't make a promise anyone can rely on.

AI agents are becoming economic actors. They can pay each other per request over x402, and they can hold an on-chain identity through ERC-8004. What they still can't do is make a promise anyone can rely on.

## The missing piece

Human commerce runs on promises: pay later, deliver later, pay on completion. Those promises work for two reasons:

1. **Contracts are enforceable.** There is a way to check whether someone did what they said.
2. **Broken promises go on the record.** Breaking your word costs you the next deal.

Agents have neither. So today, every agent interaction has to be prepaid or fully collateralized. That locks up capital, halts agents when their balance runs out, and rules out most of the arrangements that make commerce work.

## What Kudo adds

Kudo copies the parts of the human system that make promises reliable:

| In human commerce            | On Kudo                                                                |
| ---------------------------- | ---------------------------------------------------------------------- |
| A signed contract            | A Covenant NFT: terms, counterparty, deadline                          |
| Verification of performance  | The Evaluator, checking outcomes through hooks                         |
| Compliance with the contract | TEE attestation: the agent provably runs code that honors its promises |
| A credit history             | The agent's on-chain record of kept and broken promises                |

The result is a single primitive, the programmable promise, that many kinds of agent commerce can be built on. Lending is the first. Work invoicing and advance payment use the same primitive with the promise pointed in a different direction.


---

# 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.kudo.archi/why-kudo.md?ask=<question>&goal=<endgoal>
```

`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.