---
title: Connect your platform
description: Implement the OneHazel Operator Contract once and every game studio, KYC, payments and responsible-gaming vendor in the Marketplace works against it.
---

# 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](/connect/start-here) is the one path from a new OneHazel account to a game live on your casino, in fifteen stages.

## Modules

| Module | Who calls whom | What it is for |
|---|---|---|
| `wallet` | OneHazel calls you | Seamless wallet for every game studio: session, balance, bet, win, rollback, free rounds |
| `player` | OneHazel calls you | Player facts (currency, country, status, restrictions) for studios, KYC and responsible gaming |
| `webhook.receive` | OneHazel calls you | Event delivery (KYC verdicts, responsible-gaming actions, payment outcomes) |
| `launch` | You call OneHazel | `POST /connect/v1/launch` and `/demo-launch` return a game URL |
| `events.push` | You call OneHazel | Push players, transactions and sessions in ([Data Ingestion](/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](/connect/getting-started): six steps, each ending in a check you can run.
2. **With a sample.** Start from a [generated sample](/connect/contract#samples) 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](/connect/mcp).

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

## Pages

- [Start here](/connect/start-here): the whole path, from a new account to a game live on your casino
- [Getting started](/connect/getting-started): the six-step track with a Check per step
- [The contract](/connect/contract): wire rules, operations, errors, samples
- [Conformance](/connect/conformance): the scenarios OneHazel runs before a module goes live
- [Connect with MCP](/connect/mcp): let a coding agent do the build
- [How to integrate with AI](/connect/how-to-integrate-with-ai): the step-by-step for the person setting up the agent
- Module guides: [wallet](/connect/modules/wallet), [player](/connect/modules/player), [webhook.receive](/connect/modules/webhook-receive), [launch](/connect/modules/launch), [events.push](/connect/modules/events-push), [attribution](/connect/modules/attribution), [widget](/connect/modules/widget), [payments.intent](/connect/modules/payments-intent)
- [Troubleshooting](/connect/troubleshooting): symptom, cause and fix
- [FAQ](/connect/faq): questions engineers and CTOs ask first
- [Samples guide](/connect/samples): what each sample contains and how to run it