> ## Documentation Index
> Fetch the complete documentation index at: https://docs.musterbox.org/llms.txt
> Use this file to discover all available pages before exploring further.

# Build connected gaming experiences with MusterBox

> The MusterBox developer platform connects games to player identity, tournaments, match sessions, and secure purchases — from a single, engine-native SDK.

<span className="mb-eyebrow">MusterBox Developers</span>

The MusterBox developer platform connects games to player identity, tournaments, match sessions, and secure purchases — from a single SDK. The same core ships for Unity, Godot, Unreal Engine, Bevy, Cocos, Defold, and the browser.

**Get started**

<div className="mb-entry-links">
  <a href="/getting-started/quickstart">
    Quickstart
    <small>Connect a game to MusterBox in about ten minutes.</small>
  </a>

  <a href="/sdk/installation">
    Install the SDK
    <small>Packages and configuration for your engine.</small>
  </a>

  <a href="/api/api-overview">
    API reference
    <small>The verified public API contract.</small>
  </a>

  <a href="/getting-started/overview">
    Core concepts
    <small>How games, sessions, and claims fit together.</small>
  </a>
</div>

## 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](/resources/compatibility) — SDK versions, profiles, and the compatibility matrix.
* [Support](/resources/support) — Account, security, and integration help.
* [Changelog](/resources/compatibility#changelog) — Version history and migration notes.