> For the complete documentation index, see [llms.txt](https://docs.raga.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.raga.finance/hemi/hemi-user-research.md). # Hemi User research ### Requirements of Hemi and Spectra users Raga team talked to major users of yield-trading platforms like Spectra on Hemi to understand their pain points. The top requirements from these users are - 1. Earn higher returns on deployed capital on Hemi 2. Simple interface to compound returns on their PT-asset holdings 3. Clear understanding of the risks associated with any yield-looping strategy ### How does Raga Finance solve them? Raga Finance yield-looping vaults enable Spectra users to use leverage to increase their returns on PT-holdings. These are the features of Raga Finance vaults - 1. Create and close positions in a single click 2. Leverage slider to set desired leverage 3. Easy monitoring of position risk 4. Transparent investment strategy that every user can see and understand --- # 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://docs.raga.finance/hemi/hemi-user-research.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.