Overlay for Singular.live
One HTTP call, polled every ten seconds, bound to the widgets of a Singular composition. It returns a derived number and nothing else — no runs, wickets, overs or odds — so it sits on top of whatever match feed a production already runs.
The figures above are a worked example. Enter a live match ID and a key to drive the overlay from the real endpoint.
81.5% across 19,340 predictions on 2,546 matches held out of training,
with the ten-bucket calibration table beside it — and the
unflattering cuts in the same response: 79.4% across the 18 major
competitions, 77.2% on the IPL.
Open /v1/accuracy,
no key needed.
Singular opens one request per output URL, not per viewer. A three-output production is three requests every ten seconds. Viewer numbers never reach the endpoint.
A ball takes about forty seconds and the feed behind the probability measures p50 133s stale. Polling faster shows the same number more often.
Four overs into an innings, too little has happened for the number to mean much. The API flags it and the overlay says so, rather than showing a confident-looking figure built on nothing.
A dropped request is logged and otherwise ignored. The graphic never blanks and never flashes a zero mid-match.
T20 and T20I only; the published accuracy covers nothing else. Single instance, no SLA on self-serve. Analytics and media use — not betting advice.