Service Model and Responsibilities
Aggregator.gg provides B2B SaaS infrastructure for API authentication, routing, metering and technical connectivity between Operators and Game Providers.
How the service works
Operators purchase API processing and delivery capacity through prepaid packages. Aggregator.gg separately contracts with Game Providers and pays them at agreed rates for Metered Successful API Calls.
An Operator is the business that offers games to Players and manages their accounts. A Game Provider supplies the games and operates the remote game server (RGS). The Aggregator.gg Platform provides the technical connection between them.
The Operator’s platform initiates a game-session request through the Aggregator.gg Platform. The Provider’s RGS processes the request, creates the session and executes the game logic.
How usage is charged
Only Metered Successful API Calls, as defined in Schedule A of the Operator Service Offer, deduct from an Operator’s prepaid package.
Operator charges and Provider payments are calculated using agreed API-call rates. They do not depend on wager amounts, winnings, return to player (RTP), gross gaming revenue (GGR) or other gaming financial amounts. Aggregator.gg does not receive or distribute a share of GGR.
Failed calls and the non-billable categories listed in Schedule A do not deduct from the package.
Who is responsible for what
Operator
Player accounts and relationships, wallet and Player funds, applicable operating licences, Player verification and responsible gambling obligations.
Game Provider
Its remote game server (RGS), game sessions, game logic, random number generation, return to player (RTP) configuration and applicable game certifications.
Aggregator.gg
API authentication, routing, metering and technical connectivity, together with the obligations applicable to its own services.
The Operator manages the wagering relationship with the Player. Aggregator.gg is not a party to that transaction and does not accept, hold or transfer Player funds.
Market availability
Availability depends on Provider content restrictions and the requirements applicable to each party in the relevant jurisdiction. Technical access to a game does not establish permission to offer it in a particular market.
Regulatory classification depends on the jurisdiction and the activities actually performed. Each party is responsible for the licences, registrations or approvals legally required for its own activities.
Contract and data protection
This page summarises the service model. Detailed terms, metering rules, responsibilities and liability provisions are set out in the Operator Service Offer and its schedules.