Risk Scoring API
TODO: Complete Risk Scoring Endpoints Documentation
Query operator risk scores via REST or WebSocket.
Required Sections
-
Endpoints
GET /v1/operators/{operator_address}/risk-scorePOST /v1/operators/batch/risk-scoresGET /v1/operators?risk_score_min=X&risk_score_max=Y- Historical risk score queries
-
Request Parameters
- Operator address format
- Time range (for historical queries)
- Include components flag
- Confidence threshold
-
Response Format
{
"operator_address": "0x...",
"risk_score": 42,
"risk_category": "MEDIUM",
"components": {
"slashing_history": 35,
"uptime": 25,
"avs_concentration": 40,
"reputation": 20
},
"confidence": 0.92,
"last_updated": "2024-01-21T14:32:00Z",
"update_frequency": "every_block"
} -
Batch Queries
- Query multiple operators at once
- Request size limits
- Response format for batch queries
- Performance considerations
-
Filtering & Sorting
- Filter by risk category
- Filter by risk score range
- Filter by AVS
- Sort options (risk score, name, etc.)
-
Historical Queries
- Query risk score at specific point in time
- Time series aggregation (daily, weekly)
- Backtest data availability
- Data retention period
-
WebSocket Subscriptions
- Subscribe to operator risk score updates
- Event types (risk_score_updated, threshold_breached)
- Subscription format
- Unsubscribe handling
-
Error Responses
- 404 (operator not found)
- 429 (rate limited)
- 400 (invalid parameters)
- 500 (internal error)
-
Examples
- Query single operator risk score
- Batch query top 100 operators
- Historical risk score chart data
- Subscribe to operator risk score changes
Use Cases
- Stakers vetting operators before delegation
- AVSs monitoring operator set health
- Risk dashboards & monitoring
- Programmatic trading/rebalancing
Related
Status: NOT STARTED — Requires API design & endpoint specification