assay_register

com.alphaassay/mcp · Verify this server

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).