Polymarket Crypto Up/Down Markets | BlockRun

Browse Polymarket crypto Up/Down market records. Choose an asset, market timeframe or state if needed, and get a page of contracts to compare.

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-crypto-up-down-blockrun to find crypto Up/Down prediction-market records and compare their questions, outcome prices and listed end times. Reuse my Toolmu connection; if setup is needed, follow https://toolmu.com/SKILL.md. Read get_tool for this name and check current availability, maximum credits, balance and my existing spending authority before execution. Source: https://docs.predexon.com/api-reference/markets/crypto-updown.

No selector is required. Put controls directly in queryParams, not queryParams.query. asset supports btc, eth, sol, xrp, hype, doge and bnb; timeframe supports 5m, 15m, 1h, 4h and daily; status supports open or closed. sort orders end_time asc or desc, default desc. offset is a nonnegative integer, default 0. The wrapper says limit defaults to 20 with maximum 100, while the direct source says default 50 and range 1–200. Honor valid explicit counts from 1 to 100 without asking again; when size is important use an explicit count, and clarify a request above the shared range before changing it. Omitted selectors may use input {}; report the actual returned page metadata. Do not extend the asset or timeframe enums or add wallet, market, token, event, price, volume, text-search or extra sorting controls.

end_after and end_before are independently optional nonnegative Unix integers, strictly after and before-or-at the market end time respectively. Their seconds/milliseconds unit is not explicit in this reference. Establish the authoritative unit before converting requested dates; if it is unavailable, explain the limitation and clarify how I want to proceed rather than guessing, dropping the boundary or substituting a different range. Clarify ambiguous calendar timezones and validate ordering when both boundaries are provided.

Keep nominal timeframe and nullable ISO start/end timestamps separate; do not derive the market duration or price-measurement rules from their difference or title text. Preserve nullable Up/Down outcome prices on the source 0–1 scale, with no currency, calibrated probability, executable quote, complement or winner calculation. Preserve source status and winning_side independently; null does not mean zero or a loss. Keep token and condition IDs as exact strings and event_slug as metadata without inventing a URL or relationship. Retain source USD-labelled volume/liquidity, zeros and all raw rows, without claiming a range-recalculated volume or current liquidity. An empty page does not prove no matching markets exist everywhere.

Continue only within my requested scope and budget when has_more is true and the returned offset is a nonnegative integer and the page is nonempty. Pass the next offset directly in queryParams as the returned offset plus the number of returned markets; keep all other filters and sort unchanged. If page metadata is missing or cannot advance, report that continuation cannot be determined. No cursor is declared; do not invent one, repeat a nonadvancing page, automatically retry or substitute a different asset, timeframe or status after failure.

Task:
Show a page of Polymarket crypto up/down markets with each coin, both prices, and its listed end time.

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 Crypto Up/Down Markets | BlockRun

Browse Polymarket crypto Up/Down market records. Choose an asset, market timeframe or state if needed, and get a page of contracts to compare.

You receive

Get a page of crypto Up/Down prediction markets, with each question, asset, nominal timeframe, reported status and listed times. Records include separate Up/Down prices and token IDs, a nullable winning side, and reported volume and liquidity. Your Agent can organize the returned records side by side for comparison.

Start with your task

Show a page of Polymarket crypto up/down markets with each coin, both prices, and its listed end time.

What to know

Outcome prices are not underlying crypto spot quotes or a price forecast. Listed status, prices and availability can change; a closed state alone does not confirm the winner, and a page is not a complete current inventory.

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 container for flat asset, timeframe, status, end_after, end_before, sort, limit and offset. No selector is required. Use an explicit common page count of 1–100 when count matters; confirm the end-boundary timestamp unit before conversion.
Nested query object`queryParams.query`	`object`	Optional	Optional nested object retained by the native contract. It is not flattened into the flat controls; put supported controls directly in queryParams.

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
Market records`result.markets`	`array`	One returned page of crypto Up/Down market records. Availability and details vary; this is not a price series or a complete current inventory.
Asset`result.markets[].asset`	`string`	Underlying crypto asset code for the prediction market. Read it as returned; this is not a spot-price quote.
Market question`result.markets[].title`	`string`	Source question or title. Its wording does not independently establish a schedule, status or winner.
Market status`result.markets[].status`	`string`	Market state as reported. A closed status alone does not establish a final winning side.
End time`result.markets[].end_time`	`string`	Source end timestamp in ISO 8601 when provided. It is not the time the Agent fetched the page.
Up outcome price`result.markets[].up_price`	`number`	Up outcome price, described on a 0–1 scale. May be null; no currency, calibrated probability or executable quote is established here.
Image reference`result.markets[].image_url`	`string`	Source image URL when available. It is metadata and does not mean the image has been fetched or verified.
Market timeframe`result.markets[].timeframe`	`string`	Nominal market timeframe. It is not an OHLCV interval or a duration to derive from the start and end timestamps.
Down outcome price`result.markets[].down_price`	`number`	Down outcome price on the source 0–1 scale, or null. Preserve it independently rather than calculating it from the Up price.
Event slug`result.markets[].event_slug`	`string`	Event slug metadata as returned, or null. No event lookup URL or event filter is provided by this field.
Start time`result.markets[].start_time`	`string`	Source ISO 8601 start timestamp when provided. Its role does not establish the market timeframe or a guaranteed measurement interval.
Market slug`result.markets[].market_slug`	`string`	Source identifier for this market, retained as a string. It is not a supported request selector here.
Up token ID`result.markets[].up_token_id`	`string`	Exact token identifier for the Up outcome. Keep the long string intact; it is not a price.
Condition ID`result.markets[].condition_id`	`string`	Market condition identifier as returned. No condition-ID filter is declared for this list.
Winning side`result.markets[].winning_side`	`null`	Source winner label Up or Down, or null if unresolved. Do not infer it from the title, status or outcome prices.
Down token ID`result.markets[].down_token_id`	`string`	Exact identifier for the Down outcome token. Preserve the string separately from the Up identifier.
Reported liquidity (USD)`result.markets[].liquidity_usd`	`number`	Source value labelled liquidity in USD. Zero remains zero; the calculation and available executable depth are not specified.
Reported total volume (USD)`result.markets[].total_volume_usd`	`number`	Source USD-labelled total volume. It is not underlying crypto trading volume, P&L or volume recalculated for the requested end-date bounds.
Page information`result.pagination`	`object`	Offset-based page metadata. This endpoint does not provide an opaque continuation cursor.
Reported page limit`result.pagination.limit`	`number`	Page limit reported by the source. Documents differ on the omitted default and maximum, so read the returned value and use an explicit supported count when needed.
Matching record total`result.pagination.total`	`number`	Source total matching item count, separate from the number of rows on this page. It can change with the dataset.
Current offset`result.pagination.offset`	`number`	Current numeric page offset. The source accepts nonnegative integer offsets, defaulting to 0.
More matching records`result.pagination.has_more`	`boolean`	Whether the source reports more matching items. Further pages use an offset with the same filters and ordering, within the requested scope.

Additional notes

Understanding the market timeframe

A market's timeframe names its crypto Up/Down category, such as 15m or 1h. The returned start and end timestamps do not define that nominal duration: their difference should not be used to reconstruct the category or the underlying price-measurement rules. Keep the title, timeframe and source timestamps separate.

End-date filters apply to the listed end time, not the start time or when you fetched the result. end_after is strictly after the boundary; end_before includes the boundary. The reference calls these nonnegative integers Unix timestamps without stating seconds or milliseconds. Confirm that unit before converting a calendar cutoff; do not substitute a guessed boundary.

Reading prices and resolution

Up and Down prices are outcome prices described on a 0–1 scale. They can be null and are not BTC/USD or another underlying asset's spot quote. This reference does not establish a currency, calibrated probability, an executable quote or a rule that both prices sum to one. Read each as returned.

The winner is separately reported as Up, Down or null if unresolved. A closed status, an elapsed end time or an extreme price does not independently establish the winner. Volume and liquidity retain their source USD labels; the calculation and update cadence are unspecified, and filtering by end date does not make the volume a calculation for that date range.

Choosing a page

Use an explicit count from 1 to 100 when the page size matters: this is shared by the two documented ranges. Their omitted defaults and maximum limits differ, so avoid assuming one fixed default or silently reducing a larger requested count. Pages use a numeric offset, with 0 as the starting default. The matching total can change as the underlying dataset changes; it is distinct from the number of rows you receive.

Read the official crypto Up/Down reference for the source controls and meanings. Use the Toolmu connection guide to send the request from an Agent.

Polymarket Crypto Up/Down Markets | BlockRun

Polymarket Crypto Up/Down Markets | BlockRun

You receive

Start with your task

What to know

Inputs & outputs

Input schema

Result schema

Understanding the market timeframe

Reading prices and resolution

Choosing a page

Ask your AI assistant

Start without extra details

Understand what you see