Overview
The Yields endpoint provides rolling yield/ROI predictions per pool across fixed time horizons (1D, 3D, 7D, 14D, 30D, 90D, 365D). Each prediction is anchored to a specific block/log position and includes aligned arrays for pool tokens, current reserves, observed/predicted volumes, user fees, and ROI fractions. Predictions are derived from historical swap fees and current reserve states.Endpoint Matrix
Parameter Conventions
number
required
Chain identifier for the target EVM network. See Chain enumeration for supported values.
number
Target prediction horizon in days. Supported values: 1, 3, 7, 14, 30, 90, 365.
number
Starting block height (inclusive) for yield predictions.
number
Ending block height (inclusive) for yield predictions.
string
Starting timestamp (ISO-8601). If it falls between blocks, the next block after this timestamp is used.
string
Ending timestamp (ISO-8601). If it falls between blocks, the last block before this timestamp is used.
string[]
BlockDB pool identifiers for filtering yield predictions by pool.
string[]
Pool contract addresses to scope yield data.
boolean
Only return predictions where
observed_period_days == target_period_days (no extrapolation).number
Minimum ROI threshold for filtering predictions.
Usage Guidance
- Pool ranking — Use yield predictions to rank pools by expected fee yield over a horizon
- Allocation screens — Build pool allocation signals using APR/ROI predictions with full provenance
- Model validation — Compare yield predictions against actual swap fees and reserves for backtesting
- Horizon selection — Choose
target_period_daysbased on your investment horizon (short-term vs long-term) - Full period filtering — Use
require_full_period: trueto exclude extrapolated predictions when historical data is insufficient
Yield Calculation
Yield predictions are computed using:- Historical swap fees (from
/evm/swaps/fees) — Observed fee amounts over the available window - Current reserves (from
/evm/reserves) — Current pool state for ROI denominator - Extrapolation — When
observed_period_days < target_period_days, predictions are scaled bytarget_period_days / observed_period_days
roi_predicted[i] = user_fees_predicted[i] / current_reserves[i]
Prediction Quality Indicators
Each yield record includes quality indicators:observed_period_days: Actual days of history usedis_full_period:truewhenobserved_period_days == target_period_daysis_extrapolated:truewhen history is shorter than targetextrapolation_factor: Scaling factor applied (target / observed)
Common Patterns
Rank pools by 30-day yield:Dataset Relationships
- Swap Fees → Yields: Historical swap fees are the primary input for yield predictions
- Reserves → Yields: Current reserves provide the denominator for ROI calculations
- Pools → Yields: Join pool metadata to yield predictions using
pool_uid - Fee Terms → Yields: Fee terms determine which fees are attributed to LPs/users
- Yields → Prices: Yield predictions can inform pricing models for pool tokens
See Also
POST /evm/yields— Yield/ROI predictions endpointPOST /evm/swaps/fees— Historical swap fees (input to yield models)POST /evm/reserves— Current pool reserves (input to yield models)POST /evm/entities/pools/fee-terms— Pool fee configurationPOST /evm/entities/pools— Pool metadata registry- Pool Type — AMM pool classifications