> ## Documentation Index
> Fetch the complete documentation index at: https://yieldxyz.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Why Use Yield.xyz

> Remove fragmentation and ship yield products with a single integration layer

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** for `enter / exit / manage`, and your platform signs and broadcasts using your wallet or custody infrastructure.

<Note>
  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.
</Note>

***

## 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](/documentation/build-with-api/discover-opportunities).
* **Actions**: intent-based operations that return ready-to-sign, **unsigned** transactions. See [Actions](/documentation/core-concepts/actions).
* **Portfolio**: lifecycle-aware balances for monitoring and reporting. See [Balances & Positions](/documentation/core-concepts/balances-positions).

Your integration stays clean as the catalog grows—new opportunities can be enabled through the catalog **without** requiring new client-side primitives.

***

## 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](/documentation/coverage/supported-yields) and [Supported Networks](/documentation/coverage/supported-networks) for the full catalog.

<Info>
  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.
</Info>

***

## 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](/documentation/shield-security/shield) to verify that unsigned payloads match expected safe patterns

<Warning>
  Unsigned transaction construction reduces custody risk, but it does not eliminate protocol risk. Your product should define listing rules, risk policy, and user disclosures.
</Warning>

For institutional integration patterns, see [Custody Signing Flows](/guides/enterprise/custody-signing-flows).

***

## 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](/documentation/advanced-setup/staking-extensions/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](/documentation/oavs/overview) and [OAV v3](/documentation/oavs/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](/api-reference/ProvidersController_getProviders) for the current list.

***

## Summary

<CardGroup cols={2}>
  <Card title="Faster integration" icon="bolt">
    One consistent interface instead of many bespoke builds
  </Card>

  <Card title="Stable maintenance" icon="wrench">
    New protocols don't require new client-side primitives
  </Card>

  <Card title="Self-custodial by design" icon="shield-check">
    Compatible with institutional security boundaries
  </Card>

  <Card title="Validator scale" icon="users">
    PVN and multi-validator staking with SLAs
  </Card>

  <Card title="Monetization options" icon="dollar-sign">
    OAVs enable product-level fee and automation patterns
  </Card>

  <Card title="Reduced drift" icon="arrows-rotate">
    Protocol coverage stays accurate via Providers catalog
  </Card>
</CardGroup>

***

## Next steps

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/documentation/quickstart">
    Make your first request
  </Card>

  <Card title="Core Concepts" icon="book" href="/documentation/core-concepts/actions">
    Understand the primitives
  </Card>

  <Card title="OAVs" icon="vault" href="/documentation/oavs/overview">
    Explore monetization options
  </Card>

  <Card title="Plans & Limits" icon="credit-card" href="/documentation/plans-limits/plans-tiers">
    View pricing and limits
  </Card>
</CardGroup>