mechmocks.com alias, then use the quickstart and integration guide.
Current capabilities
The canonical server provides four seeded frame templates and reads the checked-in logo asset manifests when present. Its generation route returns a demonstration receipt and a fixed sample image. It does not call a GPU inference service from that handler. Share records and render-job records are held in process memory. The render handler constructs aDISPATCHED_TO_FLEETBOOTS response without sending a network request to Fleetboots. A receipt alone is not a completed render or durable share.
Account ownership
The primary app, Google Cloud and Mintlify owner isneostile81@gmail.com, matching the MECH family. The mechmock-production project and its primary-owner IAM are confirmed. Its web OAuth client is issued and the retained credential pair matches infrastructure’s protected/masked production authority. Broker activation, real Google sign-in and MechMock authorization remain separate acceptance steps.
Documentation source lives in private GitLab project ads/mechmock, branch master, under mintlify/. Hosted publication, the custom domain and automatic repository synchronization each require their own read-back.