رسوم Jupiter وملف المنصة

البحث الأصلي باللغة الإنجليزية

Swap API

Jupiter Swap API is the quote-and-transaction path for apps that need to fetch routes and build Solana swap transactions before the user signs in a wallet.عرض المصدر ↗

Routing role

Jupiter's developer platform describes Metis, JupiterZ, and third-party routers competing on swaps, so output should be treated as route selection rather than exchange custody.عرض المصدر ↗

Ultra execution mode

Ultra should be checked as a separate execution path from legacy Swap because integrators may receive different routing, transaction, and order-handling behavior.عرض المصدر ↗

Swap failure boundary

Jupiter Support says failed swaps can come from price movement, liquidity size, token restrictions or stale routes, so a failed quote should be treated as an execution condition rather than a platform custody issue.عرض المصدر ↗

Ultra compensation boundary

Jupiter's public support text limits Ultra compensation review to defined routing, repeated failure or extreme slippage cases and says potential profit-and-loss is not compensated.عرض المصدر ↗

Route liquidity boundary

The support FAQ says 'No routes found' usually reflects insufficient liquidity, unsuitable trade size, or token restrictions; users should verify real Solana DEX liquidity before treating a route as available.عرض المصدر ↗

Platform fee boundary

Jupiter integrations must verify fee configuration in the official API docs; a quoted route does not prove that a separate platform fee, wallet fee, or network cost is absent.عرض المصدر ↗

Token-list boundary

Jupiter token-list and token API references should be used to verify mints and list status before treating a Solana asset route as safe or broadly available.عرض المصدر ↗

Transaction build path

The user decision point is the built transaction shown by the wallet: network, mint addresses, slippage, price impact, and route legs must still be reviewed before signing.عرض المصدر ↗

Query intent boundary

A Jupiter search should be sorted into test quote, live swap, token-list verification, Ultra execution review, or API/platform-fee integration before the page asks the user to open the official route.عرض المصدر ↗