Helping you navigate the sea of online sports market

This video gives you a glimpse of what we are working on: a 24/7 cloud-based product for automating and back-testing your strategies.

Step 1 is helping you quickly find the markets where you want to bet, so this demo focuses on market search. Use your own words to describe competitions, race distances, market volume, in-play status, etc., and we will use ML technology to understand you and deliver the result.

Attaching some screenshots of the UI.

More steps to come as we evolve the new product, so stay tuned!

If you would like to participate in early testing, please reach out to us at [email protected]

Hi Oxa

Interesting.

What level of granularity could be applied to these market searches?
For example could you drill down to markets starting in the next 10 mins where any selection within a given price range has a 2 tick gap between back and lay price and has a WOM greater than 0.75? Could a search like this be run continuously not worrying about data requests?

Next question of course is will conditional betting follow in forthcoming steps of the software development?

Thanks for posting this info. I will sign up for testing.

regards
Mark

Hi Mark!

As always, very good questions! Addressing them one by one:

What level of granularity could be applied to these market searches?

We plan to split the user input for market search and actions that you want to apply to the markets you have found. There is a limited amount of information you can obtain by calling BetFair API's listMarketsCatalogue endpoint, and it does not include selections' prices or volumes. So the search will cover the data available through listMarketsCatalogue and stage 2, namely triggers, will cover actions or further filters that you want to apply to the initial pool of markets retrieved from the search. This will involve repeatedly calling listMarketsBook - another API endpoint.

Could a search like this be run continuously not worrying about data requests?

In fact no, you should always be cognisant and wary of your data requests, as there is no such thing as free lunch when it comes to API usage. That is partly the reason we want to limit the parameters of the initial search, so as to not incur additional data costs by making too many requests.

Next question of course is will conditional betting follow in forthcoming steps of the software development?

Of course, this is going to be emerging soon as the next logical steps. We will try to shift away from the traditional "triggers editor" and offer intuitive UI that could generate snippets of actions that you could then mix and match inside the code directly (or dive straight into the code if you feel inspired).

Thanks for posting this info. I will sign up for testing.

Thank you for your feedback, I will reply to your request in the email.