> For the complete documentation index, see [llms.txt](https://docs.gage.cash/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gage.cash/rewards/claim-and-reinvest.md).

# Claim and reinvest

Portfolio is where a wallet takes its sGAGE: Collect all on the Agenda, or the Rewards tab's Claim, and a Reinvest sheet that pairs it with GAGE, bought or already held. The Protocol page's This week'

Portfolio is the one place a wallet takes its sGAGE, in two ways.

* **Collect all**, on the Agenda. **Now** lists the sGAGE ready from loans, Earn and the pool as one line, and Collect all takes it with everything else the wallet can collect: one signature where your wallet can send a batch, else one step at a time. It collects every pool position, claims every unlocked drip, then claims each native-engine loan's sGAGE, each Earn strategy's and each vault's.
* **Claim**, on the **Rewards** tab. `REWARDS READY` is the sGAGE unlocked from every drip, with its worth in USDG; under it, what your pool positions have earned but not collected, and what is still to unlock, with its date. Claim runs two things in order and stops at the first step you decline:
  1. **Collect**, one position at a time. Each collect settles the position's pending emissions into a seven-day drip for your wallet; a rollover lump is paid at once.
  2. **Claim**, last. The unlocked part of every drip goes to your wallet.

Collecting does not make the whole amount spendable: only its unlocked portion can be claimed or reinvested. Swap fees are separate; collect them on Uniswap's position page. See [The drip](https://docs.gage.cash/rewards/the-drip.md).

A loan's page keeps its own **Claim** beside `Loan rewards` under **Loan details** (`Claim ›` under `REWARDS · THIS DEAL` on the earlier native engines' pages). An Earn strategy's rewards also have their own claim on the strategy page.

## Reinvest

**Reinvest instead**, beside Claim, opens the REINVEST sheet, the same sheet as Pool's Add liquidity, with your unlocked sGAGE as the amount. Its **PAY WITH** row picks how the position is paid: **sGAGE** (first), **GAGE + sGAGE**, or ETH, USDG or GAGE, the same routes as Pool's Add liquidity. If that sGAGE is still in its drips, the flow claims it first, then approves it, then adds liquidity, one signature each. One amount and one button stay in view.

**GAGE + sGAGE** pairs your unlocked sGAGE with the GAGE already in your wallet: the sGAGE side starts at the unlocked amount, the GAGE side follows the range at the pool price, nothing is swapped and there is no pool fee. The flow claims the sGAGE, approves each token to Permit2 once, then mints or adds in one transaction on a signed permit. Short of GAGE, the notice offers the sGAGE routes instead.

With **sGAGE**, under **Details**:

| Choice   | Options                                                                                                                                                                       |
| -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Route    | **Zap**: use sGAGE only; part is sold in the pool at the 3% fee so the rest pairs. **Match**: buy the GAGE needed to pair with USDG or ETH from your wallet; no sGAGE is sold |
| Position | **New position**, or **Add to #id** for one you hold                                                                                                                          |
| Range    | **Recommended**, a range around the current price, or **Full**, `0 – ∞`                                                                                                       |

This position holds only one asset while the price is outside its range. Rewards accrue while in range; an out-of-range position has zero reward weight when checkpointed. The panel under the choices shows the swap, the pool fee, the minimum received or the maximum paid, the pool and a 1% slippage tolerance; **Refresh quote** renews a quote, which is good for two minutes. Unpaired tokens return to your wallet; gas is paid in ETH.

An existing position keeps its pending rewards. Newly added liquidity earns from its next checkpoint, never a share of earlier emissions.

## This week on Protocol

The Protocol page's **This week's rewards** card is the protocol's week, not yours: when the week ends, the sGAGE it has to share and their split between loans and the pool, and one link, **Your rewards on Portfolio →**. Its More numbers fold holds what is still available to assign to loans on each term, what is still scheduled for the pool, the next weeks' budgets and how rewards reach a wallet. See [Weekly budgets](https://docs.gage.cash/rewards/weekly-budgets.md).

See [Provide liquidity](https://docs.gage.cash/pool/provide-liquidity.md) and [LP score and weekly rewards](https://docs.gage.cash/pool/lp-score.md) for reward eligibility and the difference between position rewards and wallet drips.


---

# 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.gage.cash/rewards/claim-and-reinvest.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.
