> 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/start-here/readme.md).

# Zirodelta

Zirodelta builds financial modules for any app that holds money: earn, borrow, convert, settle and spend, all running on one shared balance sheet. Apps plug in the modules they need, and Zirodelta earns when those modules earn or move money.

{% hint style="info" %}
**Status, October 2026.** Every module is in development. No customer funds are pooled. See [Status](/start-here/status.md) for the detail.
{% endhint %}

## Who these docs are for

* Teams building apps that hold money, who want to understand what the modules do and how working with Zirodelta would look.
* Anyone who wants to check how the system works, what is live and what can be verified.

## Where to start

* [How Zirodelta works](/start-here/how-it-works.md): the three layers and why one balance sheet matters.
* [The modules](/modules/shared-balance-sheet.md): what each one does and where it stands.
* [Use cases](/use-cases/balances-that-earn.md): four patterns any app that holds money can use.
* [Working with Zirodelta](/for-apps/working-with-zirodelta.md) and the [business model](/for-apps/business-model.md).
* [Verify us](/trust/verify-us.md): what you can check yourself.

## The short version

* **One engine, many apps.** Each money function is built once, as a module, and offered to any app.
* **One balance sheet underneath.** Modules share one record of what is held, owed and earned, so they work together.
* **Honest status.** Nothing is called live until it is.
* **Verify, do not trust.** Claims about supply, reserves and status should be checkable by you.


---

# 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/start-here/readme.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.