01
Know what is covered
Published competitions, seasons and capabilities are visible before integration. Unsupported coverage is not presented as available.
Data integrity
Clean, current data you can verify.
SportsFoundry keeps coverage, freshness and quality evidence visible so you can decide whether the data fits your product before you depend on it.
What you can expect
Simple at the surface. Evidence underneath.
Start with the things that matter to your product: what is covered, how current it is and whether the API is consistent to build against.
02
See how current it is
Where SportsFoundry publishes freshness evidence, it appears beside the coverage so you can judge whether the data is current enough for your use case.
03
Build on one consistent model
Fixtures, results, teams and competitions use the same SportsFoundry contract, so your integration does not change with each underlying source.
Inspect the product
Trust starts with something you can check.
You do not need to understand the internal data pipeline to evaluate SportsFoundry. Start with the live customer surfaces and open the methodology only when you need the detail.
Live explorerChoose published data and see its freshness, reliability evidence and corresponding customer API route.
Coverage & freshnessSee the competitions, scopes and capabilities SportsFoundry currently publishes.
API contractInspect the developer contract and response structure when you are ready to integrate.
Methodology
Need to understand how the evidence works?
The customer journey does not depend on this detail. It is here for teams that need to inspect how SportsFoundry qualifies, reconciles and publishes data.
Open the data integrity methodology
Source evidence exists
A source response is retained with timing and provenance context so SportsFoundry can explain what it received.
Usable for a customer need
A route must prove it can satisfy the intended competition and capability before it is presented as supported.
A conflict has a decision
When qualified sources disagree, the canonical outcome can be selected explicitly while the competing observations remain retained.
Visible through the contract
Customers receive the canonical state together with the coverage and freshness signals SportsFoundry can substantiate.
01 · Observation & provenance
Keep the source observation.
SportsFoundry retains source observations with provenance and timing context. Normalisation creates the canonical model without rewriting the evidence that arrived from a provider.
RuleA canonical value should remain explainable from retained observations.
02 · Qualification & freshness
Support and currentness are both explicit.
A reachable endpoint is not enough. Coverage is presented as supported only after qualification, and freshness is shown wherever the public contract contains trustworthy evidence.
RuleNo persisted qualification evidence means no green coverage claim.
03 · Reconciliation & fallback
Disagreement is handled deliberately.
When qualified sources disagree, SportsFoundry retains the competing observations and records the selected canonical outcome. A fallback route only supports resilience when it has been qualified for the same customer need.
RulePrefer an explicit degraded state to an unsupported claim of continuity.
04 · Corrections
The canonical state can change when better evidence arrives.
A later qualified observation or reconciliation decision can update the canonical state while the earlier evidence remains available for audit. Customer applications should tolerate delayed observations and temporarily unavailable fields.
1. RetainKeep each qualified source observation and its provenance.
2. CompareIdentify fields and states that materially disagree.
3. DecideApply reconciliation policy or record a material human decision with audit context.
4. PublishExpose the resulting canonical state while retaining the observations behind it.
Coverage remains the source of truth: the methodology does not turn an unsupported competition or capability into supported data.