How we report, write and check.

Where facts come from

Scores, schedules and betting lines come from ESPN’s public scoreboard and odds data. Every line on the site names its provider and the time we read it, for example “DraftKings via ESPN · as of 7:05 PM ET”, and pregame lines are labeled as pregame. Lines move, so confirm the price on the sportsbook before you bet.

We do not fill gaps with made-up numbers. When a line or a score is not available, the page says so.

News stories start from published news reports in the sports feeds the desk follows. Sportsbook reviews summarize each book’s published terms, and every review shows the date it was last updated.

How we use AI

We use one AI model, xAI’s Grok, called from our servers. It never runs for an individual visitor: there is no chatbot and no AI search.

• News wire. The model rewrites a published news report in our own words. A separate AI pass then checks the rewrite against that report and lists anything the report does not support. Code removes those sentences, drops any number that does not appear in the report, and rejects rewrites that copy too much of it. Stories that pass can publish automatically under the “OddsListing wire desk” byline, with an AI disclosure under the headline.
• Matchup previews. Written from a fact packet and checked paragraph by paragraph; see how we write previews.
• What AI never does. It does not set a line, a score or a stat. Lines and prices are printed by code from the data, with their provider and time.

The desk can edit or unpublish any story, and unpublish any preview or ask for a new version. We never say a person reviewed a story unless one did.

How we write previews

We preview a limited set of games each day, chosen by code (for example national-TV games and ranked college matchups), up to 16 a day.

• Code builds a fact packet for each game from ESPN data: teams, records, recent results, injuries, venue, kickoff and the current line.
• The writer works from the packet only. Each paragraph lists the facts it relies on, and every number in it must appear in one of them. Code checks this, and a draft that fails is held, not published.
• A separate AI check reads each paragraph against the packet. A draft gets one pass to fix what the check found; if it still fails, it is held.
• Before release, and again 24, 8 and 3 hours before kickoff, code rebuilds the packet from fresh data. A material change, such as a line move, a new kickoff time or a key player ruled out, sends the preview back for one rewrite.

A preview can publish automatically once it passes every check. Each one shows when it was published and last updated, and the disclosure at its end gives the time and provider of its lines.

Our lean

“Our lean” is a read of the facts at a stated price and time; not advice; no records.

The preview’s writer picks a side, or says “No lean”, from the facts in the packet. Code prints the selection with the line, its provider and the time it was read. If the price has moved since then, the lean was about the old price. A lean is an opinion, not a recommendation to bet, and we keep no won-lost record, units or rankings of leans.

Corrections

If something on a page is wrong, tell us. Use “Report a problem with this page” at the end of any story or preview, the contact form, or email support@oddslisting.com. A link to a source helps.

When we confirm an error, we fix the page or take it down.

Affiliate links

Some sportsbook links are paid partner links: OddsListing may earn a commission when you open an account through them. Pages that carry them say “paid partner link”, and the links are marked as sponsored for search engines.

Partner payments do not set a line, a score, a preview or its lean, and rankings are not for sale. Read how we rate sportsbooks.

OddsListing does not take wagers. 21+. Gambling problem? Call 1-800-GAMBLER.