Overview
Yield.xyz is the ultimate yield infrastructure for Web3, providing one unified API for every yield across 75+ networks. Instead of building and maintaining your own vaults or integrating directly with individual DeFi protocols like Morpho, Aave, or Lido, you can integrate Yield.xyz once and unlock 1,000+ standardized opportunities across staking, lending, and DeFivaults. Yield.xyz’s API is self-custodial by design: it constructs ready-to-sign transactions for yield actions but leaves execution and signing entirely in your control. You fetch opportunities and action flows from Yield.xyz, and have Turnkey sign and broadcast them under your policy-controlled keys.Why Yield.xyz instead direct protocol integrations?
- No protocol maintenance – skip deploying/managing your own vaults or building dozens of one-off integrations.
- Unified API – discover, enter, exit, manage, and track positions across 75+ chains and 1,500+ yields with one interface.
- Web2 Style UX — full abstraction of Web3 complexity via Optimized Allocator Vaults (OAVs) which automatically offramp and reinvest any incentive token issued by any protocol. Additional features include charging of deposit, management, and/or performance fees, as well as modules for e.g. cross chain routing.
- Pre-configured OAVs – instantly offer access to 10–20 standardized and pre-configured Optimized Allocator Vaults (“grab-off-the-shelf”) across popular assets.
- Custom OAVs – request dedicated OAVs for specific strategies or branded products.
- Monetization – ability to layer on additional user-level fees per OAV as well as revenue sharing from validators on all staking integrations
- Note: Yield.xyz enforces a minimum 10% fee
- Note: the validator revenue share is applicable only to PVN members (>30 of the largest validator service providers)
- Security & control – Turnkey enforces transaction policies so client keys can only interact with the exact vaults/tokens you allow.
Getting started
Follow the Turnkey Quickstart to set up:- Organization ID – logical grouping of resources( e.g. users, wallets, policies).
- Root quorum user – a root user with an API key pair.
- Non-Root User – a secondary user (with its own API key) outside the root quorum.
- Wallet – hierarchical deterministic (HD) wallet having at least an Ethereum wallet account.
- Turnkey Client & Signer – initialize a Turnkey client (
TurnkeyClient) with your API key pair and connect a signer (TurnkeySigner) from@turnkey/ethersto your RPC provider.
@turnkey/sdk-server.
Also, make sure you have a wallet with an Ethereum account created within this organization and have it funded with some ETH and USDC on Base Mainnet.
Follow the Yield Project Setup to create:
- Yield API KEY – to make authenticated requests to the Yield.xyz API.
- Discover available yields with
GET /v1/yields. - Act on them with
POST /v1/actions/{enter|exit|manage}. - Track balances and status with
GET /v1/yields/{id}/balances
Setting up the policies for the non-root user
Now, we want to use the non-root user for signing transactions to Yield.xyz and restrict it to only be able to interact with the USDC and Yield vault smart contracts. We’ll define a new API client that uses the organization’s root user to create the required policies.Each policy uses the
eth.tx.data field to identify which smart contract function is being called. The first four bytes of this field represent the function selector. For the approve function, the selector is 0x095ea7b3; for deposit it is 0x6e553f65; and for withdraw, it’s 0xba087652. This allows the policies to precisely restrict the non-root user to only those permitted contract calls.
Discover a yield (with metadata)
Discovery is just a read to the Yield.xyz API — Turnkey doesn’t change this step. You’ll typically do it server-side (to keep your Yield API key secret), then surface the results to your app where you’ll later enter using your Turnkey signer. Example: USDC yields on BaseExemplary Yields
To simplify integration, Yield.xyz provides a set of ready-to-use yields across both Stablecoins/DeFi and staking — designed to offer clean UX, consistent APIs, and monetization support. These yields are already live and have seen significant adoption across our clients.Stablecoin/DeFi Yields The Stablecoin/DeFi yields provided here are wrapped using Optimized Allocator Vaults (OAVs), which automatically handle:
- Incentive off-ramping & reinvestment
- Asset wrapping (where applicable)
- Fee charging (performance, management, deposit)
- 10% fee OAVs:
4bea9274-7cef-4e43-995b-f35147469ede - 20% fee OAVs:
e35de2d4-93e2-4cf8-b016-b0838fec1f20
| Yield ID | Yield Name | Protocol | Monetization |
|---|---|---|---|
| arbitrum-usdc-gtusdcc-0x7e97fa6893871A2751B5fE961978DCCb2c201E65-4626-vault | Gauntlet USDC Core | Morpho | Available deposit, performance, management fees |
| ethereum-usds-susds-0xa3931d71877c0e7a3148cb7eb4463524fec27fbd-4626-vault | USDS Sky Savings Rate | Sky | Available deposit, performance, management fees |
| ethereum-usdc-fusdc-0x9Fb7b4477576Fe5B32be4C1843aFB1e55F251B33-4626-vault | Fluid USDC Vault | Fluid | Available deposit, performance, management fees |
| base-usdc-smusdc-0x616a4e1db48e22028f6bbf20444cd3b8e3273738-4626-vault | Seamless USDC Vault | Morpho | Available deposit, performance, management fees |
| base-usdc-aave-v3-lending | USDC Aave Lending | Aave | Available deposit, performance, management fees |
- Enables delegations to any active validator
- Supports validator revenue sharing (50–85% of validator fees) with preferred validators
- Standardizes interactions across networks (undelegation, cooldowns, reward tracking)
| Yield ID | Network | Exemplary Validator | Validator Address | Monetization |
|---|---|---|---|---|
| solana-sol-native-multivalidator-staking | Solana | Meria | H2tJNyMHnRF6ahCQLQ1sSycM4FGchymuzyYzUqKEuydk | Deposit fees and revenue share |
| tron-trx-native-staking | Tron | Luganodes | TGyrSc9ZmTdbYziuk1SKEmdtCdETafewJ9 | Revenue share |
| bsc-bnb-native-staking | Binance | Figment | 0x477cB5d87144b2a6d93f72e32f5E01a459260D68 | Revenue share |
| ethereum-eth-everstake-staking | Ethereum | Everstake | N/A | Revenue share |
| ethereum-eth-figment-staking | Ethereum | Figment | N/A | Revenue share |
| hyperevm-hype-native-staking | Hyperliquid | Meria | 0x950f8dd5e5030e1fa6ad2cdc4295809d185925d0 | Revenue share |
| cosmos-atom-native-staking | Cosmos | Chorus One | cosmosvaloper15urq2dtp9qce4fyc85m6upwm9xul3049e02707 | Deposit fees and revenue share |
Enter the yield (deposit via Yield.xyz)
First, we’ll call the Yield.xyzPOST /v1/actions/enter endpoint to get the transactions required to enter the Morpho USDC vault on Base. We need to specify the yield ID for this vault, the amount to deposit, and our wallet address. For example, Yield.xyz’s identifier for Morpho’s Base USDC vault might be "base-usdc-gtusdcf-0x236919f11ff9ea9550a4287696c2fc9e18e6e890-4626-vault"(you can discover yield IDs via the Yield.xyz API or docs). We’ll deposit 0.5 USDC in this example.
The code below calls the Yield.xyz API (using a fetch request; you could also use Yield.xyz’s SDK) and retrieves the transactions. It then uses the non-root Turnkey user to sign and send each transaction in sequence:
approve or vault deposit call (no need to find contract ABIs or addresses ourselves). After executing these, our USDC is now deposited and earning yield in the vault.
Check user balance
After depositing, we can query the Yield.xyz API to confirm our position and even fetch the current yield stats. Yield.xyz provides a portfolio endpoint to get a unified view of a user’s balances in any yield.Exit the yield (withdraw funds)
Yield.xyz’sPOST /v1/actions/exit endpoint returns the transaction data required to perform a withdrawal. Similar to the enter action, you specify the yield ID, your wallet address, and the withdrawal amount.
withdraw function under the hood). We sent it with our Turnkey signer, and once mined, ~0.1 USDC would be back in our wallet.
Monetization
Monetization of yield interactions is possible on multiple levels depending on the yield type:- Staking.
- Deposit Fees: Leverage FeeWrapper contracts (EVM) and atomic fee transfer mechanisms (non-EVM) to deduct a percentage of the deposit and transfer it to the recipient in the same transaction.
- Revenue Share: Yield.xyz has agreements with 30+ validator service providers, entitling clients to a portion of validator revenues (typically 50%–85%).
- DeFi.
- Revenue Share: Some major protocols and curators provide revenue share on deposits via the Yield.xyz API.
- User-Facing Fees via OAVs:
- Optimized Allocator Vaults (OAVs) allow deposit, performance, and management fees to be configured at the user level.
- Performance Fees: Charged on realized profits.
- Management Fees: Flat annualized rate applied on AUM.
- Deposit Fees: Automatically deducted at the time of deposit.
possibleFeeTakingMechanisms object → API Reference
Web2 UX via OAVs
Beyond monetization, OAVs deliver a Web2-grade experience for Web3 yields.- Automatic Off-Ramping & Reinvestment: Incentive tokens are automatically off-ramped into the deposit asset and reinvested, ensuring users earn pure yield in their deposit token.
- Automatic Wrapping/Swapping: Complex asset flows are handled automatically, reducing friction and mirroring the simplicity of Web2 fintech apps.
- Unified UX: End-users interact only with their deposit asset — no juggling of dozens of reward tokens, no manual reinvestments.
- 10% fee OAVs:
4bea9274-7cef-4e43-995b-f35147469ede - 20% fee OAVs:
e35de2d4-93e2-4cf8-b016-b0838fec1f20
Conclusion
With this integration you can:- Discover yield opportunities across 70+ networks.
- Enter and Exit with standardized transactions.
- Track balances and rewards.
- Use Turnkey’s policy engine to ensure signing operations can only interact with the intended smart contracts.