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

# Integration status

> Source API behavior and acceptance requirements for identity and live telemetry.

## Source API contracts

* `/health`: application identity, uptime, version and configured ports.
* `/api/nodes`: a static node demonstration array.
* `/api/agents`: a static agent demonstration array.
* `/api/gpu`: a static GPU demonstration array.
* `/api/dicc`: a static application demonstration array.
* `/api/logs`: a static log demonstration array.
* `/api/stats`: counts and totals derived from those arrays.

The handler branches on the request path. It does not fetch monitoring data from external services in these routes. Hardware names, token totals and online labels in the sample responses are not verified current measurements.

## Google and Eyedbase

The selected owner is `neostile81@gmail.com`. The project is `mechobserver-production`; the planned upstream Google callback is the production Eyedbase `google-mechobserver` broker endpoint. Google consent, issued client credentials, broker hydration, the product OIDC consumer and tenant authorization are separate steps. Retain credentials in infrastructure's approved authority rather than public documentation or browser code.

## Live telemetry acceptance

Continuous live monitoring belongs to the fleet's canonical Zabbix platform. A future MechObserver view must identify its approved source, measurement time and consumer runtime before representing a value as live. Static sample output and a healthy application endpoint cannot establish that connection.

## Documentation delivery

The assigned Mintlify project is `mechobserver`, owned by the same primary app owner. Desired source binding is canonical GitLab project `115`, branch `master`, content root `mintlify`. Existing hosted starter presence is separate from source-backed content publication, custom-domain verification and automatic synchronization.


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