Quote:
Originally Posted by AlsoEligible
That's correct, and this is what the larger whales use to send batches of bets directly to the tote system. They're not products that any individual can call up and start using.
Although there's really not that much of a difference between sending a batch of bets directly to tote, and sending a batch through a third party ADW like DRF, TWS, etc. It's mainly done to trim off any excess latency by removing any middle men (talking 1-2 seconds at most). That's important for the big guys, but not so much for the regular betting public.
|
I currently use 2 adw's and it's possible to write code to programmatically bet with both. PA has mentioned that he did this 10 years ago. Twin Spires doesn't provide a "batch" option, as far as I know, but I've had no problem sending 100s of tickets serially to them within seconds. Anyone can look at the browser's calls and reverse engineer a programmatic betting system, and I feel reasonably confident that it's possible with
any adw. I'd be happy to help anyone get set up with this, but to me it's not really useful unless you have a system that allows you to somehow output 100s of wagers after you've finished handicapping. Regardless, the point is that it doesn't require being part of some super-secret syndicate to batch bet, and claiming that this is even remotely an unfair edge they have is ridiculous.
FWIW, Twin Spires limits the number of tickets you can cancel for the day, so no one is using them to do that (unless the user has some special arrangement with TS). It's possible other adw's allow it, but I haven't checked. Frankly, you'd need tote tick prices over time to even backtest batch cancelling, which is hard to acquire unless one has been running a live system for some time. That is to say, even if I programmed a batch cancelling system, I wouldn't and couldn't use it until I had historical tote tick data with which to test it. Even then I'm not sure I'd use it...
