MarketLab Docs

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/USDT
  • HYPE/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 orderbook
  • source candles
  • source vd

Streaming behavior differs by source:

  • orderbook: websocket depth updates
  • candles: websocket candle updates
  • vd: 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-driven
  • cvd: VD-driven
  • strategy run/backtest sma-crossover: candles-driven

Stream Validation Rules

Market Lab rejects confusing flag combinations.

Examples:

  • source candles --stream rejects --from/--to
  • source vd --stream rejects --from/--to
  • study cvd --stream rejects --from/--to
  • strategy run sma-crossover allows optional --from warmup
  • strategy backtest sma-crossover requires --from and --to

On this page