Yield.xyz primary-source snapshot

Fetched: 2026-04-25 UTC

1) Official website

Source: https://yield.xyz/

Selected excerpt from the official site:

Yield.xyz - Ultimate Web3 Yield Infrastructure | Staking, DeFi, Data APIs

Additional signals from the official site:

  • The live brand is Yield.xyz rather than StakeKit
  • Even from the limited homepage extraction, the site positions the company as broad yield infrastructure spanning staking, DeFi, and data APIs rather than as a single protocol or wallet widget

2) Docs welcome page

Source: https://docs.yield.xyz/v1.0/docs/getting-started

Selected excerpts from the docs:

Welcome to StakeKit! The easiest way to build non-custodial staking, lending and vault-based yield flows into your application.

With the StakeKit API, we’re bringing the best of what worked for us building a DeFi wallet, to you.

Additional signals from the docs:

  • The docs still use the StakeKit name, which appears to be the legacy brand under the newer Yield.xyz umbrella
  • The welcome page is explicit that the target user is a developer integrating yield flows into an application, not a retail end user
  • The docs also tie the product back to Omni wallet, suggesting the API was productized from an existing wallet/yield execution stack

3) Core concepts

Source: https://docs.yield.xyz/v1.0/docs/core-concepts

Selected excerpts from the docs:

The StakeKit API and SDKs have been built to enable accessing yields as easy as possible. From native staking flows where delegations are bonded to specific validators, to auto-compounding liquid staking opportunities and even yield vaults, StakeKit has it all.

We’ve hidden the complexity that exists for many different staking integrations behind a concept we call Pending Actions.

Additional signals from the docs:

  • Yield/StakeKit is trying to normalize heterogeneous yield mechanics behind one session/action model
  • The docs reveal concrete operational details like validator selection, generated transactions, pending-action handling, and extra address/public-key requirements on certain chains
  • This makes the docs a much stronger source of truth than the marketing site for understanding what the platform actually ships

4) SDK repository

Source: https://github.com/stakekit/sdk

Selected excerpts from the public repository:

A TypeScript SDK for the most complete API for integrating non-custodial, on-chain yield — including staking, restaking, liquid staking, DeFi lending, RWA yields, vaults, and more across 70+ blockchain networks.

Self-Custodial by Design — Transactions are returned fully constructed but never executed — you sign and broadcast using any infrastructure: wallets, smart contracts, or custody platforms

AI Agents — Query all available yield actions and execute optimal strategies using standard schemas

Additional signals from the repository:

  • The SDK repo is one of the clearest primary sources for current positioning, because it enumerates supported strategy classes, integration personas, and architectural choices in one place
  • It also highlights fee/margin opportunities for integrators and a chain-agnostic API surface covering EVM and non-EVM ecosystems
  • The repo suggests Yield.xyz is not only a staking API; it is positioning toward a generalized yield abstraction layer

5) Public OpenClaw skill / agent repo

Source: https://github.com/stakekit/yield-agent

Selected excerpts from the public repository:

The yield layer for the agent era.

2,988 yield opportunities. 75+ chains. One unified interface.

Non-custodial. Schema-driven. Agent-native.

Additional signals from the repository:

  • The company is explicitly testing agentic distribution, not just traditional wallet/dashboard integrations
  • The repo documents concrete flows for discovery, entering positions, checking balances, claiming rewards, restaking, and exiting positions against the same API
  • The public skill structure exposes OpenAPI artifacts, chain-format references, and wallet-integration notes, which is unusually helpful for cataloging the platform from primary sources

6) GitHub organization

Source: https://github.com/stakekit

Selected excerpts/signals from the public org page:

  • The org still uses the StakeKit namespace despite the Yield.xyz branding on the main site
  • Public pinned repositories include SDKs, API recipes, a widget, and the agent repo, reinforcing that the company ships a developer platform rather than only a hosted app
  • The org footprint suggests a docs-first / SDK-first product strategy centered on integration rather than protocol governance

7) Trust center

Source: https://trust.yield.xyz/

Selected excerpt from the trust center:

Yield.xyz Trust Center

Additional signals from the trust center and linked repo materials:

  • The existence of a separate trust/security surface is useful because Yield.xyz is selling infrastructure to wallets, custodians, fintechs, and agents rather than to hobbyist users alone
  • The yield-agent repository also claims Yield.xyz is SOC 2 compliant, though that specific claim should be treated as coming from repository materials unless confirmed directly within the trust center

Notes

  • This pass did not locate a classic whitepaper or litepaper from official Yield.xyz / StakeKit sources.
  • The strongest primary materials were the official site, docs welcome page, core-concepts docs, SDK repository, public agent repository, GitHub organization, and trust center.
  • Yield.xyz appears best categorized as an onchain yield infrastructure layer that abstracts staking, restaking, lending, vaults, and adjacent strategy flows into a unified self-custodial API/SDK surface.
  • A notable cataloging nuance is the live-brand split: the website/trust center use Yield.xyz, while docs and GitHub still prominently use StakeKit.