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

# Our Revenue Model

Kredo’s revenue model is designed to be **protocol-native**, predictable, and non-extractive.

#### **Authorization Fees**

Rather than charging per transfer or per balance:

* Fees are assessed per **validated spending intent**
* Fees are paid by integrators, applications, or liquidity operators
* End-users may never see or handle fees directly

This aligns revenue with **actual system usage**, not speculative activity.

#### **Policy & Infrastructure Access Fees**

Entities using advanced features—such as:

* High-volume authorization throughput
* Custom identity policies
* Specialized liquidity configurations
* Compliance-oriented rule sets

Pay recurring protocol fees denominated in $KREDO or routed through i

#### **Liquidity Fog Pool Participation Fees**

Liquidity providers who contribute capital to fog pools:

* Earn usage-based compensation
* Pay protocol coordination fees for pool access
* Operate within strict invariant rules enforced by authorization logic

Kredo does not monetize user balances, because balances do not exist.

#### **No User Monetization**

Critically:

* Users are not charged custody fees
* Users do not pay account maintenance fees
* Users do not hold protocol debt

Revenue is generated at the **infrastructure and integration layer**, not at the individual user layer.


---

# 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://kredopay.gitbook.io/documentation/our-revenue-model.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.