> For the complete documentation index, see [llms.txt](https://whitepaper.kindredlabs.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.kindredlabs.ai/product-roadmap/phase-2-the-protocol/revenue-flow-and-value-transfer.md).

# Revenue Flow and Value Transfer

The Kindred Protocol facilitates seamless value exchange among all ecosystem participants, ensuring that creators, users, and investors benefit from the agent’s success.

**Revenue Streams:**

1. **User Payments:** Users interact with agents through activities such as personalized experiences, virtual goods, and premium features. Payments are made in $KIN tokens.
2. **AI Inference Costs:** A portion of the user payments is allocated to cover the operational costs of AI inference, ensuring continuous functionality and quality.
3. **Onchain Treasury:** Revenue generated by each agent flows into its dedicated onchain treasury, managed transparently and used for future growth.

**Buyback and Burn Mechanism:**

* Collected $KIN tokens are periodically used to buy back the agent’s governance tokens from the open market.
* The purchased tokens are burned, reducing supply and creating deflationary pressure to increase token value.

This self-reinforcing loop aligns the interests of creators, users, and investors, driving long-term sustainability and growth.


---

# 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:

```
GET https://whitepaper.kindredlabs.ai/product-roadmap/phase-2-the-protocol/revenue-flow-and-value-transfer.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.