Any OpenAI-compatible client + Luma Cloud

Before you start

• A client with a documented custom Base URL, API-key field and model selector. A model selector alone is not sufficient.
• A Luma Cloud API key from Dashboard → API, with Wallet funds or an eligible subscription key. SuperGPT desktop sign-in is separate.
• An exact model ID from GET /models using that key, and a client protocol matching Chat Completions or Responses.

Get an API key and a model ID →

Set up Any OpenAI-compatible client

1. Check the client's provider options

   Open Settings → Models, Providers or Connections. Look for OpenAI Compatible, Custom OpenAI or a configurable OpenAI endpoint. If it only accepts a vendor login or an Anthropic/Gemini endpoint, use one of the supported clients in this directory instead; changing a URL cannot translate the protocol.

2. Add a separate connection

   Name it Luma Cloud. Keep existing providers and the current default until the new connection is verified. In a config file, merge only the new provider entry; do not replace the whole file. Use the client's own documentation for its schema and file location.

3. Set the URL and credentials

   Use https://api.lumaos.cloud/v1 for a Base URL field. Enter your key in the client's secure credential field. If it asks for a full Chat Completions endpoint instead, use https://api.lumaos.cloud/v1/chat/completions. A header-based connector needs Authorization: Bearer followed by the actual key and Content-Type: application/json.

4. Choose the protocol and model

   Start with Chat Completions unless the client specifically requires Responses. Paste an exact model ID returned for your key. Do not add an OpenAI or Luma prefix unless that client's guide explicitly requires one. Only enable tools, vision or other optional features after checking both model and client support.

5. Save and select the connection

   Reload the client if its documentation requires it. Select Luma Cloud and the intended model in the chat or agent itself; saving a provider does not always select it. A GUI app opened from the Dock or Start menu may not inherit variables set in a terminal.

Provider

OpenAI Compatible / Custom OpenAI

Base URL

https://api.lumaos.cloud/v1

API key

Your key from Dashboard → API, stored in the client's secure field

Model ID

MODEL_ID_FROM_CATALOG

# macOS / Linux: enter the key when prompted, not in the command itself.
read -r -s LUMA_CLOUD_API_KEY
export LUMA_CLOUD_API_KEY
export LUMA_CLOUD_BASE_URL="https://api.lumaos.cloud/v1"
# Replace the value below with an ID returned for your key.
export LUMA_CLOUD_MODEL="MODEL_ID_FROM_CATALOG"

curl --fail-with-body "https://api.lumaos.cloud/v1/models" \
  -H "Authorization: Bearer $LUMA_CLOUD_API_KEY"

curl --fail-with-body -N "https://api.lumaos.cloud/v1/chat/completions" \
  -H "Authorization: Bearer $LUMA_CLOUD_API_KEY" \
  -H "Content-Type: application/json" \
  --data @- <<JSON
{
  "model": "$LUMA_CLOUD_MODEL",
  "messages": [{"role": "user", "content": "Reply with hello."}],
  "stream": true
}
JSON

$env:LUMA_CLOUD_API_KEY = Read-Host "Luma Cloud API key" -MaskInput
$env:LUMA_CLOUD_BASE_URL = "https://api.lumaos.cloud/v1"
$env:LUMA_CLOUD_MODEL = "MODEL_ID_FROM_CATALOG"

$headers = @{ Authorization = "Bearer $env:LUMA_CLOUD_API_KEY" }
$models = Invoke-RestMethod "$env:LUMA_CLOUD_BASE_URL/models" -Headers $headers
$models.data | Select-Object id

$env:LUMA_CLOUD_MODEL = Read-Host "Model ID from the list above"
$body = @{
  model = $env:LUMA_CLOUD_MODEL
  messages = @(@{ role = "user"; content = "Reply with hello." })
  stream = $false
} | ConvertTo-Json -Depth 5
$result = Invoke-RestMethod "$env:LUMA_CLOUD_BASE_URL/chat/completions" -Method Post -Headers $headers -ContentType "application/json" -Body $body
$result.choices[0].message.content

curl --fail-with-body -N "https://api.lumaos.cloud/v1/responses" \
  -H "Authorization: Bearer $LUMA_CLOUD_API_KEY" \
  -H "Content-Type: application/json" \
  --data @- <<JSON
{
  "model": "$LUMA_CLOUD_MODEL",
  "input": "Reply with hello.",
  "stream": true
}
JSON

Check the connection

1. List models with the intended key. This confirms catalog access, not a completed model response.
2. Send a short message in the client and wait for the complete response. Check Usage → API Wallet for a Wallet key, or subscription Usage for a subscription key.
3. For agent tools, ask the client to list files in a disposable folder without editing or running commands. Confirm that a real tool result returns before enabling broader actions.

For errors or a request that stops, see troubleshooting. A visible model list alone does not confirm that a chat or editing task can complete.

What to expect

• Custom API support is a client feature; not every IDE, agent mode or cloud task accepts a third-party provider.
• Chat compatibility does not promise autocomplete, embeddings, image generation, audio, hosted assistants or every agent tool.
• A universal config file would not work across different clients. Use the exact per-client guide when available.

Troubleshooting Any OpenAI-compatible client