Skip to content

fix: document expectedValue as bookmaker/fair x 100, bump to 1.2.1 - #13

Merged
odds-api-io merged 1 commit into
mainfrom
fix/expected-value-units
Nov 6, 2026
Merged

odds-api-io merged 1 commit into
mainfrom
fix/expected-value-units

Conversation

@odds-api-io

Copy link
Copy Markdown
Owner

Summary

  • examples/value_bets.py said expectedValue is a fraction (0.0523 = 5.23%) and printed expectedValue * 100. The API returns bookmaker odds / fair odds x 100: values cluster around 100, 103.42 is a 3.42% edge, below 100 is a negative edge. The example now prints and filters on expectedValue - 100.
  • ValueBet TypedDict docstring and get_value_bets docstrings (sync and async) explain the unit.
  • README arbitrage/value-bets snippet shows the edge filter and notes profitMargin is already a percentage.
  • Version 1.2.1 (pyproject, __version__, CITATION.cff, README citation), CHANGELOG. The fair-odds notebook computes its own EV and was already correct.

Test plan

  • pytest (110 passed)

expectedValue is bookmaker odds / fair odds x 100 (103.42 = 3.42% edge),
not a fraction. Fixes the value_bets example, the ValueBet and
get_value_bets docstrings and the README snippet.
@odds-api-io
odds-api-io merged commit 236cd8a into main Nov 6, 2026
3 checks passed
@odds-api-io
odds-api-io deleted the fix/expected-value-units branch November 6, 2026 14:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant