Local does not have to mean opaque.

Lizard's native server surfaces the provider and model it actually loaded, the concurrency policy it selected, and any matching measured HTTP profile. Response metadata also carries serving-path and user-performance information.

You should be able to explain a slow local reply without attaching a debugger first.

What would you want on the first screen of a local inference health check?

Engineering fact: The native HTTP health and metrics endpoints expose runtime provider, model identity, selected concurrency policy, and measured HTTP performance evidence.

Read the relevant Lizard page

#LizardNative #LizardLLM #LocalAI #GGUF #InferenceEngineering

<!-- lizard-marketing-slot:day-20-pm -->