> ## 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 > Compare one non-custodial API against integrating protocols, validators, and venues directly. Every yield source, from a lending market to a validator set, has its own contracts, reward logic, and data pipeline. Integrating each one directly means a separate build, a separate audit, and a separate maintenance burden per protocol and per network. yield.xyz replaces that per-protocol work with one API: one schema for staking, DeFi, RWA, and stablecoin yield, plus trading and borrowing, with signing and custody staying on your side. ## One API across protocols and networks One integration covers the whole catalog instead of one protocol at a time: * **Earn**: 3,300+ yields across 75+ networks and 100+ protocols, including 1,200+ staking yields across 60+ networks and 1,600+ DeFi yields. * **Trade**: Perps on Hyperliquid through one order and position model; Tokenized Stocks is upcoming. * **Borrow**: one supply/borrow/repay/withdraw model across lending protocols. Adding a new protocol or network to your product is a catalog change on yield.xyz's side, not a new integration on yours. ## Non-custodial by design yield.xyz never holds keys or funds. Every action, whether it comes from your backend or from an agent, returns an ordered, unsigned transaction. **We construct. You sign.** Before a transaction reaches your signer, you can run it through [Shield](/documentation/platform/shield/index), which validates, decodes, tamper-checks, and risk-scores it, so you are not signing opaque calldata. ## What you don't have to build or maintain Direct integration means owning this per protocol and per validator: * Protocol-specific contract logic and multi-sig or execution setup * A separate API integration for every validator * Reward-token claiming, swapping, and reinvestment to keep reported yield accurate * Re-audits and code changes every time a protocol upgrades * Country, address, and eligibility screening for compliance yield.xyz absorbs this work behind the same schema, so your integration code does not change as coverage expands. ## Data Knowing what a position actually earned means indexing TVL, APY, and rewards across every protocol it touches. [Platform › Data](/documentation/platform/data/index) normalizes discovery metadata, portfolio tracking, and historical analytics across 100+ protocols, so you query one API instead of building that indexing pipeline yourself. ## Monetization You can earn revenue on the flows you route. [Earn › Monetization](/documentation/earn/monetization) covers the fee model for yield. [Vaults & OAVs](/documentation/platform/vaults/index) let you configure deposit, management, and performance fees, enforced on-chain, with no contracts of your own to deploy. [Incentive Campaigns](/documentation/platform/incentive-campaigns) let you boost APYs and reward users in any ERC-20 token, live in about a day. On Trade, Perps orders can carry a builder-code fee of up to 0.5%, depending on the venue. ## Next steps Get an API key and run your first discover → enter → track loop. See the full RWA, DeFi, staking, and stablecoin catalog. Read how transaction validation and risk-scoring work. Endpoint specs and schemas for implementation. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.