Start with market discovery

A monitor needs real market identifiers before it can retrieve a book or explain a price. Polymarket's market-discovery documentation describes the Gamma data path. NickAI's Polymarket data node wraps discovery and market-data modes so the results can feed the next workflow step.

For the raw endpoints, identifier mapping and authentication boundary, read the Polymarket API guide. For a second venue, the Kalshi API tutorial builds a read-only market monitor.

Configure a read-only first run

  1. Create an inactive workflow with Start, Polymarket Data, a report-formatting step, and a notification destination.
  2. Choose Browse mode, active status, and a small result limit. You can use Search instead when you have a specific topic.
  3. Run the data node and inspect the markets array. Record the question, event ID, condition ID, outcome token IDs, and source timestamp for the result you select.
  4. Add a Snapshot data node for the selected market. Pass a condition ID when you need the YES and NO summary; inspect the returned bid, ask, and spread fields.
  5. Format a report using the source values. Include the market link and timestamp, and identify missing fields. Keep the workflow free of order nodes during this test.

A runnable public-data request

To inspect the upstream response directly, fetch one active market from Gamma. The same read can be made with curl 'https://gamma-api.polymarket.com/markets?active=true&closed=false&limit=1'. Results change over time, so use the identifiers returned by your request.

The upstream response and NickAI's normalized output have different shapes. In NickAI discovery output, use markets[0].conditionId for the selected condition and markets[0].tokenIds.yes for the YES token. Inspect the actual output before wiring a field. An empty array needs a no-results branch.

A concrete reporting example

The Polymarket Signal Scanner matches news to markets and sends a briefing. Its page shows the node graph and the job of each stage. Use the published design as a draft specification, then inspect the generated connections and your chosen notification destination.

A suggested report includes the market question, source URL, observation time, quoted prices, and a separate interpretation. This is a report format to implement, not a fabricated execution result. Keep the data-node output alongside the report so a reviewer can trace its claims.

Review execution as a separate path

The data node reads information. The Polymarket Order node is a separate authenticated action. Inspect account permissions, outcome token selection, order settings, fee information, and result handling before adding it. Available access and venue rules must be checked for the actual account.

Do not treat a model estimate as a verified mispricing, or an API acknowledgement as a completed fill. Record the order state explicitly and handle rejected or incomplete actions. A paper test is useful only when the chosen environment supports the assets and behavior being tested; an equities simulator is not a Polymarket execution test.