LSU 24 @ Ole Miss 32

1. Show more of what you already fetch. The post-game run already downloads 32 team categories and every player's line, then keeps 9 categories and 3 leaders. Defensive leaders, 4th downs, TFL, QB hurries, and yards per pass and per rush cost zero extra API calls.
2. Scoring summary + quarter line score from /drives. 20 rows, one call. It tells the story the box score can't: down 24–7, 17 straight to tie it, then a 14-play drive that ended in an interception at the goal line.
3. "Why it happened" panel from /game/box/advanced. Success rate, explosiveness, points per scoring opportunity, starting field position, havoc. Same vocabulary as your Season Form panel, so no new visual language. One call.
4. Closing line + result against it from /lines. Your line field is overwritten for the next opponent on Sunday morning, so the closing number for a played game is currently lost. CFBD keeps it, with the open and moneyline.
5. Swap the TV/kickoff web search (STEP A5) for /games/media + /games. Reliability fix, not a feature. Same reasoning as your AP-poll and betting-line switches.

Fields available: venue, start time, TBD flag, neutral site, conference game, attendance, quarter line scores, pregame and postgame Elo, postgame win probability, excitement index, highlights link.

Quarter line score, derived by me from /drives because CFBD's own lineScores field is still null:

Already fetched every Saturday. The unused rows are free. I'd add six and stop; a 15-row bar chart stops being readable.

Also already fetched. Defense is invisible on the site's box score today. A tackles / sacks / INT leader per team mirrors what Season Leaders already does pregame.

Also in the payload and not shown here: full receiver lists, every defender, kick and punt returns, fumbles, QBR (Leavitt 86.5, Chambliss 89.8).

Best story-per-byte in the API. 20 rows, small enough for the scheduled task's fetch tool. 25 fields per drive, including start/end field position, clock, and the score before and after.

Start position converted from CFBD's startYardsToGoal. I left end position out: some values in the response don't reconcile with plays and yards (punts appear to record where the ball landed).

Explains the result instead of restating it. LSU was the more efficient team down to down (46% success rate vs 44%) and started drives 12 yards closer. Ole Miss won on explosiveness and finishing: 5.17 points per scoring opportunity to LSU's 4.00.

PPA per play by quarter (also in the payload, split by pass and rush):

The best single visual CFBD offers, and your key can reach it. The catch: 163 plays × 16 fields is too big for the scheduled task's fetch tool to read reliably. It needs a cfbd-pick-style function that returns only play number, score and probability.

Drawn from every 10th play only, which is all I could extract through the summarizing fetch. The Q4 peak (about 55% after the tying field goal) was reported by that tool, not read from raw JSON; treat it as approximate. Hover a point for the play.

Keep The Odds API for the live pregame line; use this for history. One tiny call per played game preserves the closing number and lets each schedule row show how the game went against it.

Result: LSU lost by 8 as a 3-point favorite (did not cover). 56 total points, under 58.5.

* Open values inferred from CFBD's home-team sign convention (spreadOpen: −1.5 = home favored). A third row, "Draft Kings" with a space, duplicates DraftKings' close with no open or moneyline; dedupe it.

Rides along in the advanced box call, so it's free once that's added. Good for one "most valuable play-maker" line per team; a full table is too much for this site.

Related: /ppa/games gives team PPA by down. LSU offense: 1st down 0.24, 2nd down −0.52, 3rd down 1.07.

Not pulled, so not judged: /plays/stats, /player/usage, /ratings/srs, /recruiting/teams, /roster, /venues, /stats/game/advanced (overlaps the advanced box), /player/portal, /draft/picks.