Aggregator research
Jupiter vs 1inch: Coverage, Modes and Features
Compare Jupiter and 1inch using documented network coverage, gasless conditions, order types and developer features, without an invented price winner.
Start with the network and product you intend to use
Jupiter’s documented Spot and Swap API products focus on Solana. That does not make this a simple “Solana versus EVM” comparison: current 1inch Intent Swap documentation also includes Solana. Product mode, token coverage and execution requirements determine whether two routes can be compared for a particular trade.
Jupiter and 1inch: documented capabilities
| Research question | Jupiter | 1inch |
|---|---|---|
| Listed chain coverage | Solana | Ethereum, BNB Chain, Polygon, Arbitrum, OP Mainnet, Avalanche, Gnosis, Fantom, ZKsync Era, Base, Linea, Solana, Unichain, Sonic, Robinhood Chain, Monad, Cronos, Hyperliquid L1, Arc |
| Gasless modes | Conditional Eligible Swap V2 orders, JupiterZ quotes or an integrator-funded payer. Automatic sponsorship depends on SOL balance and trade size, and can reduce output through higher fees. Account rent and referral settings change who pays. Documented networks: Solana. Checked | Conditional Fusion execution on supported EVM networks; not Classic mode. Initial approvals may need gas. Solana Fusion requires SOL to publish the intent. Resolver execution costs can be reflected in output. Documented networks: Ethereum, BNB Chain, Base, Arbitrum. Checked |
| Intent-based execution | Not documented | Conditional Fusion and Fusion+ use resolver-filled intents; Classic swaps are a separate mode. Fusion uses auction-based execution. Solana intents start on-chain, unlike the EVM signing flow. Documented networks: Ethereum, BNB Chain, Base, Arbitrum, Solana. Checked |
| Limit orders | Available Target-price limit orders in Jupiter Spot. Order execution depends on the target price and available liquidity. Spot also documents recurring order tools. Documented networks: Solana. Checked | Available Limit orders through the 1inch interface and Limit Order API. Makers specify a target price and expiry; a fill requires a willing taker and suitable market conditions. Listed networks are a reviewed subset. Documented networks: Ethereum, BNB Chain, Base, Arbitrum. Checked |
| RFQ liquidity | Conditional JupiterZ market-maker quotes through the Meta-Aggregator path. RFQ competes with on-chain routers and is not returned by the Router-only path. Pair availability and market-maker participation vary. Documented networks: Solana. Checked | Not documented |
| Developer API | Available Swap API V2 offers managed orders and a custom transaction build path. API keys are required. Metis V1 has been superseded; integrations should use the current product documentation. Documented networks: Solana. Checked | Available Developer APIs for swap routes and signed intent orders. Use the product-specific API version and network support list. Access credentials and plan limits apply. Documented networks: Ethereum, BNB Chain, Base, Arbitrum, Solana. Checked |
| Cross-chain swaps | Not documented | Conditional Fusion+ and the Solana-EVM cross-chain swap flow. Availability depends on the source/destination assets and resolver route. A supported network does not guarantee every token pair. Documented networks: Ethereum, BNB Chain, Base, Arbitrum, Solana. Checked |
| MEV protection | Not documented | Conditional Fusion-mode execution, including documented Solana MEV resistance. The claim is specific to Fusion execution and should not be applied to every Classic swap or interpreted as a security guarantee. Documented networks: Ethereum, BNB Chain, Base, Arbitrum, Solana. Checked |
Capabilities describe the named product and its documented mode. They do not establish an execution-price winner, guarantee a fill or measure platform safety.
Compare reported metrics and other platformsWhere the comparison becomes useful
For an interface user
Begin with the supported network, token pair and order type. Compare the documented mode conditions in the table, then open each platform’s own interface to inspect an actual quote. Directory volumes cannot establish which platform will give your trade a better net result.
For a developer
Jupiter separates managed transaction assembly from a router path offering more transaction control. 1inch’s Intent Swap product uses its own order and resolver workflow. Evaluate the API product, authorization, fee handling and transaction lifecycle that fit your integration.
For performance research
Use the linked metrics comparison for reported 24-hour, seven-day and thirty-day activity. Those figures are source-reported platform metrics, not a common-chain benchmark, measured slippage or routing-quality score. Unknown capability data remains unknown rather than being counted as a disadvantage.
Official reading
Editorial guide reviewed . Individual feature sources and review dates appear with each claim. These are research pages, not executable quotes.