How to verify a sports pick with an AI assistant

Connect the BetsBeats MCP server, then ask your assistant to run verify_pick on a pick's hash. A hash commitment is a SHA-256 fingerprint published before kickoff. After the game the text behind it is revealed, so anyone can confirm it was not changed. The assistant checks that for you and reports when the pick was sealed, the result and whether the hash matches.

Examples are real responses from the live server, captured on 1 November 2026.

Why a hash commitment matters

Most pick sellers show a screenshot after the game, and a screenshot can be edited, posted late or chosen from many. A commitment fixes the pick first. BetsBeats publishes a SHA-256 hash of each pick before kickoff, computed over the game, market, selection, odds, kickoff time and a secret salt. Finding a different text with the same hash is not feasible, so the hash pins the pick down without revealing it.

Ask the assistant

With the server connected, give the assistant a hash from a result page and ask it to check. Use the full 64 characters or a unique prefix of at least 16.

Use BetsBeats to verify the pick with hash 93c087c1418ff2cf86be7b503e04786c10811971e5bcb169659b2933483e369a. Tell me when it was sealed relative to kickoff, what the revealed pick was, the result, and whether the hash matches.

The assistant calls verify_pick and gets this real response, for the main pick of 31 October 2026. It was sealed about two hours before kickoff, revealed after the game, matched, and lost. Losses are in the record on purpose.

{
  "found": true,
  "commit_hash": "93c087c1418ff2cf86be7b503e04786c10811971e5bcb169659b2933483e369a",
  "sealed_at": "2026-10-31T17:28:09+00:00",
  "kickoff_at": "2026-10-31T19:30:00+00:00",
  "revealed": true,
  "verify_url": "https://betsbeats.com/verify/93c087c1418ff2cf86be7b503e04786c10811971e5bcb169659b2933483e369a",
  "notice": "For adults 21+ only. Entertainment and analysis; no wins are promised and past results do not predict future ones. BetsBeats does not take bets.",
  "date": "2026-10-31",
  "teams": "Northwestern Wildcats — Oregon Ducks",
  "sport": "football",
  "league": "ncaaf",
  "is_main": true,
  "market": "spread",
  "selection": "Northwestern Wildcats +5.5",
  "line": 5.5,
  "odds": -129,
  "min_odds": -129,
  "result": "lost",
  "final_score": "26–34",
  "commit_version": 2,
  "preimage": "2026-10-31|Northwestern Wildcats — Oregon Ducks|spread|Northwestern Wildcats +5.5|5.50|-129.00|-129.00|2026-10-31T19:30:00+00:00|LxlEkc0mgt3FBEbmba6ZerObF5sgK1E0I6Pa6BwRJIV0vssAKXiG2TRbhyM9Lzgt",
  "recomputed_sha256": "93c087c1418ff2cf86be7b503e04786c10811971e5bcb169659b2933483e369a",
  "matches": true
}

What the check actually does

After settlement the server returns the preimage, which is the exact string that was hashed, and recomputes SHA-256 on it. You do not have to take the server's word. Hash the preimage yourself and compare the result with the published hash:

printf '%s' '2026-10-31|Northwestern Wildcats — Oregon Ducks|spread|Northwestern Wildcats +5.5|5.50|-129.00|-129.00|2026-10-31T19:30:00+00:00|LxlEkc0mgt3FBEbmba6ZerObF5sgK1E0I6Pa6BwRJIV0vssAKXiG2TRbhyM9Lzgt' | shasum -a 256
# 93c087c1418ff2cf86be7b503e04786c10811971e5bcb169659b2933483e369a  -

The standalone seal-verify scripts on GitHub do the same from a hash alone. Every field of the tool is described on its page: verify_pick

What a match does not prove

A match shows the text was not changed after sealing. It does not show the pick was a good one, and it does not show the archive is complete, because a seller could seal many picks and publish only some. That is why the record matters. Ask the assistant to run get_record and get_results, which list wins and losses, and look at whether every day appears.

Red flags when a seller offers no commitment

Picks posted after kickoff, screenshots with no hash, results that count wins and leave out losses, deleted posts, and a record nobody but the seller can check. Whatever the source, nothing predicts a future result and betting carries risk. This is for adults 21+, for analysis and entertainment.

Questions

Can an assistant verify a pick from another capper?

Only if that capper publishes a hash and later the revealed text in a form you can recompute. The BetsBeats server checks BetsBeats picks only.

Does a match mean I should bet?

No. It means the text was fixed before the game. Past results do not predict future ones, and BetsBeats does not take bets.

What if the pick has not settled yet?

verify_pick confirms the hash exists and returns sealed_at and kickoff_at. The selection is revealed only after settlement.