MMT Provider
Important behavior and constraints when using Market Lab with the MMT provider.
MMT Provider
MMT is the only external provider currently integrated into Market Lab.
Website:
Symbol Normalization
Market Lab accepts symbols such as:
BTC/USDTHYPE/USDT
MMT expects quotes usd, so Market Lab normalizes symbols before sending requests.
Example:
- app input:
BTC/USDT - MMT request symbol:
btc/usd
Time Units
Market Lab uses milliseconds internally and at the CLI boundary.
MMT range endpoints accept Unix seconds.
Market Lab converts:
- app
ms - to MMT
s - then normalizes returned timestamps back to
ms
That means you should think in milliseconds when using Market Lab commands.
Current Scope
At the moment, the docs and command examples assume:
--provider mmt
More providers can be added later, but they are not part of the current documented surface.
Source Behavior
Current MMT-backed source commands:
source orderbooksource candlessource vd
Streaming behavior differs by source:
orderbook: websocket depth updatescandles: websocket candle updatesvd: websocket candle-like volume delta updates
Study Behavior
Current MMT-backed studies use either:
- live orderbook snapshots
- websocket orderbook streams
- range candle or VD requests
Examples:
slippage,spread,depth,imbalance,vamp: live orderbook-drivencvd: VD-drivenstrategy run/backtest sma-crossover: candles-driven
Stream Validation Rules
Market Lab rejects confusing flag combinations.
Examples:
source candles --streamrejects--from/--tosource vd --streamrejects--from/--tostudy cvd --streamrejects--from/--tostrategy run sma-crossoverallows optional--fromwarmupstrategy backtest sma-crossoverrequires--fromand--to