> ## Documentation Index
> Fetch the complete documentation index at: https://docs.0xinsider.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Optional fields

> Request extra trader details, price sources, or full trades with the expand parameter.

Use `expand` when you need fields that an endpoint leaves out by default. For example, `expand=strategy,trust` adds a wallet's strategy and the source of its values to a trader response.

## Choose an expansion

| Endpoint | Accepted values | What they add |
| - | - | - |
| [Trader](/api-reference/endpoint/get-trader) and [Batch traders](/api-reference/endpoint/batch-get-traders) | `strategy`, `categories`, `quant_metrics`, `trust` | Optional wallet details, described below. |
| [Market snapshot](/api-reference/endpoint/get-market-snapshot) | `trust` | The source and freshness of `current_price` and `spread_bps`. |
| [Event replay](/api-reference/endpoint/get-event-replay-since) | `trade` | The full trade for each event, when available. |

<span id="what-it-does-not-do" />

## Limits

Other endpoints do not read `expand`. An expansion adds stored information; it does not trigger a new classification or calculation.

<span id="pass-the-parameter" />

## Add it to a request

Separate values with commas:

```bash theme={null}
curl -H "Authorization: Bearer $OXINSIDER_API_KEY" \
  "https://api.0xinsider.com/api/v1/trader/swisstony?expand=strategy,trust"
```

Repeated parameters work too: `expand=strategy&expand=trust` and `expand[]=strategy&expand[]=trust` mean the same thing. You can combine these forms.

| Input | Result |
| - | - |
| A recognized value | The endpoint adds that section if it has data for it. |
| An unrecognized value | The endpoint ignores it. |
| An empty value, such as `expand=` | The endpoint ignores the empty part. |
| Invalid percent encoding | The endpoint returns `400` with `error.param` set to `expand`. |

A section you did not request is absent from the response. A requested section can also be absent when its data is unavailable; expansion does not guarantee a value.

<span id="trader-values" />

## Trader details

| Value | Response fields | Use it to |
| - | - | - |
| `strategy` | `strategy` | Read the wallet's [strategy label](/concepts/strategy-types). `description` appears when stored; `confidence` is not returned. |
| `categories` | `category_strengths`, `category_records`, `category_skill_model` | Compare category ranks and records, and check whether the category model has enough data. |
| `quant_metrics` | `quant_metrics` | Read [risk and performance measures](/concepts/quant-metrics) computed less than 6 hours ago. |
| `trust` | `trust` | Check [sources, timestamps, and completeness](/concepts/trust-metadata) for the trader's fields. |

For example, the `strategy` part of a response can look like this:

```json theme={null}
{
  "strategy": {
      "strategy_type": "high_activity"
  }
}
```

Check category status before treating a category record as evidence of skill. Individual records can be `insufficient`, `stale`, `unknown`, or `degraded`; `category_skill_model.status` can also be `live` and describes the model as a whole.

`category_strengths` uses positions above `$20` with entry prices strictly between `0` and `1`. [Trader category records](/api-reference/endpoint/get-trader-category-records) uses a broader sample; use that endpoint for the wallet's plain win-loss record.

<Note>
  Any recognized trader expansion bypasses the 60-second response cache. Request only the sections you need; an expanded request can take longer than a basic profile request.
</Note>

<span id="expand-a-batch" />

## Expand several traders

Put `expand` in the batch JSON body. It applies to every wallet:

```bash theme={null}
curl -X POST "https://api.0xinsider.com/api/v1/traders/batch" \
  -H "Authorization: Bearer $OXINSIDER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"traders": ["swisstony", "0x0000000000000000000000000000000000000000"], "expand": ["strategy"]}'
```

The `traders` array must contain 1 to 25 entries. The response preserves their order and any duplicates; inspect each item's `status` because one wallet can fail while the others succeed.

<span id="expand-a-market-snapshot" />

## Check a price source

Add `expand=trust` to a [market snapshot](/api-reference/endpoint/get-market-snapshot). `trust.current_price` distinguishes a price reported by Polymarket from a midpoint calculated from its best quotes.

The response also adds `trust.spread_bps`. Without the expansion, you receive the values without these source details.

<span id="expand-an-event-replay-page" />

## Include trades in event replay

```bash theme={null}
curl -H "Authorization: Bearer $OXINSIDER_API_KEY" \
  "https://api.0xinsider.com/api/v1/events/feed/since?limit=100&expand=trade"
```

Each event gains the trade object returned by the [single-trade endpoint](/api-reference/endpoint/get-large-trade). `trade` is `null` when the event's wallet or market data is unavailable.

This avoids a separate trade lookup for every event. `meta.replay.expand` reports the applied expansion, and you can change `expand` between replay pages without invalidating the cursor.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.