Metis v1.0 Router: The OG Workhorse Of Solana As we move towards deploying multiple versions of our routers, including new experimental algorithms, we realize people may not understand the full scope of Jupiter, and how our routing systems work. We’ve come a long way since we started Jupiter. The Importance of Metis v1.0 Metis v1 Router is what we offer today to the ecosystem via 3 main channels - our API, a binary that we release for free, and via partners like Triton and Quicknode. It is also what we use as one of the options on our frontend today, alongside a more advanced version of Metis (v1.5), and JupiterZ. It is the workhorse of Solana DeFi, facilitating over $2 trillion in trading volume so far. It’s integrated into hundreds of applications, from wallets to trading bots, from simple frontend aggregators to the most sophisticated DeFi protocols. Across all of them, Metis v1 serves one purpose: make swaps work robustly and excellently. By plugging into Metis, projects have earned over hundreds of millions in cumulative fees - far more than Jupiter itself, which offers it largely for free or nearly free via the API and binary. This last point is actually crucial - the reliability of our Metis v1 API is what allows partners, including wallets and meta aggregators to build on top of it, since practically all routes and token pairs are served reliably by it. Metis has allowed anyone to offer world-class routing to their users without needing to build routing infrastructure themselves for free. Metis V1: Robust, Scalable, Reliable The core operating principle of Metis v1 is robustness, scalability and reliability. Metis v1 scales across every kind of frontend—wallets, browser extensions, mobile apps, pro trading terminals—and does so reliably. It handles swaps through pools that might have spiky liquidity, price slippage, or transient pricing issues. All while handling millions of transactions across different RPC providers and machines. It’s a workhorse. We also offer Metis v1 via binary. In order to make the API robust via the binary in potentially many different environments (different host machines/RPC providers/etc), we have to build up services to power these users. Markets are discovered and served from our Europa servers directly to the binary users. Europa will root out transient and low liquidity pools in order to make routing reliable for our binary users. We pay for the cost to run these Europa servers so that our binary users can enjoy the reliability of using Metis API without worrying about discovering new markets to trade on, transient markets messing with the token prices, and low liquidity pools causing high price impact to their users. When routing is reliable and accessible, everyone can innovate at higher levels of the stack. Wallets don’t have to figure out onchain pricing logic. Meta-aggregators don’t have to handle simulation errors. New DEXes don’t have to fight for discovery. Metis v1 makes the whole chain work better. Jupiter Is Way More Than Metis V1 On Jupiter’s frontend and with our new Ultra API, we have already been meta-aggregating different liquidity sources using Metis v1 as one of the liquidity sources together with our newer Metis v1.5 and also JupiterZ, our very own RFQ system. On top of that, Hashflow is also live and we are slowly ramping up traffic to DFlow. With meta-aggregation, we realize that different liquidity sources may perform differently depending on market conditions and token pairs. We have real time metrics to make sure that all these liquidity sources are performing as well as they are and our automated system will notice any abnormalities (unusually high slippage, etc) on these liquidity sources and shut them automatically. We also have a team on rotation to monitor the performance of it, too many times the team had to stay up to wonder why the landing success rate of our swap transactions was below 95%. Also, I am most excited about Metis v1.5 (which actually have been fully rolled out to all users) and the upcoming full rollout of Metis v1.6 and many subsequent updates after it. Internal tests show that trades with Metis v1.5 land 4.6x closer to the quoted price compared to v1. We obviously don’t stop just there, we are also concurrently testing a newer version of Metis v1.6 that has better pricing for our users. With the new meta-aggregation infra, we are making swap even better. It takes us a while and a lot of work to make sure that the new meta-aggregation infra has good observability for us to monitor different liquidity sources (including ours). It also allows us to experiment with different improvements we can make to Metis hence the faster improvements on Metis recently. This is important to understand: the price you get on Metis v1 is not the same as what you get on Jupiter. Jupiter is already pushing far beyond v1. We’re constantly experimenting with new routing strategies and rolling out updates directly to Jupiter first—because we can optimize for absolute quality without worrying about every possible partner edge case. We want to bring these upgrades to partners too—but we’ll only do so once we’re confident that they’re as stable and scalable as Metis v1 has been. In the meantime, partners continue to benefit from Metis v1’s robustness—but it’s crucial not to conflate the two. API Guidelines And this brings us to a simple but important request: If you're using our Metis v1 API as the basis for price comparisons or any other type of comparison to Jupiter—whether via the API or Binary—please label it accurately. Calling it “Jupiter” or labeling prices as “Jupiter prices” when they’re actually routed via Metis v1 is misleading. It causes confusion for users, especially when comparing quotes, and doesn’t reflect the upgrades already live on Jupiter today. The Jupiter trading experience means more than just routing—it includes newer engines, off-chain liquidity, deeper simulations, and advanced quote processing. We’re proud of Metis v1. We’ll continue supporting it and upgrading to higher versions when stable enough. It remains the most battle-tested, scalable, and reliable router in Solana DeFi. But it doesn’t provide the “Jupiter price.” Best Service Possible Metis v1 is the result of years of continuous investment of engineering time and resources, mostly as a public good for the Solana ecosystem. We’ve debugged DEX integrations, simulated failures, caught routing edge cases, optimized trade paths under insane network congestion, and supported partners whenever something breaks—even when it’s not our fault. Metis requires a vast and resilient network of API and RPC nodes to fetch real-time pool data, simulate trades, and submit transactions. Maintaining this infrastructure incurs substantial operational costs (upwards of millions of dollars) but is essential for delivering a seamless and reliable user experience for all. We have spent hundreds of thousands per month just to keep Metis v1’s infrastructure running smoothly. We’ve supported every major partner for free, helped launch integrations, and answered every support ticket. And since early 2025, we’ve made the binary and API version of Metis v1 entirely free. But the support doesn’t stop there even though Metis v1 is entirely free. We are still supporting our partners if they run into problems with it, especially the binary users. We are still working on feature requests from our partners to make it better, for example, allowing fees to be charged in a more flexible way (again, we don’t take any cut from this), etc. We are committed to delivering the best service possible to the users, ecosystem and partners. For users on Jupiter’s front-ends, you will get the best price, best execution and aggregations of the best routers we can find, both developed internally and externally. For the ecosystem, we will deliver the most robust Metis API for use across any given surface, keeping it as free as possible, and as updates are available and ready to be scaled, we will continue to upgrade it. For partners, we aim to deliver the best quality APIs, and we’ve continued to innovate on our developer programs with Ultra API, and our new Trigger APIs, with lots more to come.