Review historical trading volume for one Kalshi market. Returns time-bucketed notional USD volume for one Kalshi market. Use one Toolmu account and a shared prepaid balance across available Tools. Pay per use; no separate supplier subscription is required. The current execution ceiling for this Tool is 0.0288 Toolmu credits per call. This is a maximum, not the settled charge. Before execution, get the current Tool contract and check availability, the latest maximumCredits, your balance and budget. Supplier response credits_used, when present, describes supplier API credits and is not the Toolmu customer charge.
Up to 0.0288 credits / call
The final charge is based on confirmed usage. Unused reserved credits return to your available balance.
Surf
Kalshi Volume History by Ticker · Surf
Review historical trading volume for one Kalshi market. Returns time-bucketed notional USD volume for one Kalshi market. Use one Toolmu account and a shared prepaid balance across available Tools. Pay per use; no separate supplier subscription is required. The current execution ceiling for this Tool is 0.0288 Toolmu credits per call. This is a maximum, not the settled charge. Before execution, get the current Tool contract and check availability, the latest maximumCredits, your balance and budget. Supplier response credits_used, when present, describes supplier API credits and is not the Toolmu customer charge.
You receive
Returns time-bucketed notional USD volume for one Kalshi market. Notional USD volume is a different measure from contract turnover. Interpret the selected bucket interval and window before comparing markets.
Start with your task
Use [a Kalshi market link or full question] to find the market, then show how the dollar value of its trades changed over [the past 30 days]. If several markets match, ask me which one. Make clear this is dollars traded, not the number of contracts.
Inputs & outputs
Inspect the current inputs, availability, and maximum charge before starting.
Input schema
Input schema
Field / Path
Type
Requirement
Meaning
queryParamsqueryParams
object
Required
Required fields
ticker
tickerqueryParams.ticker
string
Required
Market ticker identifier. Use GET /v1/prediction-market/kalshi/markets or GET /v1/search/prediction-market?platform=kalshi&q={keyword} to discover valid tickers. Example: KXBTC2026250-27JAN01-250000.
Minimum length
1
time_rangequeryParams.time_range
string
Optional
Window of history to return: 7d, 30d, 90d, 180d, or 1y. This endpoint uses time_range only — it does NOT accept interval. Example: 30d. Defaults to "30d".
Default
30d
Options
7d, 30d, 90d, 180d, 1y
View raw JSON
{
"type": "object",
"required": [
"queryParams"
],
"properties": {
"queryParams": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"ticker"
],
"~standard": {
"vendor": "zod",
"version": 1,
"jsonSchema": {}
},
"properties": {
"ticker": {
"type": "string",
"minLength": 1,
"description": "Market ticker identifier. Use GET /v1/prediction-market/kalshi/markets or GET /v1/search/prediction-market?platform=kalshi&q={keyword} to discover valid tickers. Example: KXBTC2026250-27JAN01-250000."
},
"time_range": {
"enum": [
"7d",
"30d",
"90d",
"180d",
"1y"
],
"type": "string",
"default": "30d",
"description": "Window of history to return: 7d, 30d, 90d, 180d, or 1y. This endpoint uses time_range only — it does NOT accept interval. Example: 30d. Defaults to \"30d\"."
}
},
"additionalProperties": false
}
},
"additionalProperties": false
}
Result schema
Output fields have not been documented yet.
Additional notes
Review historical trading volume for one Kalshi market
How to use this Tool
Use the deployed input fields below. Required fields must be supplied; optional filters narrow the result.
queryParams.ticker (Required): Market ticker identifier. Use GET /v1/prediction-market/kalshi/markets or GET /v1/search/prediction-market?platform=kalshi&q={keyword} to discover valid tickers. Example: KXBTC2026250-27JAN01-250000.
queryParams.time_range (Optional): Window of history to return: 7d, 30d, 90d, 180d, or 1y. This endpoint uses time_range only — it does NOT accept interval. Example: 30d. Defaults to "30d".
What this Tool returns
Returns time-bucketed notional USD volume for one Kalshi market.
Response fields and how to read them
The table follows the official response contract, including nested fields and useful response metadata. [] denotes an array item. Required means required within its parent object, not that a conditional parent always exists. A nullable type permits null; an optional field can be absent. Use the documented conditions below to distinguish missing, empty and zero values. Units and reporting windows apply only where explicitly documented.
Field, type and presence
Meaning and conditions
data.[].notional_volume_usd
number; Required within parent; format: double
Notional volume in USD (each contract counted as $1)
data.[].timestamp
integer; Required within parent; format: int64
Unix timestamp in seconds (midnight UTC for the trading day)
meta.cached
boolean; Required within parent
Whether this response was served from cache
meta.credits_used
integer; Required within parent; format: int64
Credits deducted for this request
meta.empty_reason
string; Optional within parent
Hint explaining why the data array is empty, when applicable
meta.has_more
boolean; Optional within parent
Whether more items may exist beyond this response. For offset-paged endpoints, continue with a larger offset. For time-series endpoints without offset/cursor controls, true means the requested time range hit an upstream cap; narrow from/to to continue. Omitted when exhaustion cannot be proven.
meta.limit
integer; Required within parent; format: int64
Maximum number of items returned in this response
meta.offset
integer; Required within parent; format: int64
Number of items skipped (pagination offset)
meta.total
integer; Optional within parent; format: int64
Total number of matching items (before pagination). Omitted when total is unknown.
meta.watermark
integer; Optional within parent; format: int64
Warehouse watermark (Unix seconds) this response was computed at, on warehouse-backed endpoints (e.g. Hyperliquid /trades/aggregate) — rows up to this time come from the warehouse, newer rows from the live tail. Omitted elsewhere.
Coverage, units and freshness
Notional USD volume is a different measure from contract turnover. Interpret the selected bucket interval and window before comparing markets.
Inspect any returned observation time, cache status, watermark, pagination and errors using their documented meanings. A successful request alone does not establish complete coverage. Where no freshness or completeness guarantee is documented, treat it as unknown. Saved Examples are historical and viewing them does not refresh data or execute a new call.
Data source and references
Surf supplies this endpoint through its Data API. Response contract and deployed Tool inputs reviewed on 2026-10-03 against official OpenAPI v0.2.102. This is a contract review date, not a data observation time. Coverage depends on the selected endpoint and request.
Use one Toolmu account and a shared prepaid balance across available Tools. Pay per use; no separate supplier subscription is required. The current execution ceiling for this Tool is 0.0288 Toolmu credits per call. This is a maximum, not the settled charge. Before execution, get the current Tool contract and check availability, the latest maximumCredits, your balance and budget. Supplier response credits_used, when present, describes supplier API credits and is not the Toolmu customer charge.
Example request: Show how the dollar value of trades changed for [a Kalshi market link] over [the past 7 days]. Make clear this is money traded, not the number of contracts.
Example request: Find [the Kalshi market asking whether Bitcoin will reach $100,000 by December] and show its dollar trade value over [the past 90 days].
Use [a Kalshi market link or full question] to find the market, then show how the dollar value of its trades changed over [the past 30 days]. If several markets match, ask me which one. Make clear this is dollars traded, not the number of contracts.
Review a longer period
Example request: Use [a Kalshi market link] to show dollar trade values over [the past year], and point out the periods with the highest and lowest values.
Questions about this tool.
Inputs, results and details to know before running it.
queryParams.ticker (Required): Market ticker identifier. Use GET /v1/prediction-market/kalshi/markets or GET /v1/search/prediction-market?platform=kalshi&q={keyword} to discover valid tickers. Example: KXBTC2026250-27JAN01-250000. queryParams.time_range (Optional): Window of history to return: 7d, 30d, 90d, 180d, or 1y. This endpoint uses time_range only — it does NOT accept interval. Example: 30d. Defaults to "30d".
Returns time-bucketed notional USD volume for one Kalshi market.
Notional USD volume is a different measure from contract turnover. Interpret the selected bucket interval and window before comparing markets.
Use one Toolmu account and a shared prepaid balance across available Tools. Pay per use; no separate supplier subscription is required. The current execution ceiling for this Tool is 0.0288 Toolmu credits per call. This is a maximum, not the settled charge. Before execution, get the current Tool contract and check availability, the latest maximumCredits, your balance and budget. Supplier response credits_used, when present, describes supplier API credits and is not the Toolmu customer charge.
Ask your agent to Review historical trading volume for one Kalshi market. Provide the required inputs above. If Toolmu is already connected, reuse that connection; otherwise use the setup instructions on this page. Before a paid execution, the agent must read the current Tool contract and check availability, the credit ceiling, balance, budget and your authorization. It should then execute the Tool and explain the returned fields and limitations.
Inspect any returned observation time, cache status, watermark, pagination and errors using their documented meanings. A successful request alone does not establish complete coverage. Where no freshness or completeness guarantee is documented, treat it as unknown. Saved Examples are historical and viewing them does not refresh data or execute a new call.
