expand parameter pulls them in.
This keeps the common path fast. Expanded fields skip the cache and read fresh, so request them only when you need them.
How to pass it
expand is repeatable. Use a comma-separated list or repeat the bracketed key:
The four expand values
Available onGET /api/v1/trader/{address} and POST /api/v1/traders/batch:
| Value | Adds field | What it contains |
|---|---|---|
strategy | strategy | The trader’s ML strategy classification: strategy_type, an optional description, and confidence. See Strategy types. |
categories | category_strengths | Per-category performance, keyed by category: rank within the category, total P&L, markets traded, wins, losses, and win rate. |
quant_metrics | quant_metrics | Advanced per-trader quant metrics. The key set is additive and database-owned. |
trust | trust | Field-level trust metadata: source, freshness, reconciliation, and completeness for each derived field. |
Example
Market snapshots
GET /api/v1/market/{condition_id}/snapshot accepts expand=trust only. It adds trust metadata for the snapshot’s current_price and spread_bps. The trader-only values (strategy, categories, quant_metrics) do not apply to markets.
Cost
Expanded fields read live instead of from cache, so an expanded request is heavier than a plain one. Two habits keep this cheap:- Request only the expansions you use on a given screen.
- For many traders at once, use
POST /api/v1/traders/batchwith a singleexpandset rather than one expanded request per trader.