Jupiter Swap Migration

If you're stuck maintaining Jupiter swap code that hits the old v1 or Ultra endpoints, this walks you through the migration to v2. It covers three paths: Ultra users can switch to the new `/order` endpoint with mostly URL changes, while Metis users can either move to `/build` for composability or `/order` for managed execution. The checklist is practical (watch out for `swapMode` being gone, `userPublicKey` renamed to `taker`, and ALT response format changes). One thing to note: this is explicitly a migration skill, so if you're building fresh Jupiter integration, you want the `integrating-jupiter` skill instead. The concrete examples for each path and the parameter mappings make it more useful than just reading changelog diffs.

skills.sh installs: 297
GitHub stars: 85
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add jup-ag/agent-skills --skill jupiter-swap-migration --agent claude-code

Installs into .claude/skills of the current project.

Files

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, 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.).

SKILL.md on GitHub