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

# For Platform Operators

> How to deploy A2G as a channel into your gaming platform.

<Note>
  This section is **non-normative** — it provides implementation guidance and recommended patterns. The [Protocol Specification](/spec/overview) is the authoritative reference.
</Note>

A2G is designed to integrate with your existing gaming infrastructure as an additional communication channel — alongside your web frontend, mobile apps, and any other interfaces. Adding A2G does not require replacing your game engines, RNG systems, or identity infrastructure.

## Integration Architecture

```
┌──────────────┐   ┌──────────────┐   ┌──────────────┐
│  Web Frontend │   │  A2G Clients │   │  G2S / SAS   │
│  (Human UI)   │   │  (WebSocket) │   │  (Floor)     │
└──────┬───────┘   └──────┬───────┘   └──────┬───────┘
       │                  │                  │
       └──────────┬───────┴──────────┬───────┘
                  │                  │
            ┌─────▼──────┐    ┌─────▼──────┐
            │  Operator   │    │  Operator   │
            │  Platform   │    │  RNG / Game │
            │  (Accounts, │    │  Engine     │
            │   KYC, AML) │    │  (Certified)│
            └─────────────┘    └────────────┘
```

In this model:

* **A2G handles client communication** — identity verification, session management, game message routing
* **Your platform handles identity** — registration, KYC, payment methods, responsible gaming controls
* **Your game engine handles game logic and RNG** — using your certified systems
* **Account linkage bridges the gap** — binding A2G client wallets to your existing user accounts

## What You Need to Implement

1. **WebSocket server** supporting the A2G message format (envelope + payload)
2. **Identity endpoints** — SIWE challenge and verify (Section 6)
3. **Account linkage endpoints** — link and unlink wallets to user accounts (Section 6.5)
4. **Lobby API endpoints** — games, tables, game specs (Section 9)
5. **Funding endpoints** — balance, transactions, withdrawal authorization (Section 9.3)
6. **Message routing** from A2G envelope to your game engines
7. **Game specifications** for each game you host, with JSON Schema definitions

## What You Keep

* Your existing game engines and RNG systems
* Your existing identity/KYC infrastructure
* Your existing regulatory compliance framework
* Your existing payment processing
* Full control over game specifications and rules