How Is Live-Camera Betting Priced: Fixed Odds or Pool?
Both, set per operator: Lukk, by Adkuu, runs a house mode (its price plus the operator's liability-adjusted margin) or an AMM mode that fills at the live probability.
Lukk, by Adkuu, prices live-camera markets in one of two modes, chosen per operator account. In house mode the odds are fixed: the Lukk price plus the operator's own margin add-on, adjusted for the liability already on that outcome, which is the classical bookmaker model. In amm mode fills come from a fair curve at the live probability, the pool-style alternative. In both modes a player backs an outcome at a locked price shown as decimal odds on the button, payout is stake × odds exactly, and odds run up to ×20.
Where the price comes from
Every market starts with the camera. The vision layer tracks every car, bus, bird and pedestrian in frame; the AI writes a natural-language question from what it sees, such as "Which lands first — a cardinal, a blue jay, or neither?", freezes and hashes the rule before the first bet, and prices the question live. The feed exposes both numbers a trader cares about, the fair probability and the margined fixed odds, together with timing, status, limits, the frozen rule_hash and recent settlements (GET /api/v1/b2b/feed), with live updates on wss://api.lukk.gg/ws/v1 under the b2b:feed topic and a gRPC mirror. Markets are YES/NO or multiple-choice, some with a "Neither" option.
House mode: fixed odds with the operator's margin
In house mode the operator is the book. The price on the button is Lukk's price plus the operator's margin add-on, and the add-on is adjusted for the liability the operator already carries on that outcome, so the price offered reflects the book's position the way a sportsbook trades a market. The player sees decimal odds, taps once and, if accepted, holds a ticket at exactly that price: a ticket at 3.50 on a 10.00 stake pays 35.00 if it wins, never more or less. Because the margin is the operator's, so is the revenue; Adkuu's published commercial model is a revenue share of 5–8% of GGR with no upfront fees.
AMM mode: fair-curve fills at the live probability
In amm mode a fill is taken from a fair curve at the live probability rather than from a margined house price, so the price a player gets moves with the probability the AI is tracking rather than with the operator's book management. This is the mode to compare with pool betting and with the automated market makers used by peer-to-peer prediction exchanges. Which mode an operator runs is set on its account; the markets, cameras, settlement and wallet contract are the same in both.
How a price is locked
A tap is a request, not a fill. The sequence is the same in both modes:
| Step | What happens |
|---|---|
| Quote | On the feed path the operator fetches a quote for the market (GET /api/v1/b2b/quote/ followed by the market slug); the quote has a TTL and expires if unused |
| Tap | The player backs an outcome at the price shown |
| Acceptance delay | One to three seconds, during which the deterministic tracker holds an in-flight veto |
| Price protection | If the price moved, the ticket takes the price then current; if the outcome was suspended, the ticket is refused |
| Ticket | Odds locked, rule_hash attached, payout fixed at stake × odds |
Rejections come back with a reason: price_moved, quote_expired, in_flight_event, suspended, outcome_suspended, circuit_breaker, betting_closed, stale_price and oracle_lag from the pricing and acceptance side, and min_stake, max_stake, max_payout and insufficient_funds from the limits and the wallet. In the widget path the same pipeline runs behind the button and the postMessage bridge reports lukk:bet to the operator's page. Clock sync is available at GET /api/v1/b2b/time.
Limits, set per operator
Every account carries a minimum stake, a maximum stake and a maximum payout per bet, all in the operator's currency (EUR, USD, SOL and others), plus per-outcome liability caps and circuit breakers. Acceptance is suspended on decisive events or stale prices, oracle lag is measured so that a player on a delayed stream can be refused but never filled stale, and operator and global kill switches sit above everything. The stake presets on the button (up to six) are the operator's as well.
How the trading desk sees exposure
Lukk, by Adkuu, gives operator traders a risk desk: fair and margined prices side by side, exposure limits, circuit breakers, payout holds and a backoffice, with backoffice self-service on the roadmap. Exposure data also flows through the integration itself. The feed snapshot carries limits, status and recent settlements; settlement webhooks (X-Lukk-Event: settlement, at-least-once, with exponential backoff) and the pull endpoint GET /api/v1/b2b/settlements return page totals for netting; and the daily reconcile call cross-checks both ledgers, with Lukk alarming on any divergence and never auto-adjusting. Larger payouts carry a short verification hold before the credit is queued. The wallet mechanics are in How Does a Seamless Wallet Integration Work for Live-Camera Betting?, and the controls that keep the price honest are in Can Players Cheat or Manipulate Live-Camera Betting Markets?.
How this compares
Counting games such as 155.io's Rush Hour fix one market shape, how many objects cross an AI tracking zone, and let players bet Over, Under, Range or Exact; Lukk's AI writes questions in five shapes (race, first-to, count, happen, state-at-close) and prices each live as a YES/NO or multiple-choice market with locked odds. Sports micro-betting prices next-play markets inside a match from sports data; live-camera markets are priced from the vision layer's own reading of the scene. Each is a design choice about where the price comes from. More on the feed and the widget at Lukk for operators.
Sources
- CCTV betting: Accessible innovation or an integrity nightmare waiting to happen?
- What Is Betting on Traffic and Where to Gamble on CCTV Traffic Footage?
- AI-driven micro-markets: Betting on moments, not matches
Last verified: October 10, 2026.