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

# Integration status

> Separate implemented marketplace behavior from integrations awaiting live acceptance.

# Integration status

## Marketplace API

The canonical `server/index.cjs` implements these routes:

* `GET /health`: application status and catalog count.
* `GET /api/marketplace/apps`: catalog entries.
* `GET /api/marketplace/apps/` followed by an app ID: one app and its seeded reviews.
* `GET /api/marketplace/categories`: categories derived from the catalog.
* `POST /api/marketplace/seller/publish`: add a catalog entry to process memory.
* `POST /api/marketplace/checkout`: create an in-memory demonstration order and license string.
* `POST /api/marketplace/deploy`: return a generated deployment receipt.

These are source contracts. A production origin serving HTML for an API path has not demonstrated that the API is routed to this server.

## Eyedbase and Google sign-in

Mechfair's Google client belongs to `mechfair-production`, under the assigned MECH owner. Its callback targets the `google-mechfair` broker at the production Eyedbase realm. Credentials are retained in the infrastructure authority and must not be copied into public documentation, browser code or this repository.

OAuth client creation, broker activation, the product's OIDC client, a completed real login and the resulting Mechfair authorization are distinct acceptance steps. They remain unaccepted until the live flow supplies its own receipts.

## Fleetboots

The current deployment handler constructs a receipt with `QUEUED` status. It does not make a network request to Fleetboots. Integration acceptance requires a real fleet execution and its execution-bound result.

## Payments and licenses

The current checkout handler does not contact a payment processor. Its license generator uses a local random demonstration string; there is no signature verification or durable purchase ledger in that handler. Do not interpret the sample catalog prices, ratings or purchase receipts as a live commerce service.

## Documentation publishing

Mintlify uses the same primary owner as the app. The desired repository binding is private GitLab project `106`, branch `master`, content root `mintlify`. The existing hosted starter, repository connection, custom domain and published source revision must each be checked independently.


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