jupiter-swap-migration — Claude Code skill: what it does
jupiter-swap-migration — a Claude Code skill that guides migration from legacy Jupiter Metis v1 and Ultra endpoints to Swap API v2. Triggers when upgrading swap integrations or replacing deprecated parameters.
MIT 307 installs ★ 90 updated 2026-07-07
npx skills add jup-ag/agent-skills --skill jupiter-swap-migration -a claude-codeWhat jupiter-swap-migration does
This skill guides the transition from deprecated Jupiter endpoints like api.jup.ag/swap/v1/quote, api.jup.ag/swap/v1/swap-instructions, and ultra-api.jup.ag to the unified base URL https://api.jup.ag/swap/v2. Integrations on Ultra switch to GET /swap/v2/order combined with POST /swap/v2/execute. Metis setups can either consolidate two steps into a single /build call or move to managed execution through /order.
The guidance covers critical protocol adjustments. Swap API v2 drops ExactOut entirely, meaning flows must be rebuilt around ExactIn. In /build requests, userPublicKey becomes taker, while lookup tables switch to addressesByLookupTableAddress, removing external RPC lookups for ALT accounts. Omitting slippageBps on /build defaults the value to 50 bps.
All calls to API v2 still require an x-api-key header obtained from developers.jup.ag. The skill does not cover brand new integrations or non-swap Jupiter APIs like Lend and Recurring.
What it helps with
- migrate deprecated Jupiter swap v1 and Ultra code to Swap API v2
- consolidate Metis quote and swap instructions into a single /build call
- refactor legacy ExactOut workflows to supported ExactIn routing
- update response parsers to canonical fields inputAmountResult and outputAmountResult
Example prompts for the agent
- Migrate our Jupiter Metis v1 swap logic to Swap API v2
- Update ultra-api.jup.ag endpoints to the v2 order and execute flow
- Audit our codebase for swap/v1/quote calls and rename userPublicKey to taker
How to install jupiter-swap-migration
1Skills CLI (Vercel)
npx skills add jup-ag/agent-skills --skill jupiter-swap-migration -a claude-code2Manually: put the files in place
~/.claude/skills/jupiter-swap-migration/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/jupiter-swap-migration/
1Skills CLI (Vercel)
npx skills add jup-ag/agent-skills --skill jupiter-swap-migration -a codex2Manually: put the files in place
.agents/skills/jupiter-swap-migration/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add jup-ag/agent-skills --skill jupiter-swap-migration -a cursor2Manually: put the files in place
.cursor/skills/jupiter-swap-migration/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install jup-ag/agent-skills skills/jupiter-swap-migration2Manually: put the files in place
.github/skills/jupiter-swap-migration/SKILL.md1Skills CLI (Vercel)
npx skills add jup-ag/agent-skills --skill jupiter-swap-migration -a gemini-cli2Platform CLI
gemini skills install https://github.com/jup-ag/agent-skills --path skills/jupiter-swap-migrationManually: put the files in place
.devin/skills/jupiter-swap-migration/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add jup-ag/agent-skills --skill jupiter-swap-migration -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about jupiter-swap-migration
How to install jupiter-swap-migration in Claude Code?
Run npx skills add jup-ag/agent-skills --skill jupiter-swap-migration -a claude-code. It creates the instruction file at ~/.claude/skills/jupiter-swap-migration/SKILL.md.
What does jupiter-swap-migration do?
It guides coding agents through refactoring legacy Jupiter swap implementations to API v2, detailing endpoint changes, field mappings, and deprecated features.
What is required to use jupiter-swap-migration?
You need an active x-api-key from developers.jup.ag to interact with target base URL https://api.jup.ag/swap/v2.
Source text
SKILL.md · MIT
--- name: jupiter-swap-migration description: Migration guide from Jupiter Metis (v1) or Ultra to Swap API v2. Use when migrating existing Jupiter swap integrations, updating base URLs, or transitioning from quote+swap-instructions to the unified build endpoint. license: MIT metadata: author: jup-ag version: "1.1.0" tags: - jupiter - swap-migration - metis - ultra - swap-v2 - jup-ag --- # 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](https://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`, or `ultra-api.jup.ag`. - Updating Jupiter swap endpoints to v2. - Switching from Metis two-step flow to the unified `/build` or `/order` endpoint. Do not use when: - Building a new Jupiter integration from scratch (use `integrating-jupiter` skill 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`](./examples/ultra-to-order.md) — Minimal migration, base URL change only - [Path 2: Metis → `/build`](./examples/metis-to-build.md) — Consolidates 2 calls into 1, parameter and response mapping - [Path 3: Metis → `/order`](./examples/metis-to-order.md) — Flow change to managed execution with multi-router competition --- ## Post-Migration Checklist 1. **URL audit**: Search codebase for `ultra-api.jup.ag`, `/ultra/v1/`, `/swap/v1/quote`, `/swap/v1/swap-instructions` — all should be replaced 2. **Parameter rename**: `userPublicKey` → `taker` (for `/build` path) 3. **`swapMode` removal**: V2 only supports `ExactIn`. If using `ExactOut`, redesign the flow — this mode is no longer available 4. **`slippageBps` default**: `/build` defaults to 50 bps if omitted. For `/order`, verify the default if your integration relies on a specific value 5. **Response field names**: Verify your code uses `inputAmountResult`/`outputAmountResult` for the `/execute` response (the canonical v2 field names) 6. **ALT handling**: If using `/build`, switch from `addressLookupTableAddresses` (array) to `addressesByLookupTableAddress` (object) — remove RPC ALT resolution code 7. **Fee event parsing**: V2 instructions don't emit fee events — update any transaction parser that depends on them 8. **Route plan format**: If parsing route plans, use `bps` field (canonical) instead of `percent` 9. **Error codes**: Update error handling to match [Swap v2 error codes](https://developers.jup.ag/docs/swap/order-and-execute.md) 10. **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): - [Migration: Ultra → /order](https://developers.jup.ag/docs/swap/migration/ultra-to-order.md) - [Migration: Metis → /build](https://developers.jup.ag/docs/swap/migration/metis-to-build.md) - [Migration: Metis → Meta-Aggregator (/order + /execute)](https://developers.jup.ag/docs/swap/migration/metis-to-meta-aggregator.md) - [Order & Execute](https://developers.jup.ag/docs/swap/order-and-execute.md) - [Build](https://developers.jup.ag/docs/swap/build/index.md) - [Swap overview](https://developers.jup.ag/docs/swap/index.md) (routing and fees) - [OpenAPI spec](https://developers.jup.ag/docs/openapi-spec/swap/v2/swap.yaml)
© jup-ag · MIT · jup-ag/agent-skills