PredictionToolkit
What is Polynode?
Combine wallet, token, side, size, status and market-slug filters instead of consuming the complete event stream. Enriched records keep question, outcomes, volume and liquidity close to the activity. Dedicated surfaces add books, Chainlink references and oracle proposals, disputes and settlement. SDK and CLI resources provide integration examples. The product notice says existing APIs and documentation remain available after Polynode joined Agg.
Capacity planning needs more than a monthly request number. Keys share the account’s limits and meters; reconnecting or rotating keys does not reset them. Heavy trade history consumes its own shared bucket as well as the ordinary REST allowance. Early detected events must be tracked through later confirmation, and when snapshot_count and since are both supplied, since takes precedence.
Who it is for
- Developers building wallet alerts or copy-trading infrastructure.
- Teams combining filtered streams with historical backfills.
- Researchers joining settlements, books and market metadata.
Features and coverage
- Filtered event subscriptions
Combine wallet, token, side, minimum size, status and market filters on the server.
- Detection and confirmation
Receive detected pre-confirmation activity and process subsequent status updates separately from the initial event.
- Metadata and wallet history
Read enriched question, slug, outcomes, volume and liquidity plus public wallet activity, using batch endpoints where appropriate.
- Archives and candles
Query settlement archives and OHLCV within supported windows. Heavy trade-history queries also consume their shared heavy bucket.
- Books, references and oracle events
Use order-book depth, Chainlink reference prices and resolution events including proposals, disputes and settlement.
- Client resources and usage
Use SDK/CLI examples and monitor request counts and 2 separate WebSocket transfer meters at account level.
Workflows with Polynode
Build wallet monitoring
Start a filtered subscription, inspect its initial snapshot and retain identifiers and subsequent confirmations instead of treating detection as final.
Backfill a monitor
Query bounded historical trade windows, connect the live stream and deduplicate overlapping records.
Budget separate constraints
Account for ordinary REST, heavy history, connections and transferred bytes individually. Multiple keys share these account-level constraints.
Pricing and total cost
Plans distinguish live-stream capacity from paid standard V3 REST data. Free keys do not unlock standard V3 REST through a visible monthly meter or capacity package.
Free
US$0
- 1 event and 1 order-book WebSocket connection.
- 1-hour daily WebSocket session.
- 1 API key; standard V3 REST data unavailable.
Starter
US$50/month
- 10 event and 10 order-book WebSocket connections.
- 1000 standard V3 REST requests/minute.
- 3 API keys; unlimited session duration.
Growth
US$200/month
- 50 event and 50 order-book connections.
- 2000 standard REST requests/minute; heavy-history bucket 1500/minute.
- 10 API keys.
Enterprise
US$750/month
- Dedicated infrastructure by arrangement.
- Default standard REST limit 4000/minute.
- 25 API keys.
Fees and usage costs
- An optional US$20 package adds 10000000 API requests or 100 GB to a selected transfer meter.
- Packages last 90 days and do not unlock paid endpoints or raise instantaneous limits.
Access: Monthly meters are visible, but the guide says monthly enforcement is not active yet. Request, connection and free-session limits remain active.
Getting started
Before you start: Detection and confirmed settlement are distinct states.
- Choose live events, order-book data or historical REST.
- Create an API key through the official account flow.
- Start a filtered subscription for a wallet or market.
- Retain event IDs and process confirmation/status changes.
- Add bounded historical backfills.
- Monitor account rate headers and usage, including limits shared by all keys.
Detected pre-confirmation activity is not confirmed settlement.
Useful links
What to check
- Detection and confirmed settlement are distinct states.
- Free keys cannot access standard V3 REST data merely by adding capacity.
- Heavy history uses its shared bucket and the standard REST allowance.
- If snapshot_count and since are both provided, since takes precedence.
- Additional keys, reconnects and key rotation do not reset account usage.
A closer look
Ratings & reviews
User reviews 0
The main score switches to user ratings after 5 published reviews.
A specific example helps the next person choose the right tool.
Related tools
Browse category
Compare stock-related prediction activity with social and news sentiment using shared API access.
- Access API · CLI
A normalized prediction-market data service for dashboards, historical replay and AI clients.
- Access API · MCP
Replay short crypto rounds against recorded liquidity and keep Data API and AI-backtest entitlements separate.
- Access Web · API
Frequently asked questions about Polynode
Can subscriptions be filtered server-side?
Yes. Combine wallet, token, market-slug and size filters, among the documented options.
Does Free include standard V3 historical REST?
No. The rate-limit guide requires a paid plan for standard V3 REST data.
Do API keys have separate quotas?
No. Limits and monthly meters are shared by the account. Reconnecting or rotating keys does not reset them.
Will a package increase requests per minute?
No. It adds capacity to the selected monthly meter, without increasing instantaneous limits or opening paid endpoints.
Did joining Agg remove the API?
The product notice says existing APIs and documentation remain available.