# Auto-Claim Fees

## Overview

The Auto Claim Fees feature allows you to automate the collection and reinvestment of trading fees earned from your liquidity positions. This powerful tool helps you maximize returns by automatically handling fee claims and executing predefined actions with the claimed tokens.

You can find it on the top-right corner of the Strategy Creation timeline.

## Core Settings

### Enable Auto Claim

* Toggle to activate or deactivate the automated fee claiming system.
* When disabled, fees must be claimed manually.

### Claim Frequency

Choose how often fees will be automatically claimed:

* **Every 15 Minutes**: Most aggressive frequency for high-volume pools.
* **Every 30 Minutes**: Balanced frequency for active pools.
* **Every Hour**: Standard frequency for most pools.
* **Every 3 Hours**: Conservative frequency for lower-volume pools.

## After Claiming Options

We provide a flexible workflow for handling claimed fees:

### Primary Action

* **Do Nothing**: Claimed tokens remain in your wallet.
* **Swap to \[Token X/Y]**: Convert all claimed tokens to a single token type.
* **Swap \[Token X/Y] to USDC**: Convert one token type to USDC stablecoin.
* **Add as Liquidity**: Reinvest fees directly back into the liquidity pool.

### Secondary Action (After Swapping)

When a swap action is selected, you can configure what happens next:

* **Do Nothing**: Keep swapped tokens in your wallet.
* **Add as Liquidity**: Reinvest swapped tokens back into the liquidity pool.

### Slippage Settings

Different operations have separate slippage controls for fine-tuned risk management:

* **Swap Slippage**: Controls price movement tolerance during token swaps.
* **Add Liquidity Slippage**: Controls price movement tolerance when adding liquidity directly.
* **Post-Swap Liquidity Slippage**: Controls price movement tolerance when adding liquidity after a swap.

## Liquidity Configuration

### Liquidity Type Options

When adding liquidity (either directly or after swapping), choose the position type:

* **Two-sided (Balanced)**: Use both token types in equal value proportions.
* **Token X Only**: Create a one-sided position with only Token X.
* **Token Y Only**: Create a one-sided position with only Token Y.

### Liquidity Source (After a Swap)

When adding liquidity after swapping, choose which tokens to include:

* **Swapped Tokens Only**: Use only the tokens received from the swap operation.
* **Swapped + Original Tokens**: Combine newly swapped tokens with originally claimed tokens.

## Use Case Examples

### Compound and Grow

* **Configuration**: Claim hourly → Add as Liquidity → Two-sided
* **Result**: Automatically reinvests earned fees back into your position, compounding returns over time.

### Stablecoin Accumulation

* **Configuration**: Claim every 3 hours → Swap \[Token X/Y] to USDC → Do Nothing
* **Result**: Regularly converts earned fees to USDC, reducing exposure to volatility while keeping profits.

### Hybrid Strategy

* **Configuration**: Claim every 30 minutes → Swap to \[Token X] → Add as Liquidity (One-sided)
* **Result**: Concentrates all earned fees into one side of the pool, which can be beneficial in trending markets.

By effectively configuring the Auto Claim Fees settings, you can create a passive income system that continuously collects, reinvests, and optimizes your liquidity position rewards with no manual intervention required.


---

# Agent Instructions: 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:

```
GET https://liquid-nova.gitbook.io/liquid-nova/strategy-steps/auto-claim-fees.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.