Sardine: Kalshi crypto settlement history

• list_markets — List the Kalshi series Sardine covers, and whether each is currently served. Each entry gives the Sardine key (e.g. "BTC-15M"), the Kalshi series
• get_settlement_rate — How often has a contract like this one settled in favour of `side`? Uses the asset's live spot price. Give the contract's strike (target price)
• get_live_board — Open Kalshi contracts right now, each with Sardine's historical count. No prices. Optionally filter to one market. Each row has the contract, the minut
• get_rate_table — The full lookup table behind every Sardine number for one series. Each row is a (distance-from-strike, time-left) bucket: distance in volatilit
• get_track_record — How accurate Sardine's published numbers have been, scored against settlements. For each series and probability bucket: what Sardine said, what actuall
• list_datasets — Downloadable CSV history files, with row counts, date ranges and URLs. Files open directly in Excel, pandas or any CSV reader. Credit "Sardine
• backtest_rule — Would this rule have made money? Replays recorded Kalshi quotes, second by second. Describe a rule for Kalshi's 15-minute crypto up/down contracts: whi
• backtest_signals — Replay YOUR OWN signals on recorded per-second Kalshi quotes, after fees. `signals` is a list of {"ts": <UTC epoch seconds>, "side": "YES"|"NO",
• get_z — Where a contract sits in the table's coordinates right now: spot, sigma_1m, z and the bucket. For a builder running the table offline against Kalshi's

No hidden text found in the tool definitions.

Text a person reading a tool definition does not see and a model does. Invisible characters can be pasted in by accident; this says what is there, not why. Covers tools only, not prompts or resources.