> For the complete documentation index, see [llms.txt](https://docs.eiva.money/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eiva.money/welcome.md). # Welcome Eiva funds short-dated trade receivables: invoices for work that's already been delivered, owed by established businesses. Today those invoices come from the creative industries. eiva.money is where the capital comes from. Depositors put USDC into one of three vaults. Open pays a rate fixed for each 30 day period, and you can withdraw at any time. The 6 and 12 month notes pay a higher rate, fixed for the term, and can be redeemed early: you're paid within 45 days of the request, usually sooner, as invoices settle and the queue is paid. Every vault funds the same pool of invoices, and the fee on each invoice pays the interest. Interest is paid monthly on every vault, or compounds into your principal if you turn autocompounding on. These docs cover the invoices, the vaults, the risks and the company. If you want to deposit, [Getting started](/getting-started.md) is next. ## Links * App: \[app URL: Alpha] * Ledger: \[ledger URL: Alpha] * Transparency: \[transparency URL: Alpha] * X: @eivamoney * Email: --- # 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.eiva.money/welcome.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.