> For the complete documentation index, see [llms.txt](https://docs.resupply.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.resupply.finance/how-to-guides/using-resupply/claiming-rewards.md).
# Claiming Rewards
The [Claim page](https://resupply.fi/claim) provides users with a centralized interface to view and collect rewards accumulated across multiple markets and staked positions. Users can claim **RSUP** and **reUSD** rewards from various sources with the option to claim them individually or all at once.
| Source | What you claim |
| ----------------------------- | ------------------------------------------------------- |
| Lending markets | Rewards from borrowing/supplying (e.g. boosted rewards) |
| RSUP staking | Weekly protocol-revenue share (reUSD) |
| Insurance Pool | Revenue share + RSUP emissions |
| Savings reUSD | Auto-compounding yield (sreUSD) |
| Retention program (borrowers) | Borrower-directed RSUP emissions |
| PRISMA → RSUP vesting | Vested RSUP (if you redeemed PRISMA) |
### How to claim
* **Claim** next to a source claims just that reward.
* **Select all** + **Claim All** executes one transaction for everything claimable.
* The totals bar shows your combined claimable value.
---
# 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.resupply.finance/how-to-guides/using-resupply/claiming-rewards.md?ask=&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.
