OpenClaw-ready
OpenClaw uses the same Luma Cloud API contract.
Set the public /v1 endpoint, an API key you explicitly created, and a canonical model id. Keep private gateway, bridge, shard, and local OmniRoute details out of client-facing setup.
Open API setup
Use the public Luma Cloud /v1 endpoint from App -> API. Local dev commands are only for internal smoke work, not for customer provider setup.
Verify the branded endpoint
Call `https://api.lumaos.cloud/healthz` first, then open App → API and create a key for OpenClaw.
Create the API key
Fund the API wallet when needed, name the key, and copy its secret when it is shown. Product credentials stay internal.
Configure an OpenAI-compatible client
Set `baseURL=https://api.lumaos.cloud/v1`, use the key created in App → API, fetch authenticated `GET /v1/models`, and choose one exact id it returns. Do not substitute a hidden effort.
Confirm request-id support
Keep the x-lumacloud-request-id or error.request_id from the first failed request. Support works from public ids, not from private bridge details.
Provider setup
Use the branded base URL exactly as the provider surface.
The client should only know Luma Cloud. OmniRoute, bridge hosts, and private topology remain hidden behind the gateway boundary.
Connection values
Local alpha defaults for the first OpenClaw-style provider hookup.
Base URL
https://api.lumaos.cloud/v1
API key
Open App → API, create a named key, and copy the one-time secret.
Health check
https://api.lumaos.cloud/healthz
Local alpha truth
What is already real versus what stays future work.
Already supported
Still intentionally missing