01 / GETTING STARTED

Starting a check

1. Open “Checks”. Enter a domain or URL in “Domain or site URL”. The check collects the homepage and its loaded resources.
2. Click “Start check”. The job appears in the shared history. The current API cost limit per check is shown below the form.
3. If the domain has been checked before, choose an action. In “Domain already checked”, “View” opens a saved record and “Check again” requests a new check. An eligible successful result without limitations may be reused in the same report language. Check the date and ID of the opened result.

02 / CHECK PROGRESS

Analysis stages

1. Homepage collection. The browser saves content, screenshots, and network requests in HAR, an archive of the original data exchange. API calls, WebSocket URLs, and accessible resource code are included. Ordinary checks do not browse internal pages or launch games.
2. Signature matching. Traces are compared with manually confirmed and agent-confirmed platform references, and with saved checks of other sites.
3. Company identification. Known platforms are matched against the catalog. Sources about the company and its products are checked separately for new names and external domains.
4. Conclusion review. The researcher proposes hypotheses, the critic reviews them, and the judge assesses available evidence. The outcome and original materials are saved in the check details.

Jobs run in sequence. History and the open check update automatically. “Last successful stage” in “Check details” shows saved progress.

03 / NAVIGATION

History and statuses

In “Checks” search for the domain, check the date, and click the domain or “Open ↗”. To return from the details, click “← All checks”.

Queued / Running

The job is queued or running. The details show the current stage and “Queued” or “Running” status.

Completed

Processing has ended. The platform may remain unidentified, and the result may include limitations. Read the explanation and check for a final assessment.

Geo-blocked

A restriction in the checking region is confirmed. No final score is assigned; the reason and available actions appear in the details.

API cost

Cost of model calls. “≈” indicates an estimate, and “No data” means cost information is unavailable.

History is shared among authorized team users. Materials reflect the date of each run.

04 / INTERPRETATION

Scores and signature coverage

The column “White-label confidence” and large percentage in the details show the final assessment of support for an iGaming platform connection based on collected data. 50% does not mean a 50% probability that the entire site uses a white-label solution.

100%

The connection is confirmed under the service rules or manually. Automatic results require a technical trace and identification of the supplier as a platform. Manual confirmation has a separate label and the user's stated basis.

1–99%

Judge assessment based on available evidence. For example, a site loads a third-party resource, but the company's role as a platform supplier is unconfirmed. The reason for the specific score is shown in the details.

0%

No supporting platform connection found. Materials may still contain operator names and unverified candidates. A zero score does not prove in-house development.

—

No final assessment. Analysis is still running, or the available data or completed judge response is insufficient for an assessment.

The “Reference coverage” block shows a different metric: the fraction of matching signals in a saved capture. For example, 3 matches out of 5 give 60% coverage. Sufficiently specific matches can yield a 100% connection score even if some APIs differ.

05 / READING THE DETAILS

Evidence and confirmation

1. “Check result” and “Why this decision was made”. Review the score, platforms found, and explanation. Manual confirmation shows “Basis for manual confirmation” instead of the model's explanation.
2. “Check limitations”. Check which data could not be collected and how this limits the conclusion.
3. “Platform match and verification”. Each company has separate “Technical trace” and “Platform identity” fields. Loading a resource confirms a technical connection, but the company may still require identification.
4. “Evidence” and “Page screenshots” inside the platform card. Expand the available sections. Check quotes, URLs, and screenshots; materials are labeled “Trace on the checked site” or “Platform identity source”. Click a screenshot to open it separately.
5. “Signature recognition”. This contains known platform matches and sites with similar signatures. Expand “Reference coverage”, “Reference evidence chain”, or “Show signals” when available. Check the request URL, original capture, and reference date.
6. Download HAR and signatures. Links in the recognition section provide original requests and saved evidence. It also states whether delivery of original HAR data to the judge was confirmed.
7. “Check details”. This shows the last successful stage, API cost, URL, and run ID.

How to confirm a known platform. After the check ends, its author or an administrator can click “Confirm platform” beside a company. For another name, use “Specify another platform” or “Specify platform”. Choose an existing name or enter a new one, provide the basis, and save. Available verified signatures from this capture are attached automatically; no manual API selection is needed.

The result is labeled “Manually confirmed”. If the capture has no usable signatures, a platform name alone does not create a technical reference for future matches.

06 / CONTINUING WORK

Limitations and retries

Cloudflare, other access restrictions, DNS, timeouts, unavailable sources, and budget exhaustion may prevent a complete analysis. Read “Check limitations” and the last successful stage. “Completed” means processing of the available data has ended.

Usable homepage resources may be saved despite access restrictions. If a conclusion relies on them, read it together with the limitation. Without evidence for a final decision, the result remains without a confirmed platform or score.

If you see “Resume after…” or “Restart from the beginning”, the check's author or an administrator can use it. To run a fresh check, enter the domain in “Checks” and choose “Check again”. A new check will collect fresh data. If the queue is full, wait for space.

07 / TEAM CATALOG

Platforms, references, and access

White-label platforms

Search by name or domain. The table shows company identity, saved signature sets, and related checks. Statuses: “Known from team catalog”, “Supported by agent evidence”, and “Candidate: verification needed”. Click a platform name to see related sites without duplicates, domain search, connection basis, and links to checks. Run materials also expand in the catalog's “Evidence” column.

+ New platform

The button is at the top of the catalog. Enter the platform name and an operator site using it. Saving creates an entry and queues homepage collection; the form opens the new check. Collection requires administrator access.

Collect reference

The action beside a confirmed connection starts a new browser capture of the homepage and its resources. Usable signatures are saved for comparison with this platform. A 75% hypothesis alone does not become a reference.

Saved history

Comparison includes manually confirmed and agent-confirmed references with their original capture dates. A new HAR can confirm a previously saved signature of the same domain. Similar sites without an identified supplier are shown separately and are not assigned a platform name based only on similarity.

Access and sessions

Administrator section: user creation and deletion, roles, and sign-in history. Deleting a user revokes access and ends their sessions; check history is preserved.

A confirmed company profile in the catalog establishes who supplies the platform. Each checked site's connection is confirmed by its own data.