RWAKit

RWA Kit is the Yield API surface for regulated, off-chain assets settled on-chain that pay a yield — US Treasuries, money-market funds, fixed-income funds, private credit pools, yield-bearing notes, basis/carry strategies, and yield-bearing stablecoins. One interface, every issuer, every chain — protocol-specific quirks absorbed inside the integration. Tokenized stocks and equity ETFs are out of scope here; see StockKit for those.

API surfaces

RWAKit is one API surface — there is no separate KYC service. KYC is exposed as endpoints on the Yield API itself.

Yield types & supported products

U.S. Treasuries

Tokenized US T-Bills, money-market funds, and Treasury ETF wrappers — plus the only EU short-end fixed-income product (bC3M, included here for proximity to short-duration USD exposure).

Credit

Investment grade, high yield, municipals, CLOs, senior loans, BDCs, and private credit. ACRED is the only allowlist-gated private-credit fund live on-chain; the Dinari fixed-income dShares are coming soon.

Yield-Bearing Notes & Stablecoins

Product shapes that look like stablecoins but settle differently: Reg S Cayman secured notes (Ondo), SEC-registered face-amount certificate, and a yield-bearing ERC-20 stablecoin (Dinari).

EU Treasuries

EUR-denominated short-end government bond exposure.

Actively Managed Strategies

Performance-fee-based strategies — crypto carry / basis, structured yield, MEV arbitrage, BTC-denominated yield. No recurring management fee on Midas; Superstate's USCC is for US Qualified Purchasers only.

Actively managed strategies

¹ Screened — kycRequired is true, but there is no user-facing onboarding flow. Every wallet is automatically screened for sanctions, illicit-actor, and restricted-jurisdiction exposure.

Issuer comparison

This is the canonical at-a-glance view of every RWA issuer Yield.xyz supports for yield-bearing instruments. Equity-side coverage per issuer (tokenized stocks, equity ETFs, equity dShares, dividend streams) lives in StockKit.

How yield accrues

Each RWA token accrues yield through its own native mechanism. Partners don't need to branch on this — value always shows up in the position balance and live APY — but the mechanism matters for NAV cadence, reporting, and reconciliation.

KYC model

Every yield carries its access requirements under mechanics.requirements:

• kycRequired: false — permissionless. The user can deposit immediately. (USD+, mTBILL)
• kycRequired: true with issuer onboarding — the wallet must be on the issuer's allowlist before the deposit transaction will build. actions/enter returns 412 Precondition Failed with the issuer's authorizeUrl; the user completes the issuer's hosted KYC there, and the call succeeds once the wallet is allowlisted. (Superstate, Ondo, Securitize, Midas mGLO)
• kycRequired: true with automatic screening — no onboarding flow exists; wallets are screened automatically at the compliance layer and non-compliant wallets are rejected before any transaction is built. (Nest)

A wallet's normalized status for any yield can be polled at any time:

GET https://api.yield.xyz/v1/yields/{yieldId}/kyc/status?address=0xUserWallet

{
  "kycStatus": "not_started",   // not_required | not_started | pending | approved | rejected
  "authorizeUrl": "https://..." // present when the wallet still needs to verify
}

Yields without a KYC requirement return { "kycStatus": "not_required" }. On-chain reads distinguish approved / not_started / rejected; pending lives in the issuer's off-chain provider and isn't always readable on-chain.

The integration model

Every RWA Kit position follows the same three-phase model regardless of KYC posture or settlement style — identical to the existing Yield API lifecycle:

1. Discover — GET /v1/yields (RWA Kit yields appear inline with DeFi yields).
2. Enter — POST /v1/actions/enter returns ordered, unsigned transactions to sign client-side and broadcast.
3. Exit — POST /v1/actions/exit returns the redemption transaction(s); asynchronous redemptions surface on the balance as unstaking with an expectedSettlementAt until they settle.

For KYC-gated instruments, a 412 Precondition Failed from actions/enter carries the issuer's authorizeUrl — the user completes verification there and the call is retried once the wallet is allowlisted.

After broadcasting a signed transaction, report the hash back for indexing:

PUT https://api.yield.xyz/v1/transactions/{transactionId}/submit-hash
{ "hash": "0xBroadcastedTxHash" }

Identifying RWA instruments

GET https://api.yield.xyz/v1/yields
  ?type=real-world-asset
  &provider=midas,superstate,ondo,securitize,dinari,nest

Supported query params include type / types, network / networks, chainId, provider / providers, token, inputToken / inputTokens, search, sort, hasCooldownPeriod, hasWarmupPeriod. The RWA yield type is real_world_asset. KYC posture and eligibility are read off each yield's metadata block (below), not passed as query filters.

Yield metadata schema

RWA yields use the standard yield schema. Access requirements live under mechanics.requirements:

{
  "id": "ethereum-usdc-superstate-ustb-vault",
  "name": "Invesco Short Duration US Government Securities Fund",
  "token": { "symbol": "USDC", "network": "ethereum" },
  "rewardTokens": [{ "symbol": "USTB" }],
  "mechanics": {
    "type": "real-world-asset",
    "cooldownPeriod": { "days": 1 },
    "requirements": {
      "kycRequired": true,
      "kyc": {
        "kycMode": "external_redirect",
        "iframeAllowed": false,
        "authorizeUrl": "https://superstate.com/register",
        "eligibility": {
          "defaultPolicy": "deny",
          "countries": ["US", "..."],
          "blockedCountries": [],
          "blockedSubdivisions": [],
          "usPersonAllowed": true,
          "investorEligibility": [
            {
              "jurisdiction": "US",
              "tier": "us_qualified_purchaser",
              "verificationLevel": "third_party_attestation"
            }
          ],
          "subjectTypes": ["KYC", "KYB"]
        }
      }
    }
  }
}

Integration walkthrough — Ondo OUSG (KYC-gated)

POST https://api.yield.xyz/v1/actions/enter
Content-Type: application/json

{
  "yieldId": "ethereum-usdc-ondo-ousg-vault",
  "address": "0xUserWallet",
  "arguments": { "amount": "10000" }
}

If the wallet isn't yet allowlisted you'll receive a 412 (rendered from RwaKycError):

{
  "statusCode": 412,
  "timestamp": "2026-06-10T12:34:56.789Z",
  "path": "/v1/actions/enter",
  "message": "Address 0xUserWallet is not allowlisted for Ondo. Complete KYC at https://app.ondo.finance/signin",
  "details": {
    "address": "0xUserWallet",
    "protocol": "Ondo",
    "authorizeUrl": "https://app.ondo.finance/signin"
  }
}

The details keys are address, protocol, authorizeUrl. Hand the user off to authorizeUrl; once the wallet is allowlisted, actions/enter succeeds and you proceed exactly as in the permissionless case.

try {
  await yieldxyz.actions.enter({ yieldId, address, arguments: { amount } });
} catch (err) {
  if (err.statusCode === 412) {
    window.location = err.details.authorizeUrl; // issuer KYC portal, then retry
  }
}

Partners whose existing KYC the issuer accepts under reliance can skip the hosted flow — request a direct whitelist via the Yield.xyz team and the wallet is allowlisted without ever seeing a 412. See KYC model.

Integration walkthrough — Dinari USD+ (permissionless)

USD+ is a yield-bearing stablecoin the user holds directly — there is no intermediary share. Enter converts USDC → USD+; exit converts USD+ → USDC through an async redemption queue.

POST https://api.yield.xyz/v1/actions/enter
Content-Type: application/json

{
  "yieldId": "ethereum-usdc-dinari-usd-plus-vault",
  "address": "0xUserWallet",
  "arguments": { "amount": "1000" }
}

Mechanically (ethereum, base, arbitrum):

• Enter (USDC → USD+): an APPROVAL (USDC → minter) followed by a STAKE calling minter.deposit(USDC, amount, receiver).
• Exit (USD+ → USDC): an APPROVAL (USD+ → redeemer) followed by an UNSTAKE calling redeemer.requestRedeem(USDC, amount, receiver, owner). This queues a redemption ticket settled by Dinari's operator in 0–3 days (cooldownPeriod: 3d); it surfaces as unstaking with an expectedSettlementAt until it settles.
• Balance: the held USD+ via balanceOf. APY is live from Dinari's API.

The yield accrues off-chain and is reflected in the position; the user holds USD+ directly and never sees issuer accounts or coupon-claim flows.

Position lifecycle & balance states

Balances use the BalanceTypes enum:

Async exits

RWA exits are rarely atomic — settlement cadences range from 24/7 instant (Ondo OUSG) to T+1 NAV strikes (Superstate), 0–3 day operator settlement (Dinari USD+), 40–50 day primary lockups (Ondo USDY), and monthly liquidity windows (Apollo ACRED). actions/exit returns the redemption transaction(s); while the issuer is still settling, the pending amount appears as unstaking with an expectedSettlementAt. Once settled it flips to unstaked / becomes withdrawable, and the user completes the claim with a follow-on actions/exit (or actions/manage where claim is modeled separately).

Note, certain yields including mTBILL offer both instant and standard redemptions allowing users to select the preferred route.

Monetization — fee wrapper (rolling out)

The monetization layer is an optional fee wrapper that partners can route deposits through to add a programmable fee layer, configured per project in the dashboard. Three optional wrapper-level fees stack on top of the issuer's own fee schedule:

Beyond wrapper fees, partners also capture protocol / curator revenue share and, where the issuer supports it, partner fee passthrough. The Yield.xyz platform fee (a share of partner-configured fees and rev-share, scaling down with volume) applies once monetization is enabled.