Using Cline

Compatibility: works. Cline's OpenAI Compatible provider talks to any endpoint that serves OpenAI-style chat completions, which is what luv13 serves. How well Cline's agent works still depends on the model's tool calling, which luv13 hasn't confirmed per model.

Before you start

You need:

Cline installed in your editor. Cline's docs list VS Code, Cursor, Windsurf, VSCodium, Antigravity and JetBrains. In VS Code, open the Extensions view, search for Cline and click Install.
A luv13 API key. The Quickstart shows how to get one.
The model id luv13/glm-5.3-flash, from the live list at https://api.luv13.ai/v1/models. See GLM-5.3 Flash for details on the model.

Facts about luv13 that affect this setup:

luv13 serves one generation endpoint, POST /v1/chat/completions, plus GET /v1/models. /v1/responses, /v1/messages, /v1/completions and /v1/embeddings return 404 (checked 2026-09-30). See Endpoints.
Every model costs a flat $0.33 per 1M tokens, input the same as output. See Pricing.
The model list at https://api.luv13.ai/v1/models doesn't report context length, so luv13 publishes no per-model limits. See the model list.

Test your key and model first

Run these two checks in a terminal before you touch the tool. They take a few seconds and rule out key and model problems.

1. The model id exists. This call needs no key:

curl -s https://api.luv13.ai/v1/models

The list should include "id":"luv13/glm-5.3-flash".

2. Your key works for chat. Set the key in your shell first (export LUV13_API_KEY="your luv13 key"), then run:

curl -s https://api.luv13.ai/v1/chat/completions \
  -H "Authorization: Bearer $LUV13_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "luv13/glm-5.3-flash",
    "messages": [{"role": "user", "content": "Reply with the word ready."}],
    "max_tokens": 20
  }'

With a valid key you should get back a JSON chat completion whose choices[0].message.content holds the reply, plus a usage block. If you see {"error":{"code":401,"message":"unauthorized","type":"invalid_auth"}} instead, the key is missing or wrong, and no tool setting will fix that.

Set up Cline in your editor

These steps follow Cline's "OpenAI Compatible" provider page, read on 2026-09-30. The latest Cline release on GitHub that day was desktop-v0.0.39, published 2026-09-30.

Open Cline from the editor's sidebar.
Click the settings (gear) icon in the Cline panel.
Set API Provider to OpenAI Compatible.
Fill in the fields exactly like this:

Field	What to enter
Base URL	`https://api.luv13.ai/v1`
API Key	your luv13 key
Model	`luv13/glm-5.3-flash`
Use Azure Identity Authentication	leave unchecked

Open Model Configuration and set:

Field	What to enter
Input Price	`0.33` (per million tokens)
Output Price	`0.33` (per million tokens)
Context Window	leave Cline's default. luv13 publishes no context length.
Max Output Tokens	leave the default, or lower it to cap reply length
Image Support	leave off unless you've confirmed image input on luv13. See Image Input.
Computer Use	leave off unless you've tested it with this model

If your version shows a Verify button, click it. Cline's docs use it to confirm the connection.
Close settings and start a small task, such as "List the files in this folder and describe the project in two sentences."

Using the Cline CLI

Cline's docs say its settings live under ~/.cline/, and API keys and provider settings go in ~/.cline/data/settings/providers.json, shared by the IDE extension, the CLI and the SDK. To set up a provider from the terminal, run:

cline auth

and choose the OpenAI-compatible option. The CLI reference also lists -P, --provider <id>, -k, --key <api-key> and -m, --model <model-id> flags for a single run. The docs don't give the provider id to use with -P for OpenAI Compatible, so use the interactive cline auth flow instead of guessing it. Don't edit providers.json by hand or commit it, because it holds your key.

Common errors

Symptom	Likely cause	Fix
`401` with `{"error":{"code":401,"message":"unauthorized","type":"invalid_auth"}}`	The key is missing, has extra spaces, or isn't a luv13 key.	Paste your luv13 key again. Run test 2 above to confirm it.
`404` with an HTML page titled "404 Not Found"	The URL is wrong. Common versions: `https://api.luv13.ai` with no `/v1`, a doubled path such as `https://api.luv13.ai/v1/v1/...`, a pasted full endpoint like `.../v1/chat/completions` in the base URL field, or a trailing slash.	Set the base URL to exactly `https://api.luv13.ai/v1`. The tool adds `/chat/completions` itself.
`404` even though the base URL is right	The tool is calling an endpoint luv13 doesn't serve, such as `/v1/responses`, `/v1/messages`, `/v1/completions` or `/v1/embeddings`.	Use the tool's OpenAI chat-completions mode, and turn off features that need other endpoints. See Endpoints.
Model not found, or the model doesn't appear	The model id is misspelled or missing the `luv13/` prefix.	Use the exact id `luv13/glm-5.3-flash` from `https://api.luv13.ai/v1/models`.
Cline reports "Invalid API Key"	Cline's docs list this for a mistyped key or a key from another provider.	Paste the luv13 key again. Make sure you didn't paste an OpenAI or Anthropic key.
Cline reports "Model Not Found"	Cline's docs list this for an id the base URL doesn't serve.	Enter `luv13/glm-5.3-flash` exactly.
Connection errors	Cline's docs point to a wrong base URL, a blocked network or a firewall.	Check the base URL, then run test 2 from the same machine. Behind a proxy, the VS Code extension uses VS Code's own proxy settings, and the CLI uses the `https_proxy` and `http_proxy` environment variables.
The task stalls, loops or says a tool call failed	The model didn't return a tool call Cline could use. Tool support on luv13 isn't confirmed per model.	Try a smaller task, or another id from the live list. See Tool Calling on luv13.

General tip: Cline's cost display uses the prices you enter. It doesn't read luv13's billing. For your real spend, see Usage and Billing.

Sources

Cline docs, "OpenAI Compatible" (read 2026-09-30)
Cline docs, "Config" (read 2026-09-30)
Cline docs, "CLI Reference" (read 2026-09-30)
Cline docs, "Networking and Proxies" (read 2026-09-30)
Cline releases on GitHub (latest: desktop-v0.0.39, 2026-09-30)
luv13 endpoints and errors checked live with curl on 2026-09-30.

Related: Using Cursor, Base URL, Agents.