Frequently Asked Questions

Q1: "Everyone claims a 'Single API,' but usually that just means a 'Least Common Denominator' integration. Do I lose the provider-specific features?"

A: We built our aggregator precisely because the industry is flooded with "single API" solutions that take shortcuts—flattening complex data into rigid, oversimplified schemas that strip out valuable provider-specific details like free spins configurations, Drops & Wins mechanics from Pragmatic Play, Evolution metadata streams, variable RTP bands, and more — just to make integration "easy" at the cost of real functionality.

We refuse to cut corners like that. Instead, we invest in great engineering: our API is carefully structured to deliver comprehensive, normalized-yet-rich payloads that preserve and expose as much provider-specific information and unique features as possible. Your devs get one clean, well-documented connection with full access to the powerful tools that matter, while your marketing team retains every edge — no compromises, no dumbed-down product. Simplicity without sacrifice.

Q2: "Can I adjust the RTP (Return to Player) to fit my margin strategy?"

A: Yes — and we make it transparent and direct, unlike most aggregators that hide, delay, or completely omit RTP information.

Many top providers (Pragmatic Play, Play'n GO, and others) offer games with variable RTP bands/range options. We expose these selector switches natively in the API, so you can choose the exact RTP level that aligns with your strategy — looser for player retention or tighter for bonusing/promotions. You control the math; we just deliver the full, up-to-date data without any aggregator interference or missing fields.

Q3: "How fresh is the data in your Back Office? 'Real-time' usually means 'cached for 15 minutes'."

A: We saw too many aggregators delivering delayed, stale reporting — and decided to fix it. Our event-driven pipeline pushes bet settlements, GGR, bet counts, and player activity to your analytics within seconds of happening. No 15-minute (or worse) caching.

This real-time visibility lets your fraud team spot bonus abuse mid-session, not after the player has already cashed out via crypto. In an industry where minutes matter, we don't make you wait.

Q4: "How do you handle Geo-blocking? I don't want your API deciding which of my players get blocked."

A: Traditional aggregators often overreach with blunt, automated blocking that kills legitimate traffic (like VIPs on VPNs) or leaves you blind to restrictions. We provide the raw intelligence instead.

Our API exposes detailed, provider-specific geo-restriction data for every studio — exactly which territories are restricted, per game/provider. You get the full map and decide the enforcement logic. Full compliance without us playing internet police or costing you conversions.

Q5: "What happens if your API actually crashes? Do I just get an apology email?"

A: We put our revenue on the line with real skin in the game. If monthly availability drops below 95% (true downtime, not excuses), we slash our margin by 50% for that period. This penalty is designed to hurt us more than you, so our team loses sleep to keep things online. No vague "best effort" clauses here.

Q6: "Can I host the front-end assets myself? Your CDN might be fast in Europe, but my players are in LatAm."

A: Absolutely — and we go further than most. We saw aggregators shipping outdated, low-res slot images and thumbnails that hurt load times and player experience, especially in emerging markets.

Our solution includes an Asset Pack endpoint for scraping/caching game thumbnails, loading screens, and all static assets on your own servers or local edge nodes. You fully control the last-mile delivery for players in Brazil, Lagos, or anywhere else.

Bonus: We use AI-powered tools to generate fresh, high-quality, customized visuals when needed — so your lobby always looks modern and optimized, never stuck with stale provider defaults.

Bonus (new Q7 – addressing the "why we exist" motivation):

Q7: "Why should I switch from my current aggregator?"

A: We launched because the market was broken: missing free spins & promotional feature support, no clear RTP/volatility metadata, zero geo-block transparency, terrible/outdated documentation, and constantly outdated game images/assets.

We fixed it all — full provider functionality preserved, real-time everything, complete data transparency, AI-enhanced/customizable visuals, crystal-clear OpenAPI specification, and ready-to-use client libraries in multiple programming languages (for seamless, fast integration). One connection. Zero compromises. Your platform deserves better.