You can build straight on top of validators and DeFi protocols. But the second you need multi-chain coverage, consistent UX, and institutional-grade controls, “direct integration” turns into a permanent engineering project. Yield.xyz exists to remove fragmentation so you can ship yield products through one integration layer. Yield.xyz is non-custodial: we construct ordered, unsigned transaction flows forDocumentation Index
Fetch the complete documentation index at: https://yieldxyz.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
enter / exit / manage, and your platform signs and broadcasts using your wallet or custody infrastructure.
Yield.xyz is infrastructure, not an asset manager. Your product remains responsible for what you offer, how you communicate risk, and which users are eligible.
The problem: yield infrastructure is fragmented
Even when protocols are mature, “integrate directly” usually means you’re signing up to build and maintain a growing pile of one-off systems:- Protocol-by-protocol engineering: every protocol comes with its own contracts, reward mechanics, token behaviors, and edge cases.
- Chain-by-chain differences: staking and DeFi flows vary across EVM and non-EVM networks, widening the integration surface area.
- Ongoing maintenance and audits: upgrades and behavior changes force repeated QA cycles and security reviews.
- Operational complexity: balances, lifecycle states, incentives, and reporting all differ per protocol.
- Custody constraints: institutional signing policies can break “typical DeFi flows” unless transactions are deterministic and reviewable.
Direct integration vs Yield.xyz
| Aspect | Direct Integration | Yield.xyz |
|---|---|---|
| Time to first yield | 2–4 weeks per protocol | Days for full catalog |
| Protocols supported | 1 per integration | 2,900+ opportunities |
| Maintenance burden | Ongoing per protocol | Managed by Yield.xyz |
| Cross-chain support | Manual per chain | Built-in (80+ networks) |
| Transaction construction | You build | We provide unsigned |
| Signing & execution | You control | You control |
| Fee monetization | Protocol-defined | Configurable via OAVs |
| Breaking changes | You handle | We handle |
The Yield.xyz approach: one integration that scales
Yield.xyz unifies on-chain yield behind a consistent model you can build on once—and keep stable as coverage expands:- Discovery: standardized yield opportunities and metadata. See Discover Opportunities.
- Actions: intent-based operations that return ready-to-sign, unsigned transactions. See Actions.
- Portfolio: lifecycle-aware balances for monitoring and reporting. See Balances & Positions.
Coverage without complexity
With one integration, partners can access 2,900+ yield strategies spanning 80+ networks across staking, DeFi, vault strategies, and more. See Supported Yields and Supported Networks for the full catalog.Coverage changes over time. Treat the docs as the conceptual model and the API catalog as the source of truth for what is currently available.
Built for institutional signing and self-custody
Yield.xyz is built to preserve your security boundary—no custody compromises, no surprises:- You control signing policies, approvals, and broadcast
- Compatible with EOAs, smart contract accounts, MPC, and institutional custody
- For transaction-intent validation before signing, use Shield to verify that unsigned payloads match expected safe patterns
Staking at scale: Preferred Validator Network
If you’re integrating staking, Yield.xyz provides access to an institutional-grade validator registry (Preferred Validator Network) with pre-vetted operators, selection criteria, and consistent metadata. For multi-validator deployments, Yield.xyz supports staking across 30+ large validators with SLAs, including uptime and slashing-related provisions. See Preferred Validator Network for details.Monetization and product control via OAVs
Direct protocol integrations often cap monetization at protocol or curator rev share. With Yield.xyz, OAVs (Optimized Allocator Vaults) can enable product-level fee configuration (deposit, management, and performance fees) and automation patterns on top of underlying strategies. Where applicable, OAVs can support reward handling (e.g., incentive conversion) and reinvestment/reallocation workflows, so your end-user experience stays single-asset and consistent—without bespoke protocol logic per integration. Learn more in OAVs Overview and OAV v3.Provider catalog: keep “supported protocols” accurate
Protocol availability changes. Don’t maintain a stale list—treat the Providers catalog as the canonical source for “what protocols are supported right now.” See Providers endpoint for the current list.Summary
Faster integration
One consistent interface instead of many bespoke builds
Stable maintenance
New protocols don’t require new client-side primitives
Self-custodial by design
Compatible with institutional security boundaries
Validator scale
PVN and multi-validator staking with SLAs
Monetization options
OAVs enable product-level fee and automation patterns
Reduced drift
Protocol coverage stays accurate via Providers catalog
Next steps
Quickstart
Make your first request
Core Concepts
Understand the primitives
OAVs
Explore monetization options
Plans & Limits
View pricing and limits