Nine questions separate a betting bot you can reason about from one you are trusting on faith, and not one of them is about results. Where does the software run. Whose computer places the bet. Who can read the logins it holds. What does it record per bet. How fast can you stop it. This page answers all nine about B337, including the answers that are limits rather than features.
The short version: the bot runs on your own computer, it places nothing while that computer is off, asleep or offline, and every account it signs in to is one you hold in your own name with details you supply. What that does not mean is that everything stays on your machine, and the honest answer to several of these questions is a constraint rather than a feature.
Where it runs, and whose computer places the bet
On your own computer. A session is one logged-in bookmaker account, and one session can run several strategies; sessions log in to bookmaker and exchange accounts held in your own name, with the login details you supply. Under the Terms, every account you connect must be yours, opened in your own name. The bet goes on from the machine in front of you, in a session signed in to your own account, over your own internet connection.
That cuts both ways, which is the useful part. Nothing is placed while your computer is off, asleep or offline, so the machine being awake is part of the system and a power cut is a stop. B337 never holds your betting funds: your money stays in your own bookmaker and exchange accounts, under their terms, and they settle your bets. B337 is software, not a bookmaker or wagering service provider, so it does not take bets, set prices or accept wagers.
Note: B337 is not an agent, and the team does not place bets on a customer's behalf. A session acts only on the strategy and limits you choose, in accounts you own.
Operating systems, and whether a computer has to stay on
The supported systems are Windows 10 or 11 at 64-bit, macOS 11 or later on Apple Silicon (Intel Macs are not supported), and Linux on Ubuntu 24.04 or later or Debian 13 or later. You also need at least 4GB of RAM, 500MB of free disk space and an internet connection. Download the bot from the Downloads page in your B337 dashboard, never from a file someone sends you.
And yes, the computer has to stay on. It has to be on, awake, online and running B337 while sessions place bets. A laptop that sleeps when you shut the lid is a laptop that has stopped betting, which is as much a safety property as a constraint.
One machine, or several
Which accounts run, and on which of your computers, is one of the settings you set. So several computers can each run their own sessions, and a session belongs to the computer you launched it on. On Terminal Pro, any number of your bookmaker accounts can be logged in at once.
Where bookmaker logins are held, and who can read them
This is the question where a vague answer does the most damage, so here it is point by point.
Bookmaker credentials are held only so the bot can act on your settings, and are never shown to other users. Data is encrypted in transit. Access to stored data is restricted to your own account by database-level rules, and staff access is limited and logged. Two-factor authentication is available on the B337 account itself: once it is on, every login also needs a 6-digit code from an authenticator app. Your B337 password is stored only as a hash by the login provider, and card details for a plan are collected and held by the payment provider rather than by B337.
Two things here are not features, and both have to be said. Running on your own computer does not mean everything stays on it: login details and betting records are also held by B337, so the dashboard can show them and the bot can work. And no online system is perfectly secure. B337 does not claim otherwise, and it notifies you and the OAIC under the Notifiable Data Breaches scheme if a breach is likely to cause serious harm.
A free account asks for no bookmaker login at all. Bookmaker accounts only come in with a plan that runs sessions, and you can remove them whenever you like: deleting a bookmaker account in the dashboard also deletes the sessions that use it and takes it out of view straight away, although it does not close the account with the bookmaker. To close the B337 account and have the data deleted, email support@b337.bet, and B337 confirms within 30 days and removes bookmaker credentials first. Security problems go to security@b337.bet.
Vendor picks, or your own signal
Three answers, because these are three different products, and then the boundary that holds around all three.
B337's own strategies follow the rules you set rather than a model. Classic Racing compares each bookmaker's win price with the Betfair exchange price for the same runner close to the jump, and places a bet only where the expected value clears the edge threshold you set; it does not rate runners and is not a form guide. On racing it can optionally lay the same runner on Betfair once the bookmaker confirms the bet, in an exchange account you own: three separate settings, one each for bonus, promo and cash bets, every one of them off until you turn it on, and it never lays a tote bet. SGM Saver builds same game multis against saver offers a bookmaker has already issued to your account. Neither strategy creates, unlocks or claims an offer, so with no token on the account no promo bet is placed. Both come with Full Automation.
Your own signal goes in through the API. The Execution API places racing and sports bets from your own code into accounts you already hold, authenticated with an API key sent in the X-API-Key header, and it places what your code sends rather than picking selections. API Odds is the other half of that: live racing and sports odds for your own models and tools, placing no bets at all.
Someone else's signal is copy betting, sold as Tipping Pro. You subscribe to a tipster feed, and your own staking settings size every copy, never the tipster's.
Outside that racing auto-lay, the bot places nothing on the exchange: there is no exchange trading, no green up, no arbitrage or middles strategy and no sports hedging, so those stay yours to place in your own exchange account.
Tip: keep an API key in server-side code or an environment variable. Anyone who has it can send bets to your sessions.
Risk: Betting involves risk, and there is no guarantee of profit. A bet priced above an estimated fair price can still lose, hedging a cash bet at the exchange normally locks a small loss once commission is paid, a lay can go unmatched, and a tipster's past results are no guarantee of future results. Many bookmakers restrict automated betting in their terms. See responsible gambling for limits and support.
What the record shows, per bet
Every placement, price and settlement is recorded in your dashboard as it happens, so each bet can be checked line by line against the bookmaker's own record instead of against a monthly figure. Bets settle automatically from the bookmaker's own settled-bet list and from official racing results. Stake, return and bonus conversion are tracked per session and per bookmaker, results, summary and profit and loss views export to CSV, filters cover bet type, strategy, bookmaker and date, and bets placed elsewhere can be added by hand.
So what you get is the row rather than one headline number: the price taken, when it was taken, and how it settled, which is what any measure you care about is worked out from. Closing line value is published as a tracked figure on tipster feeds, beside strike rate, ROI and turnover, worked out by B337 from tips published through the platform and how those bets settled. For the measure itself, see closing line value.
A refused attempt is listed as well, which matters more than it sounds. A bot that skips quietly is a bot you cannot audit.
Stopping it mid-day
Stop any session from the dashboard at any time, or stop them all at once. Stopping a session stops new bets, while bets already placed stay with the bookmaker and settle as normal, because they are the bookmaker's bets now. Racing sessions can also carry profit-kill and loss-kill, which stop a session at a net profit or loss target.
Three caveats on the stop, all of them real.
- Stops and limits are ordinary settings, not a promise. A command can fail to reach your computer or act late, so treat them as a backup to the limits your bookmaker enforces.
- Profit-kill and loss-kill stop new bets only, so bets already running can take the final result past your figure.
- A running session keeps the settings it started with, so most saved changes apply from its next launch. Stopping is immediate; editing a rule is not.
The firmest stop is the one the architecture hands you, and it needs no command at all: nothing is placed while the computer is off. A kill switch is the dashboard version of the same idea.
What stops a bet at a price that has already moved
A price floor, plus the fact that the session reads the bookmaker's current price before it bets.
On the API, target_odds is a floor rather than a fixed price: below it the bet is refused, at or above it the bet goes on at the bookmaker's current price, and an optional max_odds adds a ceiling. Sessions carry the same idea as settings, with minimum and maximum odds and price floors. When a bet fails it is simply not placed, and your limits still apply, so a session will not take a price below your floor or a stake above your maximum to force a bet through. The refused attempt is listed in the dashboard.
Worked example on illustrative prices, to show the arithmetic rather than to describe a real race. Say your fair price for a runner is $2.90 and your floor is $3.00.
| What happens | Price taken | Edge against fair $2.90 | Expected value on a $50 bet |
|---|---|---|---|
| The price holds | $3.00 | plus 3.45% | plus $1.72 |
| The price shortens, the floor refuses | no bet | none | $0.00 |
| No floor, the bet is forced through | $2.80 | minus 3.45% | minus $1.72 |
The arithmetic: edge = offered price / fair price - 1, so 3.00 / 2.90 - 1 = 0.034483, or 3.45%, and 2.80 / 2.90 - 1 = minus 0.034483, or minus 3.45%. Expected value is the stake times the edge, so on $50 it is 50 x 0.034483 = $1.724, shown as $1.72 in the table, once up and once down. The two rows sit $3.45 apart on one $50 bet, and that gap is the whole job of a floor.
Risk: a floor protects against a price that has moved, not against a fair price that was wrong to begin with. Terminal prices are read on a repeating cycle rather than tick by tick, so a price on screen can trail the bookmaker's own, and the bookmaker's price at the moment of the bet is the one that settles. On the API, a timeout status means no result came back in time, so check the account's bet history before you send the bet again.
Checkout, or a fit check first
Split by how you buy it, and the split is deliberate.
Three products are self-serve through a Whop checkout, tied to your account, with access usually turning on within a minute of payment: Terminal View at $25 a month, Bet Assist at $100 a month and Terminal Pro at $300 a month, all in Australian dollars and billed monthly.
They are also the only three plans that carry a published price. The rest are set up with the team instead, in a Discord ticket or on a call: Full Automation, the Execution API, API Odds, the Screeners and Tipping Pro. None of those shows a price, and the price, including any charges on top of the plan price, is confirmed before you pay. Bets placed through B337 also use credits, a per-bet usage charge, so the cost grows with the bets you place.
Billing in one line: paid plans are billed in advance for the period shown at checkout, renew until you cancel, and can be cancelled any time from Plans and Subscription or by asking the team, effective at the end of the period already paid. Part-periods are not pro-rated, prices can change on reasonable notice from your next renewal, and none of that limits your rights under the Australian Consumer Law.
Note: For free and confidential support call 1800 858 858 or visit gamblinghelponline.org.au.
The limits, stated plainly
Five of them, because a security page that lists only the good parts has not answered the question.
- Not everything stays on your computer. Login details and betting records are also held by B337, and some service providers store or process data outside Australia, mainly in the United States. B337 does not sell personal information.
- No online system is perfectly secure, and B337 does not claim otherwise.
- B337 cannot stop a bookmaker restricting or closing an account, and makes no claim that it avoids limits. Once a bookmaker limits or closes an account the bot cannot keep betting in it, and it cannot change what that bookmaker's terms allow.
- Most bookmakers restrict automated betting, third-party access and multiple accounts in their own terms, and under those terms a bookmaker can limit stakes, void bets or close an account, so read the terms for every account you connect. B337 does not give legal advice, and the legal side is covered in are betting bots legal in Australia.
- Automation makes it possible to bet far more, far faster, than by hand. Every account must be in your own name, and automation must never be used to get around a limit, an account closure or a self-exclusion. The failure modes themselves are in betting bot risks.
The nine answers on one card
The same nine, this time with B337's answer beside each and an honest label on it, because the answers that are constraints are the ones a vendor page leaves out.
| Question | B337's answer | Feature or constraint |
|---|---|---|
| Where does the software run | on your own Windows, macOS or Linux computer, in sessions signed in to accounts in your own name | feature: your machine, your connection |
| Does a computer have to stay on | yes: on, awake, online and running B337 | constraint, and also the firmest stop there is |
| Where are my bookmaker logins held | with B337 as well as on your machine, restricted to your own account by database-level rules, staff access limited and logged | constraint: not everything stays on your computer |
| Can I bring my own selections | yes, through the Execution API, and someone else's through Tipping Pro | feature |
| What does the per bet record show | placement, price and settlement for every bet, refused attempts included, exportable to CSV | feature |
| Can I stop it right now | one session or all of them at once, from the dashboard | feature, with the three caveats above |
| How many machines | several of your own can each run their own sessions, and a session belongs to the one it was launched on | feature |
| What stops a bet at a moved price | a price floor, and the bookmaker's current price read before the bet goes on | feature |
| How do I buy it | three plans self-serve with a published price, the rest set up with the team | feature |
Nothing on that card is about profit, and that is on purpose: every one of these can be checked before you pay, while a results claim cannot be checked at all. Two of the nine are constraints rather than features, which is the whole reason for writing all nine down instead of only the good parts.
For the generic version of the exercise, aimed at any vendor rather than at this one, how to choose betting software runs twelve questions with the answers worth walking away from, and is it safe to give betting software my login takes the credential question on its own.