Why an aggregator cannot create missing liquidity

An aggregator cannot sell a token unless an eligible execution source will accept it and supply the requested output. Discovering more venues helps only when those venues contain usable liquidity or executable offers.

A route needs more than a token listing

A token can appear in a wallet or data service without having a market deep enough for your order. A displayed price might come from a very small pool, an old trade or another location. None of those observations guarantees that the amount you want to exchange can be filled.

Uniswap's pool explanation makes the underlying dependency clear: token exchange consumes actual pool inventory under the pricing rule. The aggregator can select that inventory; it cannot replace missing reserves with a price label.

Three different limits

• No connected market: no eligible source links the asset to your desired output, directly or through intermediaries.
• Insufficient useful size: a path exists, but the requested amount would produce unacceptable terms or violate a venue limit.
• Unsupported behavior: a source or token may exist onchain yet fall outside the aggregation service's integrations.

These are different explanations. A missing quote from one application does not prove the token has no market anywhere. Equally, finding one pool does not prove it can support a meaningful sale.

Consider a hypothetical pool holding 10 units of the output token. A user asking for 1,000 output units cannot obtain them from that pool through clever path selection. Splitting across other empty pools also does not solve the inventory shortage.

When assessing the statement “this token is tradable,” specify the network, asset contracts, trade direction and size. Liquidity is a capacity under conditions, not a permanent yes-or-no property. This page concerns that market limitation; token restrictions and suspicious contract behavior require a separate security assessment.