Jupiter Swap Migration

OrganizationPopular

internet-court

jupiter-swap-migration

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.

Overview

Publisher	internet-court
Repository	`internet-court-skill`
Skill name	`jupiter-swap-migration`
Stars	5.8K
Forks	106
Bundled files	3
License	MIT
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
3 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by internet-court on GitHub. Read the source before you install it.

Installation

Install the Jupiter Swap Migration AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/internet-court/internet-court-skill/tree/main/vendored/jupiter/jupiter-swap-migration

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/internet-court/internet-court-skill.git /tmp/internet-court-skill
mkdir -p .claude/skills
cp -r /tmp/internet-court-skill/vendored/jupiter/jupiter-swap-migration .claude/skills/jupiter-swap-migration

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Jupiter Swap Migration in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Jupiter Swap Migration on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Jupiter Swap Migration is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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

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 — Minimal migration, base URL change only
Path 2: Metis → /build — Consolidates 2 calls into 1, parameter and response mapping
Path 3: Metis → /order — Flow change to managed execution with multi-router competition

Post-Migration Checklist

URL audit: Search codebase for ultra-api.jup.ag, /ultra/v1/, /swap/v1/quote, /swap/v1/swap-instructions — all should be replaced
Parameter rename: userPublicKey → taker (for /build path)
swapMode removal: V2 only supports ExactIn. If using ExactOut, redesign the flow — this mode is no longer available
slippageBps default: /build defaults to 50 bps if omitted. For /order, verify the default if your integration relies on a specific value
Response field names: Verify your code uses inputAmountResult/outputAmountResult for the /execute response (the canonical v2 field names)
ALT handling: If using /build, switch from addressLookupTableAddresses (array) to addressesByLookupTableAddress (object) — remove RPC ALT resolution code
Fee event parsing: V2 instructions don't emit fee events — update any transaction parser that depends on them
Route plan format: If parsing route plans, use bps field (canonical) instead of percent
Error codes: Update error handling to match Swap v2 error codes
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
Migration: Metis → /build
Migration: Metis → Meta-Aggregator (/order + /execute)
Order & Execute
Build
Swap overview (routing and fees)
OpenAPI spec

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Jupiter Swap Migration AI skill do?

Why use Jupiter Swap Migration on TypingMind?

Because you install it once and use it with any model. Jupiter Swap Migration is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Jupiter Swap Migration in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/internet-court/internet-court-skill/tree/main/vendored/jupiter/jupiter-swap-migration. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Jupiter Swap Migration?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Jupiter Swap Migration?

As many as you like. As long as a model supports skills, you can use Jupiter Swap Migration with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Jupiter Swap Migration AI skill free?

Yes. It is published on GitHub by internet-court under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Tdd

mattpocock

CommunityPopular

Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

To Spec

Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.

To Tickets

Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket…

Triage

Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Jupiter Swap Migration Guide

Use/Do Not Use

Migration Paths

Path Details

Post-Migration Checklist

Sunset

References

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now