The data and asset-deployment infrastructure inside institutional custody.
Yield.xyz runs in production inside the leading MPC custody platforms. This brief covers two concrete areas where that infrastructure complements Google's roadmap — in both, Google exposes a rail, and the end client makes the allocation decision.
Privy
Reap
Enterprise
+ more
A live API key for your team, enabled across the full yield catalogue. Send it as an x-api-key header — nothing to sign up for. Start with the getting-started guide or the data dictionary.
Two concrete areas where we complement Google's roadmap.
Both are live infrastructure today — not roadmap items. Google chooses the depth of each; neither depends on the other.
Yield & reward data, delivered through Google Cloud
A normalized cross-chain yield layer — staking rates, validator performance, reward accrual, and realized APY — that no cloud serves today.
Explore the data layer ↓An asset-deployment layer for Google's MPC custody
One integration gives custody clients the entire deployable market — signed inside Google's rail, never ours.
Explore the deployment layer ↓The yield layer no cloud serves today.
Google Cloud's blockchain datasets cover raw chain data across major networks. What does not exist today, from any provider, is a normalized cross-chain yield layer: staking rates, validator performance, reward accrual, and realized APY across staking and DeFi venues — cleaned and comparable.
Yield.xyz produces this data as a byproduct of running this infrastructure in production, and our transaction-decoding layer normalizes reward flows that raw chain data cannot surface.
Data documentation — Yield API Data Dictionary ↗| What's in the layer | What it answers |
|---|---|
| The opportunity catalogue /v1/yields · YieldDto |
2,900+ yield opportunities across 80+ networks, spanning nine types — staking, liquid staking, restaking, lending, vaults, fixed yield, real-world assets, and liquidity pools both standard and concentrated — each with name, description, provider, curator, and tags: the reference universe every other table joins against. |
| Reward rates, by source rewardRate.components |
Current APR/APY for every opportunity, decomposed by source — staking, MEV, lending, incentives, points, RWA yield — on one comparable basis across 80+ networks. |
| Jurisdictional & investor eligibility requirements.kyc.eligibility |
Permitted and blocked jurisdictions down to the subdivision level (ISO-3166), US-person eligibility, investor-tier and verification requirements per jurisdiction, individual-versus-business subject types, geoblocking enforcement, and mandatory disclosure documents — jurisdiction-level eligibility data no cloud provider serves today. |
| Rate & TVL history /reward-rate/history · /tvl/history |
Time-series snapshots of how every rate and pool evolved — daily, weekly, or monthly resolution over any window, for trend analysis and backtesting. |
| Reward accrual /rewards/history |
Per-event reward flows decoded from raw transactions — timestamp, block, amount, yield source, and transaction hash — the events chain data alone cannot surface. |
| Positions & realized earnings /balances · /balances/history |
Position snapshots with full lifecycle state — active, entering, exiting, withdrawable, claimable, locked — plus USD values, share balances, and per-period deltas showing what a position actually earned. |
| Mechanics & constraints mechanics · metadata.supportedStandards |
Lockup, cooldown, and warmup periods, reward schedule and auto-versus-manual claiming, entry minimums and maximums, gas fee token, and supported ERC standards — the operational profile of a position before capital moves. |
| Fee structures mechanics.fee · possibleFeeTakingMechanisms |
Deposit, withdrawal, management, and performance fees per opportunity, plus which fee-taking mechanisms — including validator rebates — are open to an integrator, for net-of-fee yield comparison. |
| RWA subscription & redemption schedules investmentSchedule |
Subscription and redemption paths for fund-style RWAs — cutoff times, business-day calendars, settlement type (atomic, T+N, cohort, cooldown), and accrual boundaries — the operating calendar of tokenized funds in structured form. |
| Validator registry /yields/{yieldId}/validators |
Commission, stake, voting power, status, preferred flags, nominator counts, remaining capacity, and per-validator reward-rate breakdowns — a like-for-like current-state view across every staking network we serve. |
| Risk ratings /yields/{yieldId}/risk |
Consolidated third-party ratings from Credora and Staking Rewards — scores, annualized probability of significant loss, and links to full reports — an independent risk view alongside every rate. |
| Protocol state & adoption state · statistics |
Live capacity, liquidity, utilization, and price per share; concentrated-liquidity tick ranges, fee tiers, and 24-hour volume and fees; vault allocations with current-versus-target weights and per-strategy rates — plus per-yield TVL, unique users, and average position size. |
| Incentive campaigns /yields/{yieldId}/campaigns |
Campaign metadata — total, distributed, and remaining budgets, emission rates, payout frequency, qualification rules, and status — separating incentive-driven yield from organic yield. |
| Reference data /v1/networks · /v1/tokens · /v1/providers |
The registries that make it all joinable — networks with categories, token metadata with contract addresses and CoinGecko IDs, and protocol and validator providers with TVL, type, and audit references. |
Catalogue, rate, mechanics, and fee fields span every opportunity; jurisdictional eligibility is published for KYC-gated (primarily RWA) opportunities, and risk and protocol-state fields where the protocol or rating provider exposes them. Adoption metrics are vault-based. Validator data is point-in-time. Per-wallet reward history is served for indexed yields, and per-wallet balance history currently covers ERC-4626 vaults with indexed transfer history — coverage we expand continuously.
Joining raw chain data with normalized reward flows — validator performance benchmarking, realized-APY reporting, treasury and audit workflows — queries no other cloud can serve today.
One integration, the entire deployable market.
Institutional custody clients expect to be able to put custodied assets to work — it is native to every established platform in the category, and we are that layer in production across Utila, DFNS, Fordefi, Ledger Enterprise, and Porto by Anchorage. The unlock: one integration gives Google's custody clients the entire deployable market — feature parity on day one, expanding automatically as the market does.
The deployable market — explore each category
Centered on the custody rail, not on us.
Four steps, one invariant: keys never leave Google's MPC custody. Click through the flow.
Certified, audited, non-custodial.
SOC 2 Type II
The only provider in the category certified.
Non-custodial · on-prem available
We never hold funds, keys, or signing authority; Shield deploys inside the client perimeter.
DORA addendums executed with EU-regulated clients; MiFID (EU) and UK regulatory coverage is in the process of being obtained via partnership with Assetera. Yield.xyz is also working toward obtaining US regulatory coverage.
Questions your team will probably ask.
Where does the yield data actually come from?
Does Yield.xyz ever hold funds, keys, or signing authority?
Who decides whether custodied assets are deployed?
What does the integration surface look like?
How does Google earn from the custody integration?
What is the security and regulatory posture?
Next steps.
Dataset scoping session with Google
Schema, coverage, and the BigQuery / Google Cloud Marketplace listing path.
Technical walkthrough of the MPC custody integration
Architecture, console and API surfaces, and on-prem Shield deployment.
Yield.xyz Yield API Data Dictionary
The complete field-level reference for our unified Yield Data API. It documents every endpoint, response object (DTO), enum, and query parameter used across all supported chains and protocols — giving integrators the canonical schema needed to discover yields, read balances and rewards, and construct and track staking transactions.
View the data dictionary →