Methodology

Each slot record stores structured fields: name, slug, provider reference, game type, RTP, volatility, reel count, payline count, min/max bet, release date, and feature tags. Fields are populated from provider data and manual entry. No editorial scoring is stored.

Slots are assigned a slug on creation. Slugs are stable identifiers used in API paths and embed URLs. A slot is marked active when its metadata is sufficiently complete for public exposure.

Each slot is linked to a single provider record. Provider records store: name, slug, country of incorporation, and website URL. Providers are assigned slugs for stable URL routing.

Provider data is not scraped from third-party sources. Records are entered and maintained manually or via admin tooling.

Slots with a stored demo URL are checked on a 6-hour schedule via server-side HTTP requests. The check records response status, response time, and any redirect chain. Results are written to a validation log and the slot's availability_status field is updated accordingly.

Availability state reflects the most recent completed check. Historical check logs are retained for trend analysis.

working

Demo URL returned HTTP 200 within timeout threshold.

slow

Demo URL returned HTTP 200 but exceeded response time threshold.

blocked_geo

Demo URL returned a geo-restriction response (e.g. 403/451).

broken

Demo URL returned an error (4xx/5xx) or did not respond.

unknown

No check has been completed yet for this slot.

The API exposes slot and provider data as structured JSON. All endpoints are read-only. No authentication is required for public reads. API responses use an explicit field allow-list; fields kept for operations only are omitted from public JSON.

The API does not return rankings, recommendations, affiliate links, or editorial data of any kind.

• —No rankings or slot recommendations
• —No affiliate links or casino CTAs
• —No editorial content or review language
• —No real-money wager functionality
• —No user accounts on the public surface
• —No tracking beyond server-side infrastructure logs

SlotIndex is operated by Evergreen Media AS. Data provenance, infrastructure decisions, and validation logic are the responsibility of Evergreen Media AS.