Trades Datasets
Directional order flow split by taker buy vs. sell, broken into small/medium/large notional segments, with a flow toxicity score.
Key fields
Trade notional split into small (< $100), medium ($100–$1,000), and large (≥ $1,000) segments, with summary statistics for individual trade sizes.
Key fields
Intrabar high-low price range and full distribution statistics (mean, median, std, skewness, kurtosis) for trade prices within each interval.
Key fields
How much each unit of trading volume moves the price, measured via Amihud illiquidity, Kyle lambda, impact per notional, and large-trade reversal.
Key fields
Uptick and downtick count, volume, ratios and percentages based on price movement direction.
Key fields
Consecutive same-direction trade run lengths, imbalance, flip rate, and price change on direction flip.
Key fields
Log-return based metrics: variance, realized volatility, bipower variation, jump ratio, autocorrelation, and trendiness.
Key fields
Highlighted Metrics
Every trade has a buyer and a seller, but one of them pushed — they were in a hurry. Order flow tracks who is pushing and how hard. When a lot of urgent buyers show up at the same time prices are swinging wildly, that's when being a market maker gets expensive and dangerous.
Every trade nudges the price. Bigger trades nudge more. Impact measures how much price moves per dollar traded. In thin markets that nudge is large, so investors demand higher returns to take the risk of getting in and out. That's why less liquid assets often have higher expected returns.
Not all trades carry the same information. Barclay & Warner (1993) found that medium-sized orders — not the largest — account for a disproportionate share of cumulative price impact. Informed traders deliberately size down to avoid detection. This means aggregate volume alone is insufficient: you need to decompose flow by direction, size, and concentration to understand what it is actually telling you.
Kyle's lambda and Amihud illiquidity approach the same question from opposite ends: how much does trading move the price? Lambda measures information content per unit of signed flow; Amihud measures return per dollar of volume. Where they agree, the market is behaving consistently. Where they diverge is where the diagnosis gets interesting — rising Amihud without rising lambda points to exogenous volatility, not informed flow. Rising lambda alone means someone in the order flow knows something the quote does not yet reflect.
Use Cases
Build directional signals from taker buy/sell imbalance, volume delta, and flow toxicity scores across multiple horizons.
Identify large-order flow clusters via size-segmented metrics to infer informed trading activity.
Estimate Amihud illiquidity, Kyle lambda, and impact-per-notional for realistic transaction cost models in backtests.
Separate continuous realized volatility from jump components using bipower variation and jump ratio metrics.
Evaluate strategy fills against L1-matched slippage benchmarks, broken down by buy/sell side and order size.
Use up/down tick ratios and trade run imbalance to measure short-horizon directional persistence.
Get started in minutes
pip install aperiodicfrom datetime import date
from aperiodic import get_metrics
df = get_metrics(
api_key="your-api-key",
metric="flow",
timestamp="exchange",
interval="1h",
exchange="binance-futures",
symbol="perpetual-BTC-USDT:USDT",
start_date=date(2024, 1, 1),
end_date=date(2024, 1, 31),
)
print(df.head())Get access to our full catalog of market microstructure data.