Public API specification
Planned. RegesARC 0.0.1 does not expose a supported public API server. The app’s private Lemonade endpoint and internal preload bridge are not a public integration contract. No requests on this page should be treated as operational RegesARC commands.
Proposed route families
Section titled “Proposed route families”| Family | Proposed routes | Required semantics |
|---|---|---|
| Native inventory | GET /api/v1/models |
Actual artifact/instance identity and readiness |
| Native chat | POST /api/v1/chat |
Correlated lifecycle, text/reasoning, terminal events |
| Native lifecycle | POST /api/v1/models/load, /unload |
Exact validated settings and owned instances |
| Downloads | POST /api/v1/models/download, GET /api/v1/models/download/status/:job_id |
Immutable complete set, observed bytes, integrity and job state |
| OpenAI compatibility | /v1/models, /v1/responses, /v1/chat/completions, /v1/completions, /v1/embeddings |
A declared, tested dialect per endpoint |
| Anthropic compatibility | POST /v1/messages |
Declared headers, content blocks, tools, streaming and errors |
Compatibility describes a protocol shape. It does not host GPT or Claude, change the actual serving-model identity, or establish a provider partnership. Embeddings require a separately qualified embedding model; generation weights are not assumed to provide valid vectors.
Strict URL and error behavior
Section titled “Strict URL and error behavior”A client builder should join an origin and one declared API prefix once. A malformed raw route such as /v1/v1/models must return a structured 404, not a successful fallback. Unknown methods, malformed JSON, absent/invalid credentials, denied scopes, missing models and lifecycle conflicts need distinct errors and request correlation.
Streaming and tools
Section titled “Streaming and tools”Responses and Messages adapters need independent fixtures for item/block boundaries, argument fragments, call IDs, usage, cancellation, errors after headers and terminal completion. Assembled tool arguments must be schema-validated before host execution. A valid model-generated tool call is not permission to perform it.
Stateful response IDs, hosted tools, images, reasoning controls and structured output should be accepted only when their actual behavior is implemented. Reject unsupported fields rather than silently dropping them.
Security and release gates
Section titled “Security and release gates”Default to authenticated loopback, bounded requests, explicit model admission and host-side secrets. LAN exposure, CORS, TLS/proxy behavior and administrative operations require separate controls. Do not pass a broad runtime management key to a renderer or ordinary external client.
The reference surface was informed by LM Studio’s native API, OpenAI compatibility and Messages compatibility. Those are upstream product contracts, not evidence of implemented RegesARC support.