> For the complete documentation index, see [llms.txt](https://docs.itradingbot.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.itradingbot.net/ai-strategy-builder/compatibility.md).

# Compatibility and limits

> Knowledge package 0.6.1, checked 22 September 2026, build 03613bfa. If the copy you are reading does not carry that line, you have a cached or older revision: fetch this page again.

The inventory was checked on **15 September 2026** against the current desktop BACKTEST metadata and its new-card selector. It covers **19 families**, **44 indicator IDs / 62 role definitions for Binance**, and **41 IDs / 58 role definitions for Bybit**. The union contains **490 fields**; Bybit uses 463 of them. Counts include entry, filter and exit roles separately where they have different contracts.

## Select an exact context

The catalogue contains four contexts: Binance and Bybit, each with averaging by signal off or on. Check both `contexts[].available_definition_ids` and `definitions[].available_contexts`, then apply that context's field overrides. A definition existing elsewhere in the catalogue does not authorize it for this context.

The three Binance-only IDs are trade-count pump, trade-count pump filter and trade-count filter. Their four role definitions must not be offered for Bybit. Funding and hidden legacy cards excluded from the current selector are not supported new-card choices in this release.

## Limits and selectors

* One entry, up to ten filters and up to three cards in the exit group.
* The general Binance timeframe list includes `12h`; the Bybit list does not. Several activity and impulse definitions use smaller or fixed lists. Always read the exact field's context-specific options.
* With signal averaging off, exit actions are `ED` and `EDOP`, default `EDOP`. With it on, `AVG` is added and becomes the default. An explicit action is required; AVG is not an ending action.
* Asset fields are bound to the main instrument in this preset adapter. Cross-market conditions are outside its profile. In a multi-pair run the calculation service rewrites each condition's Asset to the pair currently being calculated, so one card is applied to every listed pair; a condition that reads one market while trading another still cannot be expressed.
* Pair count: one strategy can be sent for one pair or for a list of pairs. The account tier is checked only when a calculation starts — in the configuration reviewed on 15 September 2026, one pair without VIP and up to 600 with VIP; the ceiling is a service-side setting with one value per tier, not a per-account one, so treat these numbers as the values reviewed on that date rather than a permanent platform rule. The form metadata does not carry this limit, so no local check can anticipate it. Conditions: [FREE, PRO and VIP: conditions and payment](/akkaunt/free-pro-podpiska-i-oplata.md).

## Numeric domains and UI controls

[Condition constraints](https://1830394604-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6lHX8ZJXkBHNJALLsrDj%2Fuploads%2FCHG1WDgV2lChAvsqSDvn%2Fitb-ai-0.6.1-en-condition-constraints.json?alt=media) records source-observed bounds, inclusivity, allowed-value lists, numeric rules and dependent restrictions. [Main settings constraints](https://1830394604-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6lHX8ZJXkBHNJALLsrDj%2Fuploads%2Fal06lQ1MzU9ddPZ2qxML%2Fitb-ai-0.6.1-en-main-settings-constraints.json?alt=media) records the general bounds of the ordinary calculation. A missing bound in metadata is not evidence that the server has no bound.

`source_no_explicit_bounds` means the reviewed constructor checks impose no explicit min/max for that field. It does not mean every finite value is meaningful for every underlying indicator or dataset. Keep the exact type and other rules, explain unusual choices, and check the result in the panel.

The numeric input's UI step is recorded separately from server validation. A spinner increment is not automatically a server modulo rule. Some source domains are finite lists, and one activity multiplier uses a float/truncation/modulo condition rather than a uniform decimal step. Use the supplied validator; do not simplify these domains or silently round values.

## Break-even stop compatibility

The ordinary preset adapter supports the break-even stop only in the two BYBIT contexts. Both percentage values must travel together; trigger is greater than zero, level is at least zero and strictly below trigger. It cannot be combined with hedge.

The calculation can be prepared for any user in the Bybit backtester. Live robot support is narrower: only a Bybit Exchange Account subaccount robot accepts it. Binance and legacy Bybit API-broker robots do not. A preset link fills the backtester and does not authorize a live transfer.

## Evidence and limits

The current public metadata establishes the observed roles, fields, enums and defaults. The checked implementation establishes the documented predicates and source input checks. Local tests compare the machine contracts and native format; they do not execute a strategy or certify numerical parity with every deployed backend.

Actual available history, warmup, gaps, instrument ticks and quantity limits, symbol-specific leverage, account fees and timezone interpretation still need panel checks. Initial seeds, finite-precision behavior and every transformed-candle/accelerated-path combination have not been exhaustively verified. A narrower unresolved behavior is identified in its family passport.

## Transfer scope

Card format 0.5 transfers an ordinary, non-fast calculation, using either limit-order or signal averaging, for one pair or for a list of pairs. Hedge settings, fast mode and optimizer ranges are outside this card format. `profile.multi_enabled` is carried by the pair list, and `profile.stop_be_enabled` by the presence or absence of its exact two-value pair. The other five `profile.*` values document intent; they are not independent controls transmitted in a URL.

The preset contains 20 required main settings, the optional two-value Bybit break-even pair when enabled, the selected condition fields and, for a multi-pair test, the pair list. It neither imports a live robot task nor starts a calculation. VIP initialization can enable fast mode separately. A single-pair link does not clear a selection left in the pair table: a nonempty selection overrides the single symbol when a calculation starts. A multi-pair link ticks its own pairs and does not untick pairs selected earlier, and a pair the loaded exchange list does not contain is skipped without a message. Follow the generator's manual checks after opening the link.

A multi-pair run is **N independent calculations placed side by side, not a portfolio**: each pair is calculated separately on the full deposit, the pairs do not share capital or know about each other, and the summed profit shown on the multi-result page is the arithmetic sum of independent runs. Hedge parameters and a pair list do not combine in one link: opening a multi-pair link activates the pair-selection tab, which clears the hedge checkbox.