Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.alterscope.org/llms.txt

Use this file to discover all available pages before exploring further.

A treasury holding stablecoins or pegged assets needs early warning when a peg starts to slip and a read on whether the broader market is calm or stressed. This workflow assembles that from peg, regime, and flow data.

​
The workflow

1

Track the peg directly

GET /v2/asset/{assetId}/peg-history returns an asset’s deviation from its peg over time, sourced with block-level history — so a slow drift is visible before it becomes a break.
2

Read the market regime

GET /v2/regime/current (and GET /v2/regime/morpho/markets for market-level regime) classifies whether conditions are calm or stressed — context for how seriously to treat a wobble.
3

Follow the capital flows

GET /v2/flows/current, …/timeseries, and …/forecast show whether capital is moving toward or away from an asset or venue — flight is an early peg-stress signal. For liquid-staking assets specifically, GET /v2/graph/lido/depeg surfaces depeg risk.
4

Get alerted

Combine this with the risk-events feed and webhooks so a peg or regime change pushes an alert to your systems rather than waiting for a manual check.

​
What you learn

Whether a held asset’s peg is holding, whether the market backdrop is calm or stressed, and whether capital is quietly leaving — the combination that precedes most peg events. Each response carries freshness and quality metadata; the modeling boundaries are on the Limitations page, and full detail is in the API reference.