Config in, result out
Define reels, symbols, paylines, ways, clusters, free spins, cascades, and bonus mechanics in JSON.
Slot Math API
Cymba lets game teams send a JSON slot config and receive a complete, provably fair spin result as multipliers. You build the player experience; Cymba handles RNG, win evaluation, RTP tracking, and audit-ready outputs.
API example
POST /api/v1/spin
Authorization: Bearer cy_live_...
{
"config": "book-of-secrets",
"lines": 10,
"client_seed": "player-session-123"
}
{
"result": {
"round_id": "01JQ5K8X...",
"summary": {
"total_multiplier": 25,
"breakdown": {
"payline": 25
}
},
"result_hash": "d4e5f6..."
},
"provably_fair": {
"server_seed_hash": "a3f1c8...",
"client_seed": "player-session-123",
"nonce": 42
}
}
A slot math API is a backend service that resolves slot outcomes for a game. Instead of embedding random number generation, reel evaluation, payline logic, free-spin recursion, or bonus mechanics inside your own platform, you call an API with a game definition and receive the resolved result.
Cymba is built for teams that want to ship slot-style games without maintaining a custom math engine. A studio can define the rules of a game as JSON, store that config in Cymba, and call /api/v1/spin whenever its own app needs a result.
The response is not a balance update and not a bet settlement. It is a math result: grid positions, wins, feature events, total multiplier, and verification material.
Cymba is mainly for B2B builders in gambling-adjacent and game-adjacent markets:
The product is most useful when you already have a front end, wallet, player system, or platform layer, but you do not want to own the slot math surface yourself.
Cymba handles the deterministic math layer behind a spin. That includes RNG outcome generation, reel stop selection, win evaluation, feature resolution, result serialization, config validation, spin logging, RTP tracking, and audit exports.
The engine supports traditional paylines, ways-to-win, count-pay, and cluster-style games. It also supports common slot mechanics such as free spins, cascading reels, hold and respin, mystery symbols, wild features, dynamic reels, random multipliers, meters, jackpots, and gamble rounds.
For operators and studios, the important part is that these are config-driven. A game team can change the game definition without rewriting the math code that evaluates it.
Cymba deliberately does not handle money.
It does not provide wallets, balances, player accounts, KYC, jurisdiction checks, licensing, currency conversion, or operator compliance. Cymba returns multipliers. Your platform decides what a multiplier means for a particular player, bet size, jurisdiction, and currency.
That separation keeps the product focused: Cymba is the math and verification layer, not the casino.
Slot math is easy to underestimate. A simple three-reel game can be implemented quickly, but production games usually need repeatable RNG, seeded replay, feature recursion, max-win caps, RTP calculations, audit logs, and edge-case testing around bonus rounds.
Building that in-house means your team owns every bug in the payout model. It also means every new mechanic adds more test and audit surface.
Cymba turns that work into an integration problem. Your team sends a config, receives a result, stores whatever records it needs, and focuses on the player-facing product.
Every spin can be tied to provably fair material: server seed hash, client seed, nonce, result hash, and config hash. After seed rotation, previous spins can be replayed and verified.
For game configs, Cymba can export PAR sheets that include the canonical config, theoretical RTP data, the full math reference, and deterministic replay fixtures. This gives operators and math consultants a concrete artifact to inspect instead of a vague promise.
The fastest path is to create a free API key, clone a template, and run a spin from the dashboard playground. From there, you can edit the config, validate it, calculate RTP, export a PAR sheet, and call the public API from your own application.
Cymba is currently beta-first: free testing is open, while paid production tiers are waitlisted as billing, legal, and audit workflows harden.
Start with a free API key, clone a template, and run your first provably fair spin.