Product Outcome
Let users start from a sports entity or a program and move confidently to the related broadcast or sports context without building custom cross-dataset linkage yourself.Who Builds This
- watch guides and availability assistants
- content-discovery products
- customer support agents answering viewing questions
- editorial workflows that connect matches and programming
Recommended Tool Chain
| Step | Tool | Why it matters |
|---|---|---|
| 1 | gns_schedule_results or gns_match_info | identify the match or sports entity in play |
| 2 | gns_related_programs_by_entity | find linked broadcast programs from a sports entity |
| 3 | gns_watchability_by_entity | normalize that linkage for AI-friendly consumption |
| 4 | gns_related_programs_by_program | travel in the reverse direction from a program |
| 5 | gns_watchability_by_program | normalize program-to-entity linkage |
Minimum Inputs
- an
entityIdsuch as a match, phase, overall, team, or venue - or a
programIdwhen the user starts from broadcast data
Example End-User Prompts
- “Where can I watch this match?”
- “What sports event is this program about?”
- “Which broadcasts are related to this team or venue?”
- “Help me connect a TV schedule item to the underlying game.”
Expected Output / UX
These experiences usually need:- a clean set of related program or entity links
- relation types that explain how the connection works
- normalized fields that are easy to pass into an agent prompt or UI card
Common Mistakes
- expecting watchability tools to replace schedule or match discovery
- using raw connectivity payloads when the bundle version already normalizes them
- treating every relation as a match when the entity may be a team, phase, or venue