Use this file to discover all available pages before exploring further.
This is the canonical list of event types Alterscope emits. The same types flow through every delivery channel — Webhooks, WebSockets, and the replay feed — so a peg.depeg.start you subscribe to over a webhook is the same event you’d see on the risk-events WebSocket stream.Subscribe by exact type string. There is no wildcard matching; list each type you care about.
Every event shares one envelope. The type identifies the event, data carries the type-specific payload, and meta._agentic carries the same freshness/quality signal as REST responses (see Response envelope).
severity is one of info, warn, high, critical. subject_id follows a <resource>:<id> shape (e.g. oracle:ethereum:0xfeed:USDC, vault:base:0xpool). When an event was computed off degraded upstream input, the envelope additionally carries data_quality: "degraded". Fields shown as omitempty (chain, protocol, severity) may be absent.
The samples below show the data object for each type. Fields within data vary by event family and may evolve additively — treat unrecognized fields as forward-compatible and key your idempotency on a stable identifier (e.g. block number + subject).
Fires when an oracle feed backing a tracked market has not updated within its freshness threshold. Severity scales with staleness age (warn < 10 min, high ≥ 10 min, critical ≥ 60 min).
Fires when the meta-oracle’s classification of a feed changes — its category, provider, staleness status, risk level, or edge-case flags shift from the previously observed fingerprint.
Fires when a feed returns a structurally invalid reading (e.g. a non-positive or otherwise unusable answer) rather than merely a stale one. Carries the oracle and market identifiers; data fields are feed-specific.
Fires when a tracked asset’s observed price crosses its depeg threshold against the reference. Prices are decimal strings (never floats); deviation_bps is signed (negative = below reference).
A recovery signal in the peg family, distinct from peg.depeg.end; severity is info. Carries the peg identity in subject_id; the data object mirrors the peg envelope above.
Vault events are derived from indexed on-chain curator/governance actions on MetaMorpho-style vaults. They share a common payload shape: the vault, the caller, the affected subject, the underlying on-chain event, and the transaction coordinates.
vault.cap.changed
Fires when a vault’s supply cap is changed on chain (set_cap). Severity is info.
Fires when a vault’s performance fee is changed on chain (set_fee). Severity is warn. Same payload shape as vault.cap.changed with on_chain_event: "set_fee".
Fires when a vault’s curator role is reassigned on chain (set_curator). Severity is high — a curator change is a governance-level event. Same payload shape with on_chain_event: "set_curator".
Fires when a curator reallocates supply across markets (reallocate_supply / reallocate_withdraw). Severity is warn. Same payload shape with the corresponding on_chain_event.
Fires for curator/governance actions that don’t map to a more specific vault event — e.g. supply-queue updates, allocator/guardian/timelock changes, or lost-asset updates. Severity is info. The specific action is in on_chain_event.
Fires when available exit depth for a position collapses sharply. Severity is critical — the most actionable liquidity signal. Carries the affected market in subject_id; data fields are market-specific.
Fires when the graph anomaly detector flags a non-MEV anomaly (TVL drop/spike, concentration, flow anomaly, whale movement). Severity derives from the detector’s own grade.
Fires when a yield opportunity’s risk-factor category score drops past a threshold between snapshots. Severity is supplied by the breach (defaults to warn).
WebSocket streaming requires the Analyst tier or higher; signed webhooks require the Team tier or higher. See Webhooks for signature verification and WebSockets for stream filters and per-tier connection limits.
