Settings Overview
| Setting | Type | Default | Purpose |
|---|---|---|---|
strategy_name | text | "ETH DCA" | User-facing label for the strategy |
auto_compound | boolean | true | Whether to reinvest gains |
risk_level | single_select | "medium" | Options: low, medium, high |
max_orders_per_day | integer | 3 | Cap on daily buy orders |
buy_amount_usd | number | 50.0 | USD amount per DCA buy |
slippage_tolerance | percentage | 0.5 | Max slippage per swap |
treasury | address | "0x1234..." | Wallet for fee collection |
circuit.toml
circuit.toml
Example
How It Works
- Read settings: All seven setting types are read from
agent.settingsas their native runtime types — strings, booleans, and numbers - Rate limiting: Uses
integersetting (max_orders_per_day) with agent memory to enforce a daily order cap - Swap execution: Uses
numbersetting (buy_amount_usd) andpercentagesetting (slippage_tolerance) to configure the swap parameters - Address tracking: The
addresssetting (treasury) is validated against the agent’swalletTypeat publish time
Overriding Settings at Session Start
When users start a session, they can override any setting. For example, to run a more aggressive strategy:integer, number, percentage) all use { "number": N } on the wire. The setting’s type determines validation rules (whole numbers for integer, 0-100 range for percentage).
See Also
- Settings SDK Reference — Accessing settings at runtime
circuit.tomlReference — Defining settings