Kalshi Trade History | BlockRun

Review Kalshi trade history from a market page link and time range. Compare the reported Yes/No prices, trade sizes and recorded times. Past trades do not show current holdings or guarantee a current price.

Your AI

Use with your AI

For tasks with several steps, continue in the AI you already use.

CodexClaude CodeCursorWindsurfCline

View instructions

Use kalshi-trades-blockrun to inspect the recorded Kalshi trades for the market or event I provide. If neither ticker nor event_ticker is provided, ask for at least one; a single selector is sufficient. ticker is an exact market match and event_ticker is a prefix match. Do not infer an event from a market string or broaden my scope. Clarify conflicting selectors or unsupported requested filters before changing them. If I request time filtering, clarify any ambiguous requested calendar boundary and its time zone, and convert only the requested start_time or end_time to integer Unix seconds. Keep an open-ended range open; do not require an omitted boundary. If both boundaries are supplied and the end precedes the start, ask for clarification. Times are optional when I do not request time filtering.

Reuse my Toolmu connection; if setup is needed follow https://toolmu.com/SKILL.md. Read get_tool for this exact name and check current execution availability, maximum credits, balance, budget and existing authorization before an authorized run. Put controls directly in queryParams, not queryParams.query. Documented controls are ticker, event_ticker, optional start_time/end_time in seconds, taker_side yes/no, min_count an integer of at least 1 contract, limit an integer from 1 to 500, defaulting to 100, order asc/desc, defaulting to desc and pagination_key. Follow https://docs.predexon.com/api-reference/kalshi/trades for the exact supplier rules. Honor my requested page size within 1–500; otherwise use the documented default 100.

Explain trade_id, market ticker, count as contracts, separate yes_price/no_price decimal prices and created_time in Unix seconds. Preserve both prices and the supplier yes/no taker_side label without converting them to probabilities, inferring buy/sell actions, participant holdings or trade value. Preserve additional raw fields without guessing their units. The supplier does not name the sorting key for order. Report missing fields or an empty result without claiming complete history. Continue within my task and budget only when has_more is true and a nonempty string pagination_key is returned. Pass it unchanged directly as queryParams.pagination_key with the same selectors, filters, time range and page settings. Missing, null or empty cursor means report that continuation is unavailable; do not invent a key or repeat the first page. This query retrieves trades and does not place orders.

When I provide an individual Kalshi market-page link, parse its URL path and read the exact market ticker from the segment immediately after `markets_by_ticker`; ignore the query string and fragment. Do not ask me to find or type the ticker. If the link is not clearly an individual market page, ask me for that page link instead of guessing from a title or switching to an event-wide request. If I ask for a time period, ask for missing or unclear start/end dates and times in ordinary language with the time zone; convert them to whole Unix seconds. Never ask me to enter seconds or a timestamp. Put ticker, start_time, end_time and limit in queryParams.query, and use a limit of five unless I request another number. Preserve the returned Yes/No prices without adding a currency, probability or conversion. Show the number of contracts separately from the number of trade records, show the Yes/No label as the source provides it without calling it a buy or sell, and present created_time as a readable date and time. Do not infer current holdings or a current price from historical trades. An empty response means no records were returned for this request, not proof that no trades happened. Continue pagination only when has_more is true and a nonempty pagination_key is returned, passing that exact key unchanged with the same request. This Tool retrieves history and does not place trades.

Task:
For [Kalshi market page link], show up to five recorded trades between [start date and time, including time zone] and [end date and time, including time zone]. Compare the reported Yes/No prices, number of contracts, and the Yes/No label shown on each trade. Say if no records are returned.

Paste into your connected AI's conversation.

Connection guide

Up to 0.01122 credits / call

The final charge is based on confirmed usage. Unused reserved credits return to your available balance.

BlockRun

Kalshi Trade History | BlockRun

You receive

A page of recorded Kalshi trades for the requested market or event, with trade identifiers, decimal prices, contract counts, taker-side labels and times when returned. Your Agent can compare these fields across the returned records.

Start with your task

For [Kalshi market page link], show up to five recorded trades between [start date and time, including time zone] and [end date and time, including time zone]. Compare the reported Yes/No prices, number of contracts, and the Yes/No label shown on each trade. Say if no records are returned.

What to know

A returned page does not establish complete historical coverage, current quotes or participant holdings. Preserve the supplier price values and side labels; this query does not place orders.

Inputs & outputs

Inspect the current inputs, availability, and maximum charge before starting.

Input schema

Input schema
Field / Path	Type	Requirement	Meaning
Trade query controls`queryParams`	`object`	Optional	Provide at least one market ticker or event_ticker directly in this container. Optional start_time and end_time use integer Unix seconds; documented filters and page settings also belong here.
Nested query object`queryParams.query`	`object`	Optional	This optional nested object does not flatten into the trade request. Put the market or event selector, optional filters, time range and cursor directly in queryParams.

View raw JSON

{
  "type": "object",
  "required": [],
  "properties": {
    "queryParams": {
      "type": "object",
      "properties": {
        "query": {
          "type": "object",
          "required": [],
          "properties": {}
        }
      }
    }
  },
  "additionalProperties": false
}

Result schema

Output fields have not been documented yet.

Additional notes

Select the market and period

Provide at least one ticker or event_ticker. ticker matches one Kalshi market exactly; event_ticker matches an event ticker prefix. An event request can cover several market tickers, so keep the requested scope explicit. The supplier does not explain how the two selectors interact when both are supplied; clarify a conflicting market/event request before changing its scope.

Put these controls directly in queryParams. queryParams.query does not flatten into the trade query. Optional start_time and end_time use integer Unix seconds. Provide a time zone with calendar times so the Agent can convert them correctly. The source does not specify an earliest history date, retention period or time-bound inclusion rule.

Optional controls and pages

The supplier documents taker_side as yes or no, and min_count as an integer of at least 1 contract. limit accepts an integer from 1 to 500 and defaults to 100. order accepts asc or desc and defaults to desc; the source does not name the sorting field or tie-breaking rule. These settings do not guarantee a particular number of records or complete coverage.

pagination.count is the number of trade records on this page, not the number of contracts or the total for the period. pagination.limit is the requested page size. has_more indicates that the supplier reports additional records; pagination_key is the next-page cursor when supplied and should retain its original value. An empty page means no trades were returned by that response; it does not prove that no trading occurred or that the history is complete.

Read the returned trades

The supplier describes each trade with a trade_id, market ticker, count, yes_price, no_price, taker_side and created_time. count is the number of contracts in the trade. yes_price and no_price are separate decimal price values described on a 0–1 scale; preserve both as returned. The source does not define a currency conversion or probability calibration for these fields. Do not derive one price from the other or treat their values as verified probabilities.

created_time uses Unix seconds. taker_side is the supplier's yes/no label; it does not identify a participant or establish a buy/sell action, profit or current holdings. These are recorded trades, distinct from current orderbook quotes. Keep any additional returned fields unchanged without assigning units from their names. This query retrieves records and does not place orders.

Sources and connection

Predexon Kalshi trade-history documentation defines the selectors, time controls and returned trade fields. The matching BlockRun operation supplies this Tool's route. Connect your Agent to Toolmu, then provide the market or event you want to inspect.

Kalshi Trade History | BlockRun

Kalshi Trade History | BlockRun

You receive

Start with your task

What to know

Inputs & outputs

Input schema

Result schema

Select the market and period

Optional controls and pages

Read the returned trades

Sources and connection

Use your AI assistant

Share the market link and time range

Review past trades