> 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/fuul-mcp-server/managing-incentives/editing-incentives.md).

# Editing Incentives

The Fuul MCP lets you inspect and update incentive configurations directly from your AI assistant — including payout amounts, who gets rewarded, and the reward calculation strategy.

{% hint style="warning" %}
Changes made via MCP are saved as **drafts**. They do not take effect in production until you go to **app.fuul.xyz → Incentives → Publish**.
{% endhint %}

## 1. Find your project and incentives

> "Find my project called Fuul and list our current configured incentives"

## 3. Edit payout amounts

You can target individual incentives or apply a change across all of them.

### Change a specific amount

| Goal                        | Example prompt                                                   |
| --------------------------- | ---------------------------------------------------------------- |
| Update end user payout only | "Set the end user payout for \[incentive name] to 5"             |
| Update referrer payout only | "Set the referrer payout for \[incentive name] to 10"            |
| Update both                 | "Double the end user and referrer payouts for \[incentive name]" |

{% hint style="info" %}
Only applies to incentives where `payee_type` is `affiliate` or `both`. If the incentive only rewards end users, you'd need to change the `payee_type` first.
{% endhint %}

### Bulk-adjust all incentives by a percentage

Useful when you want to align all reward amounts with a target APR or a program-wide budget change:

> "Reduce all incentive payouts by 20%"

## 4. Change who gets rewarded

Each incentive has a `payee_type` that controls which party receives the reward. You can change it at any time:

| Value       | Who gets rewarded       |
| ----------- | ----------------------- |
| `both`      | End user and referrer   |
| `end-user`  | End user only           |
| `affiliate` | Referrer/affiliate only |

Example prompts:

> "Update \[incentive name] to only reward referrers"

> "Change \[incentive name] to reward end users only with 15 points"

> "Set \[incentive name] to reward both sides — 2 points for end users, 6 for referrers"

## 5. Change the calculation strategy

The `calculation_strategy` controls how the reward amount is interpreted:

| Strategy            | Behavior                                                                                                                                                                                                                    |
| ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `variable`          | Amount is a **rate per unit of volume** (e.g. points per USD traded). Requires a `base_currency`.                                                                                                                           |
| `fixed`             | Amount is a **flat reward per conversion** regardless of volume.                                                                                                                                                            |
| `proportional_pool` | A fixed total budget is split among participants proportionally to their contribution (volume, revenue, or conversion count) over a period. See [Pool Distribution](/core-concepts/incentive-payouts/pool-distribution.md). |
| `leaderboard`       | Users are ranked by activity over a date range; each position or range of positions receives a predetermined reward. See [Leaderboard Rewards](/core-concepts/incentive-payouts/leaderboard-rewards.md).                    |

Example prompts:

> "Switch \[incentive name] from variable to fixed rewards, keep 15 points for end users"

> "Change \[incentive name] to variable at 6 points per USD for referrers"

> "Set up a pool distribution for \[incentive name] with a 10,000 point budget split by volume"

> "Configure \[incentive name] as a leaderboard competition — 1st place gets 1,000 points, 2nd gets 500, 3rd–10th get 100 each"

{% hint style="info" %}
When switching from `variable` to `fixed`, the `base_currency` field is automatically removed — it only applies to variable rewards. Pool and leaderboard strategies have additional required fields (budget, date range, rank configuration) that the MCP will prompt you for.
{% endhint %}

## 6. Publish to production

After editing, **draft changes are not live until published**. Go to the app and publish:

1. Open [app.fuul.xyz](https://app.fuul.xyz)
2. Navigate to your project → **Incentives**
3. Click **Publish**

All changes will take effect immediately after publishing.

{% hint style="success" %}
You can review all pending draft changes in the Incentives section before publishing — useful to double-check a bulk update before it goes live.
{% endhint %}


---

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

```
GET https://docs.fuul.xyz/fuul-mcp-server/managing-incentives/editing-incentives.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.