Skip to main content

tradefloor

Formerly pretium. Versions through 0.4.3 were published under that name and remain installable forever; results recorded against them replay under those exact versions. The rename changed no behaviour: 0.5.0 reproduces the same known-answer digest on every platform.

determinism licence: MIT OR Apache-2.0 python 3.11+

A market simulator you can run a strategy against, with a Rust core and a Python API.

Give it a seed and a list of companies. It runs a market forward: prices, a limit order book, fills, and an economy that moves each day. Your orders match against real depth, so your trades move the price.

Real market data cannot tell you what happens if you trade differently, or what caused a move. This can, because it computed every price.

Documentation

The full documentation lives at https://tradefloor.dev: install, core concepts, the realism envelope, presets, the API surface, and the notebooks, whose source is maintained in a separate repository.

Install

pip install tradefloor

Wheels for Linux, macOS and Windows on CPython 3.11+. No dependencies. The same engine is a Rust crate: cargo add tradefloor.

The API can still change before 1.0. A published result cannot: new coefficients ship as a new preset, so a run you cited last month replays this month.

The demo

python examples/rate-shock/counterfactual.py

Run an agent in a controlled market, checkpoint the world and fork it, then raise rates by 200bps in one branch and compare what the same agent does next.

One changed variable, in the same world and with the same agent. The run takes two seconds and needs no keys and no network. It prints the nine checks that prove the two branches started identical, the step at which the agent's behaviour changed, and the side-by-side. The walkthrough is Your first counterfactual experiment.

First run

import tradefloor as tf

universe = tf.Universe.random(40, seed=111)

spec = tf.StrategySpec.momentum(lookback_days=1.0, top_k=5)
scores = tf.evaluate({"mine": spec}, seed=7, universe=universe, days=10)

scores["mine"].return_pct            # what it made
scores["mine"].impact_bps            # what its own footprint cost
scores["mine"].strategy_fingerprint  # sha256, cite this

That is one market draw. It tells you as much about the seed as about the strategy. tf.rank runs many seeds and compares them with a paired sign test.

Contents

engine.truth() why each price moved: nine factors that sum to the move, to 1e-16
counterfactual TCA the same seed with your orders and without them
tf.rank many seeds, paired sign tests
RunManifest version, preset, seed, universe, macro, scenario. reproduce() stops on a mismatch
World / compare fork a running experiment, change one variable, and measure where the two came apart
MCP server twelve read-only tools for a coding agent, scenarios included
more a Gymnasium environment, Arrow output, checkpoints, SEC EDGAR data, a browser build

No historical dataset carries the labels truth() gives you. Real data shows you that a stock fell. It never shows you that 60% of the fall was order flow.

To drive it from an agent:

pip install "tradefloor[mcp]"
claude mcp add tradefloor -- tradefloor-mcp

Strategies, universes and scenarios are data, so a tool argument cannot reach code. Each result carries its own caveats. See the MCP page.

Controlled scenarios

scenario = tf.Scenario.load("liquidity_crisis")   # ships with the package

control, stress = tf.branch(engine, 2)
for day in range(80):
    scenario.apply(stress, day)
    ...                                  # run both branches

A scenario is an explicit collection of market interventions and assumptions, for controlled experiments rather than for forecasting. It names targets from a registry of fields the engine actually reads, and it keeps what it asserts happened apart from what it assumes happened next:

tradefloor scenario show scenarios/oil_price_spike.yml

Exogenous shocks
  day 50+            commodity.oil            x1.4

Assumed transmission
  day 55..74 ramp    macro.inflation          +1.50pp
  day 55+            macro.corporate_yield    +0.50pp

tradefloor does not claim what a war, an election, an oil shock or a recession will do to markets. It lets you state those assumptions and measure how an agent behaves under them.

Six scenarios ship inside the package, so Scenario.load works on a plain pip install -- each one recording what it was measured to be worth. Their source is here. tradefloor scenario list names them, and tradefloor scenario targets lists every target and what it actually reaches.

Realism

tf.facts.measure() scores fourteen statistics against real-market bands. The default preset, pt-v16, holds all fourteen at one year and at two years on each of twenty-six seed blocks, thirteen of which no search ever touched, with no out-of-band row anywhere.

Five of the fourteen were calibration targets, and the bands both tuned the model and graded it. So this is a stated envelope, not a test against market data that was held back.

Five limits are measured and written down:

limit what it means
horizon one year is certified. Two and five years are measured, not certified
volatility memory it decays too fast
scenario size the response has the right sign, but one run cannot size it
macro crises an inflation crisis or a policy crisis needs a scenario to drive it
roster certification used a sector-balanced roster, which no real index is

tf.envelope.check() refuses a question that falls outside a limit, and the realism envelope says what each one forbids.

Good results here do not predict real returns. The prices come from a known model, so a strategy shaped like that model looks excellent and teaches you nothing. A strategy that fails here tells you more. There is one venue, no latency, and no counterparty that adapts to you.

Seed determinism

Each release builds five targets, runs one fixed simulation in each, and compares digests. A disagreement stops the release. The crate ships its own exp, log, sin and cos, so the platform libm cannot change a result.

pt-v16 became the default at 0.6.0, taking it from pt-v14. Naming your preset explicitly makes a run replay exactly, and every preset from pt-v1 on is still selectable.

eng = tf.Engine(seed=42, universe=u, model="pt-v10")

Examples

Twelve numbered examples/ in reading order, run by the test suite:

00-a-year-in-one-market Start here: one company, one year, two crises, one chart
01-first-simulation Universe, engine, order book, determinism
02-evaluating-a-strategy Specs, baselines, ranking across seeds
03-why-did-the-price-move The nine factors that sum to every move
04-how-realistic-is-this The realism panel and the limits
05-training-an-agent The Gymnasium environment, and what size costs
06-execution-and-impact TCA and the counterfactual run
07-research-workflow.py A whole study in one file. It runs in about five seconds
08-claude-agent.py An LLM agent trading the market through the harness
09-a-pandemic-shaped-market A real 2020-21 macro path, and which fields transmit
10-forking-a-market Fork a market, raise the rate in one branch, and compare the futures
11-scenario-fork.py A scenario file applied to one branch of a fork, and what it cost

Beside them, one directory per self-contained study. Each asks one question, and they come in no particular order.

rate-shock/ The canonical demo: checkpoint, fork, +200bps in one branch, compare
finrobot/ The same experiment with a real FinRobot agent

FinRobot integration

Evaluate a FinRobot financial AI agent inside a controlled Tradefloor market. Run shared history, checkpoint the world, fork it, raise rates by 200bps in one branch, and compare how the same agent responds. The canonical rate-shock experiment, with the agent swapped and nothing else moved.

pip install "tradefloor[finrobot]"
python examples/finrobot/rate_shock.py            # replays a real recorded run
python examples/finrobot/rate_shock.py --live     # calls FinRobot

The default run replays a genuine recorded FinRobot run and needs no API key, no network and no FinRobot install.

FinRobot is a project of the AI4Finance Foundation, licensed Apache-2.0. The notebooks above are a Tradefloor integration for FinRobot, maintained in this repository without endorsement from AI4Finance, and they form no part of FinRobot's own interface.

More

Full docs: simoncoombes.github.io/tradefloor.

To contribute, see CONTRIBUTING.md and RELEASING.md. One rule shapes the rest: a change to the simulated trajectory is a breaking change, whatever its size.

To cite the software, see CITATION.cff. To cite a result, use its RunManifest.

Licence: MIT OR Apache-2.0, at your option. See LICENSE-MIT and LICENSE-APACHE.

Metadata

Release files for tradefloor 0.6.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for tradefloor 0.6.0
File Size Uploaded
tradefloor-0.6.0.tar.gz 622.3 kB Details

Built distributions (wheels)

Table of built distributions (wheels) for tradefloor 0.6.0
File
tradefloor-0.6.0-cp311-abi3-win_amd64.whl CPython 3.11 abi3 Windows x86-64 Details
tradefloor-0.6.0-cp311-abi3-manylinux_2_34_x86_64.whl CPython 3.11 abi3 Linux glibc 2.34+ x86-64 Details
tradefloor-0.6.0-cp311-abi3-manylinux_2_34_aarch64.whl CPython 3.11 abi3 Linux glibc 2.34+ ARM64 Details
tradefloor-0.6.0-cp311-abi3-macosx_11_0_arm64.whl CPython 3.11 abi3 macOS 11.0+ ARM64 Details
tradefloor-0.6.0-cp311-abi3-macosx_10_12_x86_64.whl CPython 3.11 abi3 macOS 10.12+ x86-64 Details

Total release size: 5.1 MB

Release files / tradefloor-0.6.0.tar.gz

Download URL tradefloor-0.6.0.tar.gz
Size 622.3 kB
Tags Source
SHA-256 checksum
How to use checksums
a7f31c60668536b341959ca942c3fd3222889309982c234f453b7ecefe711531
BLAKE2b-256 checksum
How to use checksums
368d62d1311122c1f8df5ef679a9e79ef1f23d9ebda6829b484f36bb9e5e26ba
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 30, 2026.

Transparency log

Release files / tradefloor-0.6.0-cp311-abi3-win_amd64.whl

Download URL tradefloor-0.6.0-cp311-abi3-win_amd64.whl
Size 827.3 kB
Tags CPython 3.11 Windows x86-64 abi3
SHA-256 checksum
How to use checksums
df6d2a3d5315d8244bbfb93f29e29366502cff6f0e013fd37a5bc4d6c83bcd02
BLAKE2b-256 checksum
How to use checksums
f17ecc29d98cbaec729eaea6796451112dbec2f7c117c3fec8dd83e8ab92deb8
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 30, 2026.

Transparency log

Release files / tradefloor-0.6.0-cp311-abi3-manylinux_2_34_x86_64.whl

Download URL tradefloor-0.6.0-cp311-abi3-manylinux_2_34_x86_64.whl
Size 928.8 kB
Tags CPython 3.11 Linux glibc 2.34+ x86-64 abi3
SHA-256 checksum
How to use checksums
19f4cb0e348191fa0d41b5a6abc814d8295dd885214401b03c560d49244d96f2
BLAKE2b-256 checksum
How to use checksums
37384e938945189a5f212eefc6d2b29525b2c48acadf8e4be7eac0f145506b4c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 30, 2026.

Transparency log

Release files / tradefloor-0.6.0-cp311-abi3-manylinux_2_34_aarch64.whl

Download URL tradefloor-0.6.0-cp311-abi3-manylinux_2_34_aarch64.whl
Size 911.6 kB
Tags CPython 3.11 Linux glibc 2.34+ ARM64 abi3
SHA-256 checksum
How to use checksums
08cd96258d4dd7e1c88caccd61b2c3df9bd70ea8bb77ba80f847c00e208a5cb6
BLAKE2b-256 checksum
How to use checksums
39103c3527b034f1a943648301f5595aabed76a0e018ed3f0492ad51ec104f14
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 30, 2026.

Transparency log

Release files / tradefloor-0.6.0-cp311-abi3-macosx_11_0_arm64.whl

Download URL tradefloor-0.6.0-cp311-abi3-macosx_11_0_arm64.whl
Size 876.6 kB
Tags CPython 3.11 abi3 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
4b620c71d4251ab683df4e69f46ad06e9e163594cfb87e35c76beeb926649f88
BLAKE2b-256 checksum
How to use checksums
f1b2ec73159033cee316c3bc79edc378d95d77dca26f743ce7854ec71252512d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 30, 2026.

Transparency log

Release files / tradefloor-0.6.0-cp311-abi3-macosx_10_12_x86_64.whl

Download URL tradefloor-0.6.0-cp311-abi3-macosx_10_12_x86_64.whl
Size 902.3 kB
Tags CPython 3.11 abi3 macOS 10.12+ x86-64
SHA-256 checksum
How to use checksums
5265ababfb142092b6bfa5fa5fa686efd4dfaef0aeb186bfae4de0f7983d37b0
BLAKE2b-256 checksum
How to use checksums
36dcde724c627542c16190e3043708ff61393ee2ad31c431f00e8ea17c1d4ad4
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 30, 2026.

Transparency log

Release history Release notifications | RSS feed

0.9.1

6 release files

0.9.0

6 release files

0.8.8

6 release files

0.8.7

6 release files

0.8.6

6 release files

0.8.5

6 release files

0.8.1

6 release files

0.8.0

6 release files

0.7.1

6 release files

0.7.0

6 release files

0.6.2

6 release files

0.6.1

6 release files

This release

0.6.0 This release

6 release files

0.5.0

6 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page