Skip to main content

​
Source API contracts

  • GET /health: application identity, configured ports and advertised integration names.
  • GET /api/mechmock/templates: four seeded device/browser frames.
  • GET /api/mechmock/logo-mocks: the checked-in mock asset manifest, or HTTP 404.
  • GET /api/mechmock/logo-final: the checked-in final asset manifest, or HTTP 404.
  • POST /api/mechmock/generate: a generated demonstration receipt with a fixed sample image.
  • POST /api/mechmock/share: an in-memory share record and generated share URLs.
  • POST /api/mechmock/fleetboots-dispatch: an in-memory render-job receipt.
The current server has no dedicated share-record read handler. Returning a share URL does not establish that a second browser can load the saved design. Process-memory records are lost when the server restarts.

​
Google and Eyedbase

MechMock’s selected owner is neostile81@gmail.com. Its project is mechmock-production; its planned Google callback is the production Eyedbase google-mechmock broker endpoint. OAuth creation, broker hydration, the product OIDC client, real sign-in and product entitlement must be accepted individually. Credentials belong in infrastructure’s approved authority and never in public documentation or browser code.

​
GPU generation

The current generation handler creates its response locally. The model, execution-time and hardware fields in that response are demonstration data, not a measured inference result. Live acceptance requires a source-bound inference execution and its actual generated artifact.

​
Fleetboots rendering

The current dispatch handler records a job in memory without contacting Fleetboots. Live acceptance requires a real fleet execution, its result artifact and a completed product workflow. A DISPATCHED_TO_FLEETBOOTS label alone is not an execution receipt.

​
Documentation delivery

The designated Mintlify project is mechmock, owned by the same primary app owner. Desired source binding is canonical GitLab project 108, branch master, content root mintlify. The existing hosted starter is separate from published product content, custom-domain validation and automatic GitLab synchronization.