internet-court/internet-court-skill / vendored/jupiter/jupiter-swap-migration
jupiter-swap-migration
VerifiedMigration 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.
| File | Kind | Size |
|---|---|---|
| LICENSE | other | 1.0 KB |
| README.md | markdown | 1.1 KB |
| SKILL.md | skill md | 4.8 KB |
| examples/metis-to-build.md | markdown | 4.2 KB |
| examples/metis-to-order.md | markdown | 2.4 KB |
| examples/ultra-to-order.md | markdown | 2.1 KB |
README.md
View on GitHub# Jupiter Swap Migration
Migration guide for upgrading existing Jupiter swap integrations to the unified Swap API v2.
## What does the skill cover
| Migration Path | Description |
|---------------|-------------|
| Ultra → `/order` | Minimal migration — base URL change only, parameters and responses identical |
| Metis → `/build` | Moderate migration — consolidates quote + swap-instructions into single `/build` call with parameter and response mapping |
| Metis → `/order` | Flow change — switch from self-managed RPC execution to Jupiter-managed execution with multi-router competition |
## Examples
Before/after code and mapping tables in `examples/`:
- `ultra-to-order.md` — Ultra base URL swap with new response fields
- `metis-to-build.md` — Parameter mapping, response mapping, V2 instruction differences
- `metis-to-order.md` — Flow change to managed execution with trade-off analysis
## Related skills
- `integrating-jupiter` — Comprehensive Jupiter API integration guide (use for new builds, not migrations)
- `jupiter-lend` — Deep SDK-level integration with `@jup-ag/lend`
## License
MIT
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |