Network guides
Comparing DEX aggregators on BNB Chain, including Tirio
Compare BNB Chain aggregator routes with the correct network, BNB gas, quote limits and documented Tirio features.
Read article →Jupiter on Solana: routes, swap modes and transaction costs
Understand Jupiter routing on Solana and separate platform fees, network fees, priority fees and execution settings.
Establish the Solana asset first
Jupiter provides swap routing for Solana assets. When comparing a route, identify token mint addresses rather than relying only on tickers. A familiar name or image does not establish that two listed assets are the same token.
Record the input amount, expected output, minimum received and time of the quote. A route for a small amount can differ from a route for a larger amount because the available liquidity and price impact change. A cached daily volume ranking cannot answer which route is currently available for your trade.
Routing can combine several sources
Jupiter's Metis routing supports multi-hop paths and splitting across liquidity sources. A route may pass through an intermediate token instead of using a direct pool. More sources can expand the options, but they do not guarantee that every trade has a competitive path or can settle successfully.
The current developer Swap API distinguishes a multi-engine Meta-Aggregator from Metis-only Router integration. That distinction matters when researching an integration: a developer endpoint, a routing engine and a consumer interface are not interchangeable names for one execution path. Use the documentation for the product actually being compared.
Check the user-facing mode
Jupiter's user documentation distinguishes Ultra and Manual trading settings. Its fee and MEV descriptions depend on those modes and, in some cases, the pair or execution configuration. Do not apply an older API fee schedule to every trade in the current interface.
Keep platform commission separate from Solana transaction costs. Network fees, priority fees and a Jito tip are different components. A mode described as having no platform commission can still incur network-related costs. Conversely, a mode that manages those costs for the user may include them in its quoted result rather than requesting a separate payment.
Record the conditions behind the output
Check the quote's minimum received, route and settings before confirming a transaction. If a priority setting changes, record the revised cost when comparing two quotes. A larger expected output is not automatically a better net outcome if its execution costs differ.
MEV protection should be read with the mode and delivery conditions documented by Jupiter. A protection setting is not a promise that market prices will remain unchanged or that a transaction cannot fail. If the interface cannot produce a quote for the amount, keep the result unavailable instead of extrapolating from a smaller trade.
Use directory statistics for context
Jupiter's reported activity can show how the source tracks routed trading, but it does not show the number of unique people or a particular swap's price. Combine the platform comparison with the official quote when execution research is the goal. The directory remains a reference tool rather than a wallet or trading terminal.
Official references
Reviewed on 2 October 2026:
