What the console manages
Running a book day to day is mostly about control. Traders need to know what they owe on every market, cap how much one customer can stake and see results as they land. RealTimeBets puts those controls in one web console that reads from the same engine your customers see prices from.
- Markets. Every market comes from the engine with its status, open or suspended, and suspends itself after dangerous incidents.
- Margins. Every price carries a margin of about 6 percent over the fair probability, shown in each market payload.
- Liability. Watch exposure on the markets with the largest liability as bets are recorded.
- Customers. Set a maximum liability per market type and a maximum stake per customer; the risk check flags sharp customers.
- Results. Follow recorded bets as they settle won or lost, with the payout.
Keys, webhooks, usage and billing sit in the same console, so a trader and a developer can work from one team account.
Live trading without a quant team
The cost that stops most books from offering deep in-play markets is people. Pricing a tennis match point by point or an ice hockey game minute by minute needs models, and running those models live needs someone watching them. RealTimeBets runs the models for you.
Soccer and ice hockey goals use Poisson models that update with the clock and the score. Tennis follows a serve and hold model. Basketball and American football use possession models. Baseball and CS2 have their own engines as well. Each one recomputes prices every second, and micro-markets suspend for a few seconds after a goal, a card or a change of score.
Your traders move from typing prices to setting policy: how much liability per market type and how much stake per customer. That is the work a small team can do well. The engine underneath is the same one documented on the odds API page, so what traders see and what developers fetch never disagree.
Liability and customer limits in view
Exposure in live betting builds fast. A single goal can turn a quiet market into the largest liability on the board within a minute. The console shows liability for the open markets with the most exposure, updated as bets are registered through the API.
Limits work at two levels. A maximum liability applies per market, set per market type, and a maximum stake applies per customer; without your own values the defaults are 50,000 and 5,000. When a bet would push a market past the threshold, the risk check returns a reduced stake or a rejection instead of an accept. When an incident hits, micro-markets suspend and the risk check rejects bets on them before the price can be picked off.
The sharp flag decides which customers get tighter limits. A customer with at least 20 settled bets and a win rate of 60 percent or more is flagged sharp, and the risk check halves that customer's limits automatically. The full method is on the sportsbook risk management page. All of this is part of Growth and Enterprise.
Settlement and reconciliation
Late or wrong settlement is the fastest way to lose a customer and the slowest problem to clean up. RealTimeBets settles markets from the same incident feed that drives the clock and the score, so the event that closes a market is the event that resolves it.
Each bet you record settles when its market resolves, with the status, the winning selection, the payout and the time. Your backend receives a signed bet.settled webhook for every result. The signature is an HMAC SHA-256 of the timestamp and the raw body made with your endpoint secret, we try each delivery up to 3 times, and each event has an id, so your backend can ignore a repeat.
For finance, every result is tied to the bets you registered through the API, which makes reconciliation against your own ledger a matter of matching two lists. Any bet can also be looked up by its id to check its status and payout.
Roles, audit and security on Enterprise
Regulators expect a book to show who lifted a limit, who created a key and who had access to the console. Enterprise adds the controls that make that easy to prove.
- Single sign-on through SAML, so staff log in with the accounts your company already manages.
- Roles that separate trading, development, finance and read-only access.
- An audit log of changes to limits, keys and access.
- IP allow-listing for the console and the API.
- A data processing agreement and invoicing.
Enterprise also includes fair-use requests and 50 streaming connections, against 2 on Starter and 10 on Growth, and the white label sportsbook. Details of how keys, data and access are protected are on the security page.
Costs you can plan for
Sportsbook software is often sold on revenue share, which means the bill grows with every good month. RealTimeBets charges a flat subscription instead. Starter is $499 a month, Growth is $1,999 a month and Enterprise is $4,999 a month. Paying yearly halves each figure, so Growth costs $11,988 for the year.
Usage limits are clear in advance: 500,000 requests on Starter, 5,000,000 on Growth and fair use on Enterprise. The console shows how much of the period you have used. Moving to a higher plan charges the difference immediately, and you can cancel at the end of any paid period.
Every plan is bought at checkout without a call. The only thing we need before production keys go live is your licence record. Start with the sandbox key, try the console with your team and choose a plan when the numbers make sense.