> For the complete documentation index, see [llms.txt](https://hypotheca.gitbook.io/hypotheca-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hypotheca.gitbook.io/hypotheca-docs/hypotheca/conclusion.md). # Conclusion Why Hypotheca turns verified reputation, security, and economic history into measurable credit access for autonomous agents. Hypotheca does not lend against what you own. Hypotheca lends against what you have proven. Persistent agent identity, reputation, current security evidence, and verified payment history establish the evidence behind a borrow request. Credit scoring, measured LTV, oracle protection, liquidation controls, and execution-level enforcement determine whether that evidence can become credit access. **Proof over collateral.** This principle does not remove collateral. Hypotheca remains over-collateralized, with effective LTV constrained by the defined risk model. Borrowing, repayment, liquidation, and reputation updates are tied to transaction hashes. Together, these events contribute to an observable credit history. Borrowing from AMM inventory can affect liquidity providers. Defaults can also have lasting on-chain consequences. Protocol parameters remain subject to governance. Hypotheca documentation is informational only and does not constitute financial or investment advice. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://hypotheca.gitbook.io/hypotheca-docs/hypotheca/conclusion.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.