Reference
The lookup layer of the docs. Every page here answers one question, "what does this construct do, exactly?", and stops there. When you know the feature and want the precise signature, the exact default, or the term's one canonical meaning, this is where you land. When you want to be taught the feature, the tutorials and how-tos elsewhere in the docs do that; the pages here point you to them.
Two things hold across the whole section.
There is no HTTP API and no SDK. "Code" means the Signal language typed on the site, and nothing here documents a network interface. Every code block is a whole program you write in the editor.
These pages assume you know options and volatility, and assume nothing about the Signal language. They name every default that shapes a number rather than hiding it, and they never push code where the interface already does the job.
For the availability status of each feature and the few items still in progress, Platform status is the authority. Read status there once, in one place, instead of hedged across ten pages.
The pages
DSL operator & function catalog The complete set of callable names in the Signal language: constants, config builders, transforms, rolling aggregations, operators, and accessors, each with its qualified signature and return type.
DSL grammar & syntax Program structure: statements, literals, // comments, name resolution, the immutable-variable rule, and the return contract that a standalone signal must end on a Signal.
Data accessor reference Signatures, parameters, and returned columns for the bar, option, and time accessors and the book(), position(), leg(slug), and option.contract(...) backtest-context accessors.
Glossary of platform terms One definition per concept, from Signal and spine through leg, book, and roll. The same word names a concept in the interface and in the DSL.
Metrics glossary Every metric a finished backtest returns in its results summary: what it means, its units, and the exact formula the engine computes.
Platform status The single source of truth for feature availability and the few items still in progress.
FAQ & troubleshooting Each entry pairs a validation error or common symptom with its cause and the corrected pattern.
Where to learn a feature
Reference states facts. To be taught, start with the tutorial and how-to pages:
- To write your first signal and understand spines, sampling, and alignment, read the Signal language and the execution model.
- To build and run a backtest, start at backtests on Backtest.ai and the backtest lifecycle.
- To understand where a number comes from before you look it up, read how every number is produced in Data & Methodology.