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

# Why This Matters

### E-Commerce Merchants

Chargebacks cost millions. With verifiable proof, merchants can defend themselves against fraudulent chargebacks. Result: fewer disputes, lower costs, faster payments. Studies show merchants can reduce chargeback rates by 50% or more.

### AI Agents

As AI agents handle more commerce, they need to prove their actions to users and contracts. Koova lets agents generate proof of every transaction, building trust with users and enabling new use cases.

### DeFi & Smart Contracts

Smart contracts need to know what happened in the real world. Koova provides verifiable proof that contracts can trust, without relying on centralized oracles.

### Enterprise & Compliance

Supply chains, healthcare, finance—industries that need auditable records. Koova creates immutable proof of every transaction, making compliance easier and fraud harder.


---

# 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://koova.gitbook.io/koova-whitepaper/introduction/why-this-matters.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.