PredictionToolkitKalshi tools: choose a data, development or weather workflow
This selection separates Kalshi itself from software that connects to it and research that helps interpret a contract. Start with the job you need done, then compare the account, data and operating requirements.
The exchange is the reference point
Kalshi is the venue in this selection. Use its market question, ticker and settlement rules as the reference when another tool displays a price or event. Its Predictions documentation covers event-contract REST and WebSocket access; the separately documented Perps APIs concern another product.
Choose where the integration runs
PMXT open-source SDK is the code route. Its repository documents a Kalshi client, while self-hosted mode runs pmxt-core locally and uses venue-native credentials where required. This is a development dependency to operate and maintain, rather than a ready-made research dashboard.
PMXT hosted API supplies managed catalog search and a shared interface across supported venues, including Kalshi. Hosted and local operation use different credentials and infrastructure. The documented hosted write path uses PreFundedEscrow custody; do not infer the same custody model from using the same SDK method name. Check support for the particular venue, method and runtime mode.
Use weather data for the right contract
Wethr adds station observations, model comparison and weather-analysis tools, with explicit Kalshi temperature education and hourly-market links. Match the station, observation period, units and official settlement report to the contract. A forecast or nearby station reading is not itself the final settlement observation.
A practical route through the selection
- For a contract's rules or native account access, start with Kalshi.
- For a coded integration, read the Kalshi API guide before choosing direct access, local PMXT or hosted PMXT.
- For temperature research, open Wethr with the contract's exact station and date in hand.
- For a cross-venue comparison, match settlement conditions before interpreting a price gap.
Compare data-service subscriptions and infrastructure costs separately from exchange trading charges. These official sources establish the products' documented scope; account permissions, live execution and provider latency were not tested for this selection.
Included profiles
The exchange and native contract reference. Public data access does not establish permission to trade or access a particular account.
- Access Web · API · Mobile app
Hosted catalog search and supported venue methods. Hosted writes have a separate PreFundedEscrow custody model; method availability varies by mode and venue.
- Access API
A shared SDK with a documented Kalshi client. Local operation requires developer maintenance and the venue credentials needed by each method.
- Language Python · TypeScript
Station observations and weather-model research with Kalshi references. Match the station and official settlement observation; this research is not order execution.
- Access Web · API
Continue researching
- Kalshi · context: Read the venue profile before choosing an external interface.
- PMXT open-source SDK · context: Review the local integration route and venue-specific setup.
- PMXT hosted API · context: Compare hosted catalog access, method coverage and custody.
- Wethr weather research · context: Inspect observations and model tools for the contract's station.
- Kalshi API access and integration choices · context: Choose public reads, authenticated streams or account operations deliberately.