How Inverse Finance Improved UX by Integrating Enso API
What if you could slash DeFi complexity in just hours? Inverse Finance did exactly that.
As a DeFi protocol offering tools like sDOLA stablecoins, auto-compounding vaults, and liquidity solutions, Inverse uses smart contracts to simplify complex financial interactions for users.
In half a day, the team shipped a major user experience upgrade: one-click access to DeFi positions without the usual friction. Using Enso's routing API, they transformed multi-step user journeys into a single transaction across four different use cases.
As Alien from Inverse's development team puts it:
Implementation is very quick and easy... it saves quite a few steps if you use Enso.
What Users Were Experiencing
Inverse Finance users navigated a clunky, multi-step process, even for basic actions.
For example, getting sDOLA, Inverse's yield-bearing stablecoin is a two-step process, requiring a swap and a deposit: USDC → DOLA → sDOLA.
Entering liquidity positions is even more complicated than the deposit flow: it’s a process of at least 5-step, relying on careful manual execution using several tools. As Alien explains:
Instead of doing a swap for sDOLA and then splitting it into two to have the two sides of the liquidity position and then approve and deposit each... you can just have any token that is not even part of the liquidity pool position... just approve and then zap it into the LP position.
For example, entering a DOLAFRAXBP3CRV-f Curve position would comprise the following 7 transactions, all replaced by a single API call and a single Enso-crafted transaction.
The Half-Day Solution
Enso's /route API delivered exactly what users wanted with minimal development time:
- Implementation time: "Maximum half a day," according to Alien
- Technical simplicity: "The longest part would be just the swap interface... otherwise it's quite quick"
- Developer experience: "The API is so easy to use that the SDK doesn't offer much in addition to that"
The integration boils down to clean API calls:
Four Use Cases & UX Improvements
Inverse rapidly shipped one-click zapping across their product suite:
1. sDOLA Access: Direct path from any token to Inverse's yield-bearing stablecoin
2. sInv Vault Entry: Direct access to Inverse's auto-compounding tokenized vault
3. Collateral Zapping: Direct conversion to required collateral for firm markets
4. Liquidity Position Entry: One-click access to obtaining LP tokens from Curve and other protocols
But, even with this automation, Inverse approaches integration thoughtfully, allowing zaps to assets that have satisfying quotes. This way, Inverse ensures the users will get the best options for their assets.
What’s Next: Custom Stablecoins
Inverse is launching an exciting new project this summer: "a stablecoin as a service factory that allows anyone to launch their own stablecoin using any collateral with a price feed," according to Pat, Head of Growth at Inverse Finance.
As Pat notes: "If someone wants to build a stablecoin based on an LP position or even an index and they don't actually own all the underlying assets, we could just recommend Enso as a way for people to zap into whatever the underlying requirement is."
Why This Matters
The real value isn't just user convenience, it's how quickly DeFi teams can anticipate and respond to users’ needs. Usually, teams would either let users endure complex steps or take up the burden of lengthy dev cycles with manual integrations, upkeep, and debugging of several third-party DeFi protocols.
Enso enables rapid, user-focused product delivery:
- Traditional approach: complex routing infrastructure and lengthy development cycles
- Enso approach: One API, half-day implementation with immediate feature delivery.
This allows development teams to stay focused on core product innovation while still delivering the user experience improvements necessary for wider adoption.
Key Takeaways
This model of rapid, API-driven feature delivery could redefine how DeFi protocols compete on user experience, prioritizing speed and simplicity.
1. User Feedback Drives Features: Inverse built zaps because users specifically requested the convenience
2. Implementation Speed Matters: Half a day from decision to shipped feature means immediate user value
3. Technical Simplicity Enables Focus: Clean API integration allows focusing development on core products
4. Start Small, Expand Smart: Begin with proven use cases, then explore new opportunities
As Alien summarized:
For us Enso is more about making life easier for the users... It's a way to simplify the UX and make the experience a bit more convenient for users.
Sometimes the best innovations are the ones that just work, shipped fast.
Ship User-Requested Features in Half a Day
Start with Enso's /route API for one-click zap deposits, or expand to /bundle for assets bridging, automation, and custom flows.
Have your own half-day success story? We'd love to feature it.