Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.etonecarg.com/llms.txt

Use this file to discover all available pages before exploring further.

Catch Me Up on This Game

Recommended path: resolve_entities when needed -> list_schedule -> get_event_summary or get_event_center

Choose the right depth

Use get_event_summary when the UX needs the smallest sufficient answer for one event.

Variations

  • If the host already knows the eventId, skip resolution and schedule selection.
  • If the recap is stats-heavy, add get_event_stats.
  • If the recap should answer where-to-watch next, branch into get_watch_availability after the event is identified.

Avoid

  • starting with a watchability tool when the user really wants sports truth
  • using a broad live slate when the product already knows the specific event