What we verify
Our catalogue separates published mathematical data from observable demo behaviour. Source-backed RTP values take priority. When a source feed does not publish RTP, the page displays a stable catalogue estimate and labels it as such until a verified value becomes available.
How catalogue pages are assembled
Structured game records are normalised automatically so tens of thousands of releases can use the same accuracy rules. Source reviews are preserved. Where source copy is missing or too short to explain the page, an automated editorial layer adds the recorded provider, release information, available mechanics, a demo inspection checklist and clear data limitations.
How the automated newsroom works
Our newsroom monitors an allowlist of regulator, supplier and established trade-publication feeds. One AI model extracts an atomic fact sheet, a separate model writes the article, and an independent model checks every factual claim against the source text. Deterministic rules reject unsupported numbers, thin articles, promotional gambling claims and failed localisations. Articles that do not pass every publishing gate remain unpublished. Each published page links its source and discloses the automated process.
What the demo adds
Every indexed game page links the written record to a working free demo. Readers can inspect the interface, paytable and feature rules directly. Demo outcomes are never presented as evidence for RTP or likely returns.
Ratings are never invented
Structured aggregate ratings are emitted only when reviews come from a documented, verifiable user-rating system. Editorial scores are kept separate. This keeps structured data representative of visible content.
Configuration matters
Some operators use different RTP configurations. Every review asks readers to confirm the value in the in-game help screen before real-money play.