Configuration
SimulationManifest is the single source of truth for deterministic generation. Use it for batch datasets, streams, and MCP tool calls.
Validate a manifest
Section titled “Validate a manifest”- Use the MCP tool
validate_configto validate a manifest and compute its deterministic hash. - Use the MCP tool
get_config_schemato retrieve the JSON Schema for the manifest.
Validation behavior (high level)
Section titled “Validation behavior (high level)”- Unknown fields are rejected.
- Invalid ranges/types fail validation.
- The returned hash lets you record and reproduce an exact configuration.
Common knobs (high level)
Section titled “Common knobs (high level)”- Symbol & pricing:
symbol,initial_price,drift_annual,volatility_annual,seed - Jump process: intensity and jump-size distribution parameters
- Order book structure: update interval, level count, base spread, depth shape
- Trade flow: arrival intensity, clustering behavior, trade sizing distribution
- Impulse responses: impact decay and toxicity/pressure reversion controls
- Venue config: venue-specific settings when using venue presets/adapters
Safe example
Section titled “Safe example”{ "symbol": "BTC", "seed": 42, "initial_price": 50000.0, "volatility_annual": 0.8, "book_update_interval_ms": 100, "num_levels": 10}Next steps
Section titled “Next steps”- Determinism
- Generate data: API and API reference