Operator Mode

Technical walkthrough for sportsbook and compliance teams.

Inspect how the adapter, readiness layer, latency budget, responsible gambling controls, audit schema, and failure paths fit around the operator's existing authoritative systems.

Open Dashboard
Operator EmulatorIdle

Adapter request

Adapternorthstar-v1
P95318ms
Fail closedYes
Ready for simulationShake or tap to arm a fictional in-play opportunity.

Operator Adapter

Maps XBETR's simulated request into the sportsbook's market, token, wallet authority, and idempotency expectations.

Readiness Layer

Combines RTT, odds freshness, token status, market status, geolocation, and operator API health into Green, Yellow, or Red.

Latency Budget

Target flow stays under 1.8 seconds from gesture capture to accepted simulated submission.

RG Controls

Stake limit, velocity, cooldown, and self-exclusion checks run before any simulated submission can proceed.

Audit Schema

Every transition writes a timestamped event, fake device reference, odds snapshot, and hash-like audit marker.

Failure Paths

Biometric fail, network red, odds moved, market suspended, RG limit, timeout, and generic error all end safely.

State Machine

IdleWaiting for a simulated opportunity.

    Ask the Operator Agent