# BlockRun UMA Oracle Status & Event Timeline for Polymarket Market

> BlockRun UMA Oracle Status & Event Timeline for Polymarket Market is a paid API for AI agents from blockrun.ai, paid per call via x402, $0.0085/call, status unknown (last checked 2026-09-15).

Returns the current UMA oracle status and full event timeline for a single Polymarket prediction market identified by its hash

## Facts

- Endpoint: GET https://blockrun.ai/api/v1/pm/polymarket/uma/market/:hash
- Price: $0.0085/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/blockrun-uma-oracle-status-event-timeline-for-polymarket-market-d36157ab
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_4SDQx-P87rluT94_3xVr0

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability blockrun-uma-oracle-status-event-timeline-for-polymarket-market-d36157ab
```

Example prompt: What's the current UMA oracle status and event timeline for the Polymarket market with hash 0xabc123def456? I want to know if it's been disputed or resolved.

## When to prefer this

Use this endpoint when you need to inspect the UMA dispute and resolution oracle lifecycle for a specific Polymarket prediction market, especially when monitoring whether a market outcome is being challenged, resolved, or is pending. Prefer this over general market endpoints when you specifically need oracle-layer event data rather than trading or volume data.

## Known failure modes

- Invalid or non-existent market hash returns an empty or error response
- Market hash not yet indexed by the oracle returns no data
- Payment failure (402) if USDC payment header is missing or insufficient
- Malformed hash parameter causes a 400-level error
- Oracle data may be delayed if on-chain events have not yet been processed

## How this service works

Get current UMA oracle status and event timeline for a single market

## Output

Returns a data object containing the current UMA oracle status (e.g. pending, resolved, disputed) and a chronological timeline of oracle events associated with the specified Polymarket market hash.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "input": {
   "type": "object",
   "properties": {
    "query": {
     "type": "object",
     "required": [],
     "properties": {}
    }
   }
  },
  "output": {
   "type": "object",
   "properties": {
    "example": {
     "type": "object",
     "properties": {
      "data": {
       "type": "object"
      }
     }
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/blockrun-uma-oracle-status-event-timeline-for-polymarket-market-d36157ab/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from blockrun.ai](https://www.zero.xyz/host/blockrun.ai/llms.txt)