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

# Business model

**No license fee. Zirodelta earns when your balances earn or move.**

## Who earns

Your app decides how the value the modules create is shared:

* **Your app keeps it,** as a new line of revenue.
* **Your users get it,** as a feature, such as balances that earn or lower fees.
* **Both,** in whatever split you choose.

## How Zirodelta earns, per module

| Module     | What your app gets                | How Zirodelta earns                              |
| ---------- | --------------------------------- | ------------------------------------------------ |
| Yield      | Earnings on idle balances         | A share of what the strategy earns               |
| Credit     | Loans and advances for your users | Interest or fees on credit, shared with your app |
| Conversion | Swaps inside your app             | A fee per conversion, shared with your app       |
| Settlement | Payouts and transfers             | A fee per settlement                             |
| Fiat rails | Getting money in and spending it  | A share of partner fees                          |

Percentages are agreed per partner and will be published with each module, not before.

## Why this model

Zirodelta only earns when the modules produce something for you. If a module does not earn or move money for your app, it costs you nothing.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.zirodelta.com/for-apps/business-model.md?ask=<question>&goal=<user_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.

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.