Data

Manage data source coverage, symbol formats, asset classes, and future provider integration.

Live Provider Status

Loading provider status...

Current Active Provider

Yahoo / yfinance

Available
  • US stocks
  • ETFs
  • HK stocks
  • Basic China A-share through Yahoo symbols
  • Basic crypto tickers
  • Indices / FX / futures examples

Yahoo/yfinance is used for research and demo purposes. It is not treated as trading-grade data.

Asset Class Coverage

Asset ClassMarketExample SymbolsCurrent SourceStatusNotes
US StocksUSAAPL, MSFT, NVDA, TSLAYahoo / yfinanceAvailableN/A
ETFsUSSPY, QQQ, IWMYahoo / yfinanceAvailableN/A
HK StocksHK0700.HK, 9988.HK, 3690.HKYahoo / yfinanceAvailableN/A
China A-share via YahooCN600519.SS, 000001.SZ, 300750.SZYahoo / yfinancePartialAKShare planned for more China-specific coverage.
Crypto via YahooCryptoBTC-USD, ETH-USD, SOL-USDYahoo / yfinancePartialCoinGecko planned for richer crypto market data.
IndicesGlobal^GSPC, ^IXIC, ^HSIYahoo / yfinancePartialN/A
FXFXEURUSD=X, JPY=X, CNH=XYahoo / yfinancePartialN/A
Commodities / FuturesFuturesGC=F, CL=F, SI=FYahoo / yfinancePartialN/A
CSV UploadCustomlocal CSVNot connectedIn progressFor custom research datasets and model lab experiments.

Planned Providers

AKShare

In progress

Planned for China A-share. Future use: historical prices, adjustment mode, and Chinese market metadata.

CoinGecko

In progress

Planned for crypto. Future use: market cap, volume, and historical crypto market data.

CSV Upload

In progress

Planned for custom datasets. Future use: local experiments and Model Lab.

Tushare / BaoStock

Not started

Optional later. Future use: alternative China market data.

Symbol Format Guide

FormatExample
US stockAAPL
ETFSPY
HK stock0700.HK
China Shanghai via Yahoo600519.SS
China Shenzhen via Yahoo000001.SZ
Crypto via YahooBTC-USD
FXEURUSD=X
FuturesGC=F

Future Data Architecture

  • Data Source is where data comes from. Cache is temporary and rebuildable. Database stores durable research assets.
  • Future providers should normalize data into a common OHLCV schema before strategy or model code consumes it.
  • Target normalized fields: date, open, high, low, close, volume, symbol, market, data_source, adjustment, currency.
  • Cache layer: planned, not implemented.
  • Database persistence: planned for research assets, not raw OHLCV in v1.