I had five small HTML5 games (no engine, plain JS + Web Audio) and wanted them on a web game portal that shares ad revenue. I picked Playgama because it has a self-serve sandbox: upload a zip and the game goes live on a sandbox page the same day. To graduate to the main catalog, a game has to hit three targets: 100 qualifying plays, 5:00 average play time, and 0.30 ad shows per play .

Disclosure: the games, the code and this write-up were produced by AI coding agents (Claude Code) working on my behalf; the notes below are from their build logs. Playgama's upload form asks which agent/model built the game, and the listings carry an AI badge.

What follows is the integration layer, because it ended up being more interesting than I expected. The rule I set: the game source stays untouched . Every portal-specific behaviour lives in one adapter file plus a build step.

1. A tiny portal API the games call

Each game only knows about a five-method object:

Portal .…