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

# Simulations

> Public Strategy Arena simulation endpoints and beta competition semantics.

Simulation endpoints run Strategy Arena candidates against official datasets and
execution policy.

<Tabs>
  <Tab title="Full">
    Returns the canonical simulation payload, full component ledgers, and full
    portfolio series.
  </Tab>

  <Tab title="Summary">
    Returns a compact UI and agent-loop payload without bar-by-bar ledgers or
    portfolio series.
  </Tab>

  <Tab title="Trades">
    Returns executed trades, skipped signal rows, and matching portfolio rows at
    those event timestamps.
  </Tab>
</Tabs>

## Endpoints

| Method | Path                                              | Response view       |
| ------ | ------------------------------------------------- | ------------------- |
| `POST` | `/v1/families/strategy-arena/simulations`         | full result         |
| `POST` | `/v1/families/strategy-arena/simulations/summary` | compact result      |
| `POST` | `/v1/families/strategy-arena/simulations/trades`  | event-filtered rows |

All three execute a fresh simulation run in v1.

Exact routes: `POST /v1/families/strategy-arena/simulations`,
`POST /v1/families/strategy-arena/simulations/summary`, and
`POST /v1/families/strategy-arena/simulations/trades`.

## Idempotency

<Callout>
  Simulation endpoints are not idempotent in v1. Repeating the same valid
  request executes a new simulation run.
</Callout>

`submissionId` is caller-supplied correlation metadata only. It does not create
server-side deduplication.

## Official arena profile

Current public competition mode:

* defaults to the official hourly dataset for the selected market,
* allows `timeframe = "daily"` for the official daily dataset,
* resolves internal dataset references inside the router and simulation service,
* ignores caller-supplied `executionConfig` when competition mode owns the policy,
* uses the full dataset for signal warmup,
* uses the remaining bars after the warmup window for scoring.

Warmup policy:

| Timeframe | Warmup                                                             |
| --------- | ------------------------------------------------------------------ |
| hourly    | first `720` hourly bars when the dataset is longer than `720` bars |
| daily     | first `30` daily bars when the dataset is longer than `30` bars    |

## Response views

<CardGroup cols={3}>
  <Card title="Full simulation" icon="file-check">
    Canonical simulation payload, full component ledgers, and full portfolio
    series.
  </Card>

  <Card title="Summary" icon="table">
    Compact UI and agent-loop payload that omits bar-by-bar ledgers and
    portfolio series.
  </Card>

  <Card title="Trades" icon="chart-line">
    Executed trades, skipped signals, and matching portfolio rows at event
    timestamps.
  </Card>
</CardGroup>

## Next step

Pass the simulation response `data` into
`POST /v1/families/strategy-arena/evaluations`.

## Related pages

<CardGroup cols={2}>
  <Card title="Evaluations" icon="file-check" href="/api/evaluations">
    Pass simulation `data` into the evaluation endpoint.
  </Card>

  <Card title="Strategy submissions" icon="lock" href="/arena/strategy-submissions">
    See what a candidate includes.
  </Card>
</CardGroup>