---
name: ggbucks-game-integration
description: "Plan or implement a new game integration with the public ggbucks sandbox API, project and game caps, public client configuration and server-only credentials. Use when integrating a game portfolio; does not publish an SDK or authorize live payouts."
metadata:
  contract_hash: 99f61c25ff0e1d95f3711fa3a0afb27a00b8caafa4667f2aa0b18432aafb1006
  generator_version: "1"
---

# ggbucks integration starter

Implement the user's chosen game architecture. Confirm invited portal access and organization membership, then use the developer portal UI to create the organization, projects, games, finite caps, reward rules and separate public/secret keys. Do not invent long-lived developer bearer provisioning or use game keys for console authentication. The developer session comes from invited sign-in at developers.ggbucks.com; the docs site needs no login. Build reviewable code/configuration before authorized remote setup. Choose public client reads versus authoritative server event delivery; do not convert client telemetry into proof of gameplay. Plan consent readiness before promising linked players. Read [references/integration.md](references/integration.md) for current boundaries and [references/openapi.json](references/openapi.json) for exact operations and console action variants. The reusable [server example](assets/game-server.mjs) performs no calls on import; adapt it to the host's authenticated player identity, authoritative action and durable outbox.

All accounting is sandbox TEST ggbucks with no cash value; project/game hard caps remain enforced. The skill implements the requested integration and does not authorize deployment, account enforcement, messaging, key changes or live financial mutations. Generated from contract `99f61c25ff0e1d95f3711fa3a0afb27a00b8caafa4667f2aa0b18432aafb1006`; refresh this bundle when the current contract changes.