Royals @ Tigers

Totals this low need either clean starting pitching or two sleepy lineups. This game does not qualify on either side. Kansas City games have turned into chaos lately, Detroit already hit this matchup hard in the first series, and the number is still hanging at 7.5.

Both clubs are 7-9 and 2 games back in the AL Central, so this is not some dead April spot. The cleaner read is simple. Detroit has already proved it can do damage against this staff, and the Royals have been dragging almost every recent game into a run environment that lands above this number.

Why 7.5 looks light right away

Kansas City games are averaging 12.5 total runs over the last 10. Nine of those 10 games finished with at least 8 runs, which is exactly the threshold that cashes this ticket. When a team keeps living in 8, 9, 10 and 15-run games, 7.5 stops looking cautious and starts looking stale.

The Tigers have not been playing dead totals either. Four of Detroit's last five games finished with 9, 14, 7, 10 and 10 total runs. That means one side is showing an almost constant over profile and the other side is bringing enough recent variance to keep the door open.

Detroit already found the blueprint in this matchup

The first three meetings in this season series were played in Detroit, and the Tigers scored 9, 5 and 9 runs. That is 23 runs in three games, or 7.7 per game from Detroit alone. You do not need much imagination to see how Over 7.5 gets there when one lineup has already shown it can carry most of the load by itself.

Two of those three games still cleared this number, and the one miss finished 5-1. Even the lower-scoring result was not some dominant pitching duel from start to finish. It was simply the only game in the sample where Kansas City offered almost nothing back.

Kansas City pitching is turning every game into a mess

The Royals have allowed 75 runs across their last 10 games. They have given up 6 or more runs in 8 of those 10, which is the real engine behind the recent over streak. This is not a one-night blip. It has been happening almost every series stop.

The injury sheet matters here too. Kansas City still has Bailey Falter on the injured list, plus relievers Carlos Estevez and Stephen Kolek with April return dates. That is 1 starter and 2 relievers missing from a staff that is already leaking runs, and it matters even more when the posted total is only 7.5.

Detroit has enough current bats to punish soft pitching

The expected Detroit lineup is not short on active production. Riley Greene has 10 RBI and 11 runs in 16 games, Javier Baez is hitting .316 with an .815 OPS in 11 games, and Gleyber Torres has already drawn 12 walks in 15 games. That is traffic, pressure and enough table-setting to keep innings alive.

Spencer Torkelson has not shown full power yet, but a .373 OBP still matters in totals bets because it turns singles and doubles behind him into multi-run innings. Detroit does not need a perfect top to bottom card here. It just needs its better bats to keep getting men on against a staff that has not found stops lately.

The Royals still have enough offense to do their part

Kansas City is not being asked to win the game. It is being asked to help the total. Bobby Witt is carrying a .371 OBP with 8 steals in 16 games, Maikel Garcia is off to a .306 average with a .380 OBP and .864 OPS, and Jonathan India already has 2 home runs and 8 RBI in 12 games.

That kind of speed and on-base traffic is enough to create cheap runs, especially once the game gets into middle relief. Salvador Perez and Vinnie Pasquantino have not both clicked yet, which is the obvious pushback, but this over does not need Kansas City to explode. Three or four runs is probably enough if Detroit keeps doing what it has already done in this matchup.

The starter uncertainty pushes this total toward offense

Both lineup updates still list the starting pitchers as TBD. In MLB that matters, because the starting pitching matchup is usually the first thing protecting a low total. When both sides still have blank starter slots and the number is sitting at 7.5, the safer assumption is that this total is being posted before the most important run-prevention variable is even confirmed.

Detroit also has Justin Verlander on the injured list with a late-April return timeline, so there is no hidden ace arriving from nowhere. A low total with undefined starters is always fragile. A low total in a matchup that has already produced 9, 5 and 9 Tigers runs is even more fragile.

The only real objection

The fair argument against the over is that Kansas City has some cold bats. Pasquantino is sitting on a .416 OPS and Perez is at .507 through 16 games, and one of the first three meetings stayed under. That part is real.

The problem with the under case is that it asks for too many things to go right at once. It needs Kansas City to stay quiet again, Detroit to cool off after scoring 23 runs in the first three meetings, and both TBD starter situations to land on clean run suppression. That is a lot to ask against the current run environment.

Decision

The number is short because 7.5 always looks respectable in April at Comerica. The recent data says otherwise. Kansas City games keep exploding past modest totals, Detroit already proved it can do damage in this matchup, and the starter picture is still unsettled.

If Detroit gets close to its series average against the Royals, the over is live almost by itself. Add even a modest Royals contribution from Witt, Garcia or India, and 7.5 is a number worth attacking.