Backtest360
Backtest360 is a rigour-first backtesting engine with a typed API. You describe a strategy as signals and execution rules, the engine runs it over historical price data, and you get a full performance report — returns, risk, trade-level detail, and benchmark-relative metrics — computed server-side with a strict no-look-ahead discipline.
The engine is deliberately conservative about the things that make backtests lie: signals are lagged one bar before they can fill, costs and slippage are modelled explicitly, and every run reports the data-quality issues it found. The result is a number you can defend.
Three ways in, one API key
The same engine sits behind three interfaces, and one API key works across all of them.
- Python client —
pip install backtest360. A typed client for scripts and notebooks. These docs cover it in full. - REST API — call
https://api.backtest360.comfrom any language with anX-API-Keyheader. See the API Reference. - AI assistants (MCP) — point any MCP-compatible assistant at the hosted MCP server and run backtests in conversation, no install required. See Connect over MCP.
Create a free account at backtest360.com/sign-up; a free-tier API key comes with the account. See Authentication for how to configure and rotate it.
Quick example
This runs end to end with nothing but the client and a key — the engine serves a small set of bundled sample datasets, so no external data feed is needed.
from backtest360 import Client, Strategy
client = Client() # reads BACKTEST360_API_KEY from the environment
df = client.sample_data("BTC") # bundled daily OHLCV
result = client.backtest(Strategy.rsi_threshold_long(), df)
print(result.stats["sharpe"]) # e.g. 1.42
print(result.stats["max_drawdown"]) # e.g. -0.42
result.summary() # compact human-readable report
Statistics are keyed by stable metric id (sharpe, max_drawdown, cagr, …). See Result Anatomy for the full shape of a result.
Where to start
- Installation — install the client and verify it.
- Authentication — get, configure, and rotate your API key.
- Your first backtest — an end-to-end walkthrough.
- Client Reference — the full
Client,Strategy, andResultAPI. - API Reference — the interactive REST browser.
Core concepts
- Strategy shape — how a strategy document is put together.
- Signal vs execution — how a signal becomes a fill, and the lag-1 rule.
- Result anatomy — every field on a
Result, and how the metrics are keyed.
Need help?
Questions or feedback? Email hello@backtest360.com. Found a bug or want a feature? Open an issue on GitHub.