Quote
The best route for amount of inputMint into outputMint, priced against live pool
state and checked to be buildable (a route that would not fit a v1 transaction, or that your
deploy’s config does not allow, is skipped for the next one). The response is a Jupiter-shaped
quote: pass it unchanged as quoteResponse to POST /swap-instructions or POST /swap.
ExactIn: amount is what you spend; outAmount is what arrives, net of venue and
platform fees; otherAmountThreshold is the floor, outAmount × (10000 − slippageBps) / 10000.
ExactOut: amount is what must arrive; inAmount is what you spend; otherAmountThreshold
is the cap, inAmount × (10000 + slippageBps) / 10000.
A cold token (never seen by this router) is fetched within 500 ms; if that is not enough
the answer is 503 not_ready (retry) or 422 cold_unresolved (nothing found).
Differences from Jupiter: extra fields quoteId, routeTicket (only on a router with
tickets enabled; the public router issues none), platformFee.feeMint, swapInfo.walkSteps,
routePlan[].bps; no swapInfo.feeAmount / feeMint; extra parameters allowSplit,
feeOnInput, reserveKeys; maxAccounts, restrictIntermediateTokens and dynamicSlippage
are ignored; asLegacyTransaction=true is a 400.
Query Parameters
Allow two routes in one transaction (two swap instructions, see swapInstructions). Served only when it beats the best single route by at least 1 bps and fits the transaction; never for ExactOut, cycles or with a platform fee. Send it only if you sign every entry of swapInstructions
Response
The quote