KyberSwap Aggregator: scope and trade review

KyberSwap Aggregator finds an execution route across integrated liquidity sources. It is one part of a broader interface, so a page about a pool, a zap or a cross-chain service may describe a different activity from the swap you intend to make.

The aggregator documentation describes access to several source types. These include active limit orders and, on Ethereum, professional market-maker quotes. The result is not necessarily a trade against one pool bearing the KyberSwap name.

Identify the selected product first

The support matrix also separates products. Avoid assuming that a chain supporting one action supports every other action in the interface.

What to inspect in a swap

Confirm the network and token addresses, then look at the route and received amount. If you previously excluded a liquidity source, remember that the new quote may reflect that preference. The provider can only consider sources available under the request's settings.

A larger source list is useful coverage but does not establish a lower cost for this trade. Compare an actual matching quote if price matters; compare the required workflow if you need a particular order type or destination.

Keep fee claims product-specific

A fee statement for cross-chain routing cannot automatically describe a same-chain swap, and an old liquidity-pool fee cannot automatically describe the aggregator. Save the product name with any fee claim you use. That small distinction prevents many misleading comparisons.