Answered from live records · 2026-09-15
What fee does Sato Swap charge, and who receives it?
Sato Swap takes 3 bps when both legs are stablecoins it recognises and 15 bps otherwise, to the Sato fee address, inside the venue's own router. Several venues keep a share; each says so, as of 2026-09-15.
The rate is a parameter on the venue's own quote and is stated before anything is signed. A failed, reverted or unsigned trade pays nothing. 5 of the 9 adapters carry a qualifier, because on those venues the flat sentence is not the whole truth — each one below is quoted from that venue's own documentation, and none of these numbers is observed by us. Fee recipient: 0xcEE53Eb001d4d1743EF9df333Dcf45bC38622bE9.
| Venue | Qualifier on the fee sentence |
|---|---|
| 0x-protocol | No qualifier: the flat sentence is true here — 3 bps stable-to-stable, 15 bps when either leg is volatile, taken on the input leg by the venue's own router. |
| 1inch | No qualifier: the flat sentence is true here — 3 bps stable-to-stable, 15 bps when either leg is volatile, taken on the input leg by the venue's own router. |
| jupiter-aggregator | No qualifier: the flat sentence is true here — 3 bps stable-to-stable, 15 bps when either leg is volatile, taken on the input leg by the venue's own router. |
| odos | On Odos the fee is deducted from the OUTPUT tokens of the swap, not the input leg, and Odos forwards 80% of it to the recipient and retains 20% (docs.odos.xyz/home/api-monetization). The rate above is the rate sent, not the rate received. |
| kyberswap | No qualifier: the flat sentence is true here — 3 bps stable-to-stable, 15 bps when either leg is volatile, taken on the input leg by the venue's own router. |
| relay | On Relay an app fee does not move on-chain to the recipient: it accrues as an off-chain USDC balance that must be claimed (docs.relay.link/features/app-fees). Until it is claimed it is receivable, not received, and an empty paidAppFees on the executed trade means it was not collected at all. |
| debridge | On deBridge DLN the affiliate fee is paid only when the order is unlocked on the source chain, after a fill and only if the order is fulfilled (docs.debridge.finance). Until then it is receivable, not received. |
| lifi | On LI.FI the fee is collected at execution and forwarded to the fee recipient minus LI.FI's own 0.25% and a further volume-dependent share LI.FI does not publish (docs.li.fi). The net share reaching the recipient is unknown, not the rate above. |
| cow | On CoW the partner fee is taken in the surplus token and capped at 100 bps; CoW DAO retains 25% of it and pays the rest weekly in WETH, with amounts under 0.001 WETH forfeited (docs.cow.fi/governance/fees/partner-fee). The rate above is the rate sent. |
How this was answered
feeBpsFor() and VENUE_FEE_QUALIFIERS in lib/route/fees.ts. The rate is the published schedule; each venue's qualifier is quoted verbatim from the constant the adapter sends the fee with, so prose here cannot drift from the fee that is actually charged.
Every answer on this page is produced by one named function over Sato Hub's live records on the date shown. Nothing is typed by hand, no figure is carried over from a previous day, and an answer with nothing behind it says unknown rather than zero. The Sato Score measures how open, active and verifiable a project is — it is not a safety, quality or returns grade.
Go deeper
More questions
Sources — the projects' own repositories and docs
Cite this page
Sato Hub. "What fee does Sato Swap charge, and who receives it?." Sato Hub, updated 2026-09-15, accessed 2026-09-16. https://satohub.ai/answers/what-fee-does-sato-swap-charge-and-who-receives-itData last refreshed 2026-09-15; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0 and the machine-readable copy is linked in the page's Dataset metadata.