
Why teams build with Yield.xyz
- Unified interface: One schema for discovery and metadata, one for actions, one for balances — consistent across yield types and chains.
- Faster time-to-launch: Add coverage without implementing protocol-specific integrations from scratch.
- Self-custodial by design: Your security boundary stays intact; you choose the signer, policies, approvals, and broadcast flow.
- Security posture for institutions: SOC 2 Type I is completed; SOC 2 Type II is in progress. For transaction-intent validation, Shield can be used to verify unsigned payloads before signing.
What you can build
Wallets
Add yield across networks with a consistent UX while keeping signing and execution in your wallet flow.
Custody platforms
Offer yield with policy-controlled signing, auditability, and operational controls aligned to institutional workflows.
Fintechs & neobanks
Launch yield products on crypto and stablecoin balances without maintaining dozens of protocol integrations.
Agents & automation
Programmatically discover opportunities and execute actions using standardized schemas and predictable transaction flows.
What you get
Yield.xyz provides three core primitives:- Yields: Standardized opportunities (staking, lending, vaults, RWAs) with normalized metadata for discovery and filtering. See Coverage for the full catalog.
- Actions: Consistent lifecycle actions like
enter,exit, andmanage, returning ordered unsigned transactions. Learn more in Core Concepts. - Balances: Unified portfolio views across lifecycle states (active, entering, exiting, claimable, etc.). See Balances & Positions.
Protocol coverage
Yield.xyz aggregates opportunities across major on-chain ecosystems and protocols — including Aave, Compound, Morpho, Spark, EigenLayer, and DEX/liquidity venues like Curve and PancakeSwap. For the full, up-to-date list, see the Supported Yields pages and the Providers endpoint.If you need a complete list of supported protocols for an RFP, generate it from the Providers list and Supported Yields catalog to keep it accurate as coverage expands.
Where to go next
1
Quickstart
Make your first request and understand the minimal integration flow.Go to Quickstart →
2
Core Concepts
Learn how Projects, Actions, Balances, Fees, and OAVs fit together.Explore Core Concepts →
3
API Reference
Use exact endpoint specs and schemas for implementation.View API Reference →
Need help?
Email Support
Partner Support
Use your dedicated Slack or Telegram channel if provisioned.

