# Cursor + Luma Cloud

A conditional chat connection using Cursor's OpenAI base URL override.

API connection: Check client requirements. Instructions checked: 2026-09-28. Client capabilities and versions may vary; follow the verification steps below.

This is an API setup guide. SuperGPT desktop installation and sign-in are separate; use a customer API key for the client described here.

## Before you start

- Create a Luma Cloud API key in Dashboard → API and copy a model ID from the authenticated model catalog.

- Your Cursor version must expose Override OpenAI Base URL and accept the chosen model. Save your existing endpoint settings before changing them.

## Setup

1. **Check the override**
   Open Cursor Settings → Models → API Keys. Find OpenAI API Key and Override OpenAI Base URL. This override can affect other models; use a dedicated setup if you need to preserve them.

2. **Set the URL and credential together**
   In that same Models panel, paste the Luma Cloud API key into OpenAI API Key and set the enabled Base URL override to https://api.lumaos.cloud/v1. Use the API Key field on macOS, Windows, or Linux. Do not put credentials in .cursor/rules or workspace settings.

3. **Add and select a compatible model**
   If your version offers Add model, enter the exact catalog ID and enable it. Click Save for the API settings. Start a fresh chat and explicitly select that model; an automatic or built-in model selection is not evidence that Luma Cloud is being used.

4. **Test one chat request**
   Send the example below. If Cursor rejects the model, the conditional connection is not usable with that model/version. Do not rename a model to impersonate a supported one. Continue or Cline inside a supported editor can be configured independently using their own guide.

5. **Return to your earlier setup when needed**
   Restore the original Base URL override state and provider credential in Models, save, and start a new conversation. Avoid leaving a Luma key paired with the official OpenAI URL, or an OpenAI key paired with the Luma Cloud URL.

## Connection fields

- 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

## First chat request

```text
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.

## Verify

- 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.

- Check that any existing provider you keep using still works after changing the global override.

## Limits

- Cursor documents BYOK for chat and limits its OpenAI support to standard non-reasoning chat models. Reasoning and agent workflows are not guaranteed.

- Tab completion still uses Cursor's own models.

- Cursor sends BYOK requests through its backend for prompt preparation. This is not a direct-only connection from your computer.

## Troubleshooting

### Override OpenAI Base URL is not available

Check the installed Cursor version and current API settings UI. There is no documented universal Cursor config file to paste here. Use an independently configured extension or another supported client rather than modifying Cursor's application files.

### The API works elsewhere but Cursor rejects the model

Cursor's native BYOK model support is narrower than general OpenAI-compatible API support. Test a permitted non-reasoning chat model. If it still fails, restore the original settings and use the OpenCode, Continue, or Cline guide.

### An unrelated model stopped working

The Base URL override can apply beyond the custom model. Restore the saved endpoint and matching key together. Prefer a separately configured extension when you need simultaneous providers without changing the shared override.

### Tab or Agent does not follow the selected API key

This conditional setup is for native chat. Tab remains a Cursor feature, and reasoning/agent support is not established by a successful chat request.

### 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.

## Official client documentation

- [Cursor: BYOK scope and handling](https://cursor.com/help/models-and-usage/api-keys)

- [Cursor support: base URL override fields](https://forum.cursor.com/t/openai-api-key-and-override-openai-base-url-cant-be-modified/167982/5)

- [Cursor support: global override limitation](https://forum.cursor.com/t/can-the-api-key-and-base-url-corresponding-to-a-custom-model-be-set-separately-when-adding-a-cursor/137108)