> For the complete documentation index, see [llms.txt](https://liquidx-3.gitbook.io/liquidx-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://liquidx-3.gitbook.io/liquidx-whitepaper/2.-fundamentals/2.6-what-is-yield-farming.md).
# 2.6 What is Yield Farming?
Yield farming is the practice of putting your cryptocurrency assets to work to generate returns. Instead of leaving tokens idle in a digital wallet, you deposit them into a protocol that uses them productively - and the protocol shares the generated revenue with you as 'yield' (interest or rewards).
LiquidX offers multiple yield farming pools, each with different return rates and risk profiles. Importantly, LiquidX's yield comes from real protocol revenue - fees charged to borrowers - not from artificially printing more tokens (which would simply dilute everyone's holdings and is a common red flag in lower-quality projects).
---
# 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://liquidx-3.gitbook.io/liquidx-whitepaper/2.-fundamentals/2.6-what-is-yield-farming.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.