Cache Tiers
The API setsCache-Control headers based on data volatility. Three tiers:
No-Store (Real-Time)
User-specific or frequently changing data. No caching at any layer./health/positions/all,/positions/{address},/positions/{address}/loops,/positions/{address}/vaults/liquidations/user/{address}/vaults/{address},/vaults/{address}/depositors/markets/{marketId},/markets/{marketId}/history,/markets/{marketId}/positions/research/market/{marketId},/research/risk
Standard (Aggregate Data)
Protocol-wide aggregates that update every few seconds./markets,/vaults,/stats,/trends,/yields,/liquidations/alerts,/whales,/wallets/top/ratings,/ratings/vaults/risk/dashboard,/risk/protocol-health,/risk/positions-at-risk/strategies/breakdown,/chains/compare
Short (Parameterized/Derived)
Computed results that depend on query parameters./markets/search,/markets/compare,/vaults/concentration/risk/concentration,/risk/exposure/{collateral},/risk/yields,/risk/report,/risk/liquidation-map/strategy/{strategy},/simulate/position/research/deploy,/research/borrow-markets,/research/borrow-strategy/ratings/market/{marketId},/ratings/vault/{address},/ratings/methodology/agent/policy/defaults
Freshness Indicator
Themeta.freshness field in responses tells you how fresh the data is:
| Value | Meaning |
|---|---|
live | Fetched from protocol in real-time |
cached | Served from server-side cache |
snapshot | From a periodic snapshot (Supabase time-series) |