CS2 prop grader.
Every posted line, resolved against the final map.

Grading a CS2 prop sounds simple until the line is map-scoped. A kills over on maps 1–2 is not the same bet as the same number on map 1, and the book board that posted the line is gone by the time the series ends. Three things break hand-rolled graders: scope — grading a maps 1–2 line from series totals; line drift — the 18.5 you took closed at 17.5, and only the quote tape knows which line you actually held; and identity — the player who renamed between the board and the boxscore.

A graded result row joins three things: the offer the book posted, the exact line that settled, and the finalized stat it resolved against. KashRock keeps all three on one row — plus the open/close tape — so a grade can be re-checked instead of trusted.

The grader is one route: /v6/esports/cs2/results. Everything around it exists to make the grade checkable — the live board to bind a propId before the match, gamelogs for the finalized numbers, and the contract tape for the open/close behind every grade.

The same rows are on /v7/cs2/results and the get_results / v7_results MCP tools, so an agent can pull settled grades with a date window instead of an HTTP call.

Grades survive renames because they join on canonical IDs, not display strings. A player who changes their handle keeps one canonical_player_id, and the match keeps one canonical_event_id even when two books spell the teams differently.

• —propId — the book's offer; stable while the line moves
• —line_prop_id — the exact line that was graded
• —offer_id — prop + side + book; the ticket-level key
• —kr_pl_* / kr_ev_* — player and event joins that survive renames

Practical rule: bind the propId and direction at placement time. If you record only a player name and a number, you cannot prove which offer you held.

This is a real settled grade from the live feed — HeavyGod over 17.5 headshots on maps 1–2, graded a miss on 16. The line opened 18.5 and closed 17.5, so the CLV is on the row, not reconstructed later.

{
  "source": "kashrock",
  "sport": "cs2",
  "total": 19439,
  "results": [
    {
      "propId": "kr_prop_569251f0d61c",
      "line_prop_id": "kr_prop_b5b7b9755a8c",
      "book_name": "underdog",
      "player_name": "HeavyGod",
      "canonical_player_id": "kr_pl_e15bf1b3cd64",
      "stat_type": "CS2_HEADSHOTS_MAPS_1_2",
      "line": 17.5,
      "direction": "over",
      "grade": "miss",
      "actual_value": 16,
      "team": "G2 Esports",
      "opponent": "ShindeN",
      "event_time": "2026-10-05T09:00:00+00:00",
      "graded_at": "2026-10-06T18:54:01.935701+00:00",
      "canonical_event_id": "kr_ev_bededa5f4687",
      "offer_id": "kr_prop_569251f0d61c_2_over",
      "opening_line": 18.5,
      "opening_odds": -112,
      "closing_line": 17.5,
      "closing_odds": -112
    }
  ]
}

Most graders stop at the scoreboard. The difference below is whether the book's line — the thing the bet was actually against — survives to settlement with its price history intact.

Each posted line waits for the finalized map record, then resolves: the actual stat lands in actual_value, the grade follows, and the quote tape fills opening_* / closing_* where it exists.

• —Hit / miss — the canonical map record contained the stat and the line resolved.
• —Push — the stat landed exactly on the threshold.
• —Pending / error — not finalized, or no evidence; never an invented grade.

• —Bind propId + direction at placement; grades arrive on their own after settlement.
• —Page older grades with from/to on graded_at — Sandbox 30d, Hobby 90d, Builder+ vault.
• —Use line_prop_id when the same prop carried a ladder of lines.
• —Filter book, stat_type, or grade=hit|miss|push to build hit-rate views.

Keep this open: GET /v6/esports/cs2/results returns hit/miss/push with actual_value and open/close tape; grade is never invented — pending and error are explicit. Full contract: results endpoint docs.