Skip to main content
You can swap any token pair through the Jupiter aggregator. Jupiter routes orders across Solana’s DEXes to find the best price, and includes MEV protection to prevent front-running.

Execute a swap

Request parameters

string
required
The source token. Use a common symbol (e.g., USDC) or the token’s Solana mint address.
string
required
The destination token. Use a common symbol or mint address.
number
required
The amount of the source token to swap.
number
default:"50"
Slippage tolerance in basis points. Defaults to 50 (0.5%). See slippage guidance below.

Response

Response fields

object

Slippage

Slippage tolerance protects you against price movement between the time the order is submitted and when it lands on-chain. If the final price moves beyond the tolerance, the transaction is rejected rather than executed at an unfavorable price.
Setting slippage too low may cause transactions to fail during volatile conditions. Setting it too high may result in poor execution prices.

Supported tokens

Jupiter supports thousands of tokens on Solana. You can identify tokens in two ways:

By symbol

Common symbols are recognized automatically:

By mint address

For any token not covered by a common symbol, use its Solana mint address:

Jupiter integration and MEV protection

Knot routes all swaps through Jupiter, Solana’s leading DEX aggregator. Jupiter:
  • Splits orders across multiple liquidity pools (Raydium, Orca, and others) to minimize price impact
  • Uses smart routing to find the optimal path for any token pair
  • Includes MEV protection to prevent sandwich attacks on your transactions
The route field in the response shows which DEXes were used for a given swap.

Common trade scenarios

Use tight slippage for stablecoin-to-stablecoin swaps since price variation is minimal:
Use higher slippage when trading low-liquidity or volatile tokens to avoid transaction failures:
Specify tokens by their on-chain mint address when their symbol is not recognized:

Policy constraints

Trading must be enabled in your agent’s policy. If you receive a 403 error when attempting a swap, check that trading is allowed in your policy settings.