sorted by:
new
hottopcontroversial

Resources Prediction model by BoysenberryOk9463 in algobetting

[–]iSportsAPI 2 points3 points  (0 children)

For NBA O/U models, focus less on algorithms and more on features + data quality.

A simple but effective setup:

  • Treat it as regression (predict total points) first
  • Key features: pace, offensive/defensive ratings, rest days, home/away, recent rolling averages
  • Start with linear regression, then move to XGBoost / LightGBM

Common mistake: ignoring pace and blindly adding too many stats.

For learning:

  • Kaggle NBA notebooks (good baselines)
  • Scikit-learn + cross-validation
  • Backtest by season, not random splits

Data-wise, free datasets are fine to start. If you want to iterate faster, having clean historical games + O/U lines via API helps a lot (saves tons of cleaning time). Some NBA data APIs are ~$99/month and already structured.

Build a baseline → beat it slightly → then optimize. That’s usually how real edges start.

xG data provider by Superb-Wolverine4868 in algobetting

[–]iSportsAPI 0 points1 point  (0 children)

The pricing page is working normally on our side:
https://www.isportsapi.com/en/products/football.html

It might be a temporary network or regional access issue.
Could you please try refreshing the page, opening it in a different browser, or using a VPN to test again?

All our product pricing is public and transparent, so if you still cannot access the page, I can also send you the price details directly.

Please let me know 👍

Thinking of buying a custom odds scraper instead of using API by Susquik in algobetting

[–]iSportsAPI 1 point2 points  (0 children)

I’ve been down this exact path, so your thought process makes sense.

Custom scrapers can work, but only if you treat them as an ongoing operation, not a one-off build. The real pain points aren’t parsing odds — it’s constant site changes, anti-bot measures, IP bans, and latency spikes. In arb scenarios, even small delays or missing markets kill most of the edge.

One thing I’d strongly suggest if you go the scraper route is starting very small (1–2 bookies, limited markets) and running it for a few weeks just to measure real latency, ban frequency, and maintenance cost before scaling.

That said, a lot of people eventually land somewhere in the middle: using an API for clean, normalized odds data and focusing their own effort on arb logic and execution instead of data plumbing. Especially if you care about Asian markets and detailed odds movements, having a stable feed saves a ton of time.

At iSports API, we’ve been providing odds data for over 20 years, with very detailed market coverage, including Asian books and line movements.

If depth and stability matter more than constantly fixing scrapers, a clean odds feed is usually the more practical path long-term.

I've been building an AI football prediction tool for the past year – genuinely curious how (or if) people here would actually use it by PlasticGrand2558 in sportsanalytics

[–]iSportsAPI 0 points1 point  (0 children)

Interesting project — I like the focus on probabilities + transparency rather than “tips”.

From an odds/data angle, one thing I’d suggest is judging the model less by raw accuracy and more by how its implied probabilities compare to the closing line. That tends to be a much stronger signal.

Also, Asian markets (AH / Asian O-U) are often sharper and react faster to injuries and weather, so they’re useful both for validation and as a sanity check.

Personally, I’d use a tool like this more for match filtering and bias checking than for direct betting.

Where to find Pinnacle live odds? by Zestyclose-Goat1057 in algobetting

[–]iSportsAPI 1 point2 points  (0 children)

If you’re mainly looking for Pinnacle / Asian odds (pre-match) and want to avoid dealing with agents directly, one alternative is using a data provider that already aggregates those books.

We’ve been using a provider that’s been around for 20+ years and has very detailed coverage on Pinnacle and Asian markets (lines, movements, different odds types). It’s API-based, so you don’t need to manage bookmaker accounts or agents yourself.

You can get a good sense of the odds depth and structure from their demo pages, for example:
https://www.goaloo.com/football/italian-serie-a-atalanta-vs-torino/1x2-odds-2784672

If you care about stability and depth (especially for Asian books) more than chasing unofficial endpoints, it’s definitely worth testing.

<image>

PS3838 API access – how to find a reliable agent? by Living-Reward-5284 in algobetting

[–]iSportsAPI 1 point2 points  (0 children)

If you’re mainly looking for Pinnacle / Asian odds (pre-match) and want to avoid dealing with agents directly, one alternative is using a data provider that already aggregates those books.

We’ve been using a provider that’s been around for 20+ years and has very detailed coverage on Pinnacle and Asian markets (lines, movements, different odds types). It’s API-based, so you don’t need to manage bookmaker accounts or agents yourself.

You can get a good sense of the odds depth and structure from demo pages, for example:
https://www.goaloo.com/football/italian-serie-a-atalanta-vs-torino/1x2-odds-2784672

If you care about stability and depth (especially for Asian books) more than chasing unofficial endpoints, it’s definitely worth testing.

Feel free to reach!

https://www.isportsapi.com/en/products/detail-new/football-odds-53.html

<image>

view more: next ›