polynode

Polynode calls itself the fastest real-time Polymarket data API, and its own site backs that with a WebSocket that reports enriched trade data before the chain confirms it, OHLCV candles built from settlement data rather than delayed feeds, and a decoded stream of UMA optimistic oracle events covering proposals, disputes, flags and resets. It also ships a wallet tracking endpoint for any address's positions and history, a historical archive of daily-rotated settlement records, and a charts SDK for building price overlays. None of that is a page where a trader clicks buy or sell.

It sits in the infrastructure category because it hands data to other tools rather than being the tool a trader touches directly. The wallets that route volume through its builder code are thin right now, 3 across the last month, with a buy share of 99% and an average fill of $64 that points to small, active accounts rather than desks moving size. Anyone evaluating it is really evaluating the bots built on top of its feed, not a front end of its own.

A developer reaches Polynode with an API key, generated with a single POST request against its own keys endpoint, then either polls REST routes like its markets listing or opens a WebSocket subscription filtered by wallet, token, side, size range, status or slug, combined in any mix. The quickstart on its site never shows a browser trading screen or an order form, only a terminal, a key and a request.

Where the order itself goes is not Polynode's page to answer: it detects a trade at the server, again when the client receives it, and finally when it confirms on Polygon, but the trading decision and the order submission belong to whatever bot or terminal consumes the feed. The attributed volume and fills behind #177 come from that downstream code routing through Polymarket's own order book with Polynode's builder code attached, not from any execution surface on polynode.dev itself.

Nothing in the evidence describes it holding a wallet, taking a deposit or custodying a position; authentication is an API key, not a signature or a connected wallet. That also means it inherits none of the visible risk controls a trading front end might show, since it was never built to be one.

• Pre-confirmation trade detection

  Streams settlement data seconds before it confirms on-chain, giving a bot built on the feed a head start on reacting to a fill.

• Combined WebSocket filtering

  Filters wallet, token, side, size range, status and slug together in one subscription, replacing client-side filtering logic a bot would otherwise write.

• Decoded oracle resolution stream

  Surfaces UMA optimistic oracle proposals, disputes, flags and resets in real time, useful for spotting resolution risk before a market settles.

• Wallet tracking endpoint

  Returns a chosen wallet's positions, profit and loss and trade pattern history, letting a bot watch a specific trader instead of only a market.

• Historical settlement archive

  Persists daily-rotated settlement records, useful for backtesting a strategy without running a multi-year collector of your own.

Bot developers chasing speed

Settlement data arrives seconds ahead of on-chain confirmation, letting an automated strategy react before a trade is final on the ledger.

Dashboard and terminal builders

Enriched metadata and OHLCV candles remove the need to stitch Polymarket's raw feed together with separate market lookups.

Wallet and copy-trade watchers

The wallet tracking endpoint surfaces a target address's positions and history without scraping the chain by hand.

Traders holding into resolution

Decoded oracle events flag disputes and reset markets in real time, useful for anyone with a position riding on how a market resolves.

Researchers backtesting Polymarket flow

The historical archive of daily-rotated settlement records gives a base for backtesting without building a multi-year collector first.

Polynode's own site names no price. The quickstart hands a key over on a single request and the page never states a tier, a rate limit, or what changes once a bot pulls real volume through it. Polynode publishes no fee schedule, so anyone building on it should ask directly what a sustained integration costs before wiring a live bot to the feed. Polymarket's own trading fee is fixed per market and identical across every builder that routes into it, so it says nothing about what polynode itself charges. Until the operator states a number, the cost of running on this API is whatever a support conversation turns up, not anything printed on the page.

• Detects settlements seconds before they confirm on-chain, giving anything built on the feed a real head start on reacting to a fill.
• Combines wallet, token, side, size, status and slug filters in a single WebSocket subscription, cutting the client-side filtering a bot would otherwise need to write.
• Decodes UMA oracle events including disputes and flags in real time, offering early warning before a market resolves against a position.
• Keeps a daily-rotated historical archive of settlement data, useful for backtesting a strategy instead of collecting years of raw data independently.
• Includes a wallet tracking endpoint that returns a target address's positions and profit and loss without a manual chain lookup.

• Publishes no fee schedule, leaving anyone planning a paid integration to find the real cost through direct contact rather than the page itself.
• Shows 0 fills and $0 in routed volume over the most recent week, a level worth checking before assuming the builder code stays consistently active.
• Draws its attributed volume from a cohort of only 3 wallets over the last month, a narrow base rather than broad adoption.
• Offers no trading interface of its own, so it only fits someone who already has, or is willing to build, a bot or terminal on top of it.

Polynode's own evidence describes an API key, not a wallet connection: nothing on its site claims it holds funds, takes a deposit or custodies a position, since the product hands data outward rather than taking money in. That shifts the exposure toward pricing and reliability rather than custody: no page states a fee schedule, a rate limit or an uptime commitment, so any bot depending on the feed inherits whatever the operator decides later, unannounced. The attributed volume behind #177 currently comes from a small cohort of wallets, worth weighing before treating the builder code as an established, heavily used route into Polymarket.

Polynode reads as an honest infrastructure play rather than a place to route trades directly: fast settlement detection, decoded oracle events and a wallet tracking endpoint are real, documented features, not marketing gloss. What it is not is a finished trading product, and its own evidence never claims otherwise. A developer or quant who wants a data pipeline ahead of on-chain confirmation, and is comfortable building the execution layer themselves, gets real value here. A trader looking for a terminal, a fee they can compare up front, or evidence of an active, established builder code should keep looking, at least at #177 and current activity before committing.

• What is polynode?

  Polynode is a real-time data API for Polymarket that streams enriched trade, OHLCV candle and decoded oracle resolution data seconds ahead of on-chain confirmation, built for developers rather than as a trading front end.

• Is polynode safe to use?

  Its own evidence shows an API key system, not a wallet connection or custody of funds, so the main exposure is an unpublished fee schedule and no stated reliability commitment rather than losing custody of money.

• How much does polynode cost?

  The operator publishes no fee schedule; its quickstart hands out an API key on a single request without naming a tier or rate limit, so a trader has to ask directly what sustained use costs.

• How does polynode work?

  A developer requests an API key, then polls REST endpoints or opens a filtered WebSocket subscription covering wallet, token, side, size and status, receiving settlement data before it confirms on Polygon.

• Does polynode execute trades on Polymarket?

  No order form or execution screen appears in its evidence; it supplies data that other bots and terminals use to decide and place trades, with its builder code attributed once those trades route through.

• What are polynode alternatives?

  This page ranks polynode by #177 against every other builder our index tracks, from execution terminals to rival data providers, so compare its routed volume and activity before choosing a feed.