Focused on slot math
Cymba resolves slot outcomes. It does not provide a full casino platform, payment processing, or player management.
Casino Game API
Cymba is a casino game API focused on the slot math surface. Studios and operators send a game config, receive a provably fair spin result as a multiplier, and keep wallets and player accounts in their own platform.
API example
POST /api/v1/spin
Authorization: Bearer cy_live_...
{
"config": "golden-pyramid",
"lines": 25,
"client_seed": "session-99"
}
{
"result": {
"round_id": "01JR8X5Q...",
"summary": {
"total_multiplier": 100,
"breakdown": {
"free_spins": 100
}
},
"result_hash": "3c8f22...",
"config_hash": "f91a44..."
},
"provably_fair": {
"server_seed_hash": "9b1e3c...",
"client_seed": "session-99",
"nonce": 44
}
}
A casino game API is a backend service that provides the outcome logic for casino-style games. Rather than building RNG, evaluation logic, and game mechanics into your own platform, you call an API with a game definition and receive the resolved result.
Cymba is a casino game API focused specifically on slot math. It covers the full surface area of slot mechanics: reel strips, paytables, win evaluation across payline, ways, cluster, and count-pay modes, free spins, cascades, hold and respin, wilds, multipliers, meters, and jackpots.
It does not cover table games, live dealer, sports, or other casino verticals.
The teams that get the most from Cymba are usually building slot-style games for a specific platform and want to buy rather than build the math layer.
That includes social casino studios that need configurable slot math for free-to-play apps, sweepstakes operators that need clean math separated from their coin economy, crypto casino teams that need provably fair outputs, white-label platforms that want reusable slot mechanics across brands, and indie developers prototyping before hiring math specialists.
In each case the pattern is the same: the team owns the player experience and platform, Cymba owns the math.
Cymba returns multipliers, not payouts. The API result tells you the game outcome expressed as a factor — total_multiplier of 25 means the spin produced 25× the line bet. What that means in currency, virtual coins, or sweepstakes entries is determined entirely by the calling platform.
That boundary keeps Cymba out of the wallet and compliance surface. Operators control the money movement. Cymba controls the math.
Cymba treats game configs as first-class product objects. Each game is defined as a JSON config stored in the dashboard with a unique ID. The same config is used for the spin API, RTP calculation, playground testing, and PAR sheet export.
Adding a new game to a platform means creating a new config. Updating a game's math means editing the config, validating, recalculating RTP, and redeploying the config ID. No engine code changes required for common mechanics.
For platforms that need to demonstrate their games are fair, Cymba includes provably fair material on every spin: server seed hash, client seed, nonce, result hash, and config hash. PAR sheet exports package the config, RTP data, and deterministic replay fixtures into a reviewable artifact.
That combination gives operators a concrete response to regulatory or player-facing questions about game integrity.
Cymba is not a casino platform. It does not include a player lobby, game launcher, payment processor, bonus engine, KYC system, or licensing framework.
Those layers belong to the platform built on top of the math API. Cymba's role is narrower: resolve slot outcomes correctly, produce verifiable results, and give teams the tooling to manage and audit game configs.
Start with a free API key, clone a template, and run your first provably fair spin.