> ## 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. # Real-world assets > Tokenized treasuries, money-market funds, and private credit from nine issuers, and how issuers, products, and KYC eligibility fit together. Real-world-asset (RWA) yields cover tokenized treasuries, money-market funds, and private credit from nine issuers. Each one wraps an off-chain instrument in an on-chain token, and you enter and exit it like any other yield. Where an issuer requires KYC for a product, the Earn API checks the address before it builds any transaction. ## Issuer, product, and asset An issuer is the entity operating one or more RWA products, for example Midas or Securitize. Each product, such as Midas's mTBILL or Securitize's ACRED, can be deployed on more than one network. Every network deployment is a separate yield with its own input token and position (or share) token: `ethereum-usdc-midas-mtbill-vault` and `base-usdc-midas-mtbill-vault` are two yields for the same mTBILL product. Entering exchanges the product's input token, typically a stablecoin, for the position token representing your share of the strategy. Exiting reverses that exchange, subject to the product's redemption mechanics: instant, request-based, or scheduled around fixed windows, depending on the issuer. See [Issuers](/documentation/earn/rwas/coverage/issuers) for each issuer's product families and networks, and [Assets](/documentation/earn/rwas/coverage/assets) for the canonical per-asset list of input and position tokens. ## Eligibility Whether a product requires off-chain identity verification (KYC) before you can enter or exit is set by the issuer, per product, not per issuer. Midas, for example, requires KYC for mGLO, mGLOBAL, and mF-ONE, but not for mTBILL or mROX. A yield's `mechanics.requirements.kycRequired` field tells you which applies. See [KYC](/documentation/earn/rwas/kyc) for the full eligibility model, and [Issuers](/documentation/earn/rwas/coverage/issuers) for a per-issuer KYC summary. ## Discovery and actions Query `GET /v1/yields?types=real_world_asset` for the RWA yields enabled for your project. Like every yield endpoint, the response is scoped to your API key's project. See [Discover yields](/documentation/earn/core-concepts/discover) for the full set of filters and pagination. Yuzu Money's yields carry the public `type` `vault`, not `real_world_asset`, so the type filter won't return them. Find them with `providers=yuzu` instead: see [Yuzu Money](/documentation/earn/rwas/yuzu). Once you've found a yield, entering, exiting, and managing it work the same way as any other yield: see [Actions](/documentation/earn/core-concepts/actions). A KYC-gated yield also requires the address to be approved by the issuer, and the Earn API checks that approval before it builds an enter or exit transaction. Tokenized stocks and equity ETFs belong to Trade's upcoming [Tokenized Stocks](/documentation/trade/tokenized-stocks) product, not RWA yields. ## Next steps Every RWA issuer's product families, networks, and KYC posture. The canonical per-asset view: input token, networks, and KYC. How eligibility is modeled, checked, and enforced. Request enter, exit, and manage actions for any yield. Enter and exit an RWA yield, step by step. Check KYC status before you build an enter or exit, using [`GET /v1/yields/{yieldId}/kyc/status`](/api-reference/KycController_getStatus). This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.