Available as MCP tool:
polymarket_price_history - call directly from Claude / Cursor / any MCP client. See MCP Server for the 60-second setup.What it does for your agent
polymarket_price_history returns how one outcome’s implied probability changed over time. Use it after your agent has selected a market outcome and needs a clean timeline for a chart, event recap, or probability-move explanation.
Pass an outcome_token_id, choose 1h or 1d, optionally set one or two UTC time boundaries, then use limit and take_from to choose which edge to keep. The response gives ordered points with time, probability, and price.
Response
PolymarketPriceHistory
required
Probability history for one outcome token.
number
Number of returned points.
number
Always
0 for this call.number
Account credits remaining.
string
Present only when the candidate window held more bars than were returned — i.e.
limit truncated the result. The message tells the agent to narrow the window or split the query: More data exists in the requested window than the items returned; narrow the window or split the query to see more.200 OK · polymarket_price_history
Notes
Direct invocation
HTTP / SDK examples
HTTP / SDK examples
Full parameter reference
polymarket_price_history — request parameters
polymarket_price_history — request parameters
string
required
Outcome token id returned by
polymarket_market_read.string
required
1h or 1d.string
Optional inclusive ISO 8601 UTC lower boundary.
string
Optional inclusive ISO 8601 UTC upper boundary.
number
Maximum points returned after boundary filtering. Default
720 for 1h, 365 for 1d; max 20000.string
default:"latest"
Which side of the filtered window to keep when more than
limit points match. Use latest or earliest; output remains chronological.Related
Prediction Markets Events
Browse, search, and read event cards before selecting a market.
Prediction Markets Market Details
Read market outcomes and copy the
outcome_token_id you need.