Skip to main content
Protocol-reported APYs aren’t comparable: Morpho reports a smoothed average, Aave a spot supply rate, Lagoon a weekly APR, Yearn a net APR. Webacy publishes one standardized yield per vault, then breaks it down so you can see where it comes from, what fees cost, and whether you can actually get it. Every field on this page is returned on the vault metadata object by GET /vaults (list) and GET /vaults/{address} (detail), and on the V3 vault detail. The one exception is data_as_of, which is returned on the detail only. All yields are decimal ratios (0.0313 = 3.13%). This page describes the methodology and API behaviour as of November 12, 2026. The API does not yet return a version for the realized-APY methodology. The fee model and the durability score carry their own method (see the example below).
These fields are informational. None of them changes a vault’s risk score or letter grade.

What you get

Standardized APY

The vault’s realized yield, measured the same way for every protocol, with its source and window.

Incentives

Third-party reward campaigns (Merkl), kept separate from the base yield, with eligibility and end dates.

Yield durability

A 0–100 score for how much of the yield a typical depositor can count on if incentives stop.

Fees

APY before and after the vault’s fees, with the fee rates and where they came from.

Deposit status

Whether a new depositor can deposit right now, and who is allowed to.

Flow terms

Whether deposits and redemptions settle instantly or through a request queue, and any lockup.

Standardized APY

When apy_measure starts with realized_, apy is the vault’s realized share-price yield: how much the value of one vault share actually grew, annualized. Its apy_source is then onchain.share_price (Webacy’s own on-chain read) or tradingstrategy.share_price (an independent share-price feed, corroborated against a live on-chain read). When no realized yield is available, apy is the protocol’s own figure instead (a spot, smoothed, or projected rate), and apy_source / apy_measure say which. Check apy_measure before treating apy as measured depositor earnings.
  • Windows: 7, 30, and 90 days. The headline apy is the 90-day window, or the 30-day window when the vault is younger than 90 days or its 90-day window was refused (see Guards). The 7-day window is published for monitoring but is never the headline.
  • Source: share prices are read on-chain by Webacy at the block for each date (convertToAssets for ERC-4626 vaults, pricePerShare for Yearn v2, getPricePerFullShare for Beefy, the reserve’s normalized income for Aave). Where an independent share-price feed also covers the vault, the two are compared and a disagreement is flagged.
  • Net of fees by construction: protocols that take their fee inside the share price (Morpho, Euler, Yearn, Lagoon, and others) are already net of that fee.
  • Guards: Webacy’s pipeline refuses a realized window outside −95% to +50% rather than publishing it. A share price rising faster than that is usually interest accruing on debt that won’t be repaid. Funds whose share price tracks a market price (equity or gold index funds) are refused too, because that’s a price return, not yield. A measured loss, meaning a realized share-price window in which the share price fell, is published as a negative apy with apy_realized_loss: true. A realized share-price yield is published as measured: positive, exactly 0 for a flat window, or negative for a loss. A protocol’s own figure is published only when it is above 0 and at most 500%, and is null otherwise.
Two exceptions to the loss rule apply today:
  • A refused 90-day loss can fall back to a positive window. When a vault’s 90-day window is refused because it lost more than the −95% floor, the headline falls back to the 30-day window even if that window is a gain. The refused window doesn’t appear in realized_apy_windows.
  • A measured loss can read null. On a vault whose market is flagged as stuck or impaired, a measured realized loss can be published as apy: null. The loss still shows in realized_apy_windows, so check it when apy is null.
A fix for both is rolling out. A refused loss will hand the headline only to a shorter window that is also a loss; otherwise it reads apy: null, never a shorter window’s gain or zero. And a measured loss will be published as a negative apy on a flagged market too. The same release also checks each window against its neighbouring start day: a window whose result swings sharply when its start moves by one day is dropped, so one day’s share price can no longer set a 90-day headline.
A negative apy is annualized, like every realized window. An apy of −0.0271 on a 90-day window (apy_measure: realized_90d) is a share-price drop of about 0.7% in that window, not 2.7% ((1 − 0.0271)^(90/365) − 1). The −95% floor applies to the annualized figure, so on a 30-day window a real drop of more than about 22% is refused. Today, when no window survives, apy falls back to the protocol’s own figure (apy_source / apy_measure say so); with the fix that is rolling out, a refused loss reads null instead. If your code assumed apy >= 0, check apy_realized_loss before treating apy as a yield.
A gap between apy and apy_native is information, not an error. Protocol figures are often spot rates or include rewards that never reach the share price. The realized figure is what depositors actually earned.
Coming soon: a flag on each vault saying whether a protocol-reported apy includes token rewards, with the ex-rewards yield where the protocol publishes one, and a reason field when apy is null. They are not returned yet.
Vault data is normally refreshed every 6 hours, but don’t assume a record is that fresh. On the vault detail, data_as_of says when the vault’s record was last measured; a failed read keeps the previous record, so data_as_of can be older than the latest refresh. List rows don’t return data_as_of; they return last_scored_at.

Incentives

incentives describes third-party reward campaigns run through Merkl, matched to the vault by chain and address. Incentives are paid from a sponsor’s budget, not earned by the deposits, so they are never added into apy. The object is null when the vault has no Merkl campaign. Such a vault also has no durability score. That doesn’t prove it has no incentives, because rewards can come from programmes outside Merkl. Note too that apy itself can already contain rewards when it is a protocol-reported figure (see apy_source).
Read incentive_apr together with incentive_apr_restricted. An ordinary depositor’s incentive is incentive_apr − incentive_apr_restricted. When all of it is restricted, an ordinary depositor earns only the base apy.null on incentive_apr_restricted (or any eligibility APR field) means eligibility wasn’t computed. Don’t read it as 0, and don’t treat the incentive as open. APR whose eligibility is unknown is not counted as restricted, so the subtraction above can include it (incentive_apr_liquid_eligibility_unknown gives that part).
Also returned: incentive_apr_liquid_restricted, incentive_apr_liquid_eligibility_unknown, incentive_apr_liquid_low_quality (open token APR paid in a token with no reliable value), incentive_apr_boosted (campaigns with per-user boosts, so the headline is an average), incentive_eligibility_hooks, incentive_reward_qualities, incentive_self_funded, merkl_native_apr, and merkl_total_apr. Each campaign row also carries boosted.

Yield durability

incentives.yield_durability scores how much of a vault’s current yield a typical depositor can count on if incentives are not renewed. The base yield counts as fully durable; only the incentive part is discounted:
  • share is the incentive share of the yield an ordinary depositor can earn. Restricted campaigns are left out, so it can be lower than the headline incentive_share.
  • liquid_fraction is the share of the open incentives paid in tradable tokens. Points and pre-launch tokens count as 0, and so does a token with no reliable value. APR that Merkl reports but can’t attribute to a campaign, or whose eligibility is unknown, counts as 0.5. When no incentive is open to an ordinary depositor, it is 0.5 and has no effect, because share is 0.
  • renewal grows with the campaign streak: 0.25 + 0.65 × min(streak days / 365, 1), so between 0.25 and 0.90.
  • funding is 0.85 when the vault’s own curator funds the campaign, otherwise 1. Today the curator check doesn’t recognise curators of Morpho Vault V2 vaults, and no vault currently carries the self_subsidised flag, so in practice funding is 1 on every vault today.
Today a vault with a live campaign can still have no score: when Merkl reports no base yield for it (its total APR equals the incentive APR), the incentive share isn’t computed and no score is returned, even when the vault has a realized share-price apy. flags add context independent of the tier: incentive_dependent (incentives are 50% or more of the typical depositor’s yield), short_streak (under 30 days of unbroken campaigns), points_incentive / pretge_incentive, self_subsidised, and restricted_incentive (some incentive APR is gated and was excluded from the score). drivers returns the inputs above.
A vault whose incentives are all restricted can score high: for an ordinary depositor its yield is all base yield, which is fully durable. The restricted_incentive flag tells you this is the case.

Fees

fees gives the yield before and after the vault’s own fees, with the rates behind them. The object is null when nothing is known about the vault’s fees. A rate the source doesn’t provide is never assumed: apy_before_fees stays null and fee_gap_reason says why. Entry and exit fees are reported in fee_model but not folded into either APY.

Deposit status

deposit_status says whether a new depositor can deposit right now.

Flow terms

flow_terms says how deposits and redemptions settle. The object is null when nothing is known. A sync redemption can still be limited by available liquidity. See pct_tvl_withdrawable and the withdrawal signals in Vault Risk Intelligence.

Filtering and sorting

On the vault list (GET /vaults):

Example

Steakhouse High Yield USDC Edition (Morpho, Base). Excerpt of metadata from GET /vaults/0xbeeff2490feffa212fac2f6553682c219e6a8845?chain=base as returned on November 12, 2026 (data_as_of 2026-11-11T17:07:17Z), trimmed to the fields on this page. Values change with every refresh:
How to read it:
  • The vault’s realized APY is 3.13%, annualized from its share-price change over the last 90 days and measured on-chain. Morpho’s own figure is 3.27%.
  • Before the curator’s 25% performance fee, the annualized APY is 4.17%, so fees cost 1.04 percentage points a year.
  • Sponsors pay another 2.12% in incentives, but all of it is restricted (Coinbase-verified or allow-listed depositors), so an ordinary depositor earns 3.13% and a depositor eligible for both campaigns about 5.25%. incentive_apr is the authoritative total; here the two listed campaigns (1% and 1.12%) add up to it.
  • Durability is high with restricted_incentive: for an ordinary depositor the yield is all base yield. liquid_fraction is 0.5 because no incentive is open to an ordinary depositor, so it has no effect on the score.