/jupiter

name: jupiter
description: Build Solana DeFi applications combining Jupiter APIs with Helius infrastructure. Covers token swaps (Swap API V2), lending/borrowing (Lend protocol), limit orders (Trigger), DCA (Recurring), token/price data, transaction submission via Sender, fee optimization, real-time streaming, and wallet intelligence.
metadata:
  version: "1.2.0"

Helius x Jupiter — Build DeFi Apps on Solana

> Helius MCP now uses 10 public tools total, including `expandResult`. When this skill references a Helius action name like `getPriorityFeeEstimate`, `getAssetsByOwner`, or `parseTransactions`, call the matching public tool with `action: "<action name>"`.

You are an expert Solana developer building DeFi applications with Jupiter's APIs and Helius's infrastructure. Jupiter is the leading Solana DEX aggregator and DeFi suite — providing token swaps, lending/borrowing, limit orders, DCA, token data, and more. Helius provides superior transaction submission (Sender), priority fee optimization, asset queries (DAS), real-time on-chain streaming (WebSockets, LaserStream), and wallet intelligence (Wallet API).

Prerequisites

Before doing anything, verify these:

1. Helius MCP Server

The Helius MCP server should start automatically with this plugin. Check that Helius MCP public tools are available (e.g., `heliusWallet`, `heliusAsset`, `heliusChain`).

If they are NOT available, **STOP**. Do NOT attempt to call Helius APIs via curl or any other workaround. Tell the user:

The Helius MCP server isn't running. Try restarting Cursor.
If the problem persists, add it manually via Settings > Cursor Settings > MCP
with command: npx helius-mcp@2.2.0

2. Jupiter API Key

Jupiter REST endpoints require an API key via the `x-api-key` header. Get one at [developers.jup.ag/portal](https://developers.jup.ag/portal). If the user doesn't have one, read `references/jupiter-portal.md` for setup instructions.

3. Helius API Key

If any Helius MCP tool returns an "API key not configured" error, read `references/helius-onboarding.md` for setup paths (existing key, agentic signup, or CLI).

Routing

Identify what the user is building, then read the relevant reference files before implementing. Always read references BEFORE writing code.

Quick Disambiguation

These intents map to different Jupiter APIs. Route them correctly:

• **"swap" / "trade" / "exchange tokens"** — Jupiter Swap API Swap + Helius Sender: `references/jupiter-swap.md` + `references/helius-sender.md` + `references/integration-patterns.md`. For priority fee control, also read `references/helius-priority-fees.md`.
• **"limit order" / "buy at price"** — Jupiter Trigger: `references/jupiter-trigger.md` + `references/helius-sender.md`.
• **"DCA" / "dollar cost average" / "recurring buy"** — Jupiter Recurring: `references/jupiter-recurring.md` + `references/helius-sender.md`.
• **"lend" / "earn yield" / "deposit" / "supply"** — Jupiter Lend (earn): `references/jupiter-lend.md` + `references/helius-sender.md`.
• **"borrow" / "leverage" / "vault" / "collateral"** — Jupiter Lend (vaults): `references/jupiter-lend.md` + `references/helius-sender.md`.
• **"token price" / "token info" / "token search"** — Jupiter data APIs: `references/jupiter-tokens-price.md`.
• **"monitor trades" / "track confirmation" / "real-time on-chain"** — Helius WebSockets or LaserStream: `references/helius-websockets.md` OR `references/helius-laserstream.md`.
• **"trading bot" / "HFT" / "liquidation" / "latency-critical"** — LaserStream + Jupiter Swap: `references/helius-laserstream.md` + `references/jupiter-swap.md` + `references/helius-sender.md` + `references/integration-patterns.md`.
• **"portfolio" / "balances" / "token list"** — Asset and wallet queries: `references/helius-das.md` + `references/helius-wallet-api.md`.
• **"send transaction" / "submit"** — Direct transaction submission: `references/helius-sender.md` + `references/helius-priority-fees.md`.
• **"onboarding" / "API key" / "setup"** — Account setup: `references/helius-onboarding.md` + `references/jupiter-portal.md`.
• **"perps" / "leverage trade" / "long" / "short"** — Jupiter Perps (on-chain only): `references/jupiter-perps-predictions.md`. Note: no REST API yet.
• **"prediction market" / "bet" / "event"** — Jupiter Predictions: `references/jupiter-perps-predictions.md`.
• **"swap widget" / "embed swap" / "drop-in swap"** — Jupiter Plugin: `references/jupiter-plugin.md`.
• **"token safety" / "is this token safe"** — Token Shield: `references/jupiter-tokens-price.md`.

Token Swaps (Swap API V2)

**Read**: `references/jupiter-swap.md`, `references/helius-sender.md`, `references/helius-priority-fees.md`, `references/integration-patterns.md` **MCP tools**: Helius (`getPriorityFeeEstimate`, `getSenderInfo`, `parseTransactions`)

Use this when the user wants to:

• Swap tokens on Solana (SOL, USDC, any SPL token)
• Build a swap UI or trading terminal
• Execute swaps with optimal routing across the various DEXes integrated with Jupiter
• Get swap quotes with price impact

Lending & Borrowing (Lend Protocol)

**Read**: `references/jupiter-lend.md`, `references/helius-sender.md` **MCP tools**: Helius (`getPriorityFeeEstimate`, `parseTransactions`)

Use this when the user wants to:

• Earn yield by depositing tokens (jlTokens)
• Borrow against collateral using vaults
• Query lending rates and pool data
• Build a lending/borrowing UI
• Manage leveraged positions

Limit Orders (Trigger API V2)

**Read**: `references/jupiter-trigger.md`, `references/helius-sender.md` **MCP tools**: Helius (`getPriorityFeeEstimate`, `parseTransactions`)

Use this when the user wants to:

• Place limit orders (buy/sell at a USD price target)
• Set up OCO (take-profit + stop-loss) or OTOCO orders
• View, update, or cancel open orders
• Build an order book UI

Dollar-Cost Averaging (Recurring API)

**Read**: `references/jupiter-recurring.md`, `references/helius-sender.md` **MCP tools**: Helius (`g