cPanel
Use PHP 8.1 or newer with cURL, HTTPS and a writable private cache folder. No database or Node.js is required. Protect this private tool with cPanel Directory Privacy before connecting your key.
Open installation guide ↗Scores, cards, shots and match context. Automatic refresh while this tab is visible.
Add a provider key in the private server configuration. SportyBet automatic booking-code generation is not connected.
Configure your API-SPORTS key, then connect. No upcoming or completed fixtures are shown.
Live observations and model hypotheses, saved in this browser.
This package runs on PHP hosting and keeps the data key on your server.
Use PHP 8.1 or newer with cURL, HTTPS and a writable private cache folder. No database or Node.js is required. Protect this private tool with cPanel Directory Privacy before connecting your key.
Open installation guide ↗Direct API-SPORTS v3 connector for live fixtures and per-team statistics. Coverage varies; missing values remain “—”. A provider key and current-season access are needed. No key is collected in the browser.
Check coverage and plans ↗The “Book Bet” control was observed on a live selection. The external code-creation interface has not been verified. This package does not automate SportyBet betting or generate working codes yet.
The app describes who leads and compares the observed shots, shots on target, possession, corners and cards. More possession or shots alone does not establish which team is stronger or what will happen next.
Where both teams’ xG and red-card counts are available after 20 minutes, we estimate each team's goal rate as xG ÷ elapsed minutes × 90. Independent Poisson projections use those constant rates over the approximated remaining 90-minute duration. This crude extrapolation is untrained and uncalibrated. It ignores tactical changes and added duration for stoppage time. No recommendation is emitted when the input is missing, too sparse, stale, outside the model range, at half-time, at 90+ minutes, or affected by dismissals.
Fixture requests use a 15-second server cache; statistics use a 60-second cache because the provider describes minute-level statistics updates. The browser refreshes every 30 seconds while visible. “Retrieved” timestamps record when our server fetched the data, not the time of the most recent on-field event. Background refresh pauses.
One active browser watching one selected match uses approximately 180 provider requests per hour, plus initial requests and extra requests after score/phase changes or when switching matches. A local daily budget starts at 100 requests. The provider's free plan is useful for connection testing and has limited season coverage; it is not enough for continuous monitoring. Select a suitable allowance before increasing the local budget.