> 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/working-with-zirodelta.md). # Working with Zirodelta Zirodelta is looking for a small number of design partners: apps and businesses whose balances sit idle, who want to shape the modules before they ship. ## What a first conversation covers * What your app holds, in which currencies and networks. * How money moves through your app, and when. * Which country's rules apply to you and your users, and which licenses you or your partners hold. * Which of the [use cases](/use-cases/balances-that-earn.md) fits. ## How an integration is shaped * Your users, brand and interface stay yours. The modules run underneath. * You start with one module and add others as they ship. * You choose who earns: your app, your users, or both. * Every module carries a public status, and every claim is checkable. ## What exists today There is no public API or SDK yet. Integrations are designed with each partner, and the modules are in development. See [Status](/start-here/status.md). ## Talk to us Through the Zirodelta Discord: [discord.gg/wSseuK26pH](https://discord.gg/wSseuK26pH). --- # 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/working-with-zirodelta.md?ask=&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.