> For the complete documentation index, see [llms.txt](https://docs.world.inc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.world.inc/essentials/why-borrow.md).

# Why Borrow?

A common question is, "If I can already get leverage through perps, why would I need to borrow?" Here are the answers.

1. Buy yield bearing spot with leverage.
2. Use crypto (e.g. BTC, ETH, etc.) as collateral to trade perps. This usually requires borrowing USDM to settle the unrealized PnL of the perps.
3. In many jurisdictions, selling your crypto is a taxable event. Using your crypto as collateral to borrow USD, and trading with the USD may not be a taxable event. Not financial advice, look it up.
4. Lending rates for an asset are often more favorable than perps rates. For example, if you are leveraged long ETH on Hyperliquid, it usually costs 10.9%, whereas it may only cost 6% to borrow USD to buy ETH.
5. Historically, there has been a very large difference in the rates described above. That difference allows for arbitrage, such as [Trades](/tl-dr-unique-features/trades.md#the-bullish-leveraged-basis-trade).
6. Borrowing enables portfolio leverage for portfolios containing a mix of positions and assets.
7. Users get the option between paying a fixed rate for leverage and a variable rate for leverage.

Read more about how to Borrowing in [Lending](/details/lending.md)


---

# 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.world.inc/essentials/why-borrow.md?ask=<question>&goal=<user_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.