# Reported issues for Kalshi Kernel

Pod holds 7 of 7 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to [Kalshi Kernel](/mcp/kalshi-kernel).

## Most discussed

### proposal: paper ledger and fill simulator (paper-mode write path)

### User problem

The kernel has no paper-trading capability: `get_portfolio`,
`place_order`, `amend_order`, and `cancel_order` fail closed with
`capability_not_ready`. An agent cannot rehearse a trading workflow
end-to-end before any live deployment, which the README explicitly
names as the design goal ("paper mode by default"). Today there is no
safe way to test order construction, idempotency, fee accounting, or
position lifecycle through the MCP boundary.

### Proposed behavior

Add a local 

[Read the thread](https://github.com/copyleftdev/kalshi-kernel/issues/8) · 2026-08-22 · closed · 1 comment

### feat: expose get_weather_index MCP tool (GET /live_data/weather_index/{city})

## Summary
Promote Kalshi's `GetWeatherIndex` REST operation (specs/trade.yaml:3046, `GET /trade-api/v2/live_data/weather_index/{city}`) into the curated MCP tool surface as **`get_weather_index`**.

The endpoint returns the Kalshi-computed city temperature index: the canonical minute-resolution °F series behind hourly temperature markets (KXHIGH lane).

## Why
- Our primary trading lane is KXHIGH weather, yet the kernel cannot read the index those markets settle against.
- `detailed=true` retur

[Read the thread](https://github.com/copyleftdev/kalshi-kernel/issues/20) · 2026-08-24 · closed · 0 comments

### design: live execution adapter (gated, staged)

## Context
All read-only market-data tools are live (PRs #7/#12/#15) and the paper ledger + fill simulator is merged (#10). The curated surface already declares `place_order` / `amend_order` / `cancel_order` with `CreateOrderV2` / `AmendOrderV2` / `CancelOrderV2` (+ margin twins) sources; in live mode they currently return typed `capability_not_ready`. This issue proposes the design for connecting a real execution backend.

This is REAL MONEY. The design must satisfy docs/ARCHITECTURE.md ("gate 

[Read the thread](https://github.com/copyleftdev/kalshi-kernel/issues/16) · 2026-08-22 · closed · 0 comments

### proposal: live last-price / quote snapshot tool

## Summary
Add **get_last** — a single compact call that returns the live pricing snapshot for one market, so an agent can answer "what is this trading at right now?" without paging through full market metadata or order books.

Per product family:
- **event**: from `GetMarket` — `last_price_dollars`, best `yes_bid_dollars`/`yes_ask_dollars` (+sizes), `no_bid_dollars`/`no_ask_dollars`, `volume_24h_fp`, `status`, timestamps.
- **perp**: from `GetMarginMarket` — `price` (mark), `bid`, `ask`, `refer

[Read the thread](https://github.com/copyleftdev/kalshi-kernel/issues/14) · 2026-08-22 · closed · 0 comments

### proposal: candles and trade-tape tools (read-only history)

## Summary
Extend the read-only market-data surface with historical tools so agents can do time-series analysis without raw REST access:

1. **get_candles** — OHLC candlesticks for a market.
   - Sources: `trade` `GetMarketCandlesticks` (`/series/{series_ticker}/markets/{ticker}/candlesticks`) and `perps` candlesticks endpoint (`/margin/markets/{ticker}/candlesticks`).
   - Inputs: `product` (event|perp), `ticker`, `start_ts`, `end_ts`, `period_interval` (1|60|1440 minutes), optional `include_la

[Read the thread](https://github.com/copyleftdev/kalshi-kernel/issues/11) · 2026-08-22 · closed · 0 comments

### proposal: paper ledger + fill simulator (paper-only write)

### User problem

The kernel has no paper-trading capability: `get_portfolio`,
`place_order`, `amend_order`, and `cancel_order` fail closed with
`capability_not_ready`. An agent cannot rehearse a trading workflow
end-to-end before any live deployment, which the README explicitly
names as the design goal ("paper mode by default"). Today there is no
safe way to test order construction, idempotency, fee accounting, or
position lifecycle through the MCP boundary.

### Proposed behavior

Add a local 

[Read the thread](https://github.com/copyleftdev/kalshi-kernel/issues/9) · 2026-08-22 · closed · 0 comments

### proposal: market-data read adapter (search_markets / get_market / get_orderbook)

### User problem

The v0.1.1 kernel exposes `kernel_status` only; every market-data tool
(`search_markets`, `get_market`, `get_orderbook`) fails closed with
`capability_not_ready`. Agent harnesses therefore cannot perform any
read-only research workflow — the highest-value, zero-financial-risk
capability class — even though the generated REST clients already exist
from the upstream OpenAPI contracts.

Concrete missing workflows for a quant-research agent:

- discover open markets by series/event

[Read the thread](https://github.com/copyleftdev/kalshi-kernel/issues/6) · 2026-08-22 · closed · 0 comments

## Most recent

The remaining reports are on [the project's issue tracker](https://github.com/copyleftdev/kalshi-kernel/issues).