Data Sources And Analysis
Virae uses a data and analysis layer to support market discovery, event context, search, sports pages, insights, and AI-assisted surfaces.
What this layer does
The analysis layer can:
- ingest events from prediction-market venues
- normalize search and discovery data
- enrich event pages with timelines, sentiment, news, and market context
- support sports game context
- power whale-monitor and leaderboard-style insight views
- cache expensive analysis so the product can stay responsive
Current indexed venue families
Virae's data layer is not limited to one market source.
Current indexed or supported venue families include:
- Polymarket
- Predict.fun
- Kalshi
- Azuro
- Limitless
- Myriad
- Opinion
- PancakeSwap Prediction
- Probable
- SXBet
Venue support can differ by feature. A venue being indexed for discovery does not automatically mean every trading, wallet, or settlement action is supported through Virae.
Event analysis
Event pages can use analysis modules for:
- market timelines
- sentiment summaries
- thesis or preview analysis
- related news
- orderbook and market context
AI-assisted output should be treated as decision support, not as a guarantee of outcome.
Sports context
Sports features can use dedicated NBA and football/soccer context services. These services help game pages and bot flows present more useful match-level information than a generic event list.
Sports context availability depends on the event, upstream data, and cache freshness.
Whale monitor and insights
The insights layer can power:
- whale trade feeds
- whale wallet views
- trader leaderboards
- wallet tags
- AI wallet matching
- insider or large-trader views
These surfaces are intended to help users inspect market activity. They do not prove that copying a wallet or trader will be profitable.
DefiLlama and market tracking
Virae can also use DefiLlama-style protocol tracking for prediction-market category views and ecosystem analysis.
This is separate from a user's trading account state. Protocol-level statistics should not be confused with account balance, order status, or execution history.
X and social analysis
Some analysis services can monitor or process X-related signals, mentions, and account discovery workflows.
These are supporting intelligence systems. They should not be read as official market resolution sources.
Developer rule
When building on analysis output, preserve the distinction between:
- indexed discovery data
- tradable product routes
- AI-generated context
- account-authenticated execution routes
- settlement or resolution truth
Mixing those together is the most common integration mistake.