WagerDB computes custom aggregates from its casino datasets — withdrawal timing, RTP changes, migration flows, vault reserves, settlement anatomy — free of charge for journalists and researchers. No sales, no NDAs, cite us with a link.
We maintain datasets nobody else publishes: vault reserves, RTP change events, player migration, solvency coverage, cohort survival, settlement anatomy. If the aggregate you need is a slice of data we already hold, we compute it for journalists and researchers free of charge — the queries are already written.
One email is enough. Write to [email protected] with the question in one sentence. The more precisely you state the population (which casinos, which window, which metric), the faster the answer. A prefilled template is on the live page.
Need the raw material rather than one number? The standing aggregates are published as downloadable CSV/JSON dumps with column dictionaries on /research/data-dumps — same attribution rule: cite wagerdb.com with a link.
WagerDB is an independent data operation: we have no affiliate contracts, no operator relationships and nothing to sell you. The datasets above exist because we collect them continuously for our own pages — public bet feeds, on-chain hot-wallet flows across eight chains, six-hourly balance snapshots, and a monitored RTP catalogue.
If you are a journalist or researcher and the aggregate you need is a slice of data we already hold, we will compute it for you, free of charge. The underlying queries already exist, so most requests are answered within a few days. We will tell you just as plainly when a question is outside our data.
Either a small CSV with the aggregate, or a short quoted passage with the number, the exact population it was computed over, the time window, and the method. Every figure ships with its caveats attached — coverage limits, sampling gaps, and what the number cannot establish. If you publish it, cite wagerdb.com with a link; that is the entire price.
We do not provide raw feeds, address-level data, or anything that would identify individual players. Aggregates computed over fewer than 50 distinct addresses are not released, to us or to you.
We will not run numbers supplied by an operator to check against ours, sign NDAs, give embargoes on data pages, or soften a figure. If a casino disputes a number, the dispute process is the same for everyone: publish the counter-evidence and we will audit our pipeline.
Yes. Distribution is the point: every citation of a WagerDB number in a published story is worth more to the project than a data-licensing invoice. There is no catch beyond the attribution requirement — cite wagerdb.com with a link.
Simple slices of existing datasets usually come back within a few days. Questions that need a new collector or a longer observation window take as long as the data takes, and we will say so up front rather than guess.
No. Everything we release is an aggregate over at least 50 distinct addresses. We never export wallet addresses, player identities or transaction hashes — not to journalists, not to operators, not to anyone.
Yes — that is what they are for. Quote them, chart them, print them. The only conditions are attribution to wagerdb.com with a link, and that the caveats we attach travel with the figure. If a number later turns out to be wrong we will publish the correction the same way.
Yes. Academic and policy research gets the same terms: free custom aggregates, attribution with a link, caveats included. For bulk use, the public dumps on /research/data-dumps cover the most common datasets with column dictionaries.