A same-chain exchange suits a task whose input and intended output belong to the same network. You choose the token pair, amount, and network; Transit Swap aggregates DEX liquidity for the exchange. If the output must reach another blockchain, cross-chain exchange addresses that additional network requirement.

Cross-chain exchange fits a task requiring the destination asset on a different network from the input asset. Transit Swap covers EVM-compatible and non-EVM ecosystems; the Swap & Cross-Chain network dropdown lists supported networks.

Network support alone does not establish an available route for every token pair. Stop before submitting an exchange if no available route matches the intended assets and destination.

The API fits software needing swap quotes and ABI data for contract interaction. For documented Router v3 aggregation, inputs include token addresses, decimals, amountIn , chain , and destination-token recipient to , alongside other required request parameters.

amountIn uses the selling token’s base units, so the integration must account for its decimals. Use the API version’s supported-chain list when planning an integration; platform-wide network coverage has a different scope.

View image file

The response’s totalAmountOut estimates the destination-token amount, while data supplies ABI data for the router contract. An API success response returns swap data; it does not establish transaction completion. The swap application is the relevant alternative when you need an individual exchange without building a software integration.

Web Market fits questions about token trading activity before an exchange becomes the immediate task. Holder information, PNL, volume, and candlestick charts support that assessment, with TradingView supplying the charting technology.

A chart describes market activity; a swap quote estimates output for a particular exchange. Use swap functionality when the task becomes token exchange, and assess route availability for the intended assets and networks.

• Confirm whether the output token must remain on the source network or reach another supported network.
• Require a route matching the chosen assets and networks before moving beyond quote assessment.
• For an integration, match the API version, chain support, token units, and destination-token recipient.