jupiter-swap-migration

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

Updated Apr 13, 2026

Search Tags:#integration #migration #ultra #api upgrade #metis #jupiter swap #swap v2

Ready to run

npx skills add https://github.com/frederik-maker/jupiter-pulse --skill jupiter-swap-migration-frederik-maker

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: jupiter-swap-migration
Source: https://github.com/frederik-maker/jupiter-pulse/tree/main/.agents/skills/jupiter-swap-migration
Command: npx skills add https://github.com/frederik-maker/jupiter-pulse --skill jupiter-swap-migration-frederik-maker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrate existing Jupiter swap integrations from Metis (v1) or Ultra to the unified Swap API v2, reducing compatibility risk and downtime.

Core Features & Use Cases

Migration paths for Ultra → /order, Metis → /build, and Metis → /order.
Parameter mappings and endpoint changes consolidated in a single guide.
Post-migration checklist with references to official docs and example mappings.

Quick Start

Begin by reviewing the migration paths and update your codebase to point to swap/v2 endpoints, then adjust parameters such as taker and build/order usage per the guide.

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 to the Swap API v2?▼

To migrate Jupiter swap integrations from Metis to Swap API v2, update your base URLs to the swap/v2 endpoints and transition from the two-step quote/instructions flow to the unified /build or /order paths.

What is the best way to upgrade an Ultra integration to Jupiter Swap API v2?▼

The best way to upgrade an Ultra integration to Jupiter Swap API v2 involves migrating your existing endpoints to the new /order path and adjusting renamed parameters like taker to match the v2 response structures.

How does the unified Build/Order/Execute path work in Jupiter Swap v2?▼

The unified Build/Order/Execute path in Jupiter Swap v2 replaces the old two-step quote and instructions flow, consolidating parameter mappings and endpoint changes into a single, streamlined API transaction process.

Do I need to change the taker parameter when upgrading to Jupiter Swap v2?▼

Yes, you need to update renamed parameters such as taker when upgrading to Jupiter Swap v2, ensuring your codebase adjusts to the new response structures for a smooth transition without compatibility risks.

Can I migrate directly from Metis to the /order endpoint in Jupiter Swap v2?▼

Yes, you can migrate directly from Metis to the /order endpoint in Jupiter Swap v2, as the migration guide provides specific paths for both Metis to /build and Metis to /order transitions.

What are the limitations when moving from a two-step quote/instructions flow to Jupiter Swap v2?▼

When moving from the two-step quote/instructions flow to Jupiter Swap v2, you must account for endpoint changes and new response structures to avoid downtime, requiring a thorough post-migration checklist.