Skip to main content
This page is for teams that need more than a simple scoreboard. Use it when the product needs standings, bracket logic, phase context, conference or division slicing, or a series/championship story that spans multiple leagues.

​
Product Outcome

Launch league tables, tournament flows, and championship tracking surfaces that stay grounded in canonical competition structure.

​
Who Builds This

  • league hubs and tournament centers
  • editorial products covering playoff or championship races
  • assistants that answer standings or bracket questions
  • products with conference, division, or tier filters
StepToolWhy it matters
1gns_resolve_entityresolve the league or series the user means
2gns_league_structureunderstand phases, groups, rounds, and related IDs
3gns_league_standings or gns_league_bracketsanswer table or knockout questions
4gns_series_league_overviewconnect a series to the leagues inside it
5gns_series_championship_snapshotcreate a one-call championship summary

​
Minimum Inputs

  • leagueId or leagueSeasonId for league experiences
  • seriesId or seriesSeasonId for multi-league championship flows
  • optional conferenceId, divisionId, or tierId for narrower standings

​
Example End-User Prompts

  • “Show me the current standings for the WNBA.”
  • “How does the playoff bracket look right now?”
  • “Which leagues feed into this championship?”
  • “Compare the title race across these two seasons.”

​
Expected Output / UX

Strong tracking experiences surface:
  • clear competition structure before deep data
  • the right standings slice for the user’s filter
  • bracket context where knockout phases exist
  • a path from series context into league-specific detail

​
Common Mistakes

  • skipping gns_league_structure and guessing competition structure
  • passing both leagueId and leagueSeasonId
  • using current-season tools when a historic season was requested
  • flattening series and league concepts into one thing

​
Where To Go Deeper