Interface preview
Analytics dashboard
This is the workspace SportsWager will render once market data providers are connected. Every widget below shows its layout, axes, and the exact fields its feed must supply — and nothing else. No prices, probabilities, volumes, forecasts, or availability reports are displayed, because none are connected.
Dashboard widgets
Coverage
Market overview
- Markets covered
- Venues compared
- Median hold
- Coverage window
Count of tracked markets
Permitted venues in scope
De-vigged overround
Earliest → latest fixture
Expected fields: market_count · venue_count · median_hold · coverage_window
Repricing
Line movement
- 1
- 2
- 3
Expected fields: event · market · open_price · current_price · delta_pts · observed_at
Generated
AI summary
Publication rule
A generated summary is only published when every figure it references comes from a connected source and is cited inline. Until then this widget stays empty rather than writing prose about data the platform does not have.
Expected fields: generated_at · headline · bullets[] · citations[] (required)
Depth
Most active markets
- 1
- 2
- 3
- 4
- 5
Ranking will be ordered by traded volume from permitted venues only, with the venue named on every row.
Expected fields: event · venue · traded_volume · book_depth · share_of_total
Attention
Trending sports
League rows are fixed by the platform. Attention values stay blank until a schedule provider is connected — no ranking is implied by the order shown.
Expected fields: league · fixture_count · measured_attention · observed_at
Conditions
Weather factors
- Temp
- —°F
- Wind
- —mph
- Precip
- —%
Conditions are only shown for outdoor venues, attributed to a named meteorological provider. A pricing effect is displayed only where it has been measured, never asserted.
Expected fields: venue · kickoff · temp_f · wind_mph · precip_chance · forecast_issued_at
Availability
Injury reports
Designations are quoted verbatim from the issuing league or club report. The platform does not classify player health itself.
Expected fields: player · team · official_designation · report_issued_by · issued_at
Schedule
Market calendar
Grid renders the shape of a fixture month. Day cells fill in with event counts once a schedule provider is connected — no dates are highlighted today.
Expected fields: fixture_date · league · event_count · first_market_open
Deltas
Probability explorer
Probability axis
Change distribution
The explorer compares an exchange-implied probability with the de-vigged sportsbook price for the same outcome. Both inputs must be connected before any figure appears.
Expected fields: outcome · probability_from · probability_to · window · venue · observed_at
What each widget is waiting on
Widgets read their state from a single integration registry. When a provider is connected there, the matching widget switches from this preview to sourced values with a provider name and retrieval timestamp — no widget markup needs to change.
- Odds & pricingIntegration Pending
Posted prices across venues, used for implied-probability and hold calculations.
- Schedules & resultsIntegration Pending
Fixtures, start times, and official results for settlement context.
- Prediction market dataIntegration Pending
Event-contract prices, order-book depth, and open interest from permitted venues.
- WeatherIntegration Pending
Venue forecasts used to explain how conditions enter outcome distributions.
- Participation reportsIntegration Pending
Official league availability reports, attributed to the issuing league.
- Flow & positioningIntegration Pending
Ticket-versus-handle splits, only where an operator publishes them.
- Regulatory researchIntegration Pending
Statutes, regulator publications, and dated review notes for each jurisdiction.
- Editorial pipelineIntegration Pending
Published, by-lined analysis with citations and review dates.