Company
Why we are building this
An athlete’s schedule and record are theirs. Today they are scattered across whichever platforms happened to run each event — and that costs the athlete more than it costs anyone else.
The athlete owns the record
A player’s season exists in fragments: a tournament platform has the bracket, a league site has the standings, a scoring app has the box score, and a club app has the practice calendar. None of them was built to hand any of it back, and none of them talks to the others.
We think that is backwards. The games a player played, the results, the table those results produced — that record belongs to the athlete, not to whichever software their club happened to buy. Making it flow is the whole point of an interchange.
Visible enough to be found
The practical consequence of a fragmented record is that talent goes unseen. A player whose achievements live in five systems that do not export is harder to notice than one whose club bought the platform a scout already reads — and that is a bad reason for a door to be closed.
We want an athlete’s results and achievements to be visible outside the walls of the system that recorded them, so that being seen depends less on which product their club purchased.
- Today: schedules and team-level results are the public tier, readable by anything, with the source of every field attached
- Next: results, standings and box scores — team lines public, player lines only where the organization has granted access
Visibility never at the cost of a child
The athletes here are mostly children, so "more visible" cannot mean "publish everything". Schedules, venues, team names and team-level scores are already public on thousands of sites, and the hub treats them as public. Rosters and per-player statistics are children’s personal data and sit behind a different door: an organization grants a named consumer access, revocably and logged, and a deletion request propagates as an event every subscriber must honour.
Where access has not been granted, the API says what it is withholding rather than quietly returning less. Player-level data gets a formal COPPA and state-law review before any of it ships.
And an API anyone can actually use
None of the above happens if the plumbing is hard to adopt. So the spec is open and Apache-2.0, the conformance vectors are public, test mode is free and resettable, and every error links to a page explaining that error. A club with no engineers should be able to join by pasting a URL, and a developer should be able to push their first batch in five minutes.
That is the bar: easy enough that the data actually moves.