Inspect recorded NFL results
Inspect the NFL source evidence an AgentCore application could read, from a game result to its captured records.
Guide context
Browse five real NFL game results with sportsbook-specific closing spreads and captured public source evidence.
Inspect five captured NFL results and the public-source evidence behind each one. Compare the displayed score, sportsbook-specific closing spread, and recorded against-the-spread result with its retained capture. The workspace does not simulate corrections or run an agent.
On this page · 5 sections
Inspect a captured game
Choose a captured game
Open one of the five games and its supplied records.
Inspect a supplied record
Read its State, Raw fields, and captured Evidence.
Follow recorded references
Inspect only the references supplied in this capture; no execution order or revision history is inferred.
One workflow, from game to evidence#
Open a captured game, then inspect a supplied score, closing spread, against-the-spread (ATS) result, profile reference, or recap. State shows the recorded value, Raw shows its allowlisted fields, and Evidence identifies the retained capture. No account is required.
What was captured#
Five game-detail requests returned ready public responses between 04:44:38 and 04:44:48 UTC on October 26, 2026. Eight other requests did not return a ready result. The selected games are not complete-week coverage.
Capture time and the source response’s as-of time are separate. Each game names its selected sportsbook; no league-wide or official closing line is implied. The source did not supply a score certification timestamp.
What this snapshot establishes#
Displayed scores, spreads, recorded grades and identities were checked against retained public responses and their capture receipts. The interface does not calculate ATS grades, fabricate earlier revisions or simulate a correction.
Records are grouped by type, not execution order. Only supplied references are linked. Stage statuses do not establish a complete dependency graph; profile identities do not include rolling statistics, and the closing record does not include a full certificate body.
This example shows the source records an AgentCore application could inspect. The application owns calculations, decisions and explicit Kam calls; AgentCore hosts agents and tools. These public captures do not independently establish Kam State admission, live customer serving or a Rust runtime cutover.
Use a keyboard or phone#
Game choices, search and inspection tabs use ordinary controls. The same result and source evidence stay in one workspace. There is no autoplay, and optional hover transitions respect reduced motion. The homepage links directly to captured games.