Kalshi · Resolution sources update
Kalshi Adds The Weather Company Data for Weather-Market Verification
Kalshi says it will use The Weather Company’s enterprise-grade weather feeds as a trusted source for verifying weather-market outcomes.
What changed
Kalshi publicly identified The Weather Company’s observation data as a trusted input for verifying weather outcomes.
What did not change
Kalshi still designs the contracts, operates the exchange, and resolves markets. The announcement does not prove that every existing weather contract now names the same source.
Why this matters
Weather contracts can depend on a named station, observation window, unit, publication, or correction policy. A stronger data partnership does not replace those contract-specific instructions.
Visual proof from the official source
A practical before-and-after check
Before the check
A reader sees a weather contract and assumes a general weather app is enough to determine settlement.
Better process
The reader opens the contract rules, identifies the named observation source and cutoff, and uses the partnership announcement only as platform-level context.
Affected Platform Database field
| Field | Resolution source / settlement evidence |
|---|---|
| Verified status | Kalshi publicly identified The Weather Company’s observation data as a trusted input for verifying weather outcomes. |
| How to record it | Treat the partnership as a platform-level source update; keep each market’s named rules and verification source as controlling. |
What to verify before acting
- Open the specific Kalshi market rules.
- Record the named source, station or geography, measurement unit, and observation window.
- Check whether preliminary readings can be corrected before settlement.
Official sources
- Kalshi News: Kalshi and The Weather Company partnership — published August 27, 2026.
The claim above is limited to what these sources state. We did not use account-only screens, private balances, or secondary reporting as evidence.
Continue the check
Update log
September 4, 2026: Published after a fresh primary-source review. No correction has been recorded.