jupiter-swap-migration

Migrate Jupiter swap integrations from Metis v1 or Ultra to Swap API v2.

Updated Apr 11, 2026

Search Tags:#migration #ultra #v2 #swap #jupiter #metis

Ready to run

npx skills add https://github.com/mashharuki/jupter-sample-repo --skill jupiter-swap-migration

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: jupiter-swap-migration
Source: https://github.com/mashharuki/jupter-sample-repo/tree/main/.claude/skills/jupiter-swap-migration
Command: npx skills add https://github.com/mashharuki/jupter-sample-repo --skill jupiter-swap-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migration guidance to move Jupiter swap integrations from Metis (v1) or Ultra to the Swap API v2, covering endpoint changes, auth, and migration paths.

Core Features & Use Cases

Provides concrete migration paths: Ultra → /order, Metis → /build, Metis → /order.
Documents post-migration checks and reference materials.
Useful for ongoing maintenance and risk-free upgrade of existing integrations.

Quick Start

Consult the migration paths and execute a gradual update of base URLs and endpoints to the v2 API across Ultra and Metis flows.

Frequently Asked Questions about jupiter-swap-migration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I migrate Jupiter swap integrations from Metis v1 to Swap API v2?▼

Migrate Jupiter swap integrations from Metis v1 to Swap API v2 by updating base URLs and endpoints to the unified `/build` or `/order` execution flows. This replaces the old quote and swap-instructions process with a consolidated approach.

What is the correct migration path for Jupiter Ultra to Swap API v2?▼

The Jupiter Ultra to Swap API v2 migration path routes existing Ultra flows directly to the `/order` endpoint. This aligns your integration with the v2 API design and moves away from legacy execution logic.

When do I need to update my endpoints for Jupiter Swap API v2?▼

Update endpoints for Jupiter Swap API v2 when moving from Metis or Ultra quote and swap-instructions flows to the unified build and order execution. This ensures ongoing maintenance and a risk-free upgrade of existing integrations.

Does the Jupiter Swap API v2 migration support both Metis and Ultra flows?▼

Yes, the Jupiter Swap API v2 migration supports both flows by providing concrete paths: Ultra to `/order`, and Metis to either `/build` or `/order`. This conforms to the v2 API design and OpenAPI docs.

What are the limitations of migrating Jupiter swap integrations to v2?▼

Limitations during Jupiter swap migration to v2 involve ensuring all base URLs and endpoints are updated correctly. Consult the provided migration guides and OpenAPI docs for post-migration validation to prevent integration failures.