使用方法
- 复制安装命令，在自己的智能体环境安装前先检查源码包。
- 从原始文档核对所需工具、凭据和支持的宿主。
- 说明输入材料与期望交付物，并对照来源检查输出。
npx skills add https://github.com/jup-ag/agent-skills --skill jupiter-swap-migration开始前需了解
- 安装不包含模型订阅、API 额度或访问文件的权限。
- 仓库星数和安装量反映活跃情况，不等于独立质量或安全测试。
按源仓库内容呈现，保留标题、案例、代码、表格、链接以及原文引用的演示图片。
Jupiter Swap Migration Guide
Migrate existing Jupiter swap integrations from Metis (v1) or Ultra to the unified Swap API v2.
Target Base URL: https://api.jup.ag/swap/v2 Auth: x-api-key from developers.jup.ag (unchanged)
Use/Do Not Use
Use when:
- Migrating code that calls
api.jup.ag/swap/v1/quote,api.jup.ag/swap/v1/swap-instructions, orultra-api.jup.ag. - Updating Jupiter swap endpoints to v2.
- Switching from Metis two-step flow to the unified
/buildor/orderendpoint.
Do not use when:
- Building a new Jupiter integration from scratch (use
integrating-jupiterskill instead). - Working with non-swap Jupiter APIs (Lend, Trigger, Recurring, etc.).
Triggers: ultra, metis, ultra swap, ultra api, ultra-api.jup.ag, /ultra/v1, swap/v1, swap-instructions, migrate swap, ultra migration, metis migration, swap v1 to v2, v1 to v2, upgrade jupiter, swap-instructions deprecated, deprecated swap, old jupiter api, swap upgrade, update swap api, quote endpoint deprecated, swap stopped working, swap broken, ExactOut removed, swapMode removed, userPublicKey, parameter rename, addressLookupTable, response format changed
Migration Paths
| Source | Target | Effort | When to choose |
|---|---|---|---|
Ultra → /order | GET /swap/v2/order + POST /swap/v2/execute | Minimal (URL change only) | Default for Ultra users |
Metis → /build | GET /swap/v2/build | Moderate (parameter + response mapping) | Need transaction composability |
Metis → /order | GET /swap/v2/order + POST /swap/v2/execute | Moderate (flow change) | Don't need tx modification, want managed execution |
Path Details
Each path has a dedicated example with before/after code, parameter mappings, and response changes:
- Path 1: Ultra → `/order` — Minimal migration, base URL change only
- Path 2: Metis → `/build` — Consolidates 2 calls into 1, parameter and response mapping
- Path 3: Metis → `/order` — Flow change to managed execution with multi-router competition
Post-Migration Checklist
- URL audit: Search codebase for
ultra-api.jup.ag,/ultra/v1/,/swap/v1/quote,/swap/v1/swap-instructions— all should be replaced - Parameter rename:
userPublicKey→taker(for/buildpath) - `swapMode` removal: V2 only supports
ExactIn. If usingExactOut, redesign the flow — this mode is no longer available - `slippageBps` default:
/builddefaults to 50 bps if omitted. For/order, verify the default if your integration relies on a specific value - Response field names: Verify your code uses
inputAmountResult/outputAmountResultfor the/executeresponse (the canonical v2 field names) - ALT handling: If using
/build, switch fromaddressLookupTableAddresses(array) toaddressesByLookupTableAddress(object) — remove RPC ALT resolution code - Fee event parsing: V2 instructions don't emit fee events — update any transaction parser that depends on them
- Route plan format: If parsing route plans, use
bpsfield (canonical) instead ofpercent - Error codes: Update error handling to match Swap v2 error codes
- Test: Run end-to-end swap on devnet/mainnet with small amount to verify
Sunset
Remove this skill once Jupiter decommissions the v1 (/swap/v1) endpoints and the Ultra (ultra-api.jup.ag) domain. At that point all integrations will already be on v2.
Review by: 2026-09-01 — check if v1/Ultra endpoints have been decommissioned.
References
Migration is split into three profile-targeted guides (the old single migration page no longer exists):
