For developers and quants

A trading language that takes correctness seriously.

If you write trading code for a living, you know where the bugs hide: units, look-ahead, fills and drift between research and live. AlgoBarsX was built around those four.

Create my free account

$0 a month
No card needed
Not a trial

What gets in your way.

Unit bugs

A percent read as dollars. A distance read as a price. They compile fine elsewhere.

Look-ahead

One wrong index and the backtest has seen the future.

Research and live drift apart

Two code paths means two results.

How AlgoBarsX helps.

Units are types

Percent, distance, price, money, R and duration are tracked through inputs and arithmetic. The engine works units out from the code, not the text.

No look-ahead, and tested

The tests rewrite the future and check that the past did not move.

Same answer every time

Same script, inputs and bars give the same result to the last digit. Live uses the same runner as replay.

A real language underneath

Functions, types, enums, lists, lambdas, pattern matching, state and versioned libraries.

Published grammar

Full EBNF for building highlighters, linters and tools.

Stable error codes

50 diagnostic codes. A code is never reused for a new meaning.

Not just rules. A language.

Types, functions that may trade, and functions that may not. A plain fn that tries to place an order is a compile error.

Types and functions

type Level:

price: price

touched: int = 0

formed_at: time

enum Regime: trending, ranging, volatile

fn swing_strength(len: int) -> number:

up = highest(high, len) - close

down = close - lowest(low, len)

return (down - up) / atr(14)

action fn enter_long(size_risk: percent = 1%) -> bool:

buy risk: size_risk, stop: 20 pips, target: 2R

return true

Go straight to the detail.

What is missing today. There is no public API, SDK or command-line tool yet. They are planned. The optimiser and walk-forward code exists in the engine but has no screen yet. The language is in beta and may still change.

Good questions.

Can I run the compiler in my own pipeline?

Not yet. A public API and a command-line tool are planned. Today the language runs inside the AlgoBars Terminal.

How are fills modelled?

By 24 written, numbered rules. Market orders fill at the next bar's open. Inside a bar the 1-minute path is used, and when it cannot tell, the stop fills first. See the execution rules.

Are costs modelled?

No. Fills carry no spread, commission, fees, swaps or slippage, and the docs say so plainly.

Start free today.

Build one thing. Read it back. Test it.

Create my free account

$0 a month · No card needed · Not a trial

Trading is risky. You can lose money. It is not right for everyone.