Tested observations
The live probes produced these operational facts:
Interpretation: the data-domain API is the fast feed. Exact Kalshi ticker reads can hydrate markets that were not present in the warm registry.
sf inspect and sf book remain the richer analytical fallback because they add regime, indicators, suggestion, and CLI-native receipts.
Choose the right surface
Cold-start loop
Start broad:Data API cold start
Use data API search and movers before subscribing to individual topics:Coverage contract
The data API has two layers:
Hydration is intentionally exact-ticker only. Kalshi text search parameters are not reliable enough for arbitrary query fallback, and brute-force loading every active Kalshi market would pull in too much low-signal traffic. For broad discovery, use
sf discover, sf query, /v1/search, /v1/movers, and /v1/snapshot.
Orderbook fallback pattern
When building a market-making or alpha pipeline, use a fallback chain:WebSocket subscription
Use WebSocket when you have a known ticker set:discover, movers, search, or snapshot.
Replay record shape
For custom research, store normalized frames:Alpha research packet
A practical read-only packet for an agent:dataPoints as a warning that the result is not a full evaluation.
Market-making packet
Before creating a quote:Related docs
Real-Time Data API
Endpoint reference and WebSocket topics.
Market making
QuoteEngine workflow and operational gates.
Evaluation and replay
How to evaluate agents and strategies from traces and backtests.
World Model
Agent context and delta strategy.