> For the complete documentation index, see [llms.txt](https://docs.ston.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ston.fi/developer-section/dex/fees.md).

# Fees

Trading fees on STON.fi - per‑pool configurable fees

## Current Model

* Per‑pool configurable: Trading fees are set per liquidity pool.
* Default: 0.3% total fee: 0.2% to liquidity providers (LPs) and 0.1% to the STON.fi protocol.
* Range: The total fee and its split can be adjusted by the protocol admin within a 0%-1% range.
* Accrual: LP fees accrue to the pool and are realized pro‑rata based on each LP’s share of liquidity.

## Where to See Fees

* App: Each pool’s current fee is visible on its page in the app.
* API/SDK: Fees are also available via the [DEX API](/developer-section/dex/api.md) and [SDK](/developer-section/dex/sdk.md).

## Integrator fees

Direct DEX SDK referral parameters and Omniston RFQ parameters are different surfaces. Direct v2 builders use `referralAddress`/`referralValue` (bps); Omniston API v1beta8 uses destination-chain `integrator_address`/`integrator_fee_pips`. See [Omniston configuration](/developer-section/omniston/referral-fees.md) when the flow comes through aggregation.

### DEX v1 direct payouts

DEX v1 applies a fixed 0.1% referral fee and pays the referrer directly in the swap transaction. Inspect the payout in the transaction's token transfers.

### DEX v2 Vault payouts

DEX v2 accrues referral fees in Vault contracts for withdrawal by the owner. A Vault is identified by its router, owner, and the router's token wallet. Derive its address through the router's `getVault()` or `getVaultAddress()` methods.

Use [Claim integrator fees](/developer-section/dex/sdk/vault-operations.md) for the discover → select router → build withdrawal → send flow. For TON-denominated fees, use the router's pTON minter context. The API [wallet fee-Vault endpoint](/developer-section/dex/api/reference.md#wallet-specific-data) can discover recorded Vaults; the [fee statistics](/developer-section/dex/api/reference.md#fee-statistics) describe v2 Vault datasets.

The direct SDK/API referral rate is measured in basis points. The API's simulation surface accepts 0-100 bps; a positive fee and its effective payout depend on the deployed router and simulation. Pass consistent referral configuration to simulation and transaction building.

You can also inspect the [Vault demo](https://sdk-demo-app.ston.fi/vault) and its [source](https://github.com/ston-fi/sdk/tree/main/examples/next-js-app/app/vault).


---

# 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.ston.fi/developer-section/dex/fees.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.