> ## Documentation Index
> Fetch the complete documentation index at: https://docs.enso.build/llms.txt
> Use this file to discover all available pages before exploring further.

# Fees

> Earn a fee on the trades your users route through Enso, configured in the developer portal.

export const date_0 = "2026-10-05"

Fee capture lets you charge a fee on the transactions your integration quotes through Enso. You configure it once in the [developer portal](https://developers.enso.build); Enso then applies it to the transactions quoted with your API key and delivers your share on-chain in the same transaction. No request parameters are needed.

<Note>
  The portal walks you through each step and shows your current configuration. This page is an orientation; the portal is the source of truth for your account.
</Note>

## Set up

<Steps>
  <Step title="Activate fee capture">
    Open the [developer portal](https://developers.enso.build) and go to the **Fees** tab.
  </Step>

  <Step title="Sign the fee agreement">
    Review and sign the fee agreement for your account.
  </Step>

  <Step title="Set a payout wallet">
    Enter the wallet that should receive your share of the fees.
  </Step>

  <Step title="Add fee rules">
    Add one or more rules that set the fee for the trades they match.
  </Step>
</Steps>

## How rules resolve

A rule applies to one of four scopes: **all trades**, a **chain**, a **token**, or a **token pair**. When several rules match a trade, the most specific one wins:

1. Token pair
2. Token
3. Chain
4. All trades

A rule can optionally vary by trade size, using USD value ranges. Ranged rules also have a default fee, which applies when a trade's USD value can't be determined.

## Split and payout

The fee is split between you and Enso at the ratio recorded for your account (50/50 by default). The **Fees** tab shows your split and includes a calculator.

Fees are paid out in the same transaction that executes the trade, directly to your payout wallet. On chains where Enso operates a dedicated splitter contract for your account, the whole fee goes to that contract instead and is distributed according to its on-chain shares when the contract's `claim()` or `claimERC20(tokens)` function is called. Claiming is permissionless: anyone can call it, and the caller pays the gas.

## When changes take effect

Changes apply to newly quoted transactions, typically within about a minute. Transactions that were already quoted keep the fee they were quoted with.

## Fees in API responses

Route and Quote responses report the fee charged on the transaction:

* `feeAmount`: the fee amount charged for each input token.
* `feeBreakdown`: one entry per fee recipient, with `role` (`partner`, `enso-share`, or `splitter`), `token`, `receiver`, `bps`, and `amount`.
* `ensoFeeAmount`: Enso's own platform fee, where it applies under your agreement.

For example, a 20 bps rule with a 50/50 split on a 1,000 USDC trade:

```json theme={null}
"feeBreakdown": [
  {
    "role": "partner",
    "token": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
    "receiver": "<your payout wallet>",
    "bps": "10",
    "amount": "1000000"
  },
  {
    "role": "enso-share",
    "token": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
    "receiver": "<Enso fee collector>",
    "bps": "10",
    "amount": "1000000"
  }
]
```

When a splitter contract receives the fee, the breakdown has a single `splitter` entry for the whole fee.

<div className="text-right text-xs gray-200 font-semibold w-full" style={{marginTop: '0'}}>
  <p style={{
        color: "#b2b2b2"  
    }}>Updated {date_0}</p>
</div>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.