Aloom publishes an OpenAI-compatible request shape as documentation for a controlled deployment. It does not identify a callable public endpoint, offer API access or evidence that a customer-production service is operating.
The browser chat demonstration is paused. No public API keys, public model catalogue or production SLA are currently offered. Interface identity, credentials, models, residency, data handling, failure and recovery behaviour, metering, evidence and service terms remain deployment-specific and require an accepted configuration, contract and evidence.
Illustrative request shape / not callable
Controlled interface status summary — documentation only, not a runtime topology or service offer.
Area
Current status
Required closure
Current public posture
Request-shape reference published; browser chat paused; no public endpoint, API keys, model catalogue or production SLA offered.
No public service is declared.
Reference request shape
Documentation only and not callable. Placeholders do not identify an endpoint, credential, accepted model or streaming support.
A written project agreement would have to define any interface and credential.
Deployment decisions
Open and deployment-specific: identity, workload, residency, data handling, security, failure and recovery, metering and evidence.
Accepted configuration, contract and evidence required.
Customer-production claim gates
Required and not declared complete.
Close the service boundary, credential and trust delivery, data-flow policy, workload and loss-case tests, customer evidence and support terms.
Status map only—not a request path, runtime topology or service offer. Placeholders do not establish a callable endpoint, issued credential, accepted model or production service.
Illustrative request shape · no endpoint or credential currently offered
# DOCUMENTATION SHAPE — NOT A LIVE OR PUBLIC ENDPOINT
POST <deployment-base-url-if-agreed>/v1/chat/completions
Authorization: <deployment-specific credential — not issued here>
Content-Type: application/json
{
"model": "<accepted-model-id>",
"messages": [{"role": "user", "content": "..."}],
"stream": "<accepted-setting>"
}
Placeholders do not identify an available base URL, issued credential, accepted model or supported streaming mode. Browser-delivered reusable credentials are not an approved pattern.
Deployment decisions / required before a production interface claim
These items remain open until an accepted deployment configuration, contract and evidence close them. Listing a field does not mean a value, service or control is available.
Interface and identity — service name, base URL, client identity, credential delivery, scope, rotation and revocation.
Workload — accepted model and configuration, precision, context, latency and useful-output acceptance test.
Residency — permitted execution and data locations, named explicitly.
Data — retention, logging, prompt handling and deletion behaviour.
Security — trust chain, authentication and authorisation, key management, review and supplied evidence.
Availability — accepted failure set, recovery objective and support window; no SLA exists until contracted and evidenced.
Metering — facility input, accelerator time and useful-output measure.
Evidence — telemetry and attestation artefacts supplied to the customer.