`kalshi_event_live_data`

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

The observed underlying data behind a Kalshi event — price track, published series — from Kalshi.

Tool description as the model sees it

The REAL-WORLD measurement an event settles against, next to the odds — Kalshi’s event live-data feed (GET /live_data/events/{event_ticker}). This is the thing you cannot get by calling any other Kalshi endpoint: for a crypto event it is the underlying BTC/ETH price track from the settlement index (candlesticks + tick timeseries); for an economic event it is the actual published series the market resolves on (e.g. CPI CUUR0000SA0 from BLS, monthly, with its latest value and the target period); for other events it is whatever observation Kalshi charts behind the contract. The response’s type names the schema of details (seen live: “crypto”, “timeseries”), and the fields that matter are lifted to the top level where they exist: latest_value, unit, measure, frequency, provider, series_id, target_period, last_refreshed. COVERAGE IS PARTIAL AND WE SAY SO: most events have no live data and answer 404 — this returns found:false with the ticker rather than an error. Weather is NOT here: temperature observations are city-keyed, not event-keyed (KXHIGHNY-26SEP16 404s) — use kalshi_weather_index. The raw payload can exceed 400 KB for an active crypto event, so series are trimmed to max_points newest-first and points_total reports what existed.

Parameters

Name	Type	Required	Description
`event_ticker`	string	yes	Kalshi event ticker, e.g. “KXBTCD-26SEP1617” (crypto) or “KXUSCPIYEAR-37FEB01” (economic series).
`range`	string	no	Chart-range hint passed straight to Kalshi, e.g. “15min”, “1h”, “1d”. Honoured only by types that support it; the response reports Kalshi’s own `default_range` and any `selectable_periods` it advertises.
`max_points`	number	no	Newest points to keep per series (default 200, max 2000). `points_total` always reports the untrimmed length.

Example call

Arguments

{
  "event_ticker": "KXUSCPIYEAR-37FEB01",
  "max_points": 5
}

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_event_live_data","arguments":{"event_ticker":"KXUSCPIYEAR-37FEB01","max_points":5}}}'

TypeScript (@pipeworx/sdk)

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

const result = await pipeworx.call('kalshi_event_live_data', {
  "event_ticker": "KXUSCPIYEAR-37FEB01",
  "max_points": 5
});

More examples

{
  "event_ticker": "KXBTCD-26SEP1617",
  "range": "15min",
  "max_points": 3
}

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_event_live_data