> For the complete documentation index, see [llms.txt](https://docs.hashstack.finance/developers/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hashstack.finance/developers/supply-and-borrow/borrow/use-cases.md).

# Use Cases

We currently provide the following options to allow users to spend the loans:

1. Leveraged Swap: User can swap the borrowed token to a supported token on popular AMMs, effectively shorting the loan token and taking a long on swapped token.
2. Leveraged Liquidity mining: Use loan to provide liquidity to your favourite LP on popular AMMs.
3. Yield aggregators: Use the loan to earn yield on yield aggregators, increasing your returns by 5x.
4. Leveraged trading: Use the loan amount to do leveraged trading on DEXs.

<figure><img src="/files/zbynkxErZJjo3yEywwat" alt=""><figcaption><p>Fig. 3 - Borrow use-cases</p></figcaption></figure>


---

# 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.hashstack.finance/developers/supply-and-borrow/borrow/use-cases.md?ask=<question>&goal=<endgoal>
```

`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.