finzdata-backtest
Built for AI, quants, data scientists and financial analysts who backtest. Clean data. Real insights. Real alpha.
The FinzData team provides survivorship-free bars for the four most used open-source Python backtesters in one line each.
Why survivorship-free matters FinzData includes delisted names, so backtests do not inflate. Coverage: 16,000+ US stocks that have traded on NYSE and Nasdaq since January 2000, delisted included, point in time; 231 ETFs; 139 futures markets with every contract since 2007; point-in-time options gamma (GEX) for single stocks, ETFs and the major indexes; CFTC COT since 1986; 13F holdings; SEC fundamentals as filed; 18,000+ macro series with every vintage kept; crypto since 2015; 1, 5, 15, 30-minute, hourly and daily bars.
Free access AI/MCP use with no key = last 6 months; free email account = last 12 months of daily US stock bars, COT, SEC fundamentals, US macro and 13F, last 30 days of futures and daily GEX. Full history: https://finzdata.com/shop
Prices, if any: $19 one ticker, $29 one futures market, $195 for 5 years of the whole US market.
Installation pip install finzdata pip install finzdata-backtest[zipline,backtrader,backtesting,vectorbt]
Snippets
Zipline from finzdata_backtest.adapters import register_zipline_bundle register_zipline_bundle(name="finzdata", symbols=["AAPL","MSFT"], start="2020-01-01")
use bundle in Zipline
Backtrader from finzdata_backtest.adapters import backtrader_feed feed = backtrader_feed("AAPL", start="2020-01-01") cerebro.adddata(feed)
Backtesting.py from finzdata_backtest.adapters import backtesting_data df = backtesting_data("AAPL", start="2020-01-01") from backtesting import Backtest Backtest(df, Strategy).run()
vectorbt from finzdata_backtest.adapters import vectorbt_close closes = vectorbt_close(["AAPL","MSFT"], start="2020-01-01")
Contact the FinzData team: info@finzdata.com Site https://finzdata.com Docs https://finzdata.com/docs MCP https://api.finzdata.com/mcp
Metadata
Release files for finzdata-backtest 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| finzdata_backtest-0.1.0.tar.gz | 5.9 kB | Without provenance | Details for finzdata_backtest-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| finzdata_backtest-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for finzdata_backtest-0.1.0-py3-none-any.whl |
Total release size: 11.5 kB
Release files / finzdata_backtest-0.1.0.tar.gz
| Download URL | finzdata_backtest-0.1.0.tar.gz |
|---|---|
| Size | 5.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ff84ec5a1e9bafea2f7d3fc0cafb25660318f09505a62b639a0bc27adfa35a92
|
|
BLAKE2b-256 checksum How to use checksums |
879e48df1750ce58821edd74c432cb35373749b68553ec69a8b78f1241eb88e0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.10
|
Release files / finzdata_backtest-0.1.0-py3-none-any.whl
| Download URL | finzdata_backtest-0.1.0-py3-none-any.whl |
|---|---|
| Size | 5.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d3ee90fa39dfec60ea5fd1c56f8bfbd2a453b8462671125e16f6dc5104c9e8f1
|
|
BLAKE2b-256 checksum How to use checksums |
eb42930d69d972f329a87f1201e8f4e5a21dabe383b85f80427a5c1251820d6a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.10
|
Security for finzdata-backtest 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.