Changelog: July 2026

The Trigger API now documents DCA orders. A DCA order splits one deposit into multiple swaps that run on a fixed schedule, using the same vault, authentication, and deposit flow as price orders.

• Create with POST /trigger/v2/orders/dca (time_based or price_conditional)
• orderCount 2 or more, intervalSeconds 60 seconds to 1 year, currently $10 minimum per round
• Cancel via the two-step withdrawal flow to refund the unfilled remainder

WTM (what this means) - You can offer recurring buys and sells from the same integration you already use for limit orders, instead of the legacy Recurring API.

DCA guide · Create DCA Order API reference

Price orders support a trailing stop loss. Instead of a fixed triggerPriceUsd, set trailingBps (50–9000 basis points) on a single order: the trigger follows the market in your favour and holds when the price reverses.

• triggerCondition: "below" trails a sell (stop loss); "above" trails a buy entry
• The API seeds the trigger from the current price at create; the keeper rewrites it as the watermark moves
• Track the live trigger and peak with trailingBps and highWatermark/lowWatermark in order history
• Change the trail distance by updating trailingBps

WTM - Trailing stops are new to the Trigger API — price orders previously only took a fixed triggerPriceUsd. The moving trigger is managed keeper-side, so there is nothing to watch or rewrite yourself.

Trailing stop loss

DCA orders can earn Jupiter Lend yield on idle capital. Set jlEnabled: true on a time_based DCA order with a supported stablecoin input (USDC, USDT, or JupUSD): the budget that has not been swapped yet is supplied to Jupiter Lend between rounds and accrues yield until each round draws from it.

• Craft the deposit with jlMint, the Jupiter Lend earn token for your input stablecoin
• Track accrued yield with jlYieldUsd in order history
• Cancelling unwinds the Lend position and returns the remainder plus yield

WTM - A 12-round weekly DCA leaves most of its budget idle for months; with jlEnabled that balance earns Lend yield instead of sitting still, at no extra integration cost beyond two fields.

Earn While You Wait

The Recurring API is superseded by Trigger DCA orders. The pages remain live but are removed from the docs navigation and marked unmaintained.

WTM - Point new integrations at POST /trigger/v2/orders/dca, and plan a migration for existing Recurring integrations; it shares the vault and deposit flow with the rest of Trigger V2.

Recurring API · DCA guide

Jupiter Forecast is a native prediction market on Solana, exposed under the Prediction API as provider=bisonfi. The current markets are 15-minute Bitcoin up/down rounds settled automatically from the Chainlink BTC/USD price.

• Discover live rounds with GET /prediction/v1/events?provider=bisonfi&category=crypto&tag=15m
• Orders build as atomic USDC-to-outcome-token swaps and submit via POST /prediction/v1/execute; positions appear immediately, with no order-status polling
• Winning tokens settle automatically, so there is no manual claim step
• Each side is a Token-2022 outcomeMint worth $1 if it wins, also tradable directly through the Swap API

WTM - Forecast markets work through the Prediction API integration you may already have for Polymarket-style events; the Swap API path suits integrators who track positions themselves.

Jupiter Forecast · Execute Order API reference

The Lend AMM, a concentrated-liquidity AMM on the Liquidity Layer, now has a swap integration guide for routers, aggregators, and on-chain programs. Jupiter's own routing engine already routes through it; the guide is for everyone else.

• Quote and execute swaps from TypeScript with @jup-ag/lend-read and @jup-ag/lend/dex
• Call swap_in / swap_out via CPI from your own program, with a raw instruction recipe for non-Anchor integrators
• Five audit reports covering the AMM and its vault integration (Neodyme, OtterSec, Zenith) are published on the audits page

WTM - You can source Jupiter Lend liquidity in your own router or program without going through the Swap API.

AMM overview · Audits

Every swap transaction from the Jupiter frontend is signed by a dedicated signer, sighWH8KaiT7QhtV4w29ReVF8kG6D5yG3EQP1KYyGVF. PropAMMs integrated into Metis can verify that signature to classify the trade as retail, non-toxic order flow and quote it tighter spreads. Verify the signature, not just the address's presence in the account keys.

Integrate DEX into Metis

Jupiter's hosted Model Context Protocol server is live at https://mcp.jup.ag. Connect any MCP client and an AI agent can quote and execute swaps, place limit orders, set up DCA, lend, and read positions through 75 tools across 11 domains.

• Works without an API key at a lower rate limit; pass a Developer Platform key as a Bearer token for higher limits
• Tools that move funds return an unsigned transaction; your client signs and submits it, so keys stay with the user
• Streamable HTTP transport, with setup documented for Claude Code, Claude Desktop, Cursor, and Windsurf

WTM - Agents no longer need custom REST wiring to trade on Jupiter: point an MCP client at the server and the tools are discovered automatically.

Trading MCP guide · Developer Platform