OpenAlgo normalises order flow across 31 SEBI-registered brokers behind a single REST API. The key mechanism is elegant — and it contains a structural constraint that makes true multi-broker execution harder than it first appears.
What the symtoken solves
Every broker assigns its own internal token to every tradeable instrument. OpenAlgo solves this with a unified symtoken table keyed on a canonical instrument string.
The structural constraint
The symtoken table is populated when the user downloads the active broker's master contract. When the user switches brokers, the table is replaced. This means only one broker's tokens are resident at any time.
Why AION's approach differs
AION retains a cross-broker token registry across all active brokers simultaneously. This makes instant broker switching, multi-broker fan-out, and cross-broker validation possible.
Neither architecture is wrong. They solve different problems. Understanding the boundary between them is what prevents an engineer from expecting multi-broker behaviour from a single-broker abstraction.
OpenAlgo SymToken Broker normalization Execution infrastructure Multi-broker Indian fintech
Source: AION Analytics (India) dashboard
Mirrored under AION Research Notes series.
Top comments (0)