Build games for Slotdaddy.
The HTTP surface a running game speaks to the RGS, and the math contract that defines what a Slotdaddy game is. A small, focused API and a deterministic math format with replay built in.
HTTP API
Five endpoints: authenticate, balance, play, end-round, event. Idempotency, typed errors, schema versioning, and an optional realtime channel are built in.
- POST /wallet/authenticate · /balance · /play · /end-round
- POST /bet/event
- Idempotency-Key, typed error envelope, optional SSE
Math contract
What a Slotdaddy math package is, the book file format the runtime serves, and the typed event schema the client consumes.
- game_config / game_executables / reels layout
- book.json: deterministic, content addressed outcomes
- Typed BookEvent discriminated union
The wire shapes documented here are the player runtime surface a game client speaks to the RGS. The studio control plane (uploads, keys, environments) lives behind a separate, reserved path prefix and will be specified in its own document. Operator integration (wallet adapters, settlement webhooks) is handled per operator on a bespoke basis and is intentionally not documented here.