`kalshi_weather_index_calibrations`

Pack: kalshi · Endpoint: https://gateway.pipeworx.io/kalshi/mcp

Station weights, offsets and every recalibration behind a Kalshi city temperature index.

Tool description as the model sees it

How a Kalshi city temperature index is COMPUTED, and every time that changed — GET /live_data/weather/{city}/calibrations. Returns the launch configuration plus each weekly offset calibration and methodology update in ascending effective order: per-station weights, per-station offsets in Celsius, the city reference, the config version string, the calibration window and Kalshi’s stated reason for the change. This is the audit trail behind kalshi_weather_index: it is what lets you reproduce an index value from raw station data, and what tells you whether a settlement dispute falls before or after a methodology change. Same thirteen city ids as kalshi_weather_index.

Parameters

Name	Type	Required	Description
`city`	string	yes	Index city id — miami, dfw, houston, phl-delaware-valley, puget-sound, sf-bay, greater-boston, southeast-michigan, kansas-city, minneapolis-st-paul, nyc, chicago, la-coastal.

Example call

Arguments

{
  "city": "nyc"
}

curl

curl -X POST https://gateway.pipeworx.io/kalshi/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"kalshi_weather_index_calibrations","arguments":{"city":"nyc"}}}'

TypeScript (@pipeworx/sdk)

import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();

const result = await pipeworx.call('kalshi_weather_index_calibrations', {
  "city": "nyc"
});

Connect

Add this to your MCP client config, or use one-click install buttons:

{
  "mcpServers": {
    "kalshi": {
      "url": "https://gateway.pipeworx.io/kalshi/mcp"
    }
  }
}

See Getting Started for client-specific install steps.

kalshi_weather_index_calibrations