> 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/structure.md). # Structure Two companies. Orthyrus Ltd, trading as Eiva. Company number 15177133, registered in England and Wales. Runs the platform (eiva.co, where creatives submit invoices, as well as the eiva.money app), originates and verifies invoices, and services them to settlement. Eiva Receivables 1 Ltd. Company number \[company number: Alpha]. Wholly owned by Orthyrus Ltd. Issues the notes, holds the vaults and owns the funded invoices. Ring-fenced from the operating company: its assets are the vaults and the invoices. \[Its obligations, the notes and the intercompany loan from Orthyrus Ltd, and how they rank: solicitor] Why two companies: so that what backs your note is the vaults and the invoices, and not the operating company's other assets or liabilities. \[Solicitor to confirm this sentence] --- # 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/structure.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.