Polymarket UMA Oracle Questions | BlockRun

Choose a UMA question state to retrieve a page of Polymarket-associated oracle records. Review question IDs, status flags and any available market links or payout values with your Agent.

Your AI

Use with your AI

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

CodexClaude CodeCursorWindsurfCline

View instructions

Use markets-blockrun to list UMA oracle questions associated with Polymarket in one requested question state. This is not a general market search, trading-price query or independent settlement check. If no state is given, ask me to choose pending, proposed, disputed, reset or resolved. These are documented question states; do not infer market trading status or promise that every state request will succeed. If I request a category filter, lookup by market/question ID, date range, custom order, trading price or verified winner, explain the unavailable control and ask how I want to proceed before changing my requested scope or order. Do not assign market categories from title keywords.

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 state and an explicit integer limit directly inside queryParams, for example input {"queryParams":{"state":"resolved","limit":1}}. Do not put the controls inside queryParams.query. Use a page limit from 1 to 100: BlockRun describes a maximum of 100 and a default of 20, while the supplier describes a maximum of 200 and a default of 50. Do not rely on an omitted default. If I give no count, use an explicit initial limit of 1; if I request a page above the common limit of 100 or the meaning of count is unclear, clarify before changing it. The source orders questions by last_event_at descending; do not add sort/order, search, category or time fields. The exact supplier rules are at https://docs.predexon.com/api-reference/uma/list-markets.

Read each returned items entry's question. Keep the question id distinct from optional condition_id and market_id; retain available title, state, is_paused, is_flagged, reset_count and event/transaction references. Preserve strings, null, absence, false and zero. Read paused/flagged flags separately from question state; do not infer a final market outcome from any flag or state. Preserve reward, proposal_bond and resolved_price as exact original strings together with reward_token. The source's stated scale of 1e18 does not establish a token denomination, currency conversion or winner mapping; do not cast them to floating-point amounts or present them as USD, probabilities or winning labels. Timestamp units are not declared for request_timestamp, resolved_at, paused_at, flagged_at or last_event_at; retain original integers without seconds/ms guesses or date conversion. created_block is a block number, not a timestamp.

Report pagination.count as this page's item count, not all questions in the state. Continue only within my requested scope and existing budget/authorization when has_more is true and the returned pagination_key is a nonempty string. Pass that opaque key unchanged directly as queryParams.pagination_key on the next call, preserving state and limit. Do not decode, invent or substitute a key. If the key is absent, null or empty, explain that continuation is unavailable rather than repeating the first page. An empty items array means this request returned no questions; it does not establish complete market coverage. A failed request is not an empty list: report the failure without silently switching states or automatically retrying.

Task:
Find [5] Polymarket records with [a decision recorded]. Show available market names and payout details.

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

Polymarket UMA Oracle Questions | BlockRun

Choose a UMA question state to retrieve a page of Polymarket-associated oracle records. Review question IDs, status flags and any available market links or payout values with your Agent.

You receive

A page of UMA oracle-question records in the requested state, with question IDs, status flags and any available market titles, identifiers, oracle values and event references. Your Agent can organize the records by question and distinguish returned details from missing metadata.

Start with your task

Find [5] Polymarket records with [a decision recorded]. Show available market names and payout details.

What to know

This is oracle-question data, not trading prices or independent settlement verification. Market links can be missing, category coverage is not guaranteed, and the endpoint does not establish a currency conversion, winner mapping or unit for its event timestamps.

Inputs & outputs

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

Input schema

Input schema
Field / Path	Type	Requirement	Meaning
Question-list query options`queryParams`	`object`	Optional	Provide a question state and an explicit page limit directly in this object, with a continuation key when needed. It is not a market search or date-range input.
Optional nested query object`queryParams.query`	`object`	Optional	The interface includes this optional object. Place the endpoint's state, limit and continuation controls directly in the parent queryParams rather than here.

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

Choose a question state

This endpoint lists UMA oracle questions associated with Polymarket. Select pending, proposed, disputed, reset or resolved as the question state; these labels do not serve as a market trading-status filter. The query has no category, market-ID, question-ID, search or date-range control, and it does not guarantee coverage of a particular market category.

Provide state and an explicit page limit directly in queryParams. The BlockRun wrapper describes a maximum of 100 with a default of 20, while the supplier describes a maximum of 200 with a default of 50. An explicit count from 1 to 100 fits both documented limits; neither omitted default is established as the effective behavior. Questions are described as ordered by last_event_at descending, with no custom sort or order option.

Read the question rather than a trading quote

Each returned item contains a question record. Its id identifies the UMA question; condition_id, market_id and title link to a Polymarket market only when supplied. Read state separately from is_paused and is_flagged, and keep reset_count as a returned count rather than a complete event timeline. A missing title or identifier should remain missing.

The supplier labels reward, proposal_bond and resolved_price as strings scaled by 1e18. Preserve their original strings and reward_token: the scale label does not establish a token denomination, currency conversion or winning outcome. resolved_price is an oracle payout numerator, not a trading quote or calibrated probability. A resolved record alone does not independently verify market settlement.

Event fields such as request_timestamp, resolved_at and last_event_at are integers whose units are not stated by this endpoint. They should remain in their original form until the unit is established. created_block is a block number; transaction hashes and contract addresses are references, not a supplied event history. Nullable event times and market links remain distinct from zero and false.

Understand the returned page

pagination.count describes the current page, not every question in a state. has_more signals additional records, and pagination_key is an opaque continuation value when supplied. An empty page does not establish the absence of oracle questions across Polymarket. See the Predexon UMA question-list documentation for the question model, and use the Toolmu connection guide to connect your Agent.

Polymarket UMA Oracle Questions | BlockRun

Polymarket UMA Oracle Questions | BlockRun

You receive

Start with your task

What to know

Inputs & outputs

Input schema

Result schema

Choose a question state

Read the question rather than a trading quote

Understand the returned page

Use your connected AI

Choose what to find

Check the details