What Is a Live-World Betting Feed for Operators?
A live-world betting feed is Adkuu's term for Lukk delivered as data: the stream, AI-written markets, prices, rule hash and settlements over REST, WebSocket and gRPC.
A live-world betting feed is Adkuu's term for Lukk delivered as a data feed rather than as a widget: the live camera stream, the AI-written markets on it, their prices in both a fair and a margined view, timing, status, limits, the frozen rule hash and the settlements, served over REST, WebSocket and gRPC so an operator can render live-camera betting inside its own front end. The operator keeps the player relationship and the funds; Lukk supplies the stream, the markets, the pricing and the settlement, and money moves through the operator's own wallet API per transaction, like any other game provider on the floor.
What the feed contains
A snapshot from GET /api/v1/b2b/feed carries everything needed to show a market and take a bet on it:
| Field group | What it holds |
|---|---|
| Stream | The channel's live camera broadcast, synchronized for every viewer |
| Markets | The current AI-written question in one of five shapes (race, first-to, count, happen, state-at-close), YES/NO or multiple choice |
| Prices in both views | Fair probabilities and margined fixed odds for each outcome |
| Timing and status | When acceptance closes and the window begins and ends, and whether the market is open, suspended or settled |
| Limits | Minimum stake, maximum stake and maximum payout per bet, in the operator's currency |
| Rule hash | The frozen rule_hash that pins the settlement contract before the first bet |
| Recent settlements | The latest results, each as won, lost or refunded |
Schemas are versioned (lukk.feed.v1 for the feed, lukk.webhook.v1 for settlements).
Transports: REST snapshot, WebSocket with resume, gRPC
- REST for the snapshot:
GET /api/v1/b2b/feedfor the current state andGET /api/v1/b2b/timefor clock sync, so the operator's front end counts down in step with the stream. - WebSocket for live updates:
wss://api.lukk.gg/ws/v1, topicb2b:feed, pushes every price, status and timing change, with resume, so a reconnecting client picks up where it left off instead of re-reading the snapshot. - gRPC as a mirror of the same feed for operators whose platforms prefer it.
- Quote to ticket for placing bets:
GET /api/v1/b2b/quote/followed by the market slug returns a quote, andPOST /api/v1/betsturns it into a ticket; the ticket locks its odds when it is accepted, one to three seconds later. - Settlements as signed webhooks (
X-Lukk-Event: settlement, HMAC-SHA256 inX-Lukk-Signature, at-least-once with exponential backoff) and a pull endpoint,GET /api/v1/b2b/settlements, with page totals for netting.
Every call is signed with the operator's API key, and every money movement carries an idempotency key. Lukk never holds player funds and never sees a name, email or balance, only an opaque player_ref.
Widget or feed
Lukk ships two integration paths that share one identity model, one wallet contract, one risk engine and one settlement backbone; many operators run both.
| Widget (iframe) | Feed (API, WebSocket, gRPC) | |
|---|---|---|
| What the operator builds | A launch flow and a thin chrome (close control, balance) | Its own market display, bet slip and stream player |
| How a session starts | The operator's backend mints a single-use launch session at POST https://api.lukk.gg/api/v1/b2b/embed/sessions with the x-operator-key header; the token expires after 120 seconds and the returned launch_url is the iframe source | The operator's platform reads the feed and places bets through quote and ticket calls |
| Security | Locked to the operator's registered origins by a per-operator frame-ancestors policy | Signed calls with the operator API key |
| Events | A postMessage bridge reports lukk:ready, lukk:bet, lukk:session_expired, lukk:relaunch_request and lukk:error, and accepts lukk:relaunch, lukk:theme and lukk:refresh_balance | WebSocket updates and settlement webhooks |
| Branding | Semantic colours derived into a palette, typography, corner radius, chrome switches, up to six stake presets; English today, locale accepted for a localised widget later | Entirely the operator's own front end |
| Effort | An afternoon | Days |
The widget launches like a game, full viewport, always loads from a static edge, and shows a calm "Lukk isn't available at the moment" screen if the API is unreachable.
How it sits next to sportsbook and casino content
A live-world betting feed is a third kind of content, not a replacement for either of the existing two. A sportsbook feed delivers odds on scheduled matches, and in-stream products such as Betby's "Watch & Bet" (August 2026) lay those odds over the broadcast; casino content delivers RNG games, crash games, virtual sports and live game shows. Lukk is a real event on a real camera with betting semantics, priced and settled like a fixed-odds market and launched like a game. Because money moves through the operator's wallet with four endpoints (debit, synchronous and fail-closed: no debit, no bet; credit, queued and retried until delivered; rollback; and a daily two-party reconcile, on which Lukk alarms on any divergence and never auto-adjusts), it fits the same seamless-wallet pattern the operator already runs for its other providers.
Distribution is the other difference. 155.io's Rush Hour reaches operators through direct integrations and through Hub88, its exclusive aggregation partner since 26 February 2026; Lukk integrates directly rather than through an aggregator as of October 2026. Adkuu's other feed, Pulse, delivers prediction markets on real-world outcomes the same way, so an operator can run live-camera markets and prediction markets side by side on one commercial model.
Certification, limits and commercials
- Certification runs on a play-money account on the production surface (an operator disabled for real money); a dedicated sandbox host is on the roadmap. Keys rotate on request.
- Compliance split. The operator owns the licence, the player, the funds, KYC/AML, age verification, responsible-gambling limits and self-exclusion, geofencing, terms and disputes. Lukk is a PII-free supplier with per-ticket limits, acceptance delay, suspensions, breakers, kill switches and jurisdiction control over which markets an operator may serve. Regulatory classification of camera-resolved event contracts differs by jurisdiction and is worked through per market with the operator's legal team; Lukk carries supplier KYB, licensing and certification tracks on its side.
- Commercials. Revenue share of 5–8% of GGR, no upfront fees.
- On the roadmap. Bet-placed and bet-cancelled webhooks, session-level limits and reality-check hooks at launch, operator-owned cameras and exclusive low-latency streams, partner scene packs, backoffice self-service and a localised widget.
The operator-facing summary is at lukk.gg/operators; how the markets in the feed are written and priced is covered in What is an AI-written betting market?, and the product overview at /solutions/lukk.
Sources
- Hub88 chosen as exclusive aggregation partner for 155.io's breakthrough CCTV game Rush Hour
- Betby Watch and Bet live streaming feature
- AI-driven micro-markets: Betting on moments, not matches
Last verified: October 10, 2026.