Scootercam’s side hustle
What Is This?
Now that Scootercam has conquered meteorology, let’s turn to sports gambling.
MLB Scout is a weekly game-planning tool built around one question: which Cubs and White Sox games this week give you the best conditions to place a win bet?
It doesn’t predict scores. It doesn’t factor in bullpens, defensive shifts, or which way the wind is blowing at Wrigley. What it does — and does well — is evaluate the opposing starting pitcher for each upcoming game and score that matchup on a 0–100 scale. The idea is straightforward: a shaky starter on the mound for the other team means better conditions for a Cubs or Sox win. The tool surfaces those games so you’re not hunting through the schedule yourself.
Where the Data Comes From
All data comes from the official MLB Stats API at statsapi.mlb.com — the same free, public data source that powers many of the baseball apps and stat sites you already use. No third-party scrapers, no paid subscriptions. The API is queried by a background process that runs once per hour and saves everything to local files on the server. The page you’re reading never contacts the API directly — it reads from those saved files, so it loads fast regardless of traffic.
The data window covers three weeks: last week’s completed games (with final scores), the current week (results for games already played, look-ahead for games still coming), and next week’s full schedule preview.
The Matchup Score: How It’s Calculated
Each game receives a Matchup Score from 0 to 100, built entirely from the opposing starting pitcher’s season statistics. Higher is better — from a Cubs/Sox perspective. A score of 80 means the opposing starter looks hittable. A score of 15 means you’re facing someone who’s been dealing all season.
The score is built from four components:
ERA — 40 points maximum
Earned Run Average measures how many earned runs a pitcher allows per nine innings. It’s the oldest and most intuitive pitching stat in baseball: low ERA means a pitcher who keeps runs off the board; high ERA means they’ve been getting hit.
| ERA | Points |
|---|---|
| ≥ 5.50 | 40 (full) |
| 4.50 | 27 |
| 3.50 | 13 |
| ≤ 2.50 | 0 |
A pitcher with a 5.50+ ERA has been allowing roughly a run more per game than league average — meaningful edge. Below 2.50 you’re looking at a legitimate ace; the ERA component scores zero.
WHIP — 30 points maximum
Walks plus Hits per Inning Pitched is a direct measure of how many baserunners a pitcher allows. ERA can be influenced by defense and luck on balls in play; WHIP is cleaner — it captures how often the pitcher is putting men on base in the first place.
| WHIP | Points |
|---|---|
| ≥ 1.55 | 30 (full) |
| 1.35 | 18 |
| 1.10 | 6 |
| ≤ 0.90 | 0 |
A WHIP above 1.55 means the pitcher is averaging more than 1.5 baserunners per inning — plenty of opportunity for Cubs/Sox bats to do damage. A WHIP under 0.90 is elite-level command; the opposition is barely getting anyone on base.
K/9 — 20 points maximum
Strikeouts per Nine Innings is included because it captures something ERA and WHIP don’t: how often a pitcher ends at-bats himself versus putting the ball in play and trusting his defense. A high-strikeout pitcher is dangerous even when his ERA is middling — his stuff keeps hitters off-balance and limits traffic. A low-strikeout pitcher is more dependent on his fielders, which creates more opportunities for hits and mistakes.
For this score, lower K/9 is better for the hitting team. We want a pitcher who challenges hitters with stuff they can put in play.
| K/9 | Points |
|---|---|
| ≤ 5.0 | 20 (full) |
| 7.0 | 13 |
| 9.0 | 7 |
| ≥ 11.0 | 0 |
A pitcher with a K/9 under 5.0 is getting hit into play at every turn — that’s a lot of chances for runs. Above 11.0 you’re looking at someone elite who misses bats consistently; the Cubs/Sox lineup will have to earn everything.
Home Field — 10 points
A flat 10-point bonus when the Cubs or Sox are playing at home. Home field advantage in baseball is real, if modest: familiar surroundings, no travel fatigue, crowd support, and the tactical edge of batting last. It’s not a dramatic factor, but across a full season it matters, and it tips close matchup calls in the right direction.
Score Tiers
| Score | Label | What It Means |
|---|---|---|
| 70–100 | Strong look | Favorable starter + likely home — worth serious consideration |
| 58–69 | Favorable | Clear edge, worth a look |
| 42–57 | Neutral | Mixed signals, no strong lean |
| 30–41 | Tough | Good starter, difficult matchup |
| 0–29 | Pass | Elite or near-elite pitcher — tough conditions |
Prediction Accuracy Tracking
For completed games in the By Team section, each card shows whether the pre-game score pointed in the right direction:
- ✓ — Score said favorable (≥58) and the team won, or score said tough (≤41) and the team lost. The model read the matchup correctly.
- ✗ — Score said favorable and the team lost, or score said tough and the team won. The model missed.
- ~ — Neutral score (42–57). No strong signal was given either way.
This is a calibration tool, not a scorekeeping exercise. Baseball is full of upsets; a single ✗ means nothing. What you’re looking for over a full season is whether the Favorable games win meaningfully more often than the Tough ones. If they do, the model is earning its place.
The Snapshot System: Why Past Scores Don’t Change
This is where it gets a little technical, but it matters if you’re using the accuracy tracking seriously.
The score for a given game is based on the opposing pitcher’s season statistics. The problem: a pitcher’s ERA in April looks different from his ERA in August. If we scored April games using August stats, we’d be grading predictions with information that wasn’t available at game time — that’s not fair and it makes the accuracy tracking meaningless.
To solve this, the tool uses a pitcher snapshot cache. Here’s how it works:
- Every hour, as long as a game is still upcoming, the system fetches the opposing pitcher’s current stats and saves them alongside the game in a private cache file.
- The moment a game goes final, those stats are locked — frozen permanently as the pre-game snapshot.
- From that point on, no matter how the pitcher’s season unfolds, the score for that completed game never changes.
This means a March score reflects what that pitcher looked like in March. A September score reflects September. The accuracy tracking is apples-to-apples throughout the year.
What the Tool Doesn’t Consider
Being honest about limitations makes the tool more useful, not less.
Bullpens. The score is entirely about the opposing starter. If the starter goes five solid innings and hands it to a shaky bullpen in the sixth, that’s not reflected. Bullpen quality is real and sometimes decisive.
Lineup matchups. A right-handed strikeout pitcher against a lineup full of lefties is a different proposition than the same pitcher against a balanced lineup. The tool doesn’t split by handedness.
Weather and park factors. A pitcher with a 4.20 ERA throwing into a 25 mph wind off Lake Michigan at Wrigley is a different matchup than the same pitcher on a calm night in an average park. The tool doesn’t adjust for park effects or game-day conditions.
Injury and roster news. If a starter scratches the morning of the game and the team sends out a spot starter, the cron running an hour later will pick up the change — but the window between the scratch and the next hourly refresh won’t reflect it.
The Cubs and White Sox themselves. The score is entirely about the opponent’s starter. A Favorable score with a shaky Cubs offense still requires the Cubs to actually hit. Team-level offensive stats are shown in the Division & Team Stats section for context, but they don’t factor into the matchup score directly.
Reading the Full Page
Division & Team Stats — Live standings for the NL Central (Cubs) and AL Central (Sox), updated each hour. Includes W-L, PCT, GB, home record, away record, last 10, and current streak. Team stat chips show season-to-date offensive and pitching numbers for each club.
Three-Week Calendar — A grid view across last week, this week, and next week. Completed games show the final score (W/L and run total). Upcoming games show the start time in Central Time. Score-tier tinting carries through — favorable matchups show in amber, tough ones in gray — so you can read the week at a glance without touching the ranked list.
Best Bets This Week — All Cubs and Sox games for the coming week ranked highest-to-lowest by Matchup Score, regardless of team. This is the primary decision-making view. If you only have time to look at one thing, this is it.
By Team — The same games in chronological order, split by team. Useful when you want to see each team’s full week in sequence rather than cross-team ranked. For completed games, shows the final score alongside the pre-game Matchup Score and the ✓/✗ accuracy indicator.
A Note on Using This Responsibly
Matchup scoring is one input among many, not a system. No single-factor model beats baseball over a full season, and anyone who tells you otherwise is selling something. What this tool does well is narrow your attention — surfacing the two or three games a week where conditions look structurally favorable — so you can then apply your own baseball knowledge, lineup awareness, and judgment before deciding anything.
Use it as a starting point. Dig deeper on the games that score well. And keep an eye on the accuracy tracking over time — that’s the only honest measure of whether the model is earning its place in your decision process.
Data: MLB Stats API — free, public, no key required. Built for ScooterCam Worldwide LLC. Updated hourly during the season.
