> ## Documentation Index > Fetch the complete documentation index at: https://docs.yield.xyz/llms.txt > Use this file to discover all available pages before exploring further. # FAQs > Short answers on what Yield.xyz provides, custody and signing, coverage, fees, security, API keys, exits, KYC and history, with links to the full pages. ## Product > **What does Yield.xyz provide?** > > Yield.xyz is a non-custodial API platform for offering on-chain yield, trading and borrowing to your users. It has three products, Earn, Trade and Borrow, each with its own API: the Earn API, the Perps API (Trade, today) and the Borrow API. All three use the same project API key and the same flow: find an opportunity, request an action, sign the transactions that come back, and track the result. See the [Quickstart](/documentation/get-started/quickstart) and [Why use Yield.xyz](/documentation/get-started/why-use-yieldxyz). > **What are Earn, Trade and Borrow?** > > **Earn** covers more than 4,000 yields across 85+ networks and 100+ protocols, including staking, lending, vaults, restaking, liquid staking and RWAs, through the Earn API. **Trade** offers Hyperliquid perps today through the Perps API, including markets that track stock prices. The Trade API, coming soon, adds Lighter perps, Hyperliquid spot and prediction markets, and stocks from Dinari and Ondo Global Markets behind the same `buy`, `sell` and `manage` calls. **Borrow** lets users supply collateral and borrow against it across about 960 markets on Aave V3, SparkLend, Morpho Blue and Lista, with Compound V3 being added, through the Borrow API. See [Earn](/documentation/earn/index), [Trade](/documentation/trade/index) and [Borrow](/documentation/borrow/index). > **What is the difference between Yield.xyz and StakeKit?** > > Yield.xyz is the current name of the product previously called StakeKit. The rename reflects the move from staking alone to Earn, Trade and Borrow. The `@stakekit/widget` npm package keeps its name. > **Which networks and yields are covered?** > > Coverage changes over time, so the coverage pages are the reference. See [Networks](/documentation/earn/networks/index) for the network list, and the Earn coverage pages for [staking](/documentation/earn/staking/coverage/index), [DeFi](/documentation/earn/defi/coverage/providers), [stablecoins](/documentation/earn/stablecoins) and [RWAs](/documentation/earn/rwas/coverage/issuers). Borrow and Trade have their own pages: [Borrow coverage](/documentation/borrow/coverage) and [Trade coverage](/documentation/trade/coverage). > **Why does GET /v1/yields not return every yield?** > > `GET /v1/yields` is project-scoped. It returns the yields enabled for the project that owns the API key. A yield can be missing because it is not enabled for your project, because of region or policy restrictions, or because it is temporarily disabled. Contact support with the yield ID and your project. For Borrow, `GET /v1/markets` is project-scoped by default in the same way. ## Custody and security > **Does Yield.xyz hold user funds or private keys?** > > No. Yield.xyz builds every transaction and returns it unsigned. You sign it in your own stack, with a browser wallet, MPC, a smart contract account or institutional custody, then either broadcast it yourself or return it for Yield.xyz to submit. See [Transaction signing](/guides/transaction-signing/index). > **What is Shield?** > > Shield checks each unsigned transaction before you sign it by comparing it with the pattern expected for it, including the target contract, receiver, spender and calldata. It reduces the risk of payload tampering and blind signing. See [Shield](/documentation/security/shield/index) and the [security overview](/documentation/security/overview). > **How do I report a security issue?** > > Email **[security@yield.xyz](mailto:security@yield.xyz)** and do not disclose the issue publicly. For security review material such as reports and data-handling details, ask your account team. ## API keys and plans > **How do API keys and projects work?** > > A project holds your configuration and API key. Send the key in the `x-api-key` header. The same project key works across the Earn API (`https://api.yield.xyz`), the Perps API (`https://perps.yield.xyz`) and the Borrow API (`https://borrow.yield.xyz`). Keep keys server-side. See [Onboarding](/documentation/get-started/onboarding). > **What are the rate limits and plans?** > > Limits are enforced per API key by plan. See [Rate limits](/documentation/plans-limits/rate-limits) and [Plans](/documentation/plans-limits/plans-tiers). For pricing questions, email [hello@yield.xyz](mailto:hello@yield.xyz). > **How do fees and monetization work?** > > You set your own fees on each product, and they are paid to you on-chain. Earn supports deposit, management and performance fees, Trade a builder fee on perps trades, and Borrow a fee on Morpho Blue loans. You also receive a share of the revenue earned by validators and vault curators. For Earn, see [Monetization](/documentation/earn/monetization). Trade and Borrow have their own pages: [Trade monetization](/documentation/trade/monetization) and [Borrow monetization](/documentation/borrow/monetization). > **How does geo-blocking work?** > > Yield.xyz can block requests by country or region at the API level. A blocked request returns `403`. See [Geo-blocking](/documentation/advanced-setup/geo-blocking/index). ## Exits, KYC and history > **Why is my exit not withdrawable yet?** > > Some yields have a cooldown or unbonding period. After an `exit` action, the balance moves to `exiting`, then to `withdrawable` once the cooldown ends. On some yields you then complete a withdrawal with a pending action. Read the balance's `pendingActions` instead of assuming funds return automatically. See [Balances and positions](/documentation/earn/core-concepts/balances-positions) and [Enter and exit flows](/guides/earn/enter-exit-flows). > **How do KYC and eligibility work for RWA yields?** > > Some RWA products require the issuer to approve the depositing address. Check `GET /v1/yields/{yieldId}/kyc/status` before building an action. See [KYC](/documentation/earn/rwas/kyc) and [Check RWA eligibility](/guides/earn/rwas/check-eligibility). > **Where do I find historical data?** > > Reward-rate history and TVL history are public endpoints. Rewards history and balances history are not public. See [Rewards and history](/documentation/earn/core-concepts/rewards-history). > **How do I troubleshoot API errors?** > > `401` means the key is missing or invalid, `429` means you exceeded your [rate limit](/documentation/plans-limits/rate-limits), and `400` means invalid parameters. [Errors and retries](/api-reference/errors-retries) lists which errors are safe to retry. ## Support > **How do I get help or request a new integration?** > > Email [hello@yield.xyz](mailto:hello@yield.xyz) with the endpoint, timestamp, request or action ID and yield ID. To request a network, protocol or yield, include the name, target assets and expected volume. For onboarding steps, see [Onboarding](/documentation/get-started/onboarding). > **Where do I track changes?** > > See the [changelog](/changelog/index). > **[Quickstart](/documentation/get-started/quickstart)** > > Run the full integration loop with your first requests. > **[Contact support](mailto:hello@yield.xyz)** > > [hello@yield.xyz](mailto:hello@yield.xyz) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.