LATCH Customer API Reference

This documentation set describes the supported customer-facing HTTP surface for the self-hosted LATCH runtime.

It is intentionally limited to the parts of the product that operators and integrators are expected to use directly:

• local startup and readiness
• file and text compilation
• document listing
• querying and synchronous batch requests
• runtime telemetry visible through the public health surface
• document clearing

This documentation set does not publish:

• source-browser pages
• internal runtime modules
• licensing implementation details
• marketplace webhook flows
• legacy demo runtime helpers
• control-plane code paths

Base URL

Default local origin:

http://127.0.0.1:8091

Supported Public Surface

Use these endpoints as the supported customer API contract:

• GET /health
• GET /documents
• POST /warmup
• POST /compile_text
• POST /compile_file
• POST /query
• POST /batch
• POST /documents/clear

Related Docs

• Endpoint Reference
• Telemetry and Runtime Fields
• RunPod Quickstart
• Ubuntu GPU Quickstart
• Console Reference

Startup Contract

For the customer-supported deployment path, start the runtime with:

• LATCH_LICENSE_TOKEN or LATCH_LICENSE_TOKEN_FILE
• LATCH_LICENSE_VALIDATION_MODE=codynamics_online
• LATCH_LICENSE_VALIDATION_URL=https://cdlac-demo-api.azurewebsites.net/api/license/startup_validate

Your Gumroad license key is not the runtime token. Use the CoDynamics-issued runtime token delivered through the fulfillment flow.

Readiness Model

The runtime lifecycle visible to customers is:

• idle
• loading
• ready
• error

The ordinary customer/operator success state is:

ready to accept files for processing

Use GET /health as the source of truth before attempting compile or query operations.