Global settings

The Settings page at /admin/ai/binary-engine/settings holds the platform-wide configuration for the addon. It writes flat binaryAiEngine* keys through the core platform settings endpoint, and the engine reads them back at runtime.

There are two kinds of key here and confusing them is the most common mistake.

Nine of the twenty-two fields are the first kind. The rest are the second.

The page requires access.ai.binary_engine.settings and saves through PUT /api/admin/system/settings, which is changed-keys-only — untouched fields are not rewritten.

Engine tab — the master switches

Read on every cron cycle. When off, the cron marks the engine globally paused, stops every correlation monitor and returns immediately. Settlements record FAIR:GLOBAL_PAUSE. Engine rows keep their status; nothing is unloaded permanently, so switching it back on resumes within a cycle.

This setting fails closed: if the settings store cannot be read at all, the addon is treated as disabled rather than left running blind on unknown configuration.

The kill switch you reach for first. Engines stay loaded, so lifting the pause resumes instantly. It also suspends correlation monitoring and removes the per-order exposure caps, since a paused engine imposes no risk appetite.

Equivalent to turning simulationMode on for every engine at once, without editing any of them. Engines keep analysing buckets and recording what they would have done; settlements record FAIR:GLOBAL_PRACTICE_MODE.

Not to be confused with the per-engine practiceMode option, which is about demo accounts.

Range 1–168. Seeds winRateResetHours on new engines. The actual rollover is driven by each engine's own column.

Win Rate tab

A percentage, 20–50, stored as a percent and normalised to a fraction when read. Clamped between the min and max below before it is used, so a target outside your own band cannot be seeded.

These two are master switches, not defaults. The band is pushed to the engine on every cron cycle and applied to every decision, after tier bonuses and cooldown reductions. It is the platform-wide guarantee that no combination of per-engine settings can produce a target you did not sanction.

Min is 15–40, max is 30–55. If they cross, the reader swaps them rather than producing an impossible band. The page also clamps the trio before saving.

CUSTOM practice mode is exempt — it deliberately targets a friendlier rate than the live band allows.

Expressed in permille (‰), range 1–50, so the default 10 means 0.010 — one percentage point. Read on every cron cycle and applied to enableMlAutoApply engines. It bounds the machine, not you: a manual edit to a target is not limited by it.

Tiers tab

Percentages, each with its own upper limit (5, 7, 10, 12 and 15 respectively), normalised to fractions when read.

These are the platform-wide bonus profile. The bonuses actually applied to a bucket come from the per-engine tier rows under Users → User Tiers, which are seeded separately when the extension is enabled. If you change a bonus here and see no effect, that is why — edit the tier row.

See Tiers and cooldowns.

Cooldown tab

Seeds both enableBigWinCooldown and enableStreakCooldown.

An absolute profit amount, 0–1,000,000. Not a multiplier over average stake — that reading came from an older key which nothing ever computed, and this is a new key so a stored multiplier can never be reinterpreted as an amount.

Range 5–1440.

A percentage, 0–20, normalised to a fraction. Applied to a bucket in proportion to how many of its orders belong to users under cooldown.

Range 2–10. Streaks are counted per symbol.

Range 5–1440.

Whale tab

An absolute amount, 0–10,000,000. As with the big-win threshold, this is a new key with the correct meaning rather than a relabelled old one.

A percentage, 10–40. Seeds whaleWinRateCap. The cap is applied last, after tier bonuses, cooldown reductions and the global band, so it is the final word on a whale bucket.

See Risk controls.

Emergency tab

Six buttons, each with a confirmation step, each audited. Full behaviour is in Risk controls; the summary:

Emergency Stop requires a reason and it is recorded on every affected engine.

How the values are read

Worth knowing when a setting looks like it is being ignored:

• Everything comes back as a string. The platform settings store is text — a switch that is off is the string "false", not a boolean. Every field is coerced defensively on read.
• Percent fields are normalised. A stored 35 becomes 0.35. A stored 10 in the adjustment-speed field is permille and becomes 0.010.
• A blank or unparseable value falls back to the documented default, not to zero.
• A genuine zero is honoured on the per-engine columns. Setting an engine's steering band to 0 switches steering off; it does not restore 0.3%.

Recommended starting points

Whatever you pick, run it with the global practice switch on for a full period first and read the dashboard's settlement verdict breakdown before you commit.

Related

• Engines — per-engine fields, which override most of the above
• Snapshots and audit — rolling back a configuration change
• Platform settings — how the settings store works