yield-xyz

Yield.xyz (formerly StakeKit)

• Name: Yield.xyz (formerly StakeKit)
• URL: https://yield.xyz/
• Category: Onchain yield infrastructure / staking, restaking, lending, and vault aggregation
• Summary: Yield.xyz at the project layer is the unified API / SDK surface for self-custodial onchain yield flows across many chains and protocols. The useful product cut is the normalized interface itself: discovery, balances, validators, pending actions, and unsigned transaction construction across staking, restaking, lending, and vault workflows. The broader operator boundary now lives in yield-xyz, which is the cleaner place to reason about supported-chain coverage, schema stewardship, widget and agent packaging, trust posture, and the support shell around those integrations.
• What it does:
  • Aggregates yield opportunities across 70+ blockchain networks and multiple strategy types including staking, restaking, liquid staking, DeFi lending, RWA yields, and vaults
  • Exposes a standardized API/SDK model for discovery, balances, validators, enter/exit/manage actions, transaction construction, and transaction-status tracking
  • Returns unsigned transactions for users or integrating platforms to sign and broadcast themselves, preserving a self-custodial integration model
  • Normalizes heterogeneous protocol mechanics behind consistent schemas for metadata, actions, balances, lifecycle states, and pending follow-up actions like claim, restake, or withdraw
  • Targets wallets, custodians, fintechs, aggregators, infrastructure vendors, and now AI-agent integrations, including a public OpenClaw skill repo built around the API
• Key claims:
  • The official site title frames Yield.xyz as “Ultimate Web3 Yield Infrastructure | Staking, DeFi, Data APIs,” signaling a broad integration layer rather than a single protocol
  • The docs welcome page says the API is “the easiest way to build non-custodial staking, lending and vault-based yield flows” and explains that it grew out of Omni wallet production experience
  • Core-concepts docs say the platform covers native staking, liquid staking opportunities, and yield vaults while reducing enter-flow complexity to standardized API sessions, transaction construction, and pending-action handling
  • The public SDK repo describes “the most complete API for integrating non-custodial, on-chain yield” across 70+ networks, emphasizes unsigned transaction returns, and positions the product for wallets, custodians, fintechs, AI agents, and aggregators
  • The public yield-agent repo is especially informative because it shows Yield.xyz explicitly packaging its API for agentic use, with discovery, transaction construction, portfolio tracking, and management flows exposed through an OpenClaw skill
• Whitepaper: No classic whitepaper or litepaper was found during this pass. The strongest primary materials were the official site, docs, core-concepts documentation, SDK repository, public agent-skill repository, trust center, and GitHub organization; see ../whitepapers/yield-xyz-primary-sources-2026-04-25.md.
• Sources:
  • https://yield.xyz/
  • https://docs.yield.xyz/v1.0/docs/getting-started
  • https://docs.yield.xyz/v1.0/docs/core-concepts
  • https://github.com/stakekit
  • https://github.com/stakekit/sdk
  • https://github.com/stakekit/yield-agent
  • https://trust.yield.xyz/

Internal linkages

• Company boundary for the broader operator shell: yield-xyz.
• Useful adjacent product reads: morpho, symbiotic, and puffer.

Project / company boundary

• Keep this note on the normalized integration surface itself: discovery, balances, validators, action schemas, unsigned transaction construction, and pending-action handling across staking, restaking, lending, and vault flows.
• Use yield-xyz when the sharper question is who decides supported-chain and protocol coverage, curates semantic normalization, packages widgets and agent tooling, and becomes the support and trust shell production integrators inherit.
• That split matters because how does the yield API behave? and which named operator decides what becomes legible, first-class, and supportable inside that API? are related but not identical questions.

Control surface

• At the product layer, practical authority sits in the normalized action schema, validator and opportunity discovery model, pending-action lifecycle, and unsigned transaction-construction flow the integration exposes.

• For the wider operator dependency around supported-protocol coverage, semantic normalization, widget / agent packaging, support workflow, and trust posture, read yield-xyz.

• Read it as a yield-integration surface, not as a neutral staking baseline.

• Last reviewed: 2026-08-13 UTC