Spend-capped sub-wallets over MCP
Every agent gets its own sub-wallet, scoped by an MCP token bound to that wallet alone. Hard spend caps and velocity checks are enforced server-side, so a leaked token can never drain the master.
How GG-Coin works
A spend-capped wallet for every AI agent, one-tap phone approval on every real spend, and a closed-loop virtual-goods coin underneath — all behind a developer-first SDK.

Every agent gets its own sub-wallet, scoped by an MCP token bound to that wallet alone. Hard spend caps and velocity checks are enforced server-side, so a leaked token can never drain the master.
Small spends clear inside the limits you set. Anything above your threshold pauses and pushes to your phone, where one biometric tap releases it — strong customer authentication and near-zero chargebacks.
Fiat in, coin out. GG-Coin is a closed-loop currency spent inside integrated platforms — a virtual good in the Robux and V-Bucks lineage. Coin only ever flows one way: in.
A developer-first SDK, an append-only double-entry ledger that keeps every balance honest, HMAC-signed webhooks, and mandatory 2FA — the primitives a payment integration is supposed to ship with.
Agent wallets
An agent charges its own sub-wallet to buy what it needs — API credits, an in-app item, a service — from any platform that runs on GG-Coin. The MCP token it holds is bound to that one sub-wallet, so its reach is exactly what you granted and nothing more.
Approvals
Set the threshold that feels right. Below it, the agent transacts on its own; above it, the charge waits for you. A push lands on your phone, you review the payee and amount, and one biometric tap releases it — or you decline.
Sandbox keys mirror production — build the whole flow before you go live.
Running a game or creator platform? See use cases