API setup · Chat Completions
Kilo Code + Luma Cloud
Create a named Luma Cloud provider and select models from your API catalog.
Use your Luma Cloud API key, Base URL and an available model ID with the client-specific settings below. SuperGPT desktop installation and sign-in are separate.
Before you start
- Create a Luma Cloud API key in Dashboard → API and copy a model ID from the authenticated model catalog.
- Install the Kilo Code extension.
Set up Kilo Code
- Add a custom provider
Open Settings → Providers → Custom provider. Set a new provider ID, such as luma-cloud, and display name Luma Cloud.
- Choose the protocol
Select OpenAI Compatible for Chat Completions. Enter the Base URL and Luma Cloud API key.
- Add your models
Choose from the fetched model list, or enter the exact catalog ID manually. The display name can be Luma Cloud; the model ID must remain unchanged. Match model limits and capabilities to the selected model, then submit the provider.
- Keep credentials local
Use Kilo's API key field on macOS, Windows, or Linux. If you edit configuration files, keep credentials separate and never put a key in a shared project config or settings export. An exported Kilo configuration can contain secrets.
- Select the provider for a new task
Choose the new Luma Cloud model from Kilo's picker. Check the model again when changing profiles or task modes. Reopen the extension if the new provider is not visible after saving.
- Base URL
https://api.lumaos.cloud/v1- API key
Your Luma Cloud key, entered in the client's secret field- Model ID
MODEL_ID_FROM_CATALOG
Reply with exactly: Luma Cloud connection works.Send this in a new conversation with the Luma Cloud model selected. This is a normal API request and uses the selected key's balance or quota.
Read README.md in this test folder and summarize its first paragraph. Do not edit files, run shell commands, or access the network.Create a disposable folder containing a short README.md first. Approve only the file read. Check that a tool result and a final answer both appear.
Check the connection
- Send a short text request, then check Usage → API Wallet for Wallet usage, or subscription Usage for Builder keys. A populated model list alone does not confirm a successful response.
- Before using an agent on your project, try one read-only file task in a disposable folder. Confirm the tool result and final answer, keeping action approval enabled.
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
- Choose OpenAI Responses only for a model and workflow that support that API. Do not select Anthropic Messages for Luma Cloud.
- Model discovery does not establish tool, image, or reasoning support. Match advanced settings to the selected model.
- Adding Luma Cloud does not replace your existing provider configurations.
Troubleshooting Kilo Code
Automatic model detection returns no models
Check that Base URL is exactly https://api.lumaos.cloud/v1 and that the key is active. Try entering an ID from your authenticated catalog manually. An empty discovery list does not justify using another account's model ID.
A request reports the wrong endpoint or protocol
For this guide choose OpenAI Compatible / Chat Completions. OpenAI Responses is a separate selection. The protocol, base URL, and model must describe the same connection; remove any stale full endpoint suffix.
Settings return after you change them
Open Local Config and Global Config from Kilo settings and check which file supplies the value. Project configuration can override your global setup. Back up the affected file and change only the Luma Cloud entry.
401 or invalid API key
Paste the complete Luma Cloud API key again without quotes, spaces, or a Bearer prefix. Confirm that the same key is still active in Dashboard → API. Your dashboard password and Google sign-in are not API keys.
The request is limited or cannot be funded
Read the error message and check the key's balance or subscription quota in the dashboard. Wait for the stated retry time when provided. Repeatedly creating keys or re-entering the same credentials does not add quota.
Client documentation
Settings checked on 2026-09-28. These instructions are based on the client’s documentation; installed versions may differ.