Every trader has a setup that is not on the shelf — a specific combination of a sweep, a displacement, a session, a retest, a confluence. Sentio's Model Builder takes the description in plain English or a chart screenshot, asks a few clarifying questions, and compiles the intent into a DSL of 21 primitives. Nothing invented, nothing hidden, and it cannot go live until it has proven itself against replay data.
Every step below is a real thing the builder does — no hand-wave. Steps 4 and 5 are gates: a model that fails replay validation cannot go live, and no primitive that is not in the registry can appear in the spec.
Type it out the way you would explain it to another trader. Or attach a chart screenshot — Sentio's vision model reads the geometry and fills in the description for you.
"ES sweeps London high on 15m, NQ fails to confirm, then bearish displacement + 5m FVG retracement during NY."
The compiler will not invent operators it does not understand. If your description is ambiguous — which timeframe, which session, retest within how many bars — it asks. You answer in the same chat.
The output is a DSL of 21 primitives — sweeps, gaps, displacement, structure shifts, session windows. Nothing is hidden. If a primitive does not appear in the spec, it is not being evaluated.
smt_divergence bearishliquidity_sweep london_high 15mdisplacement down 5mfvg retest ≤ 6entry session nyBefore you can activate a model, it must produce a non-zero hit rate against ~3000 bars of cached replay data. Compiled specs that fire zero times over the buffer are flagged.
Set the timeframes you want the model to scan on (multi-select), attach discipline rules if you want them scoped to this model, and flip the toggle. It joins the roster alongside the built-in five.
Every custom model carries a persistent chat. Ask for a tighter displacement threshold, a wider session window, an extra confluence condition — the compiler regenerates the spec, re-runs replay, and shows you the diff.
The compiler will not use anything outside this list. If you describe a concept it does not recognise, it says so and asks you to phrase it in terms it can compile.
liquidity_sweep Wick through prior swing or session H/L. key_liquidity Reference to session H/L, PDH/PDL, weekly open. equal_highs Cluster of equal highs — resting sell-side liquidity. equal_lows Cluster of equal lows — resting buy-side liquidity. market_structure BOS or CHoCH on a specified timeframe. displacement ATR-qualifying impulse move — up or down. cisd Change in state of delivery — closing through the last opposing candle. order_block Last opposing candle before a displacement leg. fvg Fair value gap on a specified timeframe. inverse_fvg FVG that has been traded through and now flips polarity. bpr Balanced price range — bullish + bearish FVGs overlapping. breaker_block Failed order block — the polarity-flipped zone. smt_divergence Correlated tickers disagree (ES sweeps, NQ does not). session_window Constraint: only fire during a named session. retest Return to a level within N bars. confluence Two or more independent conditions align. entry Terminal — where the trade would fire. invalidation Where the setup dies. target Target level — R-multiple or liquidity magnet. time_of_day Filter by clock: killzone windows, macro cutoffs. candle_close Require close relative to a level, not just wick. Most AI-driven trading products generate free-form English and hope. Sentio's builder is bounded to a fixed grammar. If an idea cannot be expressed in the DSL, the compiler tells you and asks you to rephrase — rather than silently interpreting your words into something that fires unpredictably. The trade-off is intentional: you get transparency and replay-testability, and you always know what the scanner is actually looking for.
Free plan includes 3 model drafts. Trader is unlimited.