A workflow you can inspect
There is no universal hidden model panel that every NickAI prediction-market workflow automatically uses. Each workflow has configured nodes, connections, and rules. A research template can collect data and send a report without placing an order.
Open the first-party Prediction Market Edge Report to inspect one published design. It combines market discovery, screening, news context, specialist analysis, and a report. The shared template is the source for its configuration, not evidence of investment results.
From source to report
- Discover markets. Data nodes collect actual markets and identifiers from the configured venues. Review the returned results and the requested filters.
- Prepare inputs. Function and data-processing stages select records, align fields, and gather context for analysis. Inspect empty results and mismatched identifiers.
- Analyze. Model nodes receive the selected input and the prompt chosen for that stage. Inspect the provider, model, source references, and response.
- Deliver and record. A notification step sends the assembled report. Check the execution result and retain source records so the interpretation remains reviewable.
The Polymarket data reference defines the normalized output. The upstream market-discovery documentation explains the source API. Neither a model-written title nor an unverified link should replace a returned market identifier.
What an example output means
A report can show the market question, current source values, observation time, supporting links, and a separate interpretation. Treat that as a review format. This page does not present a hypothetical fill, forecast, or account action as something the workflow actually executed.
Where execution belongs
The Polymarket Order node is a separate action with authentication and order settings. Inspect every action in a workflow before enabling it. A report-only template does not become an execution bot simply because it discusses a market.
Use the read-only walkthrough for a first test. Review any later action branch independently, including order status, rejected requests, and the account's current venue permissions.
Correction to the earlier description
An earlier version described fixed models, calibration weights, and a hypothetical execution as if they represented a universal NickAI agent. Those claims have been replaced with an inspectable workflow example. Model selection, prompts, conditions, and actions belong to the configuration you actually use.