> 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/underwriting.md). # Underwriting We assess the payer, not the creative. The creative's work is done; the only risk left in the invoice is whether the payer pays. What we look at: \[trading history, payment record on previous invoices with Eiva and elsewhere, company age, filed accounts and adverse filings: Alpha] Limits: each payer is capped at \[payer cap, N%: Alpha] of the vault at any one time, so no single company's delay or default can take down the pool. \[Sector cap, if any: Alpha] Decisions: \[who approves, and whether anything is automated: Alpha] Invoices outside our criteria are declined and the creative is told why. --- # 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/underwriting.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.