Skip to content
Blog/How to Integrate the NOX Bot Into Your Trading Routine
2026-04-016 min read
GuideSetupAPI

How to Integrate the NOX Bot Into Your Trading Routine — A Practical Setup Guide

A step-by-step walkthrough for connecting the NOX Weather Alpha Engine to your Polymarket trading workflow: API key activation, reading signals, configuring risk parameters, and building a daily routine around the automated weather trading algorithm.

01

Prerequisites — What You Need Before Starting

Before you can start using the Polymarket Weather Trading Bot, you need a few things in place. None of these are complicated, but skipping any of them will block your setup.

Polymarket account — A funded account on Polymarket with at least $50 USDC deposited. You need this whether you plan to trade manually or let the automated weather trading algorithm execute on your behalf.
Proxy wallet — Export your Polymarket proxy wallet private key from the browser developer tools. The NOX engine uses this for on-chain order signing via the CLOB API.
NOX account — Register at nox.markets/login. You will receive a confirmation email with your dashboard access credentials.
API client — Any HTTP client works: curl, Python requests, or the NOX TypeScript SDK. The API is REST-based with JSON responses.

If you are planning to use automated execution (Professional plan), you will also need a machine that can run a cron job or a long-lived process — a VPS, a Raspberry Pi, or even a laptop that stays on during US market hours. The NOX Weather Alpha Engine handles the signal generation; your job is to relay those signals to Polymarket.

02

Choosing Your Plan — Observer, Trader, Professional

NOX offers three tiers. Your choice depends on whether you want to read signals and trade manually, or fully automate the process.

Observer (Free) — Access to delayed signals (30-minute lag), daily performance summaries, and the public dashboard. Good for evaluating the Prediction Market Weather Bot before committing capital.
Trader ($49/mo) — Real-time signals via the API, full signal history, webhook notifications, and the signal dashboard with filtering. You execute trades yourself based on the signals.
Professional ($149/mo) — Everything in Trader, plus the auto-execution module, custom risk parameter overrides, priority signal delivery, and direct API access to POST /v1/trade/execute for programmatic execution.

Most users start on the Trader plan to get comfortable with how the NOX Weather Alpha Engine generates signals and how those signals translate to actual market positions. Once you trust the edge and want to remove the manual bottleneck, upgrading to Professional takes about five minutes.

03

API Key Activation & Authentication

After selecting your plan, generate an API key from your dashboard at nox.markets/dashboard/keys. Each key is scoped to your plan tier — a Trader key cannot call execution endpoints, and an Observer key receives delayed data.

Base URL: https://nox.markets/v1
Auth header: X-API-Key: your_api_key_here
Rate limit: 60 requests/minute (Trader), 300 requests/minute (Professional)
Format: All responses are JSON with a consistent { "status", "data", "timestamp" } envelope

Test your key immediately after generation:

curl -H "X-API-Key: your_api_key_here" \
https://nox.markets/v1/markets

A successful response returns the list of active weather markets with their current bracket prices. If you get a 401, double-check that you copied the full key string. Keys are 48 characters, base62 encoded. Store your key in an environment variable — never hardcode it into scripts you might share.

04

Reading Trading Signals — What Each Field Means

The core endpoint is GET /v1/signals. This returns the current set of active trading signals generated by the NOX Weather Alpha Engine. Each signal is a recommendation to buy YES or NO tokens on a specific weather bracket.

station — The airport code (e.g., LGA, ORD, MIA) identifying which city's weather market this signal targets.
bracket — The temperature range. Fahrenheit stations use 2°F steps (e.g. "68-70°F"); Celsius stations use 1°C steps (e.g. "20-21°C"). Edge brackets (e.g. "below 50°F", "above 95°F") cover the tails. Each bracket maps to a specific Polymarket condition token.
direction — Either BUY_YES or BUY_NO. YES means the model thinks this bracket is underpriced. NO means it is overpriced.
model_prob — The calibrated probability from the engine (0.0 to 1.0). This is what the model believes the true probability is.
market_price — The current normalized Polymarket price for this bracket.
edge — The difference: model_prob - market_price. Positive edge means underpriced (buy YES), negative means overpriced (buy NO).
kelly_fraction — The recommended position size as a fraction of bankroll, computed using the Kelly criterion.
confidence — A composite score (low / medium / high) reflecting model agreement, forecast horizon, and historical accuracy for this station.

You can filter signals by station, minimum edge, or confidence level using query parameters:GET /v1/signals?station=LGA&min_edge=0.06&confidence=high. This is useful if you only want to trade high-conviction setups on specific markets you know well.

05

Configuring Risk Parameters — Edge Threshold, Kelly Multiplier, Max Position

The default risk parameters are tuned for the median user, but every trader has different capital, risk tolerance, and objectives. Professional plan users can override three critical parameters via the dashboard or the API.

edge_threshold — Minimum edge required to generate a signal. Default: 0.05 (5%). Setting this higher (e.g., 0.08) means fewer trades but higher average edge per trade. Setting it lower (e.g., 0.03) means more trades but thinner edge.
kelly_multiplier — Scales the Kelly fraction. Default: 1.0 (full Kelly). Conservative traders use 0.50 (half-Kelly) to reduce variance. Aggressive traders leave it at 1.0 for maximum geometric growth.
max_position — Maximum percentage of bankroll in any single trade. Default: 0.25 (25%). This is a hard cap that overrides Kelly sizing if the Kelly fraction exceeds it.

These parameters interact with each other. A tight edge threshold with a high Kelly multiplier means you trade rarely but bet large when you do. A loose threshold with a low multiplier means many small bets. The backtest data suggests that the default configuration — 5% edge, full Kelly, 25% max — produces the best risk-adjusted returns across all stations.

If you are running a smaller bankroll (under $500), consider tightening max_position to 0.15 and raising edge_threshold to 0.07. This reduces the number of simultaneous open positions and avoids overexposure to a single weather event.

06

Manual vs. Automated Execution

With signals flowing and risk parameters configured, you have two paths for getting trades onto Polymarket.

Manual execution means you read the signals from the dashboard or API, then place orders yourself on the Polymarket UI. This gives you full control — you can skip signals you disagree with, adjust sizing, or wait for better prices. The downside is latency. Weather markets move, and a signal that had 7% edge at generation might have 3% edge by the time you open the Polymarket tab.

Automated execution (Professional plan) uses the POST /v1/trade/execute endpoint. You send your proxy wallet credentials once during setup, and the engine submits limit orders directly to the Polymarket CLOB on your behalf whenever a signal passes your configured filters.

POST /v1/trade/execute
{
"signal_id": "sig_a1b2c3d4",
"amount_usd": 25.00,
"override_kelly": false
}

When override_kelly is false, the engine uses the Kelly-derived amount and ignores youramount_usd field. Set it to true if you want to specify exact dollar amounts per trade. Either way, the max_position cap is always enforced.

A middle-ground approach works well for users transitioning from manual to automated: set up webhooks at nox.markets/dashboard/webhooks to receive signal notifications via Discord, Telegram, or a custom URL, then decide per-signal whether to execute manually or let the bot handle it.

07

Building a Daily Trading Routine

Weather markets on Polymarket resolve daily, which creates a natural rhythm for your trading workflow. Here is the routine that extracts the most value from the Prediction Market Weather Bot.

06:00 UTC — Morning scan. Check GET /v1/signals for overnight signals. The engine runs every six hours, so by 06:00 you have the first batch based on fresh ECMWF and GFS model runs. Review high-confidence signals for the day ahead.
12:00 UTC — Midday update. Weather models update again. New signals may appear or existing ones may strengthen as the forecast horizon shortens. This is typically when edge is largest because market prices lag the noon model updates.
18:00 UTC — Position review. Check GET /v1/portfolio for your open positions. Evaluate whether any markets have moved against you. The engine does not auto-exit positions, but you can manually sell tokens on Polymarket if your thesis has changed.
00:00 UTC — Settlement check. Markets resolve based on actual observed temperatures. Check the dashboard for P&L attribution: which stations won, which lost, and why. This feedback loop is critical for tuning your parameters over time.

If you are running automated execution, this routine simplifies to a 5-minute daily review. The automated weather trading algorithm handles signal detection, sizing, and order placement. Your job becomes monitoring aggregate performance and adjusting risk parameters when conditions change — such as during seasonal transitions or unusual weather patterns that increase model uncertainty.

08

Monitoring & Adjusting Your Strategy

Running the NOX Weather Alpha Engine is not fully set-and-forget. While the core signal generation is autonomous, your risk parameters and station selection benefit from periodic review.

Track station-level performance. The GET /v1/portfolio endpoint includes per-station P&L breakdowns. If a particular station has been underperforming for two or more weeks, you can exclude it from your signal filters. The engine's overall edge is diversified across 10 stations, but individual station accuracy can fluctuate with seasonal patterns.

Watch your win rate by direction. BUY YES and BUY NO signals have different risk profiles. YES signals win less often but pay more per win. NO signals win frequently with smaller payouts. If your account is in drawdown, temporarily filtering to NO-only signals reduces variance at the cost of lower expected return.

Adjust for bankroll changes. If your bankroll has grown significantly, your effective position sizes may have drifted. Re-evaluate max_position quarterly. A $500 bankroll with 25% max position means $125 per trade. A $5,000 bankroll with the same setting means $1,250 per trade — which may exceed the liquidity available in thinner weather brackets.

Seasonal awareness. The NOX Weather Alpha Engine includes seasonal bias correction, but market behavior itself changes with seasons. Summer temperature distributions are tighter in many cities, which can compress edges. Winter brings more volatility and wider brackets. The engine adapts, but understanding this context helps you interpret the signals you receive.

The dashboard at nox.markets/dashboard provides a rolling 30-day summary of your trades, including total P&L, win rate, average edge captured, and a station heatmap. Review it weekly. If something looks off, the first step is always checking whether your risk parameters still match your current bankroll and risk tolerance.

Ready to start trading with NOX?