> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mechmock.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Quickstart

> Explore frame templates and inspect the registered runtime without launching a separate server.

Open [MechMock](https://mechmock.com/) to explore the frame studio and asset gallery.

## Registered local runtime

Use MechMock's existing DICC allocation and launcher. The registered browser origin is `http://localhost:7000`, with API port `6990`.

After that runtime is available, inspect these read-only endpoints:

```powershell theme={null}
Invoke-RestMethod -Uri 'http://localhost:7000/health'
Invoke-RestMethod -Uri 'http://localhost:7000/api/mechmock/templates'
Invoke-RestMethod -Uri 'http://localhost:7000/api/mechmock/logo-mocks'
```

The asset-manifest routes return HTTP 404 when their referenced manifest file is missing. The health payload advertises model and endpoint names; it does not establish GPU availability or successful fleet dispatch.

## Validate a workflow

Use the product's real sign-in when its Eyedbase integration is connected. Verify the expected user and MechMock product scope before accepting an authenticated workflow. A form that only changes the browser route is not an authenticated session.

Generation, sharing and render dispatch are write actions. Read their current behavior in [integration status](/integrations.md) before treating generated receipts as external service results. Heavy rendering runs through the canonical Fleetboots execution path when that integration is implemented and accepted.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.