Everything the casino list is built from is published as plain JSON, served straight from this site. No key, no rate limit, no endpoint to learn: fetch the file and read it. The counts below are read out of those files at build time.
| File | What it holds | Size |
|---|---|---|
/data/casinos.json |
Every casino on the list with its tier, daily value, welcome offer, minimum redemption, operator and links. 149 records. | 129 KB |
/js/state-data.json |
Per-casino restricted-state data, keyed by slug: 173 keys, including 116 brands that have left the list. | 41 KB |
/data/payout-speeds.json |
Researched payout reads, each with the source and date of the read. 24 records. | 2 KB |
/data/state_law_baseline.json |
The state law floor: what each state's own rules allow, with a source per row. 17 states. | 5 KB |
Each casino record carries 22 fields:
_idx, name, tier, editorialTier, daily, dailyRaw, welcome, redeemRaw, redeemNum, redeemed, notes, canada, ontario, parent, restricted, signupUrl, reviewUrl, slug, logo, dv, pay, restricted_states
Tiers are editorial. daily is the researched daily free-play value,
redeemNum the numeric minimum redemption, and parent the operator behind
the brand. Which states a casino is restricted in lives in state-data.json, keyed by
the same slug, not inside the record.
No API, and no key. These are static files. If you need an endpoint, a commercial licence or a fresh read on demand, ask and say what for: contact.
The correction history is public: every fix lands in the corrections log with what changed and why, and the methodology page explains how the list is ranked and how the state data is built. Send a correction through contact.