Why Continuous Monitoring Matters
Curator Actions
Catch deallocations, timelock changes, and curator behavior the moment they happen, not at your next review cycle
Depeg Detection
Track peg deviation and liquidity depth on every stablecoin and RWA in your portfolio, continuously
Live Rating in Your UI
Surface a graded, always-current rating to your users instead of a stale one-time score
- Graded rating plus operational detail: the v3 endpoints give you a letter grade; the v1 vault endpoint gives you curator, utilization, and liquidity so you know why the grade moved
- Depeg-specific signals: peg deviation, per-DEX liquidity depth, and score deltas built for stablecoins and RWAs
- Fail-closed by design: missing or stale data is treated as unknown, never as safe
- One API for the whole book: vaults, stablecoins, and RWA vaults from a single base URL
Prerequisites
Before implementing ongoing monitoring, ensure you have:- A Webacy API key (sign up here)
- Basic familiarity with REST APIs or the Webacy SDK
- The vaults, stablecoins, and RWA positions you currently hold identified, with their chain and contract address
Monitor Vaults on a Cadence
Two calls, two jobs. Call/v3/vaults for the graded letter rating you show to users. Call /vaults (v1) for the operational detail that explains why, curator, utilization, liquidity, TVL flight, and an exit recommendation.
Monitor Stablecoins and RWAs for Depeg
Every stablecoin and RWA in your book can drift off its peg between allocation checks. Poll/rwa/{address} for peg deviation, per-DEX liquidity depth, and short-term score deltas.
Monitor RWA Vaults
If a position is an RWA-backed vault rather than a plain token, rate it with the RWA graded endpoint, same composite shape as vault v3, same polarity.chain is required on both /v3/vaults/{address} and /v3/rwa/{address}, always pass it explicitly.
Set Up Alerting
Alert on state changes, not just raw levels, a vault sliding fromB+ to C matters more than a vault that’s been C for a month.
Recommended thresholds:
Poll cadence: every 5-15 minutes for depeg-sensitive positions, hourly for vault and RWA grades, which don’t move as fast as peg deviation. Never poll less often than once a day for anything you’d need to exit in a hurry.
Fail-closed: a missing endpoint, a
4xx/5xx, or a stale: true response is not a clean bill of health. Treat it as unknown risk and alert accordingly. See Hard-gating and fail behavior.
Prefer push over polling where you can. For stablecoin and RWA depeg you can subscribe to
DEPEG_TIER_CHANGE webhooks and get notified the moment a tier changes, instead of polling on a timer. See Webhooks to set them up, then keep polling as a backstop for the vault and RWA grades.Implement a Live Rating in Your UI
Surface the graded rating you’re polling directly to your users, call/v3/vaults/{address} or /v3/rwa/{address}, read composite.grade, composite.stars, and categories.*, and render a badge. No need to build your own scoring model.
For the full walkthrough, pulling the fields into a view model, rendering the badge (React and HTML), showing the category breakdown, and handling freshness and failures, see the dedicated guide:
Implement a Risk Rating in Your UI
Call the v3 endpoint, pull the grade, stars, score, and category breakdown, and render a badge, with React and HTML examples
Monitor Risk-Adjusted Yield
Yield is part of monitoring, not separate from it. For vaults, the v1 detail endpoint returns the net yield directly: readmorpho.avg_net_apy (and avg_net_apy_ex_rewards, which strips reward incentives) alongside the risk signals you are already polling, so a falling grade next to a climbing APY is easy to spot.
A high APY on its own is not a good position. An APY that spikes well above its recent average is usually a stress signal (an exploit, an oracle failure, or a liquidation cascade), not an opportunity. Webacy’s Yield Scores capture exactly this: raw APY discounted by the issuer’s safety score, with spike detection that falls back to the 30-day mean when a pool’s APY jumps. Rank yield-bearing positions by risk-adjusted APY rather than raw APY.
For the full methodology, see the Yield Scores page.
Complete Monitoring Workflow
Full TypeScript Implementation
Full TypeScript Implementation
Example Addresses for Testing
API Quick Reference
Authentication:
Ready to Ship?
- Identify your book: list every vault, stablecoin, and RWA position you currently hold, with chain and address
- Wire up the poll: call the graded and operational endpoints on your chosen cadence and run them through
checkAlerts() - Go live: ship the badge in your UI and route alerts to your team
Next Steps
New Asset Due Diligence
Screen a vault, stablecoin, or RWA before you allocate to it
Alerting with Webhooks
Subscribe to DEPEG_TIER_CHANGE events instead of polling on a timer
Monitor Stablecoin Depeg Risk
The full depeg monitoring workflow across 600+ pegged tokens
Yield Scores
How raw APY gets discounted by issuer risk
