API setup · Chat Completions
Cline + Luma Cloud
Connect the Cline extension with its OpenAI Compatible provider.
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 Cline in a supported editor.
Set up Cline
- Open Cline's own settings
Open the Cline sidebar/tool window, then its gear icon. Find API Provider and select OpenAI Compatible. Changing VS Code Chat, Cursor Models, or JetBrains AI Assistant settings does not configure Cline.
- Enter URL and key
Set Base URL to https://api.lumaos.cloud/v1. Paste the Luma Cloud key into Cline's API Key field on macOS, Windows, or Linux. Do not append /chat/completions, add a Bearer prefix, or enable Azure authentication.
- Choose the exact model
Enter MODEL_ID_FROM_CATALOG after replacing it with the ID available to your key. If your version has separate Plan and Act model selectors, configure the intended provider/model for both modes.
- Set capabilities carefully
Use the documented context and output limits for your chosen model. Enable image or tool features only when that model supports them. Keep automatic approval off for your first task.
- Save and open a fresh task
Save the settings, confirm the provider and model shown by Cline, then start a new task. If the old selection persists, reopen Cline or reload the editor. Keep keys in Cline's credential UI, not a project settings file.
- 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
- This configures Cline, not the editor's built-in assistant or autocomplete.
- A successful connection check does not confirm every agent feature. Verify tools and images separately when you need them.
- Client cost estimates may differ from the amount recorded in Dashboard → API.
Troubleshooting Cline
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.
Model not found or access denied
Copy the exact model ID available to this key from the authenticated catalog. MODEL_ID_FROM_CATALOG is a placeholder, not a model name. Do not substitute a display label or copy an ID from another provider.
Text works, but the task stops at a tool call
Select a model with native tool calling and use the small file-read check. A text response or a successful Verify button is not enough to qualify an agent workflow. Share the error and model ID with support, without your key.
The wrong model runs after switching modes
Check Cline's Plan and Act selections separately if your version exposes both. Start a new task after correcting them and confirm the displayed model before sending.
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.
