jupiter-swap-migration

# 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 | ...