> For the complete documentation index, see [llms.txt](https://docs.liquidus.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.liquidus.finance/liquidus-wallet-app/track-your-holdings-and-pools/farm-and-pool-details.md).

# Farm and pool details

1. Starting from the “Holdings” page, you can click on any pool or farm to show its details.
2. The app shows you all relevant information about the pool such as Pair, APY, Farm, Your Worth, Weekly Earnings, and the Security Rating (shield on the top left).
3. Below it shows you the token amounts you own, that form the pool (underlying tokens). If you are viewing a single token farm, you only see one token amount.
4. Under the Rewards section, it tells you the reward token and how much has been accumulated. Click on the “arrow to the right” to harvest your rewards.
5. Click the Top Up button to deposit more or click “Withdraw” to remove tokens from your pool partly or in full.


---

# 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.liquidus.finance/liquidus-wallet-app/track-your-holdings-and-pools/farm-and-pool-details.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.