Quickstart
Connect a game to MusterBox in about ten minutes.Install the SDK
Packages and configuration for your engine.API reference
The verified public API contract.Core concepts
How games, sessions, and claims fit together.
What you can build
- Published-game integration — your game launches with a match context and reports its outcome through a mutually-confirmed claims protocol.
- Player identity — the SDK handles login, token refresh, and logout; only the backend verifies identity.
- Secure purchases — PIN-verified purchases through the SDK’s
PurchaseClient, with an on-device integrity pre-flight. - Realtime events — submit events and receive session, wallet, and status events from the realtime event plane.
The core principle: the SDK is a bridge, not intelligence
The browser and the device are never the source of truth:- The backend owns identity and sessions.
- A match outcome is accepted only when both participants independently claim the same result using their own single-use session tokens.
- The SDK never sees wallet private keys — custody stays in MusterBox’s MPC layer.
Next steps
- Compatibility — SDK versions, profiles, and the compatibility matrix.
- Support — Account, security, and integration help.
- Changelog — Version history and migration notes.

