1) Which models I checked (top/visible sources)

• BetQL — simulation-based model (gave Baltimore ~67% win probability; model outputs and team props).

• SportsLine / CBS (SportsLine projection model) — 10,000-sim model; CBS preview reporting SportsLine leans OVER and projects ~51 total points. (SportsLine also publishes exact-score sims behind paywall).

• ESPN (FPI + writer picks) — ESPN FPI close to coin-flip (≈50.3% BAL) and ESPN writers posted explicit score projections (examples: 21-20, 31-26, 31-20).

• ThePlayoffs / independent previews — available public previews with explicit score projections (example: 27-24 BAL).

• Yahoo / other outlets — independent predictions (example: Chiefs 24, Ravens 20).

Note: Several models (SportsLine full score sims, Action Network proprietary outputs) are paywalled or behind dynamic graphics; I used the public outputs and the explicit score projections that were available. Where a model showed a numeric probability instead of a concrete score (e.g., BetQL), I recorded the probability and used other outlets’ exact-score projections for the averaging step.

2) Collected model score predictions (explicit scores I could find)

(These are the explicit final-score predictions available publicly.)

• ESPN — Maldonado: Ravens 21 — Chiefs 20.

• ESPN — Moody: Ravens 31 — Chiefs 26.

• ESPN — Walder: Ravens 31 — Chiefs 20.

• ThePlayoffs: Ravens 27 — Chiefs 24.

• Yahoo (independent prediction): Chiefs 24 — Ravens 20.

Average of those five explicit predictions (simple mean):

• Ravens average points = 26.0

• Chiefs average points = 22.8 → round to 23

Model-averaged final score (from the explicit-score set): Ravens 26 — Chiefs 23 (Total ≈ 49).

(Again: BetQL and SportsLine provided probabilities and simulation guidance — e.g., BetQL shows Baltimore favored ~67% and SportsLine’s projection leans to 51 total — which is consistent with the averaged score landing near 49–51.

3) News & injury check (last updates I found)

• Ravens TE Isaiah Likely: expected to be available / listed questionable — could be eased in (adds receiving/run-blocking depth). This helps Baltimore’s offensive packages.

• Ravens DL changes: Nnamdi Madubuike and Broderick Washington placed on IR; Ravens elevated C.J. Okoye and Josh Tupou for depth. That weakens interior run defense vs. Chiefs OL/running.

• Chiefs DT Chris Jones: reported to be returning/expected to make kickoff (news/travel item but expected available). His presence helps KC pass rush and run defense matchups.

• SportsLine / Sports injury lists: list several Ravens questionable (Ronnie Stanley, Isaiah Likely, Travis Jones) and Chiefs questionable (Mike Danna, Ashton Gillotte, Kristian Fulton). Overall injuries are notable but not game-cancelling for top QBs.

4) My independent analysis (method + inputs)

I combined:

• Pythagorean expectation (using team offensive/defensive points per game) — quick check using ESPN’s season efficiency ranks: Baltimore’s offense is top-ranked in scoring; but Baltimore’s defense ranks poorly (yards, points allowed). Kansas City’s defense is middle-to-upper (T11 overall). That implies Baltimore should score more but their defense makes games higher-variance.

• Strength of Schedule (SOS) context: both teams 1-2; recent opponents and remaining schedules matter — early tough matchups have inflated Baltimore’s defensive numbers. On raw SOS, KC’s Arrowhead home edge and historical series success vs BAL matter. (I weighted home-field + previous KC success lightly ~ +2.5 points to KC.)

• External factors: injuries listed above (Ravens DL losses reduce their run defense; Likely possibly helps offense a bit; Chris Jones presence helps KC). Travel/rest: Ravens are road team but not on short rest. Recent form: Ravens gave up 38 to Detroit; Chiefs held Giants to 22-9 (momentum to KC).

Pythagorean-style expectation (qualitative):

• Baltimore’s offensive clutch: +

• Baltimore’s defense liability: −

• Kansas City: middling offense so far but improving; D can keep it close at Arrowhead.

Net: small edge to Baltimore because their offense (when healthy) is the more explosive unit — but the margin is narrow and variance is high.

5) My final numerical prediction (independent)

My projected final score: Baltimore Ravens 27 — Kansas City Chiefs 24

• Implied total = 51 (so I lean OVER 48.5).

• My model says Ravens cover the 2.5-point spread (so take Ravens -2.5) and the game is a close high-scoring affair.

Confidence: Moderate — ~56–60% on the side of Ravens covering (lower for ML because ML is pay/win dependent). Why moderate? Ravens’ offense and positive turnover edge push them, but Baltimore’s defensive injuries and KC home-field/history keep it tight.

Betting notes:

• Primary: Ravens -2.5 (if price favors it vs ML).

• Alternate/prop: Over 48.5 (models / SportsLine lean slightly OVER — SportsLine projected ~51).

• If you want less variance: consider small unit on Ravens moneyline (-149) plus a small unit on OVER — but the spread (-2.5) gives better protection. (I prefer the spread here.)

6) How the model-average vs my pick compare

• Model-average (explicit-score models) → Ravens 26 — Chiefs 23 (Total ≈ 49).

• SportsLine (simulations) → leans OVER, projects about 51 total.

• BetQL → heavy Baltimore win probability (~67%) but that’s a win-probability, not exact score.

Comparison: My pick (27–24, total 51) is slightly higher-scoring than the explicit-score average (49) and aligns with SportsLine’s OVER tilt and BetQL’s Baltimore favoritism. So the consensus tilt across models + my read → Ravens, narrow, with a lean to OVER.

7) Quick actionable

My Pick: Baltimore Ravens Spread -2.5 (LOSE)