Where liquidity lives
See which pools actually hold depth for a token today — useful when the "main pool" on a chart isn't where size gets filled.
PLATFORM 6 · SOLANA SWAP NETWORK
Aggregators split a single order across many pools and hop through intermediate tokens to find more output. RouteCraft asks Jupiter for a live quote and draws the journey as a transit map — every line, every interchange, every split.
Live Jupiter quote for 1 SOL, refreshed every 20 s while this tab is visible.
Line 1 · The planner
Type a token symbol or paste a mint address. RouteCraft fetches a live Jupiter quote and draws what the router would do right now. Nothing is signed or sent.
Pick an example journey or enter your own to draw the map.
Line 2 · How it works
Symbols are looked up with Jupiter's token search (verified tokens preferred), giving each mint's address and decimals so "10 SOL" becomes 10,000,000,000 lamports.
Your browser calls Jupiter's public quote endpoint with the amount and slippage. The answer lists every leg: venue, pool address, input and output amounts, and what share of the tokens at that station take that line.
RouteCraft turns legs into a graph: tokens are stations, pools are lines. It works out how much of your original order flows through each line, then lays the stations out left to right by hop.
Line thickness is the share of your order. Optionally a second quote restricted to direct (single-pool) routes shows what all the splitting and hopping earns you.
Line 3 · Uses
See which pools actually hold depth for a token today — useful when the "main pool" on a chart isn't where size gets filled.
Run the size sweep: small orders often go through one pool, large ones fan out over many lines and through USDC or SOL.
Impact is shown next to the route that causes it, so you can see whether a big number comes from a thin hop.
The direct-only comparison puts a number on what routing across venues earns versus the best single pool.
Meet the AMMs behind the label: constant-product pools, concentrated liquidity, DLMM bins and proprietary market makers.
A drawn map beats a JSON blob. Use RouteCraft to show a friend why their swap touched five protocols.
Line 4 · Routing guide
Every AMM pool prices along a curve: the more you buy from it, the worse the next unit gets. An aggregator such as Jupiter compares many pools at once and splits your order so that the last unit filled in each pool costs about the same. Two pools of similar depth will usually each take about half; a deep pool next to a shallow one takes most of the flow. That split is the "percent" you see on each line.
The deepest markets on Solana are against SOL and USDC. Swapping JUP to WIF directly may only have a thin pool, but JUP→USDC and USDC→SOL→WIF can each be very deep. A multi-hop route trades a little extra fee per hop for much less price impact. Each intermediate token is an interchange station on the map.
In a Jupiter quote, each leg's percent is the share of the tokens sitting at that leg's input station, not of your original order. If 6% of your SOL goes to USDT and 100% of that USDT goes on to USDC, the second leg carries 100% of a 6% slice. RouteCraft multiplies these through so line thickness shows share of the whole order.
Price impact is how much worse your quoted rate is than the current market price, caused by your own order moving the curves. Slippage tolerance is a safety limit you choose: if the price moves against you between quote and execution by more than that, the transaction fails instead of filling. The quote's otherAmountThreshold is the minimum output after applying slippage.
Labels in a route are Jupiter's names for on-chain programs. Some are classic constant-product AMMs (Raydium AMM and CPMM, PumpSwap), some concentrated-liquidity (Orca Whirlpool, Raydium CLMM), some bin-based (Meteora DLMM). Many of the newer high-volume labels are proprietary AMMs operated by market makers, which update their quotes from off-chain prices every slot. All are just programs holding reserves — RouteCraft shows the pool address so you can check each one.
A quote is computed from pool states at a specific slot (shown as contextSlot). Solana produces a new slot roughly every 400 ms, so the same request a few seconds later can return a different split. That's normal — the router is chasing a moving target.
Line 5 · Questions
No. RouteCraft is read-only. There's no wallet connection and nothing is signed. Use the quote as information and swap wherever you normally do.
It's the route Jupiter's public quote API returns at that moment for those parameters. Wallets and apps may use different settings (excluded venues, platform fees, different slippage), and routes change every few seconds.
Some pairs have no single pool connecting them (for example two small tokens that each trade only against SOL). Jupiter then answers "no route", which RouteCraft shows as "no direct line".
Pool fees are already taken out of each leg's output amount. When Jupiter's response includes an explicit fee field RouteCraft shows it; otherwise the implied rate per leg already includes the fee.
For very liquid pairs and small sizes impact can round to zero, and occasionally a route finds a rate slightly better than the reference price, which shows as a tiny negative impact.
It asks for quotes at 1%, 10%, 100% and 1,000% of your amount (four requests, spaced out) and shows how output per unit, impact and the number of venues change with size.
No. There's no backend. Requests go straight from your browser to Jupiter's public API.