API access
Same data on every plan. The difference is window and frequency.
Every plan reads the same live feed and the same fields. What changes is how far back you can page with /v1/history and how often it's worth polling.
Plan ladder
Four plans, one schema.
History windows are hard limits — cursor paging on /v1/history stops at your plan's edge and returns next_cursor: null. Requesting past the window returns 402 window_exceeded.
300 req/mo · poll ~2 hours
10,000 req/mo · poll ~4 minutes
150,000 req/mo · poll ~17 seconds
1,000,000 req/mo · poll ~3 seconds
ULTRA's ~17 second polling interval is shorter than the fastest table's spin cycle, so it catches every round on every table we track. Evolution listings have no MEGA tier — their capture history isn't old enough yet to promise a 30-day window.
RapidAPI listings
10 listings across three providers.
Each listing is its own product on RapidAPI, with its own key and its own plans — BASIC, PRO and ULTRA everywhere, MEGA where the table's history is deep enough (not yet on Evolution). Subscribing to one listing does not grant access to another provider's tables.
Playtech
12 live-dealer tables in a single listing.
Ezugi
5 live-dealer tables, sold individually and as a 5-table bundle.
Evolution
3 live-dealer tables, sold individually. No MEGA tier — history is younger here.
Honesty
What these numbers do and don't mean.
Coverage is measured, not claimed
Playtech, Ezugi and Evolution each operate more tables than we capture. We publish results for 12 Playtech, 5 Ezugi and 3 Evolution live-dealer roulette tables — not a claim about the rest of their catalogue.
Live data is identical across plans
/v1/livereturns the same fields no matter which plan you're on. Plans differ only in how far back/v1/historycan page and how much request volume you get per month.Gaps are marked, not hidden
When a table has a missing span, history responses include it as an explicit gap object rather than silently closing the hole. Recovered rounds are flagged
backfilled: true.
Read the reference
Endpoint details live on the docs page.
Request shapes, error codes and field definitions for /v1/live, /v1/history and /v1/meta.