LATCH Customer Docs
LATCH Customer API Reference
Customer-facing HTTP API and telemetry surface for the self-hosted LATCH runtime.
Telemetry and Runtime Fields

Runtime Status

The health endpoint exposes the customer-safe runtime lifecycle:

  • idle
  • loading
  • ready
  • error

The normal success message is:

ready to accept files for processing

Identity Fields

These are the safest fields to use when you need to verify what runtime is actually loaded:

  • service_rev
  • profile_id
  • config_class
  • base_model_class
  • router_enabled

The customer health surface intentionally does not expose raw internal file paths for checkpoints, projectors, or other artifact locations.

Capacity and Decode Fields

Use these fields to understand the active room limits and defaults:

  • max_doc_tokens
  • default_memory_tokens
  • memory_temperature
  • default_max_new_tokens
  • fallback_mode
  • deterministic_generation

Room State Fields

Use these fields to understand the current active room:

  • documents_total
  • service_uptime_s

The document list endpoint adds per-document compile and extraction timings plus cache size metrics.

Operator Guidance

  • Poll GET /health until ready=true before compile or query calls.
  • Use GET /documents after every compile to confirm the active compiled set.
  • Treat service_rev plus profile_id as the primary runtime identity check when you compare two environments.