Enso vs. NEAR Intents
Rift Research
Last updated
TLDR: Enso is a DeFi action and shortcut layer. NEAR Intents is a multichain intent and solver network. Consider Enso when you need multi-step DeFi intents, not only a simple swap. Consider NEAR Intents when you need unusual pairs, non-EVM routes, or solver-sourced liquidity. Confirm the live winner on rates.gg.
What each protocol is
Enso. Enso is a unified DeFi API. The Route API finds a path into a destination token, LP or vault. The Bundle API composes ordered actions (swap, lend, borrow, deposit) into one transaction. Enso constructs transaction data for the integrating product to present for signing. The signing flow and underlying protocols determine permissions and custody assumptions. Official docs: Enso Docs. App: enso.finance.
NEAR Intents. NEAR Intents is a multichain intent protocol. You specify the outcome (asset in, asset out, destination). Market makers compete to fill it. The verifier contract settles intent batches on NEAR. Cross-chain deposits and withdrawals use token bridges, with their own settlement and refund conditions. Official docs: NEAR Intents Docs. App: near-intents.org.
Short version
| Dimension | Enso | NEAR Intents |
|---|---|---|
| Role | DeFi action and shortcut layer | Multichain intent + solver network |
| Fee | Depends on the composed route and underlying protocols | Solver spread set in the winning quote |
| Coverage | Multi-chain DeFi primitives connected through Enso integrations | Bitcoin, EVM chains, Solana, NEAR, TON, Sui, Stellar and other listed assets |
| Settlement | Atomic bundled transaction when using Bundle; otherwise the returned route tx | Atomic via the intents verifier on NEAR |
| Trust model | Enso router / wallet adapters plus each underlying protocol | Verifier contract on NEAR, solver liquidity, and the token bridges used for deposits and withdrawals |
| Good fit for | Multi-step DeFi intents, not only a simple swap | Unusual pairs, non-EVM routes, and solver-sourced liquidity |
| Docs | Enso Docs | NEAR Intents Docs |
Where each fits
Enso may fit when:
- The job is swap-plus-deposit, zap, or another multi-step action
- You want Enso to build the calldata while you keep the wallet UX
- A single-hop bridge or AMM swap is not enough
NEAR Intents may fit when:
- The pair or chain sits outside most EVM-only aggregators
- You want solvers competing on a signed intent
- Native settlement across non-EVM ecosystems matters
Key differences
Enso and NEAR Intents should be compared on the job you need to complete: the input asset, destination asset and chain, trade size, execution method and custody assumptions. They may overlap on some routes and complement each other on others. A broader chain list or faster advertised fill does not establish a better net rate. Compare executable quotes in the same window, including gas and every underlying step.
When to use which
- Use Enso when you need multi-step DeFi intents, not only a simple swap.
- Use NEAR Intents when you need unusual pairs, non-EVM routes, or solver-sourced liquidity.
- If both can quote the same route, take the better net output after fees, time and settlement type. Check that print on rates.gg.
FAQ
Which is cheaper, Enso or NEAR Intents?
Neither has a universal price advantage. Enso: Depends on the composed route and underlying protocols. NEAR Intents: Solver spread set in the winning quote. Compare executable quotes for the same size, destination and time window, including gas, underlying venue costs and any extra transfer. Expected output and minimum received are different figures; compare like with like.
Is Enso a substitute for NEAR Intents?
Only on overlapping pairs and chains. When both can quote the same route, take the better net output after fees and time. When only one supports the asset or chain, that one is the only option.
Where are the official Enso and NEAR Intents docs?
Enso: Enso Docs. NEAR Intents: NEAR Intents Docs. Live rate comparison: rates.gg.
Official sources
- Enso docs: Enso Docs
- Enso app: enso.finance
- Enso — Developer home: docs.enso.build/home
- Enso — Use cases: docs.enso.build/pages/use-cases
- Enso — API: api.enso.finance/api
- NEAR Intents docs: NEAR Intents Docs
- NEAR Intents app: near-intents.org
- NEAR Intents — What are intents?: docs.near-intents.org/getting-started/what-are-intents
- NEAR Intents — NEAR chain-abstraction overview: docs.near.org/chain-abstraction/intents/overview
- NEAR Intents — 1-Click Swap API: docs.near-intents.org/
Get the Best of Both With Rift
Rift is a strong alternative to choosing between Enso and NEAR Intents. It brings routes from both together with additional venues on supported pairs, comparing available quotes to find the best net execution for your order. You get the strengths of both through one API.
Rift adds no router fee and uses secure hardware enclaves to enforce noncustodial execution. Underlying venue fees, spreads and network costs still apply, and availability depends on the asset, chain and order size. The live quote shows the route and expected output.