Leaderboard & Traders
Performing strategies and copyable traders, with honest metrics.
GET/context/leaderboard
Ranked strategies running on Superior, with backtest and live metrics side by side.
Response — 200
{
"computed_at": "2026-07-28T10:00:00Z",
"strategies": [
{
"id": "strat_01j7…",
"name": "donchian-strong-regime",
"venue": "hyperliquid",
"timeframe": "4h",
"backtest": { "return_pct": 6.7, "max_drawdown_pct": 4.8, "trades": 41, "window_days": 162 },
"live": { "return_pct": 2.1, "days": 34, "deployments": 12 }
}
],
"disclaimer": "Past performance does not predict future results. Backtest and live windows differ per strategy."
}
Both windows are always shown because they always differ — a strategy with a strong backtest and a thin live record is exactly that, and the response makes it visible rather than blending the numbers.
GET/context/traders
Traders available for copy trading, ranked by verified on-venue performance.
Response — 200
{
"traders": [
{
"wallet": "0x3f8b…c21a",
"venue": "hyperliquid",
"pnl_30d_usd": 48210.55,
"win_rate_30d": 0.58,
"max_drawdown_30d_pct": 11.2,
"volume_30d_usd": 2140000,
"trades_30d": 312
}
]
}
GET/context/traders/:wallet
The same metrics plus recent fills and per-market breakdown for one trader — enough to judge how the PnL happened (one lucky position vs. a repeatable pattern) before copying.
Note on copy execution
These endpoints are context: discovery and evaluation. Actually mirroring a trader is a runtime concern and ships as a strategy template on the deployment surface, not as a separate API — a copy-trade is just a deployment whose strategy follows a wallet instead of an indicator.