Skip to main content
Metis is Jupiter’s original, low-level routing engine designed for maximum flexibility, transparency, and composability. It was the foundation that set the standard for reliable, general-purpose liquidity aggregation on Solana, and its learnings directly informed the development of newer engines like Iris (which powers Jupiter Ultra). Unlike Jupiter Ultra and its routing engines (Juno, Iris, JupiterZ), which focus on end-to-end execution and abstraction, Metis exposes granular control over raw swap instructions. This is beneficial for developers and integrators who need to fine-tune every aspect of their swap transactions.

​
We recommend using Ultra Swap API

Ultra Swap API is the spiritual successor to Metis Swap API, and is much simpler to use than Metis Swap API. If you are first starting out on your Solana development journey, using Ultra Swap API is highly recommended over Metis Swap API.
For more information about Ultra Swap API, please refer to the Ultra Swap API documentation.
Using Metis Swap APIRequires your own maintenance, optimizations and dependencies.
  • Upkeep of RPCs: To retrieve wallet balances, broadcast and retrieve transactions, etc.
  • Deciding transaction fee: Including, but not limited to, priority fee, Jito fee, etc.
  • Deciding slippage: The optimal slippage to use to balance between trade success and price protection, do note that RTSE is only available via Ultra Swap API.
  • Broadcasting the transaction: Ultra uses a proprietary transaction sending engine which dramatically improves landing rate and speed.
  • Parsing the swap results: Polling and parsing the resulting transaction from the RPC, including handling for success and error cases.
Though comes with other ways to use Jupiter.
  • Add custom instructions.
  • Use via Cross Program Invocation (CPI) calls.
  • Choose your own transaction broadcasting method (like Typical RPCs, Jito, etc).
  • Modify the number of accounts to use in a transaction.

​
Getting Started with Metis Swap API

  1. Get Quote: Request for a quote which consists of the route plan, and other params such as integrator fee, slippage, etc.
  2. Build Swap Transaction: Post the quote to build a swap transaction.
    • You can utilize other methods to return swap instructions or use CPI rather than the default swap transaction.
    • You can utilize other parameters such as priority fee, dynamic slippage, etc to customize the transaction.
  3. Send Swap Transaction: Sign and send the swap transaction to the network via your own RPC or other methods.
Other Guides