Game content
25,000+ titles from 160+ studios through one integration, currency-aware from the first round. What the catalogue contains and how it reaches your lobby.
One integration, two currencies
The catalogue is requested in a currency context and a round settles in the currency it was launched in. A title runs as a Gold Coin game or a Sweeps Coin game through the same integration — there is no second catalogue and no second build.
That is the whole reason this works: the currency is established at the boundary, by the request, before anything is written. What that means for your ledger is set out on the wallet architecture page, and what it means for the mathematics is on RTP parity.
What the catalogue contains
25,000+ titles from 160+ studios, in seven categories.
- SlotsThe bulk of any catalogue, and the category the two-currency question is usually decided on.
- Fish gamesA sweeps-market signal. A catalogue without them is a real-money catalogue that has been pointed at this market.
- Crash titlesShort-round, high-frequency. Worth knowing how they behave against your reporting granularity before you enable them.
- Table gamesBlackjack, roulette, baccarat and the rest.
- Video poker
- Live dealerOperationally the heaviest category in the catalogue, and the one most worth confirming against your own launch date.
- SportsbookAvailable, and it sits under a different legal analysis from casino-style play — several of the 2026 state instruments treat sports wagering as its own subject. The state reference on this site covers casino-style sweepstakes and does not answer the sportsbook question.
How content reaches your lobby
Three steps and no surprises. You fetch the catalogue for a currency. You request a launch for a title and a player. The round executes at the studio’s game server and settles against whichever ledger holds the balance.
The commands, the authentication and the shapes are documentation rather than sales copy, and they live in the documentation — specifically the games reference. This page does not reproduce them.
What you control on each route
This is the cluster where the two routes stop being a variation on one product. On the API integration the catalogue is not a feature of a platform — it is substantially what you are buying, and the wallet callback exists so that the round can settle against your system.
| API integration — you run the platform | Managed platform — we run the platform | |
|---|---|---|
| The catalogue and the launch layer | casinoapi.tech | casinoapi.techThe one thing that is ours on both routes. On the API integration it is substantially the whole product. |
| Which titles appear in your lobby | You | YouYours on both routes. We supply the catalogue; what a player sees and in what order is your product decision. |
| Bringing a new studio onto the platform | casinoapi.tech | casinoapi.techWork on our side rather than an integration your team schedules. Making a newly available title visible in your lobby is then your lobby decision. |
| Running a title in a currency context | casinoapi.tech | casinoapi.techThe catalogue is requested per currency and the round settles in the currency it was launched in. |
| Where the round settles | You | casinoapi.techOn the API integration the round settles against your ledger — you are wallet of record. On the managed platform it settles against ours. |
| The mathematics of a title | The studio | The studioNeither of us. The model belongs to the studio that built it and is certified as their product. We distribute it; we do not tune it. |
The third badge is the one worth noticing. The mathematics of a title belongs to neither of us — it is the studio’s, certified as their product. We distribute it. Nobody at casinoapi.tech tunes a game’s model, and any supplier who implies they do is describing something you should ask more questions about.
Where this sits in the wider offer: the API integration and the managed platform.
How we count studios
160+ is not a round number somebody chose. It is 166 verified distinct studios, rounded down so it survives a recount.
Every competitor in this category publishes a provider count and none of them publishes how it was reached, which is why the counts do not agree with each other. Ours is set out in full on the providers page — the source, the normalisation, what was excluded and why, and what the number is not.
Where the integration is documented
The documentation is public and needs no sign-up. What Sweeps Coins can be won on is a product decision rather than a technical one, and it is covered on the currencies page.
Comparing us against an aggregator rather than a platform? The questions on the aggregation page are written to be asked of us too. Ask them.