OneHazel Docs

Appearance

For LLMsView as Markdown·

Connect your platform ​

The Operator Contract is the one surface your platform implements so OneHazel can plug any Marketplace vendor into it. You build each module once; every vendor that needs that module works the day you pass conformance. Per-vendor quirks stay inside OneHazel's adapters and never reach your code.

New here? Start here is the one path from a new OneHazel account to a game live on your casino, in fifteen stages.

Modules ​

ModuleWho calls whomWhat it is for
walletOneHazel calls youSeamless wallet for every game studio: session, balance, bet, win, rollback, free rounds
playerOneHazel calls youPlayer facts (currency, country, status, restrictions) for studios, KYC and responsible gaming
webhook.receiveOneHazel calls youEvent delivery (KYC verdicts, responsible-gaming actions, payment outcomes)
launchYou call OneHazelPOST /connect/v1/launch and /demo-launch return a game URL
events.pushYou call OneHazelPush players, transactions and sessions in (Data Ingestion)

You only build the modules the vendors you want need. Each Marketplace listing states its required modules.

Three ways in, one result ​

  1. By hand. Follow Getting started: six steps, each ending in a check you can run.
  2. With a sample. Start from a generated sample for your language and framework; it already verifies signatures, enforces idempotency and routes test traffic to a test ledger.
  3. With your coding agent. Point Claude Code, Cursor or any MCP client at OneHazel and let it build to the contract: Connect with MCP.

Nothing is MCP-only. Every step has a path through the app and the REST API.

Pages ​