> For the complete documentation index, see [llms.txt](https://docs.fuul.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fuul.xyz/core-concepts/types-of-rewards/automated-claims.md).

# Automated Claims

Token rewards normally sit as claim checks until someone submits a transaction. Automated Claims closes that loop for you: on a schedule you set, Fuul submits the claim transactions for your users and sponsors the gas, so recipients receive tokens without doing anything.

{% hint style="success" %}
Tokens settle **directly to the recipient** in each claim check. Fuul never takes custody of your funds at any point in the process.
{% endhint %}

## Three ways tokens reach a wallet

Automated Claims is one of three options. They are not exclusive, and most programs use more than one:

| Option               | Who submits the transaction | Who pays gas             | Best for                                                             |
| -------------------- | --------------------------- | ------------------------ | -------------------------------------------------------------------- |
| **User claims**      | The end user                | The end user             | Default. Users who are already onchain-native                        |
| **Claim on behalf**  | Your project, ad hoc        | Your project             | One-off pushes, a campaign wrap-up, VIP users                        |
| **Automated Claims** | Fuul, on a schedule         | Fuul, billed back to you | Ongoing programs where you want claiming to disappear as a user step |

{% hint style="warning" %}
Claim checks do **not** distribute automatically unless one of these is in place. A common misconception is that payouts are pushed to wallets by default. They are not: a reward becomes a claim check, and a claim check needs a transaction.
{% endhint %}

## How it works

1. Your project opts in and Fuul approves it
2. You set a cadence, plus a day of the week for weekly runs
3. On each scheduled run, Fuul collects the project's available claim checks, batches them into claim transactions, and submits them onchain
4. Each run records which users were claimed for, the per-currency amounts distributed, and what the run cost

Automated Claims sits on top of the existing claim pipeline. It does not change how payouts or claim checks are created, only how they get redeemed. See [Types of Rewards](/core-concepts/types-of-rewards.md) for how claim checks are generated in the first place.

## Configuration

Projects configure this from the **Automated Claims Hub**, at **Activity → Reward Payouts → Automate claims**.

| Setting            | Description                                                                          |
| ------------------ | ------------------------------------------------------------------------------------ |
| **Master toggle**  | Turns automated claiming on or off for the project                                   |
| **Cadence**        | How often runs happen. Weekly runs also take a day of the week                       |
| **Native fee cap** | Upper bound on native token spend per run, so a single run cannot exceed your budget |

The Hub also shows metric cards and a paginated run history, with the claim batches for each run.

{% hint style="info" %}
Enabling the toggle is not sufficient on its own. A run executes only once the project is both enabled and approved by Fuul. Contact <ecosystem@fuul.xyz> to get set up.
{% endhint %}

## Costs

Fuul sponsors two things per transaction: the network gas, and the protocol's `nativeUserClaimFee`. Both are metered per run, converted to USD, and accumulated into a monthly per-project total for billing and reconciliation.

Your `native_fee_cap` bounds native spend per run. If a run would exceed it, it stops at the cap rather than continuing.

## Availability and limitations

|                       | Status                                                                                                          |
| --------------------- | --------------------------------------------------------------------------------------------------------------- |
| **Networks**          | EVM only                                                                                                        |
| **Per-currency caps** | Not available. The cap applies to native spend per run, not to how much of any given reward currency goes out   |
| **Cost reporting**    | Run cost is shown as a single combined figure. Gas and the protocol fee are not broken out separately in the UI |

{% hint style="warning" %}
If your program pays on a chain where no project has run the relayer before, treat it as a first-time enablement rather than a toggle. Confirm timing with the Fuul team before committing a launch date to your users.
{% endhint %}

## Related

* How claim checks are created and what the voucher model buys you → [Types of Rewards](/core-concepts/types-of-rewards.md)
* Keeping the pool funded so runs don't fail → [Budgets & Smart Contracts](/core-concepts/budgets-and-smart-contracts.md) and [Rewards Pool Budget Alerts](/core-concepts/budgets-and-smart-contracts/budget-alerts.md)
* Building your own claim button instead → [Claim Flow Integration](/developer-guide/claim-frontend.md)