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.
git clone --depth 1 https://github.com/internet-court/internet-court-skill /tmp/jupiter-swap-migration && cp -r /tmp/jupiter-swap-migration/vendored/jupiter/jupiter-swap-migration ~/.claude/skills/jupiter-swap-migrationSKILL.md
# 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](https://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`](./examples/ultra-to-order.md) — Minimal migration, base URL change only - [Path 2: Metis → `/build`](./examples/metis-to-build.md) — Consolidates 2 calls into 1, parameter and response mapping - [Path 3: Metis → `/order`](./examples/metis-to-order.md) — Flow change to managed execution with multi-router competition --- ## Post-Migration Checklist 1. **URL audit**: Search codebase for `ultra-api.jup.ag`, `/ultra/v1/`, `/swap/v1/quote`, `/swap/v1/swap-instructions` — all should be replaced 2. **Parameter rename**: `userPublicKey` → `taker` (for `/build` path) 3. **`swapMode` removal**: V2 only supports `ExactIn`. If using `ExactOut`, redesign the flow — this mode is no longer available 4. **`slippageBps` default**: `/build` defaults to 50 bps if omitted. For `/order`, verify the default if your integration relies on a specific value 5. **Response field names**: Verify your code uses `inputAmountResult`/`outputAmountResult` for the `/execute` response (the canonical v2 field names) 6. **ALT handling**: If using `/build`, switch from `addressLookupTableAddresses` (array) to `addressesByLookupTableAddress` (object) — remove RPC ALT resolution code 7. **Fee event parsing**: V2 instructions don't emit fee events — update any transaction parser that depends on them 8. **Route plan format**: If parsing route plans, use `bps` field (canonical) instead of `percent` 9. **Error codes**: Update error handling to match [Swap v2 error codes](https://developers.jup.ag/docs/swap/order-and-execute.md) 10. **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](https://developers.jup.ag/docs/swap/migration/ultra-to-order.md) - [Migration: Metis → /build](https://developers.jup.ag/docs/swap/migration/metis-to-build.md) - [Migration: Metis → Meta-Aggregator (/order + /execute)](https://developers.jup.ag/docs/swap/migration/metis-to-meta-aggregator.md) - [Order & Execute](https://developers.jup.ag/docs/swap/order-and-execute.md) - [Build](https://developers.jup.ag/docs/swap/build/index.md) - [Swap overview](https://developers.jup.ag/docs/swap/index.md) (routing and fees) - [OpenAPI spec](https://developers.jup.ag/docs/openapi-spec/swap/v2/swap.yaml)
0G Compute Network guide for decentralized AI inference, fine-tuning, and GPU services. Covers chatbots, image generation, speech-to-text, SDK integration (0g-serving-broker), processResponse API, broker.inference methods, CLI commands (0g-compute-cli), and account management. Use this skill for any 0G compute, 0G AI, or decentralized GPU question.
Give the AI agent its own EVM wallet with admin-controlled policies the agent CANNOT bypass even under prompt injection. Encrypted keystore (AES-256-GCM, scrypt KDF), policy file the agent has no tool to write, deterministic policy gate on every signing operation, optional local HTTP dashboard. Triggers: agent wallet, give the agent a wallet, agent address, fund the agent, agent autonomy, policy gate, kill switch, agent permissions, bounded autonomy, ERC-4337 alternative, session-key alternative.
Crypto wallet operations via the awal CLI — sign in, check balances, send USDC/ETH/POL/SOL, trade tokens, fund the wallet, and use the x402 payment protocol to discover paid services, pay for API calls, monetize an API, or query onchain data. Use whenever the user mentions signing in, login, authentication, wallet status, balance, address, sending money, paying someone, transferring tokens, ENS names, swapping/trading/converting tokens, funding/topping up/onramp, USDC, ETH, POL, SOL, the x402 bazaar, paid APIs, monetizing an endpoint, or querying onchain data on Base.
Help developers write code that interacts with Alkahest escrow contracts using the TypeScript, Rust, or Python SDK
Interact with Alkahest escrow contracts as a buyer, seller, or oracle using the CLI
Use this skill when the user asks to list, create, inspect, update, disable, re-enable, or revoke AltLLM Portal API keys for external agents or applications. Do NOT use for wallet login, billing history, or payment links.
Use this skill when the user asks to log in or out with a wallet session, fetch a wallet sign-in challenge, verify an externally signed challenge, or troubleshoot AltLLM Portal wallet login for the local altllm CLI. Do NOT use for API key management, billing history, or payment links.
Use this skill when the user asks to inspect AltLLM Portal balance, redeem a promo code, review billing transactions, or view usage analytics by period, model, or API key using the local altllm CLI. Do NOT use for API key lifecycle management or payment-link execution.