On Nimb, every number comes from Polymarket's public APIs. Prices stream live over the CLOB WebSocket, volumes and liquidity refresh every minute from the Gamma API, and the list of markets and holders is rebuilt every 6 hours, with the open map rechecking it every 5 minutes.
Nimb is not affiliated with Polymarket and has no private feed. It reads the same public data anyone can request, and turns it into a map and plain sentences so that reading the market takes seconds, not tabs.
Where does Nimb get its data?
From three Polymarket services, all public and free to query:
- The CLOB (central limit order book): best bid, best ask and last trade for each outcome, pushed over a WebSocket, plus hourly price history.
- The Gamma API: Polymarket's catalogue of events and markets, with titles, tags, end dates, prices, volume over 24 hours, 7 days and 30 days, and order-book liquidity.
- The Data API: individual trades (for money flow) and the largest holders of each outcome, with their entry price and profit and loss.
Polymarket documents these services at docs.polymarket.com. Nimb does not buy data, scrape private pages or use any other venue. Kalshi and other exchanges are not covered.
How fresh is each number?
Nimb updates in three layers, each as fast as its source allows.
| Layer | What it covers | How often |
|---|---|---|
| 1. Live prices | Best bid/ask midpoint and last trade for every outcome on the map, the open market panel and the order ticket | Seconds: pushed by Polymarket's CLOB WebSocket as the book changes |
| 2. Volumes and liquidity | 24H, 7D and 30D volume and order-book liquidity; circle sizes follow | Every 60 s (Gamma API) |
| 3. Markets and holders | Which markets are on the map, their 30-day price history, trades and top holders | Every 6 hours (scheduled build); an open map also re-runs the market selection every 5 minutes |
Layer 3 is the slowest because it is the heaviest: a full build pulls hourly prices, trades and holders for several hundred outcomes and takes about 15 minutes. Between builds, an open map asks Polymarket every 5 minutes which events are trending, re-scores them in your browser with the same formula, and loads details only for markets that just qualified. When a newer build is published, the map offers "New trending markets · Update".
Which API supplies each number?
| Data | API | Cadence |
|---|---|---|
| Current price (midpoint of best bid and ask; last trade if the spread is wider than 10 points) | CLOB WebSocket wss://ws-subscriptions-clob.polymarket.com/ws/market | Live; the panel and ticket redraw at most once a second |
| Volume (24H, 7D, 30D) and order-book liquidity per outcome | Gamma API /markets | 60 s |
| Trending events (candidates for the map) | Gamma API /events, top 300 by 24-hour volume; top 300 by 7-day and 30-day volume | 5 min (24-hour list); 30 min (7-day and 30-day lists) |
| Full universe for the scheduled build | Gamma API /events, top 2,100 by 30-day volume plus top 600 by 24-hour volume | 6 h |
| Hourly price history, last 30 days | CLOB /prices-history | 6 h; on entry for markets that join between builds |
| Trades (money flow) | Data API /v2/trades | 6 h; on entry (most recent 1,000 trades) |
| Top holders, 25 per side, with entry price and P&L | Data API /v2/holders | 6 h; on entry |
| Static pages: /markets, one page per market, the docs | Built from the latest snapshot | 6 h |
The scheduled build starts at 17 minutes past 00:00, 06:00, 12:00 and 18:00 UTC. Holders, trades and price history therefore lag by up to about 6 hours and 15 minutes, while prices and volumes do not.
Why can the market pages be up to 6 hours old?
The map is drawn with JavaScript, and most search crawlers and AI answer engines do not run it. So each build also writes plain HTML pages, one per market, that say the same things in sentences and tables. Those pages are a snapshot: they are only as fresh as the last build. The map itself is not limited this way, because it connects to Polymarket directly once it is open in your browser.
If a build fails, the previous snapshot stays online until the next one succeeds. Always check the timestamp before you read a number from a static page.
How do you know how old a number is?
Every page built from a snapshot carries the line "Data from Polymarket" with the time the data was taken, for example: "Data from Polymarket, updated November 7, 2026 at 13:00 UTC." The markets index adds the build time ("Last build: November 7, 2026, 13:00 UTC"). The snapshot time is the end of the last full hour of price history in that build.
In the app, prices that arrive over the WebSocket replace the snapshot price as soon as they come in; where no live connection is possible (a blocked network or an embedded preview), the map stays on its snapshot. The portfolio view states "Prices as of" with the snapshot time.
Is any data private?
No. Everything Nimb shows is public: market data from Polymarket's APIs, and positions that are recorded on the Polygon blockchain. Holder names are the Polymarket username only when the holder has made it public; otherwise Nimb shows Polymarket's pseudonym or a shortened wallet address.
Nimb has no accounts and asks for no email. When you connect a wallet, Nimb reads that wallet's public positions and asks your wallet to sign orders; it never holds funds or keys. The site counts page views with aggregate, cookie-free analytics.
Why might a number differ from Polymarket's site?
| Difference | Why |
|---|---|
| Price a point or two off | Timing (snapshot versus live), or a wide spread: Nimb shows the midpoint when the spread is 10 points or less, otherwise the last trade. |
| Volume much lower | Polymarket's event page often shows all-time volume; Nimb shows volume over the selected timeframe. |
| Fewer outcomes | Nimb lists up to 5 outcomes per event, those priced 1–99% with the most 7-day volume. Circle size still counts every outcome. |
| Short-window volume | Gamma has no hourly volume, so volume for views shorter than 24H is estimated from trades (see known limitations). |
| Different holder list | Nimb fetches 25 holders per side, nets out wallets that hold both Yes and No in the same market, and hides net positions under $500. |
| Liquidity versus open interest | "Liquidity in the book" is resting orders, not the value of positions held. See volume and open interest. |
If a gap is larger than these explain, Polymarket is the source of record. Changes to sources or cadence are listed in the changelog.
Last reviewed 2026-11-07 · Data from Polymarket · Not financial advice · Nimb is not affiliated with Polymarket.