Bet CLV Tracker: Closing Line Value vs Sharp Odds avatar

Bet CLV Tracker: Closing Line Value vs Sharp Odds

Pricing

from $0.80 / 1,000 results

Go to Apify Store
Bet CLV Tracker: Closing Line Value vs Sharp Odds

Bet CLV Tracker: Closing Line Value vs Sharp Odds

Measure closing line value for your bets. Compare each bet's odds with the sharp bookmaker's no-vig closing price: CLV %, whether you beat the close, and expected value at close, plus a summary across all bets.

Pricing

from $0.80 / 1,000 results

Rating

0.0

(0)

Developer

MrDoe

MrDoe

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

1.2 hours

Issues response

15 days ago

Last modified

Categories

Features

Limited permissions

Share

Bet CLV Tracker: Closing Line Value vs Sharp Odds - See whether you beat the closing line: your bet odds against the sharp bookmaker's no-vig close, for every bet.

What does Bet CLV Tracker: Closing Line Value vs Sharp Odds do?

Bet CLV Tracker grades your bets against the closing line. You give it a list of bets with decimal odds and one or more bookmaker odds datasets captured just before the games started. By default, it builds the fair closing price as a consensus across every bookmaker in your datasets - each book's price is de-vigged on its own, then averaged - rather than depending on one named "sharp" book being present. It matches each bet to its game and returns closing line value as a percent, whether you beat the close and the expected value at close. A summary record gives the average CLV and the share of bets that beat the closing line.

Why use Bet CLV Tracker: Closing Line Value vs Sharp Odds?

  • CLV is the fastest signal of long-term betting edge.
  • A multi-bookmaker consensus closing price by default - not locked to a single named book.
  • Matches bets to games across bookmakers despite name differences.
  • Summary with average CLV and beat-the-close rate.
  • Works with the odds datasets you already collect.

What makes this different

Most CLV tools either lock you into one sportsbook import, or benchmark against a single "sharp" book's price - which breaks the moment that one book's data is missing or late. This Actor takes plain bets and any bookmaker odds datasets you already collect and builds the fair close from however many of them actually have a usable quote for that match, de-vigging each one and averaging the result - the same methodology serious closing-line tracking uses, computed transparently from your own data instead of a black-box third-party feed. Prefer a single named book instead? Switch Closing price method to "sharp bookmaker only" and it works exactly as before.

How it works

Bet CLV Tracker: Closing Line Value vs Sharp Odds workflow: your input, collection, output

  1. Your input — paste your bets and pick the closing-odds datasets.
  2. The Actor collects it — the Actor matches each bet to its game and removes the sharp book's margin.
  3. Your output — you get CLV per bet and a summary record.

What data can you extract?

The dataset has 20 fields per row:

FieldTypeDescription
idstringYour bet id.
eventobjectHome, away and start time.
marketstringmoneyline or total.
linenumberTotal line.
selectionstringhome, draw, away, over or under.
bookmakerstringBookmaker you bet with.
betOddsnumberYour decimal odds.
stakenumberYour stake.
statusstringmatched, no-closing-price, incomplete-closing-market, or not-a-closing-snapshot.
closingPriceSourcestringconsensus or sharpBookmaker, depending on the Closing price method used.
contributingBookmakersarrayWhich bookmaker(s) the closing price was built from.
contributingBookmakerCountnumberHow many bookmakers contributed - higher is a stronger consensus.
closingOddsnumberThe sharp bookmaker's raw closing odds (sharp-bookmaker-only method only; null for a consensus close, since no single book's raw price applies).
closingFairOddsnumberNo-vig fair closing odds.
closingFairProbabilitynumberNo-vig fair closing probability.
clvPercentnumberClosing line value in percent.
beatClosingLinebooleanTrue when CLV is positive.
expectedValueAtCloseUnitsnumberExpected value at the close in stake units.
hoursBeforeKickoffnumberHours between the closing quote's scrapedAt and kickoff (negative if scraped after kickoff); null when unknown.
demobooleanTrue for the built-in sample.

How to use Bet CLV Tracker: Closing Line Value vs Sharp Odds

Bet CLV Tracker: Closing Line Value vs Sharp Odds input form

  1. Open the Actor and go to the Input tab.
  2. Paste your Bets as JSON, pick the closing Odds datasets, and press Start. With no input it runs a built-in sample.
  3. Optionally set filters and a Max results limit.
  4. Click Start. A default run finishes in under a minute.
  5. Open the Output tab, then download the dataset or connect it to your tools.

Input Parameters

ParameterTypeRequiredDefaultDescription
betsarrayNo[]Bets to grade, as JSON. Each needs home, away, market (moneyline or total), selection (home, draw, away, over, under) and decimal odds; optional startTime, line (for totals), stake, bookmaker and id. Example: {"home":"Arsenal","away":"Chelsea","market":"moneyline","selection":"home","odds":2.2,"stake":10}. Leave empty to try a built-in sample.
oddsDataset1stringNo—Closing odds: a dataset from a bookmaker odds Actor run taken just before the games start (it must include the sharp bookmaker).
oddsDataset2stringNo—Another dataset of the same kind.
oddsDataset3stringNo—Another dataset of the same kind.
oddsDataset4stringNo—Another dataset of the same kind.
closingPriceMethodstringNo"consensus""consensus" averages the no-vig price across every bookmaker in your datasets (recommended); "sharpBookmakerOnly" requires one named bookmaker instead.
sharpBookmakerstringNo"Pinnacle"Only used when Closing price method is "sharpBookmakerOnly". Bookmaker whose no-vig closing price is the fair closing line. Must match the bookmaker field in the datasets.
maxStartDiffHoursnumberNo3Listings count as the same match when start times are within this many hours.
closingWindowHoursnumberNo6A sharp price is only treated as a genuine closing line when it was scraped within this many hours before kickoff (and not after kickoff). A snapshot outside this window is reported as not-a-closing-snapshot instead of being used as if it were the close.
maxResultsintegerNo5Maximum number of bets returned. Default is 5 for a quick test; set 0 to return everything available.

Output Data

Bet CLV Tracker: Closing Line Value vs Sharp Odds dataset table

clvPercent is bet odds times the closing fair probability minus 1, as a percent: positive means you got a better price than the fair closing price. status is no-closing-price when the game or market was not found. A SUMMARY record in the key-value store has the average CLV and the beat-the-close percentage.

Bet CLV Tracker: Closing Line Value vs Sharp Odds field map of one record

A real dataset item:

{
"id": "demo-1",
"event": {
"home": "Pittsburgh Pirates",
"away": "San Francisco Giants",
"startTime": "2030-01-01T19:00:00.000Z"
},
"market": "moneyline",
"line": null,
"selection": "away",
"bookmaker": "FanDuel",
"betOdds": 2.75,
"stake": 10,
"status": "matched",
"closingPriceSource": "consensus",
"contributingBookmakers": ["Pinnacle", "Circa"],
"contributingBookmakerCount": 2,
"closingOdds": null,
"closingFairOdds": 2.586,
"closingFairProbability": 0.3866,
"clvPercent": 6.32,
"beatClosingLine": true,
"expectedValueAtCloseUnits": 0.63,
"hoursBeforeKickoff": null,
"demo": true
}

Usage Examples

Grade three bets

{
"bets": [
{
"home": "Arsenal",
"away": "Chelsea",
"market": "moneyline",
"selection": "home",
"odds": 2.2,
"stake": 10
}
],
"maxResults": 0
}

Pin to one named sharp book instead of the consensus

{
"closingPriceMethod": "sharpBookmakerOnly",
"sharpBookmaker": "Pinnacle",
"maxResults": 0
}

Try the sample

{}

Tips for Best Results

  • Default is 5 results for a fast test. Set the max to 0 to return everything available.

Known Limitations

  • Closing prices are only as close as the datasets you capture; run the odds Actors just before start times.
  • Only moneyline and total bets are graded.
  • For the consensus method, a bookmaker's total-line quote is only used when it matches the bet's own line (or the most common line among your datasets, if the bet doesn't specify one) - books quoting a different line for the same match are excluded from that bet's consensus rather than blended in.
  • Each bookmaker's quote is weighted equally in the consensus (a simple average, not weighted by a book's size or sharpness).
  • Team matching is fuzzy; unusual name differences can leave a bet unmatched.
  • A closing price is only accepted when it was scraped within the configured window before kickoff (default 6 hours) and not after kickoff; with the consensus method, a stale quote from one book is simply excluded rather than failing the whole bet, as long as at least one other book's quote is still in-window.
  • A three-way sport's closing quote missing its draw price is excluded the same way, not silently priced as two-way.

Integrations

Run it from the Apify API, on a schedule, or from a webhook. Send results straight to Google Sheets, Make, Zapier, Slack or your own database with Apify's built-in integrations.

Export Formats

Download the dataset as JSON, CSV, Excel, XML, HTML table or RSS from the Output tab or the API.

Frequently Asked Questions

Does it need an account or API key?

No. The Actor only needs the bets and odds datasets you provide.

Am I charged for failed results?

No. You are only charged for results that are written to the dataset.

Do I need an account or login?

No. The Actor only needs the bets and odds datasets you provide.

Am I charged for failed runs or empty results?

You are only charged for results that are actually written to the dataset.

Can I run it on a schedule?

Yes. Create a Task with your input and add a schedule in Apify Console. With monitor mode on, each scheduled run returns only what changed since the previous one.

Support

Questions or a missing field? Open an issue from the Issues tab on this Actor's page and it will be looked at.

You are responsible for how you use these results, including compliance with bookmaker terms and the gambling laws that apply to you. This Actor is analysis only and does not place bets. Gambling is age-restricted; if you or someone you know has a problem, seek support such as BeGambleAware or 1-800-GAMBLER.