When an app offers a custom provider or OpenAI-compatible provider, use these fields.
Field
Value
What it controls
Prefix
None
Do not add a provider prefix to the model ID.
API Type
OpenAI-compatible
Use the app’s OpenAI-compatible chat-completions adapter.
Base URL
https://aiwave.live/v1
Keep /v1; do not append /chat/completions.
API Key
AIWAVE_API_KEY
Paste the key into the app’s secret field; never put it in a public prompt or screenshot.
Model ID
deepseek-v4-flash
Use the exact current ID from Models; do not invent an alias.
If the app has both Base URL and Endpoint fields
Put https://aiwave.live/v1 in Base URL and leave a separate endpoint field at its default, unless the app explicitly asks for the full chat-completions path.
3. Cursor and Continue
Both tools can use an OpenAI-compatible custom provider. Keep the configuration small, then make one short test call.
Cursor
Open Settings, find the model provider or OpenAI-compatible provider section, set the Base URL to https://aiwave.live/v1, paste the key in the secret field, and select the exact Model ID from Models. Start with a short prompt before enabling larger context or agent actions.
Continue
In the model configuration, choose the OpenAI-compatible provider, set apiBase to https://aiwave.live/v1, set the model to deepseek-v4-flash, and load the key from an environment variable or the tool’s secret store. Do not commit the configuration with a key value.
Verify before debugging the tool
Run the curl smoke test first. If curl returns 200 but the editor fails, inspect the editor’s provider type, Base URL normalization, selected model ID, and whether it loaded the current environment variable.
The four setup mistakes to check first
Symptom
Likely cause
Fix
404 or an HTML page
Wrong domain or missing /v1
Use https://aiwave.live/v1.
401
Key has whitespace, is not loaded, or was placed in the wrong provider
Reload the key into the tool’s secret store and do not print it.