Now in early access

QUANT RESEARCHFOR CRYPTO PERPETUALS

Research → Backtest → Paper → Live
Your own AI authors the strategy over MCPBuilt for the people who measure before they act.

Statly dashboard preview
YOUR AI

Your assistant writes the strategy. Statly measures it — and runs that exact version to live.

Connect Claude, ChatGPT or any MCP-capable assistant to your Statly workspace. It reads the research catalog, composes the rules, saves a strategy version and asks for the evidence. No Statly chatbot, no second engine: the version your assistant saved is the one that runs in backtest, in paper and, when you say so on the website, live.

Your AI, your subscription

The assistant you already pay for does the thinking; Statly never bills you for AI usage. Research processing uses Research Tokens, an allowance included in the plan — not AI tokens.

Permissions you grant, one by one

Read, author, execute and cancel are separate approvals on the Statly consent screen. None of them reaches an order, an exchange key or a live deployment — that path does not exist through MCP.

The workspace is the record

Versions, jobs, results and trial history live in your workspace, not in a chat. Close the conversation, switch assistants, come back next month — the work, the holdout policy and the attempt count are exactly where you left them.

What your assistant reads through MCP is shared with that AI provider under its terms.

RESEARCH

A pattern earns the catalog by surviving a gauntlet — not by looking good once.

Nine live data lanes from Binance and Hyperliquid feed one pipeline: collect, label on two decision horizons, compute 26+ features daily, and validate through eight fail-closed gates. The verdict is net post-cost Sharpe on two independent holdouts — everything else is a diagnostic. This catalog is what your assistant reads before it writes a single rule.

CONNECTED VENUES
Binance
Hyperliquid

Live data across both,
execution on your own accounts.

01 / Collect9lanes
02 / Label2horizons
03 / Features26+computed
04 / Gauntlet8gates
05 / Catalogvalidatedsurvivors
THE PIPELINE
01 / Collect
9 data lanes

Nine live streams from Binance and Hyperliquid, across twelve perpetual-futures symbols. What the venue printed is what gets tested.

INTAKEBINANCE · HYPERLIQUID · 12 PERPETUAL-FUTURES SYMBOLS
01Tradesevery print the venue tape producedtick-levelRAW
02CandlesOHLCV aggregated from the trade tape1m · 5m · 1hDERIVED
03Top of bookbest bid and ask, continuously sampledcontinuousRAW
04L2 depthresting size beyond the touchsnapshotsRAW
05Fundingevery settlement, to the millisecond8h · 4hRAW
06Open interestoutstanding contracts across the venue5m · 288/dayRAW
07Liquidationsforced exits, as they firedevent-drivenRAW
08Oracle pricesthe venue's resolved reference price5m · resolvedRAW
09Mark-index basisthe perp's premium over its index1m · 1440/dayDERIVED
RAW captured as the venue printed itDERIVED computed on our side from the raw feeds
THE GAUNTLET

Eight ways to get rejected

Each gate fails closed: a candidate without complete evidence is refused, and the serving boundary refuses anything without a passed packet. These are rejection bars — not promises.

LEAKAGE

Leakage screens

Purged, embargoed chronological folds plus truncated-tape and correlation screens — future data can't leak into past tests.

CONCENTRATION

Factor concentration

If one latent factor explains more than 80% of the variance across symbols, the candidate is rejected.

DOSSIER

Decision dossier

Reference class, base rate, pre-mortem, and the economic rationale — written down before the verdict, not after.

CAPACITY

Capacity ceiling

Per-symbol notional ceilings sized to real book depth — a pattern must hold up at the size customers actually run.

REGIME

Regime scorecard

Scored across volatility, trend, and liquidity-stress regimes — no single-weather patterns.

OVERFITTING

Overfitting controls

Deflated Sharpe and combinatorial overfitting probability on purged folds — luck gets discounted, not rewarded.

TRIALS

Trial ledger

Every attempt is counted in a persistent ledger. The more we try, the higher the bar automatically gets.

THE BAR

Dual-tier post-cost Sharpe

The decisive test: portfolio Sharpe net of fees, funding, and slippage — on two independent holdouts, both re-run at 1.5× costs.

CURRENT BARS · VERSIONED IN THE DOCS

Both tiers must pass, and both must survive a 1.5× cost-stress re-run. Fail either, and the candidate never reaches the catalog.

Tier 1 · recent & broadSharpe ≥ 0.70 · DD ≤ 15%

Three-month holdout across all twelve symbols — the first bar every candidate must clear.

Tier 2 · deep & longSharpe ≥ 0.50 · DD ≤ 20%

Six-month holdout on the longest-history symbols — consistency over time, not just lately.

DIAGNOSTICS — THEY EXPLAIN, NOT DECIDE
IC rank correlation with the forward outcomeIC IR consistency of IC across foldsPositive folds share of folds above zero
BACKTESTS

Test a saved version against history — and get the same answer twice.

Your assistant submits a saved strategy version; Statly runs it against frozen historical data — pinned to a manifest, partition IDs and the exact commit — so any result is re-runnable and auditable, on the website or back in the chat. Empirical evidence about the past, never a promise about the future.

Deterministic replay

Same version, same partitions, same commit — same equity curve. No hidden randomness, no look-ahead.

Reproducible artifacts

Equity curve, drawdown, per-trade ledger, and behaviour by regime — pinned to the run that produced them, so anyone can verify.

Variant sweeps

Sweep parameters in one pass, rank by post-cost Sharpe, stress under heavier costs. Each survivor is its own saved version, and earns the next rung: paper.

EXECUTION

From paper to live — the same version, on your own accounts, on your terms.

A saved version climbs a one-way ladder — paper, then live — and only you advance it: signed in on the website, with the account, capital and limits in front of you, bound to that exact version. Your assistant can prepare; it can never activate. Statly is non-custodial: your own API keys, no withdrawal permission, no discretionary trading on your behalf.

Paper first

The same saved version runs forward on live data with realistic costs before a dollar is at risk — same rules, same position logic, same cost treatment as the backtest.

Your keys, your control

Your own Binance and Hyperliquid keys, scoped without withdrawal. Statly never holds your funds — not an exchange, broker, or wallet.

You decide

Nothing goes live automatically, and nothing goes live from a chat. Statly runs only the version you activate on the website, inside the limits you set. A later edit is a new version — the one that is live never changes underneath you.