> For the complete documentation index, see [llms.txt](https://docs.kyberswap.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kyberswap.com/getting-started/fee-schedule.md). # Fee Schedule KyberSwap does not charge a protocol fee for swaps made directly on KyberSwap.com. Each product and service listed below has its own fee structure - these fees are not applied collectively, and only the fee relevant to the specific product being used applies. ### **Introduction** By using the Sites or the Services, a Transaction Fee may be charged for each transaction executed, for the use of or execution of transactions on a blockchain network or in connection with the Services. Therefore, in addition to the network fees associated with their transactions, KyberSwap may charge a Transaction Fee depending on the product being used. The Fee Schedule below provides details of the specific Transaction Fee for each product on KyberSwap. ### **Fee Summary Table**
ProductFee TypeFee RateNote
Swap *No feeNo fee
Limit OrderFixed0.01% - 1%depends on volatility level of the tokens
EarnFixed0.01% - 0.25%
Widget/ iFrameVariableVariableConfigured by protocol using (not by KyberSwap)
Cross-chain SwapFixed0.05% - 0.25%depends on route and volatility level of the tokens
Smart ExitFixed0.025% - 0.3%
Stop MarketFixed0.015% - 1%depends on volatility level of the tokens
Other value-added service (Market Overview, Analytics, Token Checker, and MEV Protection)No feeNo fee
\ \* For Swap (KyberSwap Aggregator), we do not charge a protocol fee. However, positive slippage and dust collector are applied to certain trades. For more information, please refer to [KyberSwap positive slippage surplus collection](/developer-guide/aggregator-api/aggregator-api-specification/evm-swaps.md#kyberswap-positive-slippage-surplus-collection) and [KyberSwap Dust Collector](/developer-guide/aggregator-api/aggregator-api-specification/evm-swaps.md#kyberswap-dust-collector). ### **Product-Specific Fee Details**
Swap KyberSwap does not charge fees to users who trade on [KyberSwap.com](https://kyberswap.com/) or call directly from KyberSwap Aggregator API. Other integrators may apply their own fees, which are configured by the integrators themselves. However, we have positive slippage applied to certain trades. For more information, please refer to [KyberSwap positive slippage surplus collection](/developer-guide/aggregator-api/aggregator-api-specification/evm-swaps.md#kyberswap-positive-slippage-surplus-collection).\ \ **Note:** Other platforms or channels may add their own fees by including fee parameters in kyberswap.com URL. When such fees are applied, they are always displayed transparently on the swap interface. KyberSwap itself does not charge any platform fee for swapping. No platform fee is applied when accessing [KyberSwap.com](https://kyberswap.com/) directly.\ Users are advised to review the fee details on the swap interface when accessing KyberSwap from external sources.
Tip-enabled swap link A tip-enabled swap link is a shareable swap link that allows the person who creates it (the "sharer") to receive an optional tip when other users trade through the link and choose to tip. For example:
* **Anyone can create a tip-enabled link:** Any user can generate a tip-enabled link through the menu located in the top-right corner of the interface, or via .
* **The tip is optional for the user:** When a user makes a transaction through a tip-enabled link, paying the tip is optional. The tip is displayed transparently on the swap interface before the trader confirms the trade. * **Tips go directly to the sharer:** If a user chooses to pay a tip, it is sent in full directly to the wallet address configured by the sharer when the link was created. KyberSwap does not retain any portion of the tip and does not charge a platform fee on swaps made through these links. Users are advised to review the URL and all details on the swap interface before confirming.
Limit Order To support the continued development of the Limit Orders feature, KyberSwap will charge variable taker fees for orders filled on the following chains: * Ethereum (ChainID: 1) * BSC (ChainID: 56) * Arbitrum (ChainID: 42161) * Polygon (ChainID: 137) * Optimism (ChainID: 10) * Avalanche (ChainID: 43114) * Fantom (ChainID: 250) * Base (ChainID: 8453) * ZkSync (ChainID: 324) * Linea (ChainID: 59144) * Mantle (ChainID: 5000) * Scroll (ChainID: 534352) * Blast (ChainID: 81457) The fees charged will be according to the most exotic token in the trading pair. The section below lists the fees whereby the highest fee category will apply based on the classification of the input and output tokens. There are 4 categories of tokens with an additional special category for trades involving KNC. **Super stable (0.01%)** * Ethereum (ChainID: 1) * USDC: [`0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48`](https://etherscan.io/address/0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48) * USDT: [`0xdac17f958d2ee523a2206206994597c13d831ec7`](https://etherscan.io/address/0xdac17f958d2ee523a2206206994597c13d831ec7) * DAI: [`0x6b175474e89094c44da98b954eedeac495271d0f`](https://etherscan.io/address/0x6b175474e89094c44da98b954eedeac495271d0f) * BSC (ChainID: 56) * USDT: [`0x55d398326f99059ff775485246999027b3197955`](https://bscscan.com/address/0x55d398326f99059ff775485246999027b3197955) * USDC: [`0x8ac76a51cc950d9822d68b83fe1ad97b32cd580d`](https://bscscan.com/address/0x8ac76a51cc950d9822d68b83fe1ad97b32cd580d) * DAI: [`0x1af3f329e8be154074d8769d1ffa4ee058b1dbc3`](https://bscscan.com/address/0x1af3f329e8be154074d8769d1ffa4ee058b1dbc3) * BUSD: [`0xe9e7cea3dedca5984780bafc599bd69add087d56`](https://bscscan.com/address/0xe9e7cea3dedca5984780bafc599bd69add087d56) * Arbitrum (ChainID: 42161) * USDT: [`0xFd086bC7CD5C481DCC9C85ebE478A1C0b69FCbb9`](https://arbiscan.io/address/0xFd086bC7CD5C481DCC9C85ebE478A1C0b69FCbb9) * USDC: [`0xaf88d065e77c8cC2239327C5EDb3A432268e5831`](https://arbiscan.io/address/0xaf88d065e77c8cC2239327C5EDb3A432268e5831) * DAI: [`0xDA10009cBd5D07dd0CeCc66161FC93D7c9000da1`](https://arbiscan.io/address/0xDA10009cBd5D07dd0CeCc66161FC93D7c9000da1) * Polygon (ChainID: 137) * USDT: [`0xc2132d05d31c914a87c6611c10748aeb04b58e8f`](https://polygonscan.com/address/0xc2132d05d31c914a87c6611c10748aeb04b58e8f) * USDC: [`0x2791bca1f2de4661ed88a30c99a7a9449aa84174`](https://polygonscan.com/address/0x2791bca1f2de4661ed88a30c99a7a9449aa84174) * DAI: [`0x8f3Cf7ad23Cd3CaDbD9735AFf958023239c6A063`](https://polygonscan.com/address/0x8f3Cf7ad23Cd3CaDbD9735AFf958023239c6A063) * Optimism (ChainID: 10) * USDT: [`0x94b008aa00579c1307b0ef2c499ad98a8ce58e58`](https://optimistic.etherscan.io/address/0x94b008aa00579c1307b0ef2c499ad98a8ce58e58) * USDC: [`0x7f5c764cbc14f9669b88837ca1490cca17c31607`](https://optimistic.etherscan.io/address/0x7f5c764cbc14f9669b88837ca1490cca17c31607) * DAI: [`0xda10009cbd5d07dd0cecc66161fc93d7c9000da1`](https://optimistic.etherscan.io/address/0xda10009cbd5d07dd0cecc66161fc93d7c9000da1) * Avalanche (ChainID: 43114) * USDT: [`0x9702230A8Ea53601f5cD2dc00fDBc13d4dF4A8c7`](https://snowtrace.io/address/0x9702230A8Ea53601f5cD2dc00fDBc13d4dF4A8c7) * USDC: [`0xB97EF9Ef8734C71904D8002F8b6Bc66Dd9c48a6E`](https://snowtrace.io/address/0xB97EF9Ef8734C71904D8002F8b6Bc66Dd9c48a6E) * DAI.e: [`0xd586E7F844cEa2F87f50152665BCbc2C279D8d70`](https://snowtrace.io/address/0xd586E7F844cEa2F87f50152665BCbc2C279D8d70) * USDT.e: [`0xc7198437980c041c805A1EDcbA50c1Ce5db95118`](https://snowtrace.io/address/0xc7198437980c041c805A1EDcbA50c1Ce5db95118) * USDC.e: [`0xA7D7079b0FEaD91F3e65f86E8915Cb59c1a4C664`](https://snowtrace.io/address/0xA7D7079b0FEaD91F3e65f86E8915Cb59c1a4C664) * Fantom (ChainID: 250) * fUSDT: [`0x049d68029688eabf473097a2fc38ef61633a3c7a`](https://ftmscan.com/address/0x049d68029688eabf473097a2fc38ef61633a3c7a) * USDC: [`0x04068DA6C83AFCFA0e13ba15A6696662335D5B75`](https://ftmscan.com/address/0x04068DA6C83AFCFA0e13ba15A6696662335D5B75) * DAI: [`0x8D11eC38a3EB5E956B052f67Da8Bdc9bef8Abf3E`](https://ftmscan.com/address/0x8D11eC38a3EB5E956B052f67Da8Bdc9bef8Abf3E) **Stable (0.02%)** * Ethereum (ChainID: 1) * MAI: [`0x8D6CeBD76f18E1558D4DB88138e2DeFB3909fAD6`](https://etherscan.io/address/0x8D6CeBD76f18E1558D4DB88138e2DeFB3909fAD6) * BOB: [`0xB0B195aEFA3650A6908f15CdaC7D92F8a5791B0B`](https://etherscan.io/address/0xB0B195aEFA3650A6908f15CdaC7D92F8a5791B0B) * MIM: [`0x99D8a9C45b2ecA8864373A26D1459e3Dff1e17F3`](https://etherscan.io/address/0x99D8a9C45b2ecA8864373A26D1459e3Dff1e17F3) * BSC (ChainID: 56) * MAI: [`0x3F56e0c36d275367b8C502090EDF38289b3dEa0d`](https://bscscan.com/address/0x3F56e0c36d275367b8C502090EDF38289b3dEa0d) * BOB: [`0xB0B195aEFA3650A6908f15CdaC7D92F8a5791B0B`](https://bscscan.com/address/0xB0B195aEFA3650A6908f15CdaC7D92F8a5791B0B) * MIM: [`0xfE19F0B51438fd612f6FD59C1dbB3eA319f433Ba`](https://bscscan.com/address/0xfE19F0B51438fd612f6FD59C1dbB3eA319f433Ba) * Arbitrum (ChainID: 42161) * MAI: [`0x3F56e0c36d275367b8C502090EDF38289b3dEa0d`](https://arbiscan.io/address/0x3F56e0c36d275367b8C502090EDF38289b3dEa0d) * MIM: [`0xFEa7a6a0B346362BF88A9e4A88416B77a57D6c2A`](https://arbiscan.io/address/0xFEa7a6a0B346362BF88A9e4A88416B77a57D6c2A) * Polygon (ChainID: 137) * MAI: [`0xa3Fa99A148fA48D14Ed51d610c367C61876997F1`](https://polygonscan.com/address/0xa3Fa99A148fA48D14Ed51d610c367C61876997F1) * BOB: [`0xB0B195aEFA3650A6908f15CdaC7D92F8a5791B0B`](https://polygonscan.com/address/0xB0B195aEFA3650A6908f15CdaC7D92F8a5791B0B) * MIM: [`0x49a0400587A7F65072c87c4910449fDcC5c47242`](https://polygonscan.com/address/0x49a0400587A7F65072c87c4910449fDcC5c47242) * Optimism (ChainID: 10) * MAI: [`0xdFA46478F9e5EA86d57387849598dbFB2e964b02`](https://optimistic.etherscan.io/address/0xdFA46478F9e5EA86d57387849598dbFB2e964b02) * BOB: [`0xB0B195aEFA3650A6908f15CdaC7D92F8a5791B0B`](https://optimistic.etherscan.io/address/0xB0B195aEFA3650A6908f15CdaC7D92F8a5791B0B) * Avalanche (ChainID: 43114) * MAI: [`0x5c49b268c9841AFF1Cc3B0a418ff5c3442eE3F3b`](https://snowtrace.io/address/0x5c49b268c9841AFF1Cc3B0a418ff5c3442eE3F3b) * YUSD: [`0x111111111111ed1D73f860F57b2798b683f2d325`](https://snowtrace.io/address/0x111111111111ed1D73f860F57b2798b683f2d325) * MIM: [`0x130966628846BFd36ff31a822705796e8cb8C18D`](https://snowtrace.io/address/0x130966628846BFd36ff31a822705796e8cb8C18D) * Fantom (ChainID: 250) * MAI: [`0xfB98B335551a418cD0737375a2ea0ded62Ea213b`](https://ftmscan.com/address/0xfB98B335551a418cD0737375a2ea0ded62Ea213b) * MIM: [`0x82f0B8B456c1A451378467398982d4834b6829c1`](https://ftmscan.com/address/0x82f0B8B456c1A451378467398982d4834b6829c1) **Normal (0.1%)** * Top 50 tokens by market cap (identified via multiple on and off-chain services), excluding tokens under the super stable, stable, and KNC categories. **Exotic (0.3%)** * All remaining tokens not covered in the super stable, stable, normal, and KNC categories. **High Volatility (0.5%)** * Tokens that have been added in the Token Catalog from 2 weeks to 1 month. **Super High Volatility (1%)** * Tokens that have been added in the Token Catalog for less than 2 weeks. **KNC (0.1%)** * Trades to and from KNC will be charged a flat 0.1% fee.
Earn There are two types of fees incorporated into the Zap API:\ \ **Protocol fees** Protocol fees are charged by KyberSwap in input token for Zap. In feature, and are based on 4 different token pair categories: | Pair Category | Protocol Fee | | --------------- | ------------ | | Stable pair | 0.01% | | Correlated pair | 0.025% | | Common pair | 0.1% | | Exotic pair | 0.25% | * Please refer to the example file below for a list of PancakeSwap v3 pools for each of the category above. PancakeSwap v3 pools not in the list belongs to the "Exotic pair" category.
**Partner fees** * Partner fee configuration is sent by the partner client via the API to charge a partner fee on top of the protocol fees * Similar to protocol fees, partners will only be able to charge the fee by the input token for Zap In. * Provides both a valid non-zero feeAddress and a positive integer feePcm (the unit is per cent mille, i.e. 1-1000th of 1%) in the API call to [GetRoute](broken://pages/Us7l8h6mTydXM419G26f#get-route). Otherwise, no fee will be collected for partner.
Widget/ iFrame The Widget/iFrame fee structure is **not applied universally across all integrations**; it depends on the specific protocols using it. These fees are not technically charged by KyberSwap—instead, they are configured by the partner protocols themselves. KyberSwap provides the underlying infrastructure that enables these protocols to implement and manage their custom fee customizations. For further details, refer to [Widget/iFrame Fee](/developer-guide/aggregator-api/how-to-guides/kyberswap-widget/widget-iframe-fee.md). Users trading directly on [KyberSwap.com](http://kyberswap.com/) UI are not subject to this fee structure.
Cross-chain Swap To support the continued development and maintenance of the Cross-Chain Swap, KyberSwap applies a platform fee for using this feature. Below is the detailed fee structure:
RouteStable tokens & Same native tokenCommonExoticHigh-volatility
EVM ↔ EVM0.05 %0.10 %0.15 %0.25 %
Near ↔ EVM0.1%0.2%0.2%0.2%
Solana ↔ EVM0.1%0.2%0.2%0.2%
BTC ↔ EVM0.25 % 0.25 % 0.25 % 0.25 %
Non-EVM ↔ Non-EVM0.25 %0.25 % 0.25 % 0.25 %
Smart Exit To support the continued development and maintenance of the Smart Exit, KyberSwap applies a platform fee for using this feature. When reviewing a Smart Exit order, the applicable platform fee is displayed as “Platform Fee” in the Confirmation section before the order is confirmed.
Pair CategoryPlatform Fee
Stable pair0.025 %
Correlated pair0.05%
Common pair0.15%
High volatility pair0.75 %
Exotic pair0.3 %
Stop Market The fee is a single charge covering two things: the KyberSwap fee for the order, which is set by the token pair, and the network gas for executing the swap on-chain. ### **How the fee is calculated** The fee rate applied to an order is the greater of two figures: the tier rate for the pair, and the rate that the chain's minimum fee represents for an order of that size. ``` feeRate = max( tierRate , minFee / orderValueAtTrigger ) // fixed when the order is placed feeAmount = feeRate × amount received from the swap // charged at execution ```
TermMeaning
tierRateThe pair's rate from the table below
minFeeThe chain's minimum fee, in its native token
orderValueAtTriggerWhat the order is worth if it is executed exactly at your trigger price, in the same unit as minFees
The fee is charged in the token you receive, converted from this amount at the execution price.
TierRate
Super stable0.015%
Correlated0.05%
Normal0.15%
Exotic0.3%
High volatility0.5%
Super high volatility1%
### **When the fee is a large share of a small order** There is no minimum order size for a Stop Market order, and a small order is never blocked. Instead, the Fee (incl. gas) tooltip in the confirmation box sets this out when both of these are true: * the minimum fee applies — it is higher than the tier rate would give, and * the fee is more than **5%** of your order value Both conditions matter. An order paying the tier rate is paying exactly the published rate, however large it is, so the tooltip does not carry this warning. It is there to tell you that the minimum has pushed your fee above the rate in the table. The gas-spike clause appears because an order paying the minimum has the least headroom — see below. ### **Minimum fee by chain** The minimum is set in each chain's native token, not in US dollars. The cost it covers is gas, which is paid in the native token, so a minimum denominated the same way tracks it automatically as the native price moves. | Chain | **Minimum** | | --------- | ----------- | | Base | 0.00005 ETH | | Optimism | 0.00005 ETH | | Arbitrum | 0.00005 ETH | | Polygon | 2 POL | | BSC | 0.0003 BNB | | Ethereum | 0.001 ETH | | Robinhood | 0.00005 ETH | | Hyper EVM | 0.002 HYPE | | Avalanche | 0.015 AVAX | #### **Why a minimum exists** Most of the gas used to execute a Stop Market order is fixed overhead — the routing, the on-chain hook, and the Oracle price update — and does not scale with the size of the order. A $20 order costs nearly as much to execute as a $20,000 one, for example. The minimum reflects that fixed cost. It is not a surcharge on small orders. #### When network gas is unusually high The fee covers the on-chain execution cost, so an attempt is skipped when the estimated gas for that fill would exceed **90%** of the fee it would collect. Nothing is cancelled: the order stays in your Active Orders, shows as **Retrying**, and is attempted again once gas settles. A separate safeguard covers larger shifts. When network gas rises far above its recent baseline, execution pauses rather than proceeding at a loss, and orders hold in **Retrying** until it comes down. Small orders are the most likely to wait during a gas spike, because their fee covers less gas. Where an order is paying the minimum fee, the **Fee (incl. gas)** tooltip in the confirmation box sets this out for you to review before you sign - see [When the fee is a large share of a small order](#when-the-fee-is-a-large-share-of-a-small-order).
*Additional notes:* *\*For Third Party Integrated Services, users are responsible for complying with the third party's fee schedule.* *\*\*This Fee Schedule may be updated from time to time by KyberSwap. Please refer to our Terms of Use for further details.* --- # 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.kyberswap.com/getting-started/fee-schedule.md?ask=&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.