Jupiter

Showing 25 of 75 from the live probe.

• Search Tokens

  Search for Solana tokens by name, symbol, or mint address. Returns token metadata including mint address, symbol, decimals, and logo. Use this when the user wants to look up, discover, or identify a token, not as the primary tool when they want to swap, trade, or check price. Pass up to 100 comma-separated mint addresses to resolve many tokens in one call. Also useful to resolve a token name/symbol to its mint address when the token is not in the well-known list embedded in other tools. If multi

• List Tokens by Tag

  List tokens filtered by tag: 'lst' (liquid staking tokens) or 'verified' (Jupiter-verified tokens). Returns the full set of matching tokens with metadata.

• List Tokens by Category

  List trending or top-performing tokens by category and time window. Categories: 'toporganicscore', 'toptraded', 'toptrending'. Intervals: '5m', '1h', '6h', '24h'. Returns up to 100 tokens ranked by the selected metric.

• List Recent Tokens

  List the most recently added tokens on Jupiter. Useful for discovering newly launched tokens.

• Check Verification Eligibility

  Check whether a token is eligible for Jupiter VRFD express verification and metadata updates. Returns whether the token exists on-chain, is already verified, and whether a verification request or metadata update can be submitted. Call this first in the express verification flow: if both canVerify and canMetadata are false the submission will be rejected before payment is charged, so there is no need to craft a payment transaction.

• Build Verification Payment

  Build the unsigned Solana transaction that transfers 1000 JUP as payment for Jupiter VRFD express verification. Use this after confirming eligibility with tokens_get_verification_eligibility. Returns a base64-encoded unsigned transaction and a requestId. WORKFLOW: the senderAddress wallet must sign the returned transaction, then pass the signed transaction and requestId to tokens_execute_verification. The crafted transaction expires, so execute promptly.

• Execute Verification

  Submit the signed 1000 JUP payment transaction to complete Jupiter VRFD express verification. Records the payment, creates a verification request, and optionally submits token metadata updates (verification and metadata are reviewed independently). Returns the on-chain transaction signature and whether the verification and metadata requests were created. PREREQUISITE: call tokens_build_verification_payment first to obtain the unsigned transaction and requestId, sign the transaction, then call th

• Get Token Prices

  Fetch current USD prices for one or more Solana tokens by their mint addresses (comma-separated, max 50). Returns price, liquidity, and 24h change. Use this when the user asks how much a token is worth, its price, or its value. Well-known mints — SOL: So11111111111111111111111111111111111111112, USDC: EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v, USDT: Es9vMFrzaCERmJfrF4H2FYD4KCoNkY11McCe8BenwNYB, JUP: JUPyiwrYJFskUPiHa7hkeR8VUtAeFoSYbKedZNsDvCN, BONK: DezXAZ8z7PnrnRJjz3wXBoRgixCa6xjnB7YaB1pPB26

• Get Trigger Auth Challenge

  Step 1 of Trigger Order authentication: request a challenge to sign with the user's wallet. Returns a message (standard wallets) or a base64 transaction (hardware wallets) that expires in 5 minutes. WORKFLOW: Sign the returned challenge with the wallet, then call trigger_verify_challenge to obtain a JWT used by every other trigger tool.

• Verify Trigger Auth Challenge

  Step 2 of Trigger Order authentication: submit the signed challenge from trigger_get_challenge to receive a JWT token valid for 24 hours. Pass this token as the jwt argument to every other trigger tool. There is no refresh endpoint; repeat the challenge flow when it expires.

• Get Trigger Vault

  Retrieve the Privy-managed vault associated with the authenticated wallet. The vault holds deposits for trigger orders. Returns 'Vault not found' if none exists yet; call trigger_register_vault to create one.

• Register Trigger Vault

  Create a Privy-managed vault wallet for the authenticated account. Call this once per wallet before depositing; subsequent calls return the existing vault. The vault holds funds for trigger orders.

• Build Trigger Deposit

  Build an unsigned transaction to deposit tokens from the wallet into its trigger vault: the first step of creating a trigger order. The orderSubType must match the order you will create (single, oco, or otoco). WORKFLOW: Sign the returned transaction, then pass requestId and the signed transaction (as depositRequestId and depositSignedTx) to trigger_create_order.

• Create Trigger Order

  Create a price trigger (limit) order. Submits the signed deposit on-chain and activates the order. Use this when the user wants a limit order, take-profit, or stop-loss. Required for single/otoco: triggerCondition + triggerPriceUsd. Required for oco/otoco: tpPriceUsd + slPriceUsd (take-profit must be greater than stop-loss). Minimum order 10 USD; expiresAt is required (milliseconds, future). WORKFLOW: First call trigger_build_deposit with the matching orderSubType, sign its transaction, then pas

• Update Trigger Order

  Update the trigger price, slippage, or take-profit/stop-loss of an existing open trigger order in place. No new deposit is needed. Only valid while the order is open.

• Build Trigger Cancellation

  Step 1 of cancelling a trigger order: returns an unsigned withdrawal transaction and a requestId. The order immediately stops filling. WORKFLOW: Sign the returned transaction, then pass it and the requestId (as signedTransaction and cancelRequestId) to trigger_confirm_cancel to return the funds to the wallet. Also used to retrieve funds from an expired order.

• Confirm Trigger Cancellation

  Step 2 of cancelling a trigger order: submit the signed withdrawal transaction from trigger_build_cancel to complete the cancellation and return the funds to the wallet. If the step is interrupted, retry with the same cancelRequestId.

• List Trigger Orders

  List the authenticated wallet's trigger (limit) orders, active or past, with their state and event history. Use this when the user wants to see their limit orders or check an order's status. Filter by state and mint, paginate with limit/offset, and sort by updated_at, created_at, or expires_at.

• Create DCA Order

  Set up a recurring DCA (Dollar Cost Average) order using the latest Trigger V2 DCA deposit flow. Use this when the user wants to auto-buy, schedule recurring purchases, DCA into a token, or dollar cost average over time. Well-known mints — SOL: So11111111111111111111111111111111111111112 (9 dec), USDC: EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v (6 dec), USDT: Es9vMFrzaCERmJfrF4H2FYD4KCoNkY11McCe8BenwNYB (6 dec), JUP: JUPyiwrYJFskUPiHa7hkeR8VUtAeFoSYbKedZNsDvCN (6 dec), BONK: DezXAZ8z7PnrnRJjz3

• Cancel DCA Order

  Initiate cancellation of an active recurring DCA order using the latest Trigger V2 DCA flow. This first step is one-way: it moves the order into withdrawal, stops future fills immediately, and cannot be reverted back to active even if the confirmation transaction later fails. Returns an unsigned withdrawal transaction and a requestId. WORKFLOW: Sign the returned transaction, then call recurring_execute with jwt, requestId, signedTransaction, and the same order id to confirm the cancellation.

• Execute DCA Transaction

  Finalize a signed recurring DCA transaction using the latest Trigger V2 DCA flow. For order creation, pass jwt, requestId, signedTransaction, and the same DCA parameters used in recurring_build_order. For price-conditioned DCA, pass triggerMint when the volatile leg cannot be inferred automatically. For cancellations, pass jwt, requestId, signedTransaction, and order to confirm the withdrawal.

• List DCA Orders

  List a wallet's recurring DCA orders using the latest Trigger V2 DCA history endpoint. Use this when the user wants to see their active DCA orders, recurring buy history, or check what they're dollar cost averaging into.

• Deposit to Lending

  Deposit tokens into Jupiter Lend/Earn to earn yield (token-denominated). Use this when the user wants to lend tokens, earn interest, earn yield, or deposit into Jupiter lending. Well-known mints — SOL: So11111111111111111111111111111111111111112 (9 dec), USDC: EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v (6 dec), USDT: Es9vMFrzaCERmJfrF4H2FYD4KCoNkY11McCe8BenwNYB (6 dec), JUP: JUPyiwrYJFskUPiHa7hkeR8VUtAeFoSYbKedZNsDvCN (6 dec), BONK: DezXAZ8z7PnrnRJjz3wXBoRgixCa6xjnB7YaB1pPB263 (5 dec), WIF: EK

• Withdraw from Lending

  Withdraw tokens from Jupiter Lend/Earn (token-denominated). Use this when the user wants to withdraw, pull out, or remove tokens from Jupiter lending. Well-known mints — SOL: So11111111111111111111111111111111111111112 (9 dec), USDC: EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v (6 dec), USDT: Es9vMFrzaCERmJfrF4H2FYD4KCoNkY11McCe8BenwNYB (6 dec), JUP: JUPyiwrYJFskUPiHa7hkeR8VUtAeFoSYbKedZNsDvCN (6 dec), BONK: DezXAZ8z7PnrnRJjz3wXBoRgixCa6xjnB7YaB1pPB263 (5 dec), WIF: EKpQGSJtjMFqKZ9KQanSqYXRcF8fB

• Mint Lending Shares

  Deposit into Jupiter Lend/Earn by specifying a number of vault shares to mint (share-denominated). Use this when the user wants to deposit by share count rather than token amount. For depositing by token amount, use lend_build_deposit. WORKFLOW: The returned transaction must be signed by the signer wallet and submitted directly to the Solana network via sendTransaction. There is no separate execute tool for lending.