Available as MCP tools:
polymarket_event_browse + polymarket_event_search + polymarket_event_read - call directly from Claude / Cursor / any MCP client. See MCP Server for the 60-second setup.What it does for your agent
Prediction Markets events group related market questions into one agent-readable card. Usepolymarket_event_search for natural-language questions such as “Bitcoin ETF approval” or “Fed rate cut odds”; use polymarket_event_browse only for list requests or exact filters such as q=ETF, tag=policy, or min_volume=10000.
The event card is the entry point, not the final stop. After browse or search returns an event_card_id, call polymarket_event_read to load the event description, lifecycle state, tags, and child market previews before choosing a market.
Agent flow
Response
Browse and search response
Browse results use lifecycle and liquidity ordering. Search results use semantic relevance.
Number of returned events.
Pagination cursor for browse, when more events are available.
Always
finance for this product surface.1 for browse and 2 for search.Account credits remaining.
200 OK · event search
Event read response
One event card with the same fields returned by browse/search, plus full event metadata.
Always
0 for event read.Account credits remaining.
Notes
Direct invocation
HTTP / SDK examples
HTTP / SDK examples
Full parameter reference
polymarket_event_browse — request parameters
polymarket_event_browse — request parameters
One of
active, inactive, closed, or active_or_recently_closed.Optional exact lexical filter across event title, slug, tags, child market questions, and outcome labels. Max 200 characters.
Optional finance tag, such as
crypto or policy.Optional asset or entity filter, such as
BTC.ISO 8601 UTC start. Must be used with
end_time.ISO 8601 UTC end. Must be used with
start_time.Optional minimum event-level market volume.
Optional minimum event-level market liquidity.
Maximum events returned. Range
1-100.Pagination cursor from
meta.nextCursor.polymarket_event_search — request parameters
polymarket_event_search — request parameters
Natural-language query. Max 2,000 characters.
One of
active, inactive, closed, or active_or_recently_closed.Optional finance tag.
ISO 8601 UTC start. Must be used with
end_time.ISO 8601 UTC end. Must be used with
start_time.Maximum events returned. Range
1-20.polymarket_event_read — request parameters
polymarket_event_read — request parameters
Event id returned by browse or search; the alias
pme_902959 is also accepted.Related
Prediction Markets Market Details
Read market outcomes and implied-probability history.
MCP Server setup
Connect Claude / Cursor / any harness in 60 seconds.