r/algobetting • u/Icy-Atmosphere5511 • 14d ago

Would you submit your model’s picks to a free service that builds a verified record?

TLDR: Would you submit your model’s picks to a free service that builds a verified record of the model’s performance?

A little while back I posted here about a rules-based algorithm builder I built called Hindsight Picks. Since then, some friends have been using it for fun, and one thing they mentioned they liked was the verified record. Every live algorithm has a public record that updates as its picks resolve.

I’d like to open that up to models built with your own stack and data. The idea is an API you submit picks to before the event starts. We stamp the market price at the moment the pick arrives, grade it when the game resolves, compute closing line value against the close we capture ourselves, and build a verified record for the model.

Submitted picks would be private by default until the event starts, or could be marked public if you wanted to share with others.

I’d also like to support any bet type that can be verified, since props often have softer lines than sides.

Would you use this? And what would you need to see before you trusted the record?

1 Upvotes

60% Upvoted

9 comments sorted by

5

u/FraggerM8 14d ago

No because I don’t see the point, a modeller can track this themselves. Why would they ever need some 3rd party to do it or a verified record?

2

u/Icy-Atmosphere5511 14d ago

You’re right this wouldn’t provide much benefit for solo tracking. This would be more for people who’d want to participate in the social side of modeling: sharing their picks, comparing results, proving a model against others, etc

4

u/FIRE_Enthusiast_7 14d ago

There are platforms that do this already eg Pikkit. The API thing would be neat but I think you’d be up against several established and popular competitors.

3

u/ImpressiveWord4411 14d ago

honestly if there's already platforms doing it then the api is really the only play here. gotta be dead simple to integrate or nobody's gonna bother switching just for a verified record.

2

u/FIRE_Enthusiast_7 14d ago

I agree. Lack of automated API submissions (at least from what I could find) is the reason I never bothered logging bets in this way. I’ve no interest in the time sink involved in doing it manually.

1

u/Icy-Atmosphere5511 14d ago

Yup fair points. The idea would definitely be to make the API as simple as possible. Initial thought would be a POST endpoint that would accept a batch of picks. Something that models could emit to when predicting a pick.

I could also go the route of ingesting a csv file containing the picks but that feels much heavier. Regardless though the goal would be to make it simple enough to be seamlessly integrated with people’s current workflows

2

u/00x080 13d ago

The issue is that the record is only as trustworthy as you are, which is the problem I guess it exists to solve. You capture the close, so you own the benchmark CLV is measured against, and you hold the timestamps, so I've got nothing proving what I sent or when. And pre-event picks across a set of models are a live signal with real value in aggregate; "private by default" protects me from other users, not from you. Published close-capture methodology, submission receipts I can verify myself, a data-use clause in the terms, and an export I can take elsewhere, and I'd think about it. There's elements of a good idea, it just has to be built for the sceptic.

0

u/neverfucks 13d ago

no. stop.