You want a public dashboard or internal review tool that ranks vault curators by realized risk-adjusted return, not by self-reported APY.Documentation Index
Fetch the complete documentation index at: https://developer.alterscope.org/llms.txt
Use this file to discover all available pages before exploring further.
What you build
A small scheduled job that hits the curator endpoints, joins them by address, and writes the result to your database.1. List curator addresses you care about
A curator profile is keyed by the manager address. You can either supply a list (your watchlist) or page overGET /v2/curators if your tier permits.
2. Pull each profile + track record
3. Refresh policy
Curator data updates on cap changes, fee changes, and at most once per hour for performance metrics. Polling every 15 minutes is wasteful; an hourly job is enough. For change-driven updates, subscribe tocurator.cap.changed and curator.fee.changed via webhooks.
4. Troubleshooting
- Sparse track record: a curator with
tenure_days < 90has too little data for a meaningful Sharpe. Hide them or annotate “insufficient history”. - Address mismatch: addresses are case-insensitive but checksum-formatted in the API response. Compare with
addr.lower().