integrating-jupiter

Single skill for all Jupiter APIs, optimized for fast routing and deterministic execution.

jup-ag/agent-skills|Updated Apr 8, 2026

Works with

Claude CodeCursorClineWindsurfCodexGoose

Installation Guide

Select your AI agent

How to use integrating-jupiter on Cursor

AI-first code editor with Composer

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

›Cursor installed and configured on your machine
›Node.js 16+ with npm — verify with node --version
›Active project directory where you want to add integrating-jupiter

Run the install command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/jup-ag/agent-skills --skill integrating-jupiter

Fetches integrating-jupiter from jup-ag/agent-skills and configures it for Cursor.

Select Cursor when prompted

The CLI shows a list of agents. Use arrow keys and space to select Cursor:

◆ Which agents do you want to install to?

│

│ ── Universal (.agents/skills) ────────────────

│ · Cline · Codex · Goose · Windsurf

│ ●Cursor(selected)

│ · Cursor · Aider · Continue

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/integrating-jupiter

Restart Cursor to activate integrating-jupiter. Access via /integrating-jupiter in your agent's command palette.

⚠

Security Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.

›View source on GitHub ›Skills CLI docs ›About Cursor ›What are agent skills?

Documentation

List & Monetize Your Skill

Submit your Claude Code skill and start earning

Get started →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

✓

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

✓

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Use/Do Not Use

Use when:

The task requires choosing or calling Jupiter endpoints.

The task involves swap, lending, perps, orders, pricing, portfolio, send, studio, lock, or routing.

The user needs debugging help for Jupiter API calls.

Do not use when:

The task is generic Solana setup with no Jupiter API usage.

The task is UI-only with no API behavior decisions.

The agent context is not DeFi/crypto (generic triggers like buy, sell, trade assume a DeFi domain).

Triggers: swap, quote, gasless, best route, buy, sell, trade, convert, token exchange, jupiter api, jup.ag, ultra, metis, ultra swap, ultra api, ultra-api.jup.ag, lend, borrow, earn, yield, apy, deposit, liquidation, perps, leverage, long, short, position, futures, margin trading, limit order, trigger, price condition, dca, recurring, scheduled swaps, token metadata, token search, verification, shield, price, valuation, price feed, portfolio, positions, holdings, prediction markets, market odds, event market, invite transfer, send, clawback, create token, studio, claim fee, vesting, distribution lock, unlock schedule, dex integration, rfq integration, routing engine, status page, health check, service health, accumulate, auto-buy

Developer Quickstart

import { Connection, Keypair, VersionedTransaction } from '@solana/web3.js'; const API_KEY = process.env.JUPITER_API_KEY!; // from portal.jup.ag if (!API_KEY) throw new Error('Missing JUPITER_API_KEY'); const BASE = 'https://api.jup.ag'; const headers = { 'x-api-key': API_KEY }; async function jupiterFetch<T>(path: string, init?: RequestInit): Promise<T> { const res = await fetch(`${BASE}${path}`, { ...init, headers: { ...headers, ...init?.headers }, }); if (res.status === 429) throw { code: 'RATE_LIMITED', retryAfter: Number(res.headers.get('Retry-After')) || 10 }; if (!res.ok) { const raw = await res.text(); let body: any = { message: raw || `HTTP_${res.status}` }; try { body = raw ? JSON.parse(raw) : body; } catch { // keep text fallback body } throw { status: res.status, ...body }; } return res.json(); } // Sign and send any Jupiter transaction async function signAndSend( txBase64: string, wallet: Keypair, connection: Connection, additionalSigners: Keypair[] = [] ): Promise<string> { const tx = VersionedTransaction.deserialize(Buffer.from(txBase64, 'base64')); tx.sign([wallet, ...additionalSigners]); const sig = await connection.sendRawTransaction(tx.serialize(), { maxRetries: 0, skipPreflight: true, }); return sig; }

Intent Router (first step)

User intent

API family

First action

Swap/quote

Swap

GET /swap/v2/order -> sign -> POST /swap/v2/execute

Lend/borrow/yield

Lend

POST /lend/v1/earn/deposit or /withdraw

Leverage/perps

Perps

On-chain via Anchor IDL (no REST API yet)

Limit orders

Trigger

JWT auth -> POST /trigger/v2/orders/price

DCA/recurring buys

Recurring

POST /recurring/v1/createOrder -> sign -> POST /recurring/v1/execute

Token search/verification

Tokens

GET /tokens/v2/search?query={mint}

Price lookup

Price

GET /price/v3?ids={mints}

Portfolio/positions

Portfolio

GET /portfolio/v1/positions/{address}

Prediction market integration

Prediction Markets

GET /prediction/v1/events -> POST /prediction/v1/orders

Invite send/clawback

Send

POST /send/v1/craft-send -> sign -> send to RPC

Token creation/fees

Studio

POST /studio/v1/dbc-pool/create-tx -> upload -> submit

Vesting/distribution

Lock

On-chain program LocpQgucEQHbqNABEYvBvwoxCPsSbG91A1QaQhQQqjn

DEX/RFQ integration

Routing

Choose DEX (AMM trait) vs RFQ (webhook) path

API Playbooks

Use each block as a minimal execution contract. Fetch the linked refs for full request/response shapes, TypeScript interfaces, and parameter details.

Swap

Base URL: https://api.jup.ag/swap/v2

Triggers: swap, quote, gasless, best route

Fee: Variable by pair — 0 bps (Jupiter tokens/pegged), 2 bps (SOL-Stable), 5 bps (LST-Stable), 10 bps (most pairs), 50 bps (tokens < 24h). Referral fees: 50-255 bps (Jupiter retains 20%).

Rate Limit: 50 req/10s base, scales with 24h execute volume (see Rate Limits)

Endpoints: /order (GET), /execute (POST), /build (GET, Metis-only raw instructions)

Routing: 4 routers compete — Metis (API value: iris), JupiterZ (jupiterz), Dflow (dflow), OKX (okx). Response mode field: "ultra" (all routers, default params) or "manual" (restricted by optional params). /build uses Metis only.

Gasless: Three paths — automatic (Jupiter-covered), JupiterZ (MM-covered), integrator-payer (payer param, Metis-only routing). Eligibility varies by balance, trade size, and parameters used. See Gasless docs for current thresholds and disqualifying params.

Gotchas: Signed payloads have ~2 min TTL. Transactions are immutable after receipt. Split order/execute in code and logging. Re-quote before execution when conditions may have changed. referralAccount/referralFee/receiver disable JupiterZ only (Metis/Dflow/OKX remain). payer reduces routing to Metis only (per gasless docs; routing docs group all four as disabling JupiterZ but do not itemize the additional Dflow/OKX restriction). /build transactions cannot use /execute — self-manage via RPC.

Migrating from an older integration? Use the jupiter-swap-migration skill.

Common error codes returned by /swap/v2/execute with recommended actions:

Code

Code	Category	Meaning	Retryable	Action
`0`	Success	Transaction confirmed	—	—
`-1`	Execute	Missing/expired cached order	Yes	Re-quote and retry
`-2`	Execute	Invalid signed transaction	No	Fix transaction signing
`-3`	Execute	Invalid message bytes	No	Fix serialization
`-1000`	Aggregator	Failed landing attempt	Yes	Re-quote with adjusted params
`-1001`	Aggregator	Unknown error	Yes	Retry with backoff
`-1002`	Aggregator	Invalid transaction	No	Fix transaction construction
`-1003`	Aggregator	Transaction not fully signed	No	Ensure all required signers
`-1004`	Aggregator	Invalid block height	Yes	Re-quote (stale blockhash)
`-2000`	RFQ	Failed landing	Yes	Re-quote and retry
`-2001`	RFQ	Unknown error	Yes	Retry with backoff
`-2002`	RFQ	Invalid payload	No	Fix request payload
`-2003`	RFQ	Quote expired	Yes	Re-quote and retry
`-2004`	RFQ	Swap rejected	Yes	Re-quote, possibly different route
`429`	Rate limit	Rate limited	Yes	Exponential backoff, wait 10s window

integrating-jupiter

Installation Guide

How to use integrating-jupiter on Cursor

Prerequisites

Run the install command

Select Cursor when prompted

Verify installation

Security Notice

Documentation

List & Monetize Your Skill

Use Cases

User Story & Requirements Generation

Competitive Analysis

Roadmap Prioritization

Install Skill

Jupiter API Integration

Use/Do Not Use

Developer Quickstart

Intent Router (first step)

API Playbooks

Swap

Lend

Stakeholder Communication

Implementation Guide

Best Practices

When to Use This

Learning Path

Related Skills

grill-me

premortem

deslop

framer-motion

write-a-prd

travel-planner

Reviews

Discussion