Connection check
verified live · 20h ago
alphaassay-mcp
Fail-closed backtest/signal validation: overfitting, leakage, deflated Sharpe. NOT financial advice.
Tools
21
GitHub stars
—
Installs / wk
—
Licence
—
Transport
streamable-http
Last checked
20h ago
Tools & capabilities
21 toolsRead from the running server on 20h ago.
assay_backtest
can modify data
spec*api_keyrequest_idsketch_opt_outohlcv_by_symbol*fee_bps_per_side
+1
Use this when you want a code-computed DSL backtest whose deflated- Sharpe verdict still means something after repeated searching -- every run is priced into your family's trial le… Use this when you want a code-computed DSL backtest whose deflated- Sharpe verdict still means something after repeated searching -- every run is priced into your family's trial ledger. A research audit, not buy/sell advice. Ledger-aware DSL backtest with honest family-level trial accounting. Define the strategy as an executable JSON DSL (indicators: sma, ema, rsi, atr, roc, zscore, price; ops: cross_above, cross_below, gt, lt, and, or, not), supply your own candles, and get net-of-cost per-bar returns plus a deflated-Sharpe family verdict. Every call is recorded in your family's trial ledger, so repeated searching deflates future verdicts -- that is the feature, not a bug: the verdict stays meaningful. The ledger is keyed to your authenticated account, never to a caller-supplied name. Data minimisation on request: sketch_opt_out=true skips persisting the 32-bucket return sketch -- the honest price is that without provable proximity this trial counts IN FULL toward the family budget (no evidence, no discount; the response discloses sketch_retained). Included in the flat price. The response is code-computed and ledger-dependent: a new call can change the family budget. Byte-identical output is promised only by stored replay of the same non-empty request_id with the same canonical request. Price: per check; see https://api.alphaassay.com/v1/meta/pricing (api_key required -- account setup at https://api.alphaassay.com/account).
assay_batch
can modify data
gridspecsapi_keybase_specrequest_idsketch_opt_out
+2
Use this when you optimised over a grid and want to submit the WHOLE sweep honestly -- every variant a ledger trial the family budget prices, so selection bias cannot hide. A resea… Use this when you optimised over a grid and want to submit the WHOLE sweep honestly -- every variant a ledger trial the family budget prices, so selection bias cannot hide. A research audit, not buy/sell advice. Submit your WHOLE parameter sweep honestly -- one call, every variant a ledger trial. You searched N variants; showing only the winner is exactly the selection bias the family budget prices. This tool makes the honest path the cheap path: send up to 25 DSL spec variants (as a specs list, OR base_spec + grid of dot-paths like {"signal.left.window": [2,3,4]} -- the built-in sweep adapter expands it in canonical order), plus your candles. Every variant is recorded in your family's trial ledger and verdicted with the CUMULATIVE deflation its siblings created -- later variants see the budget the earlier ones burned. The report is demote-only by construction: survives/deflated_out counts and per-variant verdicts, never a ranking, never a best pick. Metering is per valid processed variant (journaled individually, settle-before-run); if credit runs out mid-batch you get exactly what was paid for and an explicit declined count -- no silent truncation. Data minimisation on request: sketch_opt_out=true applies to every variant -- no return sketches persisted, every variant counts IN FULL toward the family budget (no evidence, no discount; disclosed per variant). The response is code-computed and ledger-dependent: a new call can change the family budget. Byte-identical output is promised only by stored replay of the same non-empty request_id with the same canonical request. NOT a buy/sell signal. Price: per valid variant; see https://api.alphaassay.com/v1/meta/pricing (api_key required -- account setup at https://api.alphaassay.com/account).
assay_calibration
read-only
Use this when you want to inspect AlphaAssay's current public calibration state for free rather than trust marketing. Calibration v0 is a population/status disclosure, not an outco… Use this when you want to inspect AlphaAssay's current public calibration state for free rather than trust marketing. Calibration v0 is a population/status disclosure, not an outcome score or track record. Self-calibration of the validator's mature pre-registration population: the published contract exposes a bucketed evaluated-registration counter, an explicit forward-outcomes status of accumulating, and honesty=insufficient_history until a separate mature-outcome metric exists. It does not score historical audit, shape, or forensics results as forward predictions. A fresh verified snapshot is signed with the platform key; missing, expired or invalid evidence fails closed as signed=false and stale=true with a reason code. It is population and status evidence only, not a performance claim. NOT financial advice. Price: free.
assay_certificate_verify
read-only
certificate*signature_b64*public_key_pem*
Use this when someone hands you a signed AlphaAssay certificate and you want to verify both its Ed25519 signature and current platform trust. A verification tool, not buy/sell advi… Use this when someone hands you a signed AlphaAssay certificate and you want to verify both its Ed25519 signature and current platform trust. A verification tool, not buy/sell advice. Verify a signed AlphaAssay certificate against externally rooted public trust. This hosted verifier evaluates full platform trust. The caller PEM is key evidence, never a trust root. A full valid result additionally requires the service's externally pinned signed keyring, complete revocation-head history, retained certificate-purpose key and no matching revocation. alphaassay-verify signature-only checks raw cryptographic evidence offline; full offline trust also requires the signed trust bundle and independent root/checkpoint pins. Price: free.
assay_conformal
can modify data
api_keyoutcomes*request_idintervals_lower*intervals_upper*calibration_size
+1
Use this when your model emits prediction intervals or confidence bands and you want to audit whether realised outcomes actually fall inside them at the claimed coverage -- a calib… Use this when your model emits prediction intervals or confidence bands and you want to audit whether realised outcomes actually fall inside them at the claimed coverage -- a calibration audit, not advice. Does your model's confidence label survive contact with outcomes? Coverage audit over prediction intervals -- confidence claims are the third claim type after return claims and risk forecasts. Submit the prediction intervals your ML model produced (lower and upper bounds, one pair per point), the realised outcomes, and the coverage the model claims (e.g. 0.9). The miss count is graded against the EXACT distribution that claim implies: binomial for a pointwise claim, or -- when you disclose the split-conformal calibration_size -- the beta-binomial the split-conformal guarantee actually promises (Vovk 2012: realised coverage is Beta-distributed around the claim), so a CORRECT procedure with a small calibration set is never punished for its honest variance. Zones reuse the same traffic-light boundaries as the VaR cell (green below cumulative probability 0.95, yellow to 0.9999, red above); red earns the named demote CONFORMAL_COVERAGE_SHORTFALL. Efficiency is disclosed, never assumed: intervals wider than the whole observed outcome range flag the advisory conformal_intervals_uninformative (coverage bought by construction), over-conservative intervals flag conformal_overcovered -- advisories, never kills, demote-only throughout. Code-computed end to end, fail-closed on malformed, inverted, undersized or oversized input. References: Vovk/Gammerman/Shafer 2005; Lei et al., JASA 2018. NOT financial advice; no order path. Price: per check; see https://api.alphaassay.com/v1/meta/pricing (api_key required -- account setup at https://api.alphaassay.com/account).
assay_cpcv
can modify data
specpurgeapi_keyembargoreturnsn_groups
+4
Use this when you have a return history and want the full combinatorial purged cross-validation (CPCV) distribution -- not one walk-forward number -- to see how path-dependent the… Use this when you have a return history and want the full combinatorial purged cross-validation (CPCV) distribution -- not one walk-forward number -- to see how path-dependent the edge really is. The FULL combinatorial purged CV distribution over your return history -- not one number, the whole picture. The gauntlet's cpcv stage answers a single question; this tool hands over everything behind it: the annualized Sharpe of EVERY purged combinatorial half-partition of your history as quantiles (worst, p05..p95, best) and a histogram, the number of recoverable full backtest paths (phi = C(N, N/2) * (N/2) / N, Bailey/Lopez de Prado), purge/embargo accounting, and the documented demote line: fewer than 60% of partitions with a positive Sharpe = cpcv_unstable (Arian/Norouzi/Seco, Knowledge-Based Systems 305, 2024 -- combinatorial purged CV dominates walk-forward at false-discovery prevention). Send a net-return series directly, OR a DSL spec + candles (the series is computed with the same primitives the gauntlet uses). Exhaustive enumeration with no RNG and nothing to seed; fail-closed on every structural shortfall. Demote-only: a pass means this one attack did not bite, never an endorsement. No ledger write. NOT financial advice. Price: per check; see https://api.alphaassay.com/v1/meta/pricing (api_key required -- account setup at https://api.alphaassay.com/account).
assay_demo
read-only
Use this when you want to see AlphaAssay's exact verdict envelope -- schema, findings, leakage taxonomy -- on a built-in example before spending a check. A methodology audit; no bu… Use this when you want to see AlphaAssay's exact verdict envelope -- schema, findings, leakage taxonomy -- on a built-in example before spending a check. A methodology audit; no buy/sell advice. Free demo verdict -- see AlphaAssay's full output shape in one call. Runs the real fail-closed validator over a built-in 40-trade example and returns the complete verdict envelope (verdict, qualitative findings, leakage taxonomy, provenance hashes) plus the machine-readable remediation explanation -- and a free synthetic-null preview: three seeded no-edge worlds (Heston stochastic volatility, Merton jump diffusion, symmetric drift bursts) showing the process-placebo machinery the paid falsify battery attacks your strategy with. No auth, no payment, no input needed. Use this first to understand the schema before submitting your own strategy with assay_signal. Price: free.
assay_falsify
can modify data
spec*api_keyrequest_idohlcv_by_symbol*fee_bps_per_side
Use this when you want your strategy actively attacked -- execution lag, cost stress, regime split, parameter neighbourhood, drift-burst -- to see what kills it first. Demote-only;… Use this when you want your strategy actively attacked -- execution lag, cost stress, regime split, parameter neighbourhood, drift-burst -- to see what kills it first. Demote-only; it does not give buy/sell advice. We do not check your signal -- we actively try to KILL it. An adversary runs a battery of stress attacks against your strategy (execution-lag push, cost stress, time jackknife, regime split, parameter-neighbourhood perturbation, combinatorial purged CPCV partitions, synthetic no-edge worlds, drift-burst window stripping -- does the PnL survive without its flash-crash bars?) and returns a survival map: which attack kills it first, which it withstands and up to what limit, plus a weakest-link headline. The graveyard sharpens the attack order -- families that mostly died of cost get cost-stressed first. Surviving every attack is the strongest evidence of robustness this platform can give (still not a profit promise). Supply an executable DSL spec + your own candles. Code-computed, demote-only. Price: per check; see https://api.alphaassay.com/v1/meta/pricing (api_key required -- account setup at https://api.alphaassay.com/account).
assay_forensics
can modify data
api_keyrequest_idsignal_events*ohlcv_by_symbol*primary_horizon
Use this when a signal looks good but you suspect leakage or look-ahead and want to know WHY it fails, not just that it fails -- a diagnostic audit, it does not give buy/sell advic… Use this when a signal looks good but you suspect leakage or look-ahead and want to know WHY it fails, not just that it fails -- a diagnostic audit, it does not give buy/sell advice. Leakage forensics: WHY your signal fails, not just that it fails. Upload your own decision timestamps (symbol, decision_time with explicit timezone, long/short) plus OHLCV candles and get a forensic diagnosis: does the edge collapse with a realistic one-bar execution delay (look-ahead leak)? Does the move happen BEFORE your decision (front-loading / anticipation)? Does it beat matched random timing? Do your trades collapse onto few independent events? Code-computed, demote-only, plain-language explanations per finding. Naive timestamps are rejected -- timezone ambiguity is the top source of fake edges. Price: per check; see https://api.alphaassay.com/v1/meta/pricing (api_key required -- account setup at https://api.alphaassay.com/account).
assay_gauntlet
can modify data
spec*api_keyrequest_idsketch_opt_outohlcv_by_symbol*fee_bps_per_side
+4
Use this when you want the whole reality-check battery on a strategy in one call -- overfitting, leakage, costs, regimes and a matched-random placebo -- as a demote-only dossier, n… Use this when you want the whole reality-check battery on a strategy in one call -- overfitting, leakage, costs, regimes and a matched-random placebo -- as a demote-only dossier, never buy/sell advice. The full reality-check battery in ONE call -- validator, family deflation, matched-random placebo, capacity ceiling and graveyard prior chained into a single consolidated dossier. Instead of pass/fail you get WHICH gate killed the signal first (machine-readable failure_codes), the placebo percentile, the tradable capacity ceiling, how often the family was already buried, and the family's remaining search budget. Built for iterating agents: it is training feedback with budget economics, not a bare verdict. Supply the strategy as an executable DSL spec plus your own candles; optional per-symbol ADV in USD unlocks the capacity gate, and optional per-symbol daily volatility (sigma_by_symbol_pct, percent) sharpens its impact model for volatile assets. Trading perpetuals? Supply funding_by_symbol ({symbol: [{ts, rate}, ...]}, decimal per-settlement rates, positive = longs pay) and the funding_edge stage charges the funding leg against every holding period: it kills what only looked profitable because funding was ignored (funding_erases_edge) and what is carry income masquerading as timing skill (edge_is_funding_carry); a series that fails its own audit keeps the funding question open instead of acquitting. Data minimisation on request: sketch_opt_out=true skips persisting the 32-bucket return sketch, and the trial counts IN FULL toward the family budget (no evidence, no discount -- disclosed in the budget block). The response is code-computed and ledger-dependent: a new call can change the family budget. Byte-identical output is promised only by stored replay of the same non-empty request_id with the same canonical request. Demote-only. Price: per check; see https://api.alphaassay.com/v1/meta/pricing (api_key required -- account setup at https://api.alphaassay.com/account).
assay_graveyard
read-only
variantstrategytimeframefingerprint
Use this when you want to check, for free, how often a signal family (e.g. sma_cross) has already been falsified and what usually kills it, before spending a check. Anonymised stat… Use this when you want to check, for free, how often a signal family (e.g. sma_cross) has already been falsified and what usually kills it, before spending a check. Anonymised stats only -- no buy/sell advice. Free lookup: how often has this signal family already died? Anonymised falsification statistics per structural signal family -- tested / killed / survived counts, top kill reasons, and the crowd prior your submission would be deflated by. Check BEFORE you spend weeks on an idea whether the crowd already buried it. k-anonymous: families with fewer than 5 distinct submitters fall back to coarser taxonomy stats. Price: free.
assay_pbo
can modify data
purgeapi_keyembargon_groupsrequest_idreturns_matrix*
+1
Use this when you have the T x N returns of a grid search and want the probability of backtest overfitting (PBO, CSCV) -- did the sweep find an edge or manufacture one? A demote-on… Use this when you have the T x N returns of a grid search and want the probability of backtest overfitting (PBO, CSCV) -- did the sweep find an edge or manufacture one? A demote-only audit, not buy/sell advice. Did your parameter sweep FIND an edge -- or manufacture one? PBO over the whole trial matrix. Submit the full T x N payoff matrix of every configuration you tried (rows = time-ordered per-period returns, columns = the candidates from your grid search / parameter sweep / optimisation run) and get the Probability of Backtest Overfitting via combinatorial symmetric cross-validation (CSCV, Bailey/Borwein/Lopez de Prado/Zhu 2017) with purge and embargo against overlapping-label leakage: the fraction of train/test splits in which your in-sample winner ranks at or below the out-of-sample median. The dossier adds the performance-degradation slope (does out-of-sample decay as in-sample shines?), the probability of out-of-sample loss, and first-order stochastic dominance of your selected picks versus the whole pool. Complements the trial ledger: the ledger counts how many tries your family burned, PBO grades whether the SELECTION PROCESS itself is overfit -- PBO >= 0.5 earns the named demote PBO_HIGH. Exhaustive enumeration with nothing to seed, fail-closed on undersized, oversized or non-numeric input. Demote-only: it can kill a selection, never bless one. NOT a buy/sell signal. Price: per check; see https://api.alphaassay.com/v1/meta/pricing (api_key required -- account setup at https://api.alphaassay.com/account).
assay_preflight
read-only
spectradesohlcv_by_symbol
Use this when you want to lint the SHAPE of a submission (DSL spec, candles or trades) for free before spending a check, so a typo never costs you one. A format check only -- it gi… Use this when you want to lint the SHAPE of a submission (DSL spec, candles or trades) for free before spending a check, so a typo never costs you one. A format check only -- it gives no buy/sell advice. Free payload lint -- fix your submission BEFORE spending a check. Validates the SHAPE of what you are about to submit, with the same machine-readable failure vocabulary the paid tools use: DSL schema validity, OHLCV sanity (finite positive prices, aligned series, strictly increasing timestamps), per-symbol data presence, trade-row types, and an honest size warning when the sample is below the paid gates' evidential floor. Send the same spec/ohlcv_by_symbol/trades you would send to assay_gauntlet or assay_signal; get back ok plus named findings (dsl_invalid, timestamps_not_monotonic, ohlcv_non_finite_or_non_positive, ohlcv_series_misaligned, symbol_data_missing, trades_rows_invalid, sample_below_engine_floor) with plain-language details. Shape lint only -- a clean preflight is NOT evidence of an edge and never blesses a signal; it just means your paid check will not bounce on format. Code-computed, no ledger write, no account needed. NOT financial advice. Price: free.
assay_provider_protocol
read-only
Use this when you want to judge ANY signal seller -- including us -- with a machine-readable seven-test falsification protocol you can run in an afternoon. It scores methodology, n… Use this when you want to judge ANY signal seller -- including us -- with a machine-readable seven-test falsification protocol you can run in an afternoon. It scores methodology, not markets: no buy/sell advice. Test ANY signal provider in an afternoon -- the falsification protocol as machine-readable rules. Seven falsifiable tests that separate edge from selection, runnable against any signal seller (paid channel, platform, bot) without their cooperation: provenance (tamper-proof timestamps or it did not happen), survivorship (the full issue history incl. losers), pre-registration (ten sealed forward calls), placebo (does random timing do as well?), costs (profitable AFTER fees/spread/slippage?), trial accounting (one winner out of how many quiet attempts?), and the examiner test (apply it all to whoever grades the signals -- including AlphaAssay: golden specimens, hosted full-trust certificate verification with separate raw signature-only and full offline trust paths, current persisted calibration snapshot). Each test carries a machine-checkable failure_condition, and tests 3-6 name the AlphaAssay endpoint that automates them. Static and code-computed: this tool hands you the checklist, it does not rate, score or rank any provider and it never fetches external data. NOT financial advice. Price: free.
assay_register
can modify data
spec*api_keyhypothesisrequest_idembargo_barsmaturity_bars
Use this when you want to seal a strategy and its success criteria NOW, before the forward data exists, so that registration cannot be adapted or backfilled against those later bar… Use this when you want to seal a strategy and its success criteria NOW, before the forward data exists, so that registration cannot be adapted or backfilled against those later bars -- a commitment audit, not buy/sell advice. Pre-register a signal NOW; freeze its terms before the forward evidence exists. Signal commitment: your strategy spec (executable JSON DSL) is canonically hashed and committed in tenant state now, then queued for later daily operator-published Merkle inclusion. The register response is not an inclusion proof, and the built-in chain is not independent time evidence; that requires a separately present and pinned external anchor. The later verdict (assay_verdict) uses exclusively data from AFTER registration. That prevents adapting this registration to those forward bars, but does not prove the strategy or family was not selected through earlier research or repeated trials; the family ledger and deflation disclose and penalise those trials. v2: optionally seal a machine-writable HYPOTHESIS tuple alongside the spec -- declared_pass_sharpe_annualized (your pre-committed success bar), max_evaluation_bars (ex-ante window cap: waiting longer than promised cannot improve the verdict), fee_bps_per_side and trading_calendar (the sealed evaluation terms), plus an optional rationale. The tuple is canonically hashed and bound into the same queued commitment as the spec, and assay_verdict ENFORCES it: deviating terms are recomputed under the seal and flagged goalpost_moved -- success criteria chosen after seeing the data are not criteria. Registrations are idempotent, withdrawals still count toward your family's trial budget (anti-gaming). Registrations are keyed to your authenticated account. Price: per check; see https://api.alphaassay.com/v1/meta/pricing (api_key with the register scope required -- account setup at https://api.alphaassay.com/account).
assay_reproduce
can modify data
tradesapi_keyclaimedrequest_idohlcv_by_symbolfee_bps_per_side
Use this when someone hands you a claimed track record and you want to recompute it yourself from the fills and candles -- an arithmetic audit of the numbers, not buy/sell advice.… Use this when someone hands you a claimed track record and you want to recompute it yourself from the fills and candles -- an arithmetic audit of the numbers, not buy/sell advice. Independently recompute a claimed track record -- audit the arithmetic, not the story. New audit object: not the signal, the CALLER'S CALCULATION. Send the trades (entry/exit time, price, side), the candles they were filled on, and the claimed headline metrics (total_return_pct, win_rate, max_drawdown_pct, n_trades, sharpe_annualized); the engine rebuilds the equity book independently and grades the claim against disclosed per-metric tolerances (published cross-engine divergence reaches 3.71%, so the band is explicit output, never a hidden judgment). Checks every fill against its bar's [low, high] (a fill outside the range was never physically available: FILL_OUTSIDE_BAR_RANGE), prices formally undecidable stop/limit exits worst-case -- both bracket levels inside one OHLC bar cannot be ordered (Maier-Paape/Platen) -- and reports that fill-ambiguity haircut (FILL_AMBIGUITY_MATERIAL when worst-case pricing flips the book's sign). Also returns an implementation-uncertainty interval: every fill pushed to the best and worst end of its bar, the spread a legitimate re-implementation could produce; a claim outside EVERY convention earns RESULT_NOT_REPRODUCED. Demote-only: 'reproduced' means the numbers follow from the fills -- it is NOT evidence of an edge and never endorses a strategy. Code-computed; no ledger write (auditing arithmetic is not a new trial). Timestamps must carry explicit timezones; structurally invalid input is refunded. NOT financial advice. Price: per check; see https://api.alphaassay.com/v1/meta/pricing (api_key required -- account setup at https://api.alphaassay.com/account).
assay_signal
can modify data
labelapi_keyn_trialsequity_csvrequest_idtrades_csv
+6
Use this when you have a backtest result or live track record (a trades log, equity curve or QuantConnect export) and need to know whether the edge is real or just overfitting, sur… Use this when you have a backtest result or live track record (a trades log, equity curve or QuantConnect export) and need to know whether the edge is real or just overfitting, survivorship or luck. Validate a trading strategy export: fail-closed statistical verdict. Reality-check for backtest results, trade lists and equity curves (overfitting detection, deflated Sharpe, multiple-testing deflation via n_trials, cost stress, look-ahead signature, sample-size floor). Accepts CSV text (trade list with pnl / return %, equity curve, signal series) or a QuantConnect/LEAN backtest JSON -- crypto, stocks, futures, FX alike. Returns pass / conditional / fail / insufficient_evidence with qualitative findings and canonical provenance hashes; code-computed, no LLM scoring. Declare n_trials honestly (omitting it earns a named TRIALS_UNDISCLOSED finding): it is the count of variants you searched to find this one (best-of-N selection from a parameter sweep); the verdict then answers whether the winner is real or an artifact of the search. Optional pit_evidence attaches an already-computed point-in-time / look-ahead guard report (e.g. a same-session vs prior-settle rank-consistency check): an explicit computed material_look_ahead verdict hard-fails the submission (pit_lookahead); missing or inconclusive evidence changes nothing -- the field can demote, never bless. Optional source_rights attaches attested data-rights evidence: an explicit negative (source_rights_clean=false or a missing_source_rights status) withholds any positive outcome as insufficient_evidence with agent_action=owner_data_decision_required (a verdict on data you may not use is a liability, not evidence); fail stays fail, unclear evidence changes nothing. NOT a buy/sell signal. Price: per check; see https://api.alphaassay.com/v1/meta/pricing. Debited from your prepaid account (api_key required -- create one at https://api.alphaassay.com/account; the current allowance is published by runtime pricing).
assay_survivors
can modify data
alphaapi_keyrequest_idn_bootstrapblock_lengthreturns_matrix
+1
Use this when you ran a grid or parameter sweep and want to know WHICH variants survive family-wise error control (FWER) rather than surfacing by chance -- an error-budget disclosu… Use this when you ran a grid or parameter sweep and want to know WHICH variants survive family-wise error control (FWER) rather than surfacing by chance -- an error-budget disclosure, not buy/sell advice. WHICH variants of your sweep survive family-wise error control -- an error-budget disclosure, never a ranking. Send the same T x N trial matrix assay_pbo grades (rows = time-ordered periods, columns = every configuration you tried) and get Romano-Wolf stepwise multiple testing over it: studentized per-config statistics, circular block bootstrap over the time rows (serial dependence respected), stepdown max-statistic critical values (Romano/Wolf 2005, Econometrica; Hansen SPA 2005). Answer, per variant IN INPUT ORDER: could this family's evidence kill it at family-wise error rate alpha, and in which stepdown round? Survival- map framing by construction: the verdict vocabulary is fail (nothing survives: NO_SURVIVORS_AT_FWER), conditional (survivors disclosed -- explicitly NOT a pass) or insufficient_evidence (blocked with a named reason); this tool structurally cannot bless, rank or recommend. Natural partner of assay_pbo -- one matrix, two questions: is the SELECTION overfit (pbo), and which variants does the error budget leave standing (survivors). The bootstrap is seeded from the input digest; fail-closed on size, budget and numerics; no ledger write. NOT financial advice. Price: per check; see https://api.alphaassay.com/v1/meta/pricing (api_key required -- account setup at https://api.alphaassay.com/account).
assay_tradelog
can modify data
tradesapi_keyrequest_idtrading_calendar
Use this when you have a raw fill or trade log and want it scanned for internal contradictions -- look-ahead timestamps, pnl that disagrees with the row's own prices, duplicate or… Use this when you have a raw fill or trade log and want it scanned for internal contradictions -- look-ahead timestamps, pnl that disagrees with the row's own prices, duplicate or out-of-order fills. Interrogate a raw fill log for internal contradictions -- no candles needed. assay_preflight lints shape, assay_reproduce audits arithmetic against candles; this tool needs nothing but the log itself and asks whether it is internally consistent: exact duplicate fills (double counting inflates every headline number: tradelog_duplicate_fills), time travel (exits before entries, decisions stamped AFTER the entry they supposedly caused: tradelog_time_travel -- the anatomy of a look-ahead), PnL or return_pct contradicting the row's own prices (tradelog_pnl_inconsistent), naive/unparseable/future timestamps (tradelog_timestamps_invalid -- ambiguous clocks are the top source of fake edges), and fills booked outside the declared calendar (tradelog_outside_calendar, e.g. weekend fills under trading_calendar='weekdays'). Checks run only where fields exist and the report SAYS which ran (checks_run) -- an absent field is untestable, never innocent. Demote-only: a defect-free log earns 'conditional', because internal consistency is NOT evidence of an edge. Code-computed; no ledger write; structurally invalid input is refunded. NOT financial advice. Price: per check; see https://api.alphaassay.com/v1/meta/pricing (api_key required -- account setup at https://api.alphaassay.com/account).
assay_var_es
can modify data
alphaapi_keyreturns*request_ides_forecastsvar_forecasts*
+2
Use this when you have VaR or Expected-Shortfall forecasts and need to know whether reality breached them more often or deeper than your claimed tail level allows -- a risk-forecas… Use this when you have VaR or Expected-Shortfall forecasts and need to know whether reality breached them more often or deeper than your claimed tail level allows -- a risk-forecast audit, not buy/sell advice. Does your risk model's VaR/ES forecast survive contact with reality? Exceedance backtest over YOUR forecasts -- a new claim type: risk numbers, not return claims. Submit realised per-period returns plus the VaR forecasts your model produced ex ante (positive loss thresholds at tail level alpha, e.g. 0.05 for a 95% VaR), optionally the matching expected-shortfall forecasts. The breach count is graded on the EXACT binomial Basel traffic-light zones (Basel Committee 1996: green below cumulative probability 0.95, yellow to 0.9999, red above) -- published boundaries, no house thresholds; red earns the named demote VAR_BREACH_RATE_EXCESS. Kupiec's proportion-of-failures LR (1995) and Christoffersen's independence LR (1998) ride along -- clustered breaches flag the advisory var_breaches_clustered (a model blind to volatility clustering). If ES forecasts are supplied, a joint (VaR, ES) mixture e-process (e-backtesting, Wang & Ziegel) grades breach DEPTH: crossing Ville's anytime-valid 1% line earns ES_TAIL_UNDERSTATED. Supply benchmark_var_forecasts (and optionally benchmark_es_forecasts, e.g. a rolling historical quantile) and the assay also tests EQUAL PREDICTIVE ABILITY: Diebold-Mariano (1995) on a strictly consistent loss (quantile tick, or the joint FZ0 loss of Fissler & Ziegel 2016 when both sides carry ES) -- a naive benchmark that beats your model past the one-sided 5% line earns RISK_FORECAST_DOMINATED_BY_BENCHMARK; the attention zone to 10% is the advisory risk_forecast_lags_benchmark. Demote-only: too many breaches can kill, too few is the mis-calibration advisory var_breach_rate_sparse -- conservative models pass with a flag, never a blessing. Code-computed end to end, fail-closed on malformed or undersized input (a series too short to reach the red zone answers insufficient_evidence instead of a hollow pass). Works for any asset class. NOT financial advice; no order path. Price: per check; see https://api.alphaassay.com/v1/meta/pricing (api_key required -- account setup at https://api.alphaassay.com/account).
assay_verdict
can modify data
api_keyprereg_id*request_idohlcv_by_symbol*fee_bps_per_sidetrading_calendar