Search Polymarket Events | BlockRun

Browse Polymarket event topics, descriptions, dates and event-level statistics. Request a general list or narrow it by title, open or closed status, or event identifiers; child markets are optional.

Your AI

Use with your AI

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

CodexClaude CodeCursorWindsurfCline

View instructions

Use the exact Tool polymarket-events-blockrun to find up to 3 open Polymarket events with Bitcoin in their titles, include up to 2 child markets per event, and compare descriptions, end dates and reported market counts. Reuse my Toolmu connection; if needed, follow https://toolmu.com/SKILL.md. Read get_tool for this exact name and the event rules at https://docs.predexon.com/api-reference/markets/events. Check current availability, maximum credits, balance and my existing authorization and budget before executing.

Put endpoint controls directly in queryParams, not queryParams.query. No selector is required for a general list. Honor any valid choices I provide: status open/closed, category, title search of 3–100 characters, or id/slug/tag string arrays of up to 50 values. Use declared sort codes (default created), an integer event limit from 1 to 100 (default 20), and nonnegative min_volume for 7-day event USD volume or min_open_interest for current event USD open interest. Child lists require include_markets=true and markets_per_event from 1 to 50 (default 10); they are capped and described as volume-sorted, not a complete child inventory. Do not ask again for an already valid count or selector. If requested date filters, Boolean combinations or ordering semantics are unsupported or undefined, clarify how I want to proceed before changing my scope; do not silently drop a condition or substitute another one.

Report actual event records and keep page count, event market_count and child-list length separate. Preserve null, empty lists/strings, zero and false. Keep nullable ISO 8601 event dates as supplied; event status is not a child status or settled outcome. Preserve generic event rolling_metrics and series context without assigning child-only units or refresh rules. If child outcomes appear, retain their raw labels, IDs, prices and winning_side; do not infer price currency, probability, complement or settlement. If the request fails or returns empty, explain the result without an automatic broader request. For additional pages already within my requested scope and budget, continue only when has_more is true and a nonempty returned cursor string exists; send that cursor unchanged directly as queryParams.pagination_key with all filters, sort and child settings unchanged. Do not decode or invent the cursor, use positive offsets, or repeat the first page when continuation is unavailable.

Task:
Show a page of Polymarket events. Say what each is about and whether it is open or closed.

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

Search Polymarket Events | BlockRun

Browse Polymarket event topics, descriptions, dates and event-level statistics. Request a general list or narrow it by title, open or closed status, or event identifiers; child markets are optional.

You receive

Get a page of Polymarket events with descriptions, source statuses, date fields, reported market counts and event-level volume, liquidity or open interest when provided. An event groups related markets; you can request a capped list of its child markets alongside it. Your Agent can organize the returned events into a comparison and keep event statistics separate from any child-market details.

Start with your task

Show a page of Polymarket events. Say what each is about and whether it is open or closed.

What to know

Inline child markets are optional and capped, so they may not enumerate every market in an event. Null is not an empty list. Event statuses and dates do not prove final outcomes, current tradability or real-time freshness.

Inputs & outputs

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

Input schema

Input schema
Field / Path	Type	Requirement	Meaning
Query controls`queryParams`	`object`	Optional	Optional query container. Put documented event controls directly here, such as status, search, limit and include_markets; no identifier or search term is required.
Generic nested query`queryParams.query`	`object`	Optional	Optional generic object with no declared child fields. Place this endpoint’s controls directly in queryParams instead of nesting them here.

View raw JSON

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

Result schema

No fixed output contract is available. Field types reflect saved result evidence; individual responses can differ.

Result schema
Field / Path	Type	Meaning
Event records`result.events`	`array`	Events returned on this page. Each event groups related markets; the page is not a complete venue inventory.
Event ID`result.events[].id`	`string`	Source event identifier, kept as a string. The id filter selects events, rather than child markets or outcome tokens.
Event slug`result.events[].slug`	`string`	Source event slug. Use the slug filter for this endpoint; it differs from a child market slug.
Tags`result.events[].tags`	`array`	Tag metadata objects supplied for the event. An empty list stays empty; do not assign tags from the title.
Event title`result.events[].title`	`string`	Topic or title supplied for the event. It does not independently establish category, status or an outcome.
Series metadata`result.events[].series`	`array`	Series objects associated with the event. Their statistics and flags describe that series and must remain separate from event statistics.
Event status`result.events[].status`	`string`	Status supplied for the event. It differs from request success, individual child-market statuses and final resolution.
Event ticker`result.events[].ticker`	`string`	Source event ticker string. It is metadata, not a declared ticker filter or an outcome-token ID.
Embedded markets`result.events[].markets`	`null`	Optional child markets requested with include_markets=true, capped by markets_per_event. Null means no inline list was supplied, rather than no markets belonging to the event.
Category`result.events[].category`	`string`	Category supplied by the source. Preserve an empty string instead of inferring a category from other text.
Event end date`result.events[].end_date`	`string`	Nullable ISO 8601 end timestamp supplied for the event. It is not a guaranteed settlement time or the time this request finished.
Icon reference`result.events[].icon_url`	`string`	Source icon URL metadata. A reference does not confirm that the image was fetched or checked.
Negative-risk flag`result.events[].neg_risk`	`boolean`	Source neg_risk boolean metadata. The flag alone does not establish payout rules, tradability or a resolved outcome.
Image reference`result.events[].image_url`	`string`	Source image URL metadata. Preserve the supplied reference or empty value.
Event start date`result.events[].start_date`	`string`	Nullable ISO 8601 start timestamp. Keep it distinct from creation, ending and closure timestamps.
Closed timestamp`result.events[].closed_time`	`null`	Nullable ISO 8601 closure timestamp. A null value must not be replaced by an inferred date or a zero.
Description`result.events[].description`	`string`	Description or rules text supplied for the event. It describes the topic; it does not confirm that a described result occurred.
Reported market count`result.events[].market_count`	`number`	Market count reported for the event. It can exceed the capped inline list and differs from the number of events on this page.
Creation-date field`result.events[].creation_date`	`string`	Nullable ISO 8601 creation-date value supplied by the source. Preserve it without deriving listing age or freshness from other dates.
Event liquidity (USD)`result.events[].liquidity_usd`	`number`	Event-level liquidity in the source USD-labelled field. The response does not establish executable depth or a calculation formula.
Current open interest (USD)`result.events[].current_oi_usd`	`number`	Current event open interest in the source USD-labelled field. It is distinct from volume, liquidity, wallet holdings and profit.
Rolling metrics`result.events[].rolling_metrics`	`object`	Additional event metrics supplied as a generic object. Keep the raw values and any supplied computation metadata; no event-wide refresh interval or leaf formula is specified.
All-time trade count`result.events[].trades_all_time`	`number`	Source all-time trade count for the event. It is not a count of markets, shares or distinct traders.
Total volume (USD)`result.events[].total_volume_usd`	`number`	Source total event volume in its USD-labelled field. The min_volume filter instead uses 7-day volume, so keep these scopes separate.
Orderbook flag`result.events[].enable_order_book`	`boolean`	Source orderbook-enabled flag. This event-list response does not supply orderbook depth or place orders.
Resolution reference`result.events[].resolution_source`	`string`	Source resolution-reference text or URL. It is not confirmation that the reference was read or the event was finally resolved.
Negative-risk market ID`result.events[].neg_risk_market_id`	`null`	Nullable source identifier associated with the negative-risk metadata. Preserve null and the original string without inventing an outcome mapping.
Page context`result.pagination`	`object`	Cursor-based pagination metadata for events. It describes this page and does not provide a total count of all matching events.
Events on this page`result.pagination.count`	`number`	Number of events returned in this response, rather than total matching events or child-market count.
Page limit`result.pagination.limit`	`number`	Source page limit for events. The documented request range is an integer from 1 to 100, defaulting to 20.
More events available`result.pagination.has_more`	`boolean`	Source flag indicating additional matching events are available. It does not guarantee an unchanging or exhaustive inventory.
Continuation cursor`result.pagination.pagination_key`	`string`	Opaque continuation value, nullable by the source. It is distinct from an event ID; preserve it unchanged for the same filters and sort.

Additional notes

Filtering event topics

The title search uses search, with 3–100 characters. A known event can instead be selected through id or slug; tag selects tag slugs. Each of these three selectors accepts a string list of up to 50 values. Category names follow the source vocabulary. Their combination rules and the direction or tie order of every sort option are not fully defined, so a requested interpretation should not be replaced with a guessed one.

Child markets are an opt-in detail: include_markets defaults to false. When enabled, markets_per_event is an integer from 1 to 50, defaulting to 10. The source describes the subset as volume-sorted without specifying its exact volume window or direction. A capped list can be shorter than market_count; null means no inline list was supplied, rather than no associated markets.

Reading event values and dates

The min_volume threshold is event volume over the last 7 days in USD; min_open_interest targets current event open interest in USD. Both are nonnegative. Keep these separate from total_volume_usd and liquidity_usd. Event rolling_metrics and series objects provide additional raw context; series statistics have a different scope, and no event-wide refresh cadence or normalization formula is established.

Event date fields are nullable ISO 8601 timestamps. Keep start_date, end_date, creation_date and closed_time separate, including unexpected values. An event status or ending date alone does not confirm a child's status or final outcome. If child outcomes are included, keep their labels, identifiers, nullable prices and winning-side values as supplied; no price currency, probability or settlement formula is specified here.

Page scope and references

The event limit is an integer from 1 to 100, defaulting to 20. Pagination count means events in the current response; no total count is returned. The pagination_key is an opaque continuation reference for the same filters and sort, rather than an event identifier. Positive offsets are no longer supported. Page counts, event market_count and capped child-list lengths describe different things.

See the official event documentation for the supported filters and optional child structure. Use the Toolmu connection guide to connect your Agent.

Search Polymarket Events | BlockRun

Search Polymarket Events | BlockRun

You receive

Start with your task

What to know

Inputs & outputs

Input schema

Result schema

Filtering event topics

Reading event values and dates

Page scope and references

Connect the AI assistant you use

View the event list

Understand open and closed