# Polymarket tools are stale and unactionable
> Source report: https://gapforapp.com/reports/polymarket-tools-are-stale-and-unactionable

## 1. What we're building
A live Polymarket intelligence layer: real-time market and wallet monitoring, cross-venue divergence alerts, category-specific trader scoring, and AI summaries grounded in current order books with explicit action ranking.

**Working name:** LivePolymarket Edge
**Tagline:** Real-time order book intelligence, divergence alerts, and grounded action ranking.
**Main goal:** Make traders consistently able to act on live mispricings using grounded, ranked recommendations.
**Target users:** Active Polymarket traders and day traders who need fast, evidence-based decisions using live order books and cross-venue divergence.

**Main user result:** A user sees a live Polymarket contract state and immediately understands whether cross-venue divergence justifies action.
**5-minute outcome:** Create one divergence or price-move alert, then open the Market Inspection panel to see grounded order book context and ranked next steps.
**What we solve first:** Replace stale tooling with websocket-updated inspection + divergence alerts + grounded action ranking for the single most important decision loop.
**Out of scope for MVP:**
- Automated trade execution or copying trades
- Advanced portfolio optimization across many wallets
- Full multi-market portfolio backtesting

## 2. Why this is worth building
- Verdict: **LOW** (55/100)
- The complaint is repeated across many independent threads and takes a consistent shape: users cannot turn Polymarket data into a timely, trustworthy decision workflow. They repeatedly ask for live data, better ranking/prioritization, cross-platform comparison, and wallet/trader filtering because raw dashboards and generic AI are not enough. The problem is not merely UX polish; it directly affects trading outcomes through latency, stale data, and misleading signals. That makes this a strong, persistent, product-level pain point.

**Current pain:** Polymarket-native tooling doesn’t provide cross-market context, real-time alerts, or decision support; users still rely on third-party analysis. General LLM tools and scraping bots are described as stale or hallucination-prone because they aren’t grounded in live order books.
**Current workaround:** Traders manually check markets, then manually compare with sportsbooks elsewhere and interpret signals without a consistent, live divergence workflow.
**Why existing tools fail:** Existing tools focus on browsing or partial signals; they miss the live-edge loop of websocket updates, divergence detection, and grounded action ranking based on the current order book state.

## 3. Must-have capabilities
### 3.1 Live market inspection panel (question, resolution criteria, order book, last trade, liquidity, close date)
**Why:** Users need a single, non-stale view of the full market state to base decisions on.
**Evidence:** post #7964 — *"Pulls the market’s question, resolution criteria, current order book"*

### 3.2 Websocket-based real-time updates (no minute polling for critical data)
**Why:** Staleness is a core complaint; real-time push is explicitly called out as the fix.
**Evidence:** post #8097 — *"real-time websocket push instead of minute polling"*

### 3.3 Configurable price-movement alerts per contract (threshold/volatility spike)
**Why:** Users want alerts tied to actionable movements rather than passive dashboards.
**Evidence:** post #8137 — *"alert system for price movements"*

### 3.4 Cross-market comparison view (overlay Polymarket vs adjacent venues)
**Why:** Polymarket native tooling is described as insufficient; users rely on third-party comparisons.
**Evidence:** post #8137 — *"cross-market comparison"*

### 3.5 Divergence tracker: prediction-market vs sportsbook implied probabilities
**Why:** A specific “divergence tracker” and sportsbook spread alerts are repeatedly demanded.
**Evidence:** post #7902 — *"The divergence tracker, which flags gaps between prediction market contracts"*

### 3.6 AI summaries grounded in live order books + explicit action ranking
**Why:** General LLM tools are flagged as stale/hallucination-prone; summaries must be grounded and ranked.

### 3.7 Trader scoring by category (feeds ranking + alert prioritization)
**Why:** Users need guidance on which markets to trust/act on; scoring reduces manual filtering noise.

### 3.8 Wallet tracking with real-time monitoring and “follow-up” decision support
**Why:** Competitors are largely non-actionable; users need monitoring and reaction mechanics, not just signals.

## 4. Use cases & user stories
A web SaaS dashboard that shows one-click live Market Inspection (question, resolution criteria, order book, last trade, liquidity, close date) using websocket push. It detects prediction-market vs sportsbook implied-probability divergence and produces grounded AI summaries with explicit next-step ranking based on the current live inspection data.

### Use cases
**4.1 React to divergence before the market prices it in**
A trader opens the divergence tracker for a live Polymarket contract and instantly sees that sportsbook-implied probabilities are drifting away from the prediction-market price. The system overlays cross-venue context, highlights the spread magnitude, and triggers an alert when the spread exceeds the user’s threshold. The trader then clicks the AI summary, which is grounded in the current order book and produces an explicit action ranking (e.g., “consider buy-side liquidity vs. wait”).

**4.2 Follow a tracked wallet position change with timely decision support**
At market open, a user has several wallets tracked (whales or their strategy operators). When a wallet opens or changes a position, the dashboard updates immediately via websocket push and prioritizes that contract in the alert queue based on market category scoring and order-book context. Instead of copying blindly, the user checks the grounded inspection panel (resolution criteria, close date, liquidity) and the ranked AI action suggestion before placing a trade.

### User stories
- **As a Active Polymarket trader**, I want cross-market divergence alerts when sportsbook implied probabilities drift from the Polymarket contract price, *so that* I can act on mispricings quickly with evidence rather than guessing or relying on stale tools
- **As a Retail day trader**, I want real-time price movement alerts and an order-book-grounded summary that ranks the action, *so that* I don’t miss fast moves and I’m not exposed to hallucinated or outdated analysis

## 5. Pages & form factor
**Form factor:** Web SaaS dashboard with optional Chrome extension companion
**Why:** A web dashboard lets us centralize live order-book/wallet intelligence, cross-market overlays, and ranked actions in one place. It also avoids browser-context fragility while we build reliable websocket-driven data plumbing; a later companion can surface deep links and quick actions.

### Pages
**5.1 Dashboard**
Shows what to watch right now: hot contracts, active divergence alerts, and wallet follow-ups.
Key elements:
- Hot contracts list (ranked)
- Active alerts feed (price moves + divergence)
- Wallet monitoring status (connected accounts)
- Cross-market divergence snapshot panel
- Live websocket health indicator

**5.2 Market Inspection**
Single-pane deep dive for one contract: question, resolution criteria, order book, last trade, liquidity, and close date.
Key elements:
- Market identity header (question + resolution criteria)
- Close date + key timestamps
- Order book ladder + liquidity summary
- Last trade + micro-price movement
- Real-time update status (no polling)

**5.3 Cross-Market Comparison**
Overlay Polymarket vs adjacent venues and visualize divergences to guide action.
Key elements:
- Contract mapping selector (Polymarket ↔ adjacent)
- Side-by-side implied probability chart
- Spread and divergence meter
- Event-alignment notes (e.g., same underlying outcome)
- One-click “Create alert” from divergence view

**5.4 Divergence Tracker**
Prediction-market vs sportsbook implied probabilities gap detection with threshold-based surfacing.
Key elements:
- Divergence table (contract, spread, direction)
- Implied probability sources badges
- Threshold controls (spread/percentile)
- Timeline view of spread changes
- Action recommendation column

**5.5 Alerts & Triggers**
Configure and manage alert rules for price moves and divergence events.
Key elements:
- Alert rule builder (contract, condition, threshold)
- Volatility spike detection toggles
- Cross-market divergence alert settings
- Delivery channels (in-app, email/push)
- Rule enable/disable and test button

**5.6 Wallet Monitor**
Real-time wallet tracking plus “follow-up” decision support when positions or balances change.
Key elements:
- Connected wallets list + sync time
- Position/holdings changes stream
- Recent orders/settlement events
- Follow-up recommendations per wallet
- Connection troubleshooting panel

**5.7 AI Action Board**
Grounded summaries plus explicit next-step ranking using live order books and current divergence.
Key elements:
- Contract action cards (ranked)
- Grounding panel (what data was used: book + last trade + liquidity)
- Explanation trace (why this action, what changed)
- “Create alert” shortcuts from recommendations
- Confidence/conditions-to-recheck

**5.8 Integration Settings**
Connect data sources (Polymarket, sportsbooks) and tune websocket subscriptions, alerts, and thresholds.
Key elements:
- API/websocket endpoints status
- Source mapping config (book sources, odds sources)
- Subscription health and rate limit warnings
- Notification preferences
- Data refresh / reconnect controls

### Key functions
- **Open Market Inspection** *[on: Dashboard]*
  - Trigger: User clicks a contract row from Hot contracts list
  - Opens a live Market Inspection panel with question/resolution criteria and real-time book/trade/liquidity/close date.
- **Inspect Live Order Book** *[on: Market Inspection]*
  - Trigger: User views an open contract; websocket stream starts
  - Renders order book and last trade that update via websocket (not minute polling) for tactical decision making.
- **Create Price-Move Alert** *[on: Alerts & Triggers]*
  - Trigger: User clicks “Create alert” in Market Inspection or AI Action Board
  - Creates a threshold/volatility spike alert tied to the current contract and updates in real time.
- **Create Divergence Alert** *[on: Divergence Tracker]*
  - Trigger: User clicks “Alert me when spread exceeds” on a divergence row
  - Creates an alert when prediction-market vs sportsbook implied probability spreads exceed the configured threshold.
- **Overlay Cross-Market Implied Probabilities** *[on: Cross-Market Comparison]*
  - Trigger: User selects a Polymarket contract and mapped adjacent venue
  - Shows overlays of implied probability and highlights where the markets disagree.
- **Rank Next Actions** *[on: AI Action Board]*
  - Trigger: User opens a contract category or receives a triggered alert
  - Generates an explicit ordered list of what to do next using live order book context + divergence signals.
- **Generate Grounded Market Summary** *[on: Market Inspection]*
  - Trigger: User clicks “Summarize” after reviewing the live book
  - Produces a summary grounded in the inspection panel’s live data (order book, last trade, liquidity, close date).
- **Follow Up on Wallet Change** *[on: Wallet Monitor]*
  - Trigger: Websocket event: new order/position/balance change for a tracked wallet
  - Suggests next decisions (e.g., adjust exposure, check divergence) based on the wallet’s live status.
- **Test Alert Rule** *[on: Alerts & Triggers]*
  - Trigger: User clicks “Test” on an unsent rule
  - Runs a one-shot evaluation against the current live contract state to confirm triggers behave as expected.

### UX details
- **Market Inspection panel:** Place question + resolution criteria in the same header as the live book so users don’t context-switch during execution.
- **Live data refresh strategy:** Use websocket updates for critical trading fields (order book + last trade) and avoid minute polling behaviors entirely for those components.
- **Divergence alerting:** Default divergence thresholds are based on spread magnitude to ensure alerts correspond to economically meaningful gaps, not noise.
- **Cross-market comparison view:** Highlight divergences with directional cues (which venue implies higher probability) rather than only showing absolute differences.
- **Alert rule builder:** Support both fixed thresholds and volatility-spike triggers as first-class options in the same rule builder.
- **AI Action Board ranking:** Show a “why now” grounding snippet that references the same live fields visible in Market Inspection (book/trade/liquidity/close date).
- **Wallet Monitor:** When wallet status changes, automatically surface relevant divergence and price-move checks in the follow-up recommendation area.

## 6. Monetization
**Model:** subscription

### Suggested pricing tiers
**Starter** — $19/month — *Solo trader, just getting started*
- Watch up to 5 markets/alerts
- Market inspection + grounded AI summaries (read-only)
- Email alerts for price movement thresholds

**Pro** — $49/month — *Active trader, multiple positions*
- Unlimited markets/alerts
- Cross-venue divergence + sportsbook spread alerts
- Websocket real-time updates and prioritized action ranking
- Priority alert delivery (email + Discord)

**Team** — $199/month — *Fund / multi-trader team*
- 5 team seats + shared alert rules
- API access for divergence/market signals (read endpoints)
- White-labeling limited to dashboard branding
- Priority support + onboarding

## 7. Competitors to beat
| Name | Why it fails | Price | Mentions |
|---|---|---|---|
| Copy trading tools and risk settings | They only work when the copied trader’s edge is not speed-dependent; users report copying arrives too late and small adverse fills erase returns. | - | - |
| Polymarket native interface | It does not provide cross-market comparison, external data integration, or alerts, and users still rely on third-party tooling for analysis. | free / native product | - |
| Generic sentiment scrapers / volume-based bots | They lag price movement and mostly chase after the contract has already moved. | Unspecified | - |
| ChatGPT / Claude / Gemini for trading analysis | General-purpose LLMs are described as stale, hallucination-prone, and not grounded in live order book data. | unspecified | - |
| Polymarket Whales (browser extension) | Useful as a signal, but users say they were just copying trades without thesis and got burned. | Free/unspecified | - |
| Polymarket Recovery Tool | It errors out for some cases, returning a proxy-wallet deployment failure instead of completing recovery. | Unspecified | - |
| Polymarket US API | Docs and production behavior mismatch; parameter names and active-market queries do not behave as advertised. | not stated | - |
| PillarLabAI | Presented as a specialized alternative, but users still frame it as solving selected gaps rather than eliminating the broader problem of noise and delayed action. | subscription-based / not stated | - |

## 8. Distribution
- reddit
- x_twitter
- discord
- seo
- Top subreddits to launch in: r/techsupport, r/Polymarket, r/Daytrading, r/cryptocurrency, r/help, r/CryptoMarkets, r/sportsbook, r/web3, r/options, r/PillarLab

## 9. Users & roles
**Primary persona:** Active Polymarket trader
**Secondary personas:**
- Retail day trader

**Roles:**
- **Subscriber** — Create alert rules, view live contract inspections, and receive divergence/wallet notifications.

## 10. Data model & integrations
- (no data model extracted)

## 11. States
**Empty state:** Dashboard shows no watched contracts or alerts yet, with a prompt to create the first alert rule.
**Error state:** A banner indicates which feed failed (Polymarket websocket or sportsbook odds) and shows the last known timestamp.

## 12. Analytics & metrics
- (not synthesized for this report)

## 13. Risks & open questions
- (no risks/questions extracted)

## 14. Post-launch
- See https://gapforapp.com/reports/polymarket-tools-are-stale-and-unactionable for DM-able hot leads (workarounds × buying intent).
- See https://gapforapp.com/reports/polymarket-tools-are-stale-and-unactionable for verified key quotes you can use as landing copy.

## 15. Suggested build order (3-week MVP cut)
- Week 1: §3 must-haves + §5 page 1.
- Week 2: §5 remaining pages + auth/persistence if needed.
- Week 3: §6 monetization wiring + analytics + launch checklist.

## 16. Setup hints (your stack overrides these)
- `pnpm create next-app . --typescript --tailwind --app`
- `npx shadcn@latest init`
- The agent SHOULD ask the user before committing to a stack.

## 17. How to use this file
You're an AI coding agent reading this in AGENTS.md. Your job:
1. Confirm the stack with the user (their preferences override this file).
2. Scaffold an MVP covering §3 + §5 page-1 first.
3. Defer §6 (monetization) and §14 (post-launch) until §3 ships and works.
4. Re-fetch the live PRD anytime via:
   curl https://painfinder-api.fly.dev/api/public/reports/polymarket-tools-are-stale-and-unactionable/export.json?size=compact

## 18. Verbatim key quotes (top 10)
> "free dashboards that show you data but don't tell you what it MEANS."  
> — post #7901

> "Most tools do not do this. Most tools just show you what is already on the Polymarket interface, dressed up slightly differently."  
> — post #7899

> "tracking whales isn't the same thing as catching insiders."  
> — post #7921

> "prioritization is the real gap."  
> — post #7908

> "Most tools I tested failed on at least two of these."  
> — post #8136

> "I’m looking for something that shows win rates by trader or category breakdown."  
> — post #7910

> "Live API data, not cached prices"  
> — post #8136

> "The problem was not the model. The problem was that ChatGPT had no idea what the contract was actually trading at when I asked."  
> — post #8219

## 19. Manual workarounds users cobble together (top 15)
- (none extracted yet — see live report)

## 20. "I would pay for…" quotes (top 10)
- (none extracted yet — see live report)

## 21. Hot leads summary
- (none extracted yet — see live report)

## 22. Full competitor list (top 10)
| Name | Why it fails | Price | Mentions |
|---|---|---|---|
| Copy trading tools and risk settings | They only work when the copied trader’s edge is not speed-dependent; users report copying arrives too late and small adverse fills erase returns. | - | - |
| Polymarket native interface | It does not provide cross-market comparison, external data integration, or alerts, and users still rely on third-party tooling for analysis. | free / native product | - |
| Generic sentiment scrapers / volume-based bots | They lag price movement and mostly chase after the contract has already moved. | Unspecified | - |
| ChatGPT / Claude / Gemini for trading analysis | General-purpose LLMs are described as stale, hallucination-prone, and not grounded in live order book data. | unspecified | - |
| Polymarket Whales (browser extension) | Useful as a signal, but users say they were just copying trades without thesis and got burned. | Free/unspecified | - |
| Polymarket Recovery Tool | It errors out for some cases, returning a proxy-wallet deployment failure instead of completing recovery. | Unspecified | - |
| Polymarket US API | Docs and production behavior mismatch; parameter names and active-market queries do not behave as advertised. | not stated | - |
| PillarLabAI | Presented as a specialized alternative, but users still frame it as solving selected gaps rather than eliminating the broader problem of noise and delayed action. | subscription-based / not stated | - |
| Synthesis.trade | Helps with discovery, but the broader problem still requires manual interpretation and special filtering rules. | Not mentioned | - |
| PolySift | Helps compare market families, but it is a narrow solution rather than a full live-edge workflow. | free | - |

## 23. Where this conversation lives (top subreddits)
- r/techsupport (51 posts)
- r/Polymarket (45 posts)
- r/Daytrading (40 posts)
- r/cryptocurrency (37 posts)
- r/help (28 posts)
- r/CryptoMarkets (20 posts)
- r/sportsbook (17 posts)
- r/web3 (15 posts)
- r/options (15 posts)
- r/PillarLab (13 posts)