Our principles
PropSports collects, organizes, verifies, and analyzes factual sports information.
We do not claim ownership of the sporting events we cover. Our contribution is the historical record we assemble, the systems we build to reconcile information, and the software and original intelligence we develop around it.
A score is one observation. Connecting that observation to the correct game, teams, players, historical context, and subsequent corrections is the work of a data business.
We believe independent publishers and data businesses should be judged by their actual collection methods and products—not by their size.
We stand behind our work. Specific concerns deserve specific evidence, and we address them on their merits.
From observation to intelligence
Our methodology separates what was observed, how it fits the historical record, and what our analysis derives from it.
Match the identity
Connect observations to the correct game, competition, teams, and players. Similar names alone are not a reliable identity match.
Keep the context
Organize records by season, competition, and event so a new observation can be understood alongside the history already assembled.
Check the evidence
Use available source records and provenance to investigate conflicting reports. A missing value stays unknown; it is not silently turned into zero.
Separate facts from analysis
A recorded score is an observation. A probability, model signal, or derived rating is analysis. They should not be presented as the same kind of information.
Freshness is part of the meaning
When a route provides observation times, update times, or cache information, those fields help explain how current the underlying record is. The time an API response arrives is not necessarily the time a sporting event occurred or its data changed.
Coverage and update cadence vary by sport, competition, and route. A historical result, a live observation, and a prediction have different uses. Check the route documentation rather than assuming that every field is available in real time.
Corrections deserve evidence
Accuracy includes recognizing when a report changes. Our standard is to investigate discrepancies against the relevant records, preserve the context needed to understand a correction, and distinguish a verified update from an assumption.
Report a data issue or specific concern. Include the game or record identifier, affected URL or API route, date and time, the value you observed, and any supporting evidence. Do not include API keys or account secrets.
What this means for developers
Build around documented identities, available timestamps, stated coverage, and explicit missing values. Keep observed facts distinct from model output in your own interface.
This page explains our principles and methodology. The API data contract, commercial-use documentation, and Terms of Service describe the specific behavior and use of the service.
Published October 15, 2026.