DeFi yield for Openfort embedded wallets

When a team builds an app with Openfort, every user gets an embedded wallet automatically. The new vaults.fyi recipe lets that app do more with the wallet than hold a balance. Users can browse vaults from across 80+ protocols, ranked by APY, and deposit in a couple of taps without leaving the app or reaching for a seed phrase.

The recipe is now live in the Openfort recipe hub. It pairs the embedded wallet with the vaults.fyi API to discover vaults, deposit, track positions across every protocol, and claim rewards. One integration for the app team. One flow for the user.

Openfort exists so every user gets a wallet without the key-management overhead. This recipe lets apps turn that wallet into a place to earn, with the full range of DeFi vaults to choose from. That is what accessible yield should look like.
Joan Alavedra, co-founder at Openfort

What the app can offer users

Earning DeFi yield normally means managing your own wallet, comparing dozens of protocols yourself, holding a gas token, and tracking the position after the deposit. The recipe gives the app what it needs to handle each one.

• The whole market in one view. Discovery spans 80+ protocols, with vaults ranked by APY. The app decides how much of that to surface, from a curated shortlist to the full ranked list for users who want to compare. Either way the options are comparable side by side.
• No app to leave. The deposit happens inside the app the user already signed into. The Openfort embedded wallet signs it. No browser extension, no seed phrase, no separate DeFi front-end.
• No gas token to hold. An optional Openfort fee sponsorship policy lets the app cover gas, so a user depositing USDC never needs to acquire a separate token to pay for the transaction.
• A real position, not a wrapper. The deposit calldata targets the canonical protocol contract directly. No wrapper contract, no idle cash buffer, no required user-facing fee. The position is identical to one a user would hold by interacting with Morpho, Sky, or Aave from any other wallet. Accessibility does not cost users a cut of their yield.

How the integration works

One API across 80+ protocols, 1,000+ vaults, and 20+ networks. Discovery and deposit are two calls. The recipe wires the result to the Openfort embedded wallet for signing:

import { VaultsSdk } from "@vaultsfyi/sdk";

const sdk = new VaultsSdk({ apiKey }, { apiBaseUrl });

// 1. Discover vaults across 80+ protocols, ranked by 7-day APY.
const { data: vaults } = await sdk.getAllVaults({
  query: {
    allowedAssets: ["USDC"],
    allowedNetworks: ["base"],
    onlyTransactional: true,
    sortBy: "apy7day",
    sortOrder: "desc",
  },
});

// 2. Build the deposit. Swapping protocols is one field: vaultId.
const { currentActionIndex, actions } = await sdk.getActions({
  path: {
    action: "deposit",
    userAddress,
    network: "base",
    vaultId: vaults[0].vaultId,
  },
  query: { assetAddress, amount },
});

// 3. The Openfort embedded wallet signs each step.
for (const step of actions.slice(currentActionIndex)) {
  await sendTransaction(step.tx);
}

Moving a user from a Morpho vault to a Sky vault to an Aave market is a change to one vaultId. No new ABIs, no new connectors, no new code.

Monetization

The recipe shows the discovery and deposit path. The same API also lets the app earn on the deposits it routes. When an app sends a user into a curated vault, the curator can rebate a share of its performance fee back to the app that drove the deposit. That revenue share settles automatically. There is no wrapper contract to deploy and no fee plumbing for the team to build.

This is how wallets and exchanges already monetize yield through vaults.fyi. The app gets a revenue stream without charging the user. The position stays canonical, and the rebate comes out of fees the curator already collects, not a new layer on top. To turn it on for an app, DM @vaultsfyi on X.

Getting started

Pull the recipe:

pnpx gitpick openfort-xyz/recipes-hub/tree/main/vaults-fyi openfort-vaultsfyi && cd openfort-vaultsfyi

The recipe README walks through Openfort credentials, the vaults.fyi API key, and the backend setup. Sign up for an API key at portal.vaults.fyi. The recipe keeps that key server-side behind a dev proxy so it never reaches the browser bundle. For production, swap the proxy for your own backend route that adds the same header. The full walkthrough is on the Openfort Recipes Hub.

Questions, feedback, or interest in turning on monetization: @vaultsfyi on X.

About Openfort

Openfort provides wallet infrastructure that abstracts crypto complexity for both users and developers, with smart wallet capabilities, agentic workflows, and gas sponsorship built in. The Openfort recipe hub is a set of self-contained code samples for common onchain flows, with recipes already covering Aave, Morpho, Hyperliquid, and more. Each single-protocol recipe wires up one protocol's contracts directly. The vaults.fyi recipe covers all of them through one API.

About vaults.fyi

vaults.fyi is the data and execution layer for DeFi yield. The API gives wallets, fintechs, and apps a single integration to surface vaults across 80+ protocols and 20+ networks, build deposit and withdrawal transactions, and track positions and rewards. Wallets and exchanges use it to ship yield without taking on protocol-by-protocol integration overhead.