Platform Overview
polyMonitor platform variants, capabilities, and specialized monitoring configurations for Polymarket intelligence, quantitative research, and event-specific coverage.
polyMonitor runs three specialized workspaces from a single codebase, each optimized for different monitoring needs.
Platform Variants
| Variant | URL | Focus |
|---|---|---|
| polyMonitor | polymonitor.club | Market-wide Polymarket intelligence, lifecycle monitoring, chain flow, oracle state, news context, and modular dashboard panels. |
| Quant Workspace | polymonitor.club/quant | Research and backtesting workspace for Polymarket price series, frontend price history, block-close prices, strategy runs, equity curves, and trade exports. |
| World Cup Workspace | polymonitor.club/?workspace=worldcup | FIFA World Cup 2026 monitoring surface with schedule, match detail, host-city map, weather, news, market links, odds context, and tournament intelligence. |
Each workspace keeps the same core data model - market identity, price history, order-book state, OrderFilled flow, oracle resolution, external context, and runtime snapshots - while changing the interface around the task at hand.
polyMonitor
The default workspace is the general Polymarket monitoring surface. It is organized around market discovery, market workspace inspection, lifecycle state, chain-level OrderFilled flow, oracle state, and cross-domain context. The goal is to make a market inspectable as a living system rather than a single probability number.
| Capability | Description |
|---|---|
| Market Lifecycle | Connects Gamma market identity, slug, condition id, outcome tokens, active status, close state, oracle state, settlement, and archival context. |
| Flow & Trading | Surfaces live order book state, sample chain trades, global OrderFilled activity, suspicious flow, whale activity, and liquidity anomalies. |
| Oracle Watch | Tracks UMA request, proposal, dispute, settlement, final outcome, transaction hashes, and matched market context. |
| Context Panels | Adds news, research links, macro, crypto, finance, weather, sports, and time-aware context to explain why market probabilities are moving. |
Quant Workspace
The Quant workspace is the research and backtesting variant. It focuses on reproducible price data, strategy simulation, and inspection of generated trades rather than broad dashboard surveillance.
| Capability | Description |
|---|---|
| Price Sources | Compares frontend price history and block-close price series so researchers can detect source drift and choose the right backtest input. |
| Backtest Runs | Creates strategy runs through /wm-api/quant/backtest-runs and tracks status, parameters, metrics, equity, and trades. |
| Research Output | Shows equity curves, drawdown, performance summaries, trade tables, properties, and exportable CSV/JSON artifacts. |
| Build Monitoring | Exposes price-build status so users can tell whether the quant dataset is fresh, partial, or still catching up. |
World Cup Workspace
The World Cup workspace is an event-specific variant for FIFA World Cup 2026. It treats the tournament as a monitoring surface where schedule, venues, teams, weather, news, odds, and Polymarket markets all affect interpretation.
| Capability | Description |
|---|---|
| Schedule & Match Detail | Loads the 2026 fixture structure, match metadata, stage/group labels, selected-match detail, and linked market context. |
| Host-city Map | Uses a World Cup map workspace for city-level monitoring, venue context, regional risk, and match-linked inspection. |
| Weather & Venue Context | Surfaces host-city weather and operational context that can matter for travel, match conditions, and related prediction markets. |
| Market Intelligence | Connects World Cup news, odds references, Polymarket market links, roster/team context, and runtime intelligence feeds. |
Shared Stack
All variants share the same serving philosophy. Expensive collection and enrichment run outside the browser; the frontend reads normalized endpoints through /wm-api/; responses should expose fresh, cached, stale, empty, or degraded states instead of hiding missing data.
This keeps the platform extensible. A new vertical workspace can reuse the same market identity, OrderFilled, oracle, snapshot, and runtime API layers while changing only the interface and panel composition.