Work in your editor
Cline →Use the verified connection walkthrough, then test a small file edit separately.
Practical guide · Updated October 15, 2026
A working connection is the first step. Use a small real task to decide whether free Qwen is enough, which tool fits, and when a paid model is worth testing.
Use the verified connection walkthrough, then test a small file edit separately.
Use Python or JavaScript on the server. Check non-empty text before adding streaming or tools.
Start with the tested server-side CLI example. Hosting and browser UI need separate verification.
Free provides 30M tokens/month, 128K total context and 160K TPM. $10 cumulative net recharge unlocks 100M/month, 128K context and 300K TPM; $50 unlocks 300M/month, 256K context and 600K TPM. These are recharge thresholds, not subscriptions.
A higher Qwen tier changes allowance, context, TPM and queue priority. It uses the same model; it is not evidence of better answer quality. Maximum output stays 8,192 tokens and shared capacity has no SLA.
For a coding evaluation, use an empty folder and a disposable Git branch. Ask your tool to make two files and run the tests. Review any requested file and command actions.
Create slugify.mjs exporting slugify(value), and slugify.test.mjs using node:test.
Convert to lowercase, trim whitespace, replace runs of non-ASCII-alphanumeric characters with one hyphen, and remove leading/trailing hyphens.
Test these exact cases:
" Hello, World! " -> "hello-world"
"API Key" -> "api-key"
"---" -> ""
"" -> ""
Run node --test slugify.test.mjs and report the result. Do not install dependencies.For document Q&A, use a short document with five answers you already know. Ask for source quotations and mark each answer correct, unsupported or missing. For a chat feature, test five representative user requests and one request it should decline or hand off.
Check credentials, endpoint and output budget using the tutorial. A larger paid model does not fix a wrong configuration.
Check monthly usage, TPM and input plus requested output. Reduce concurrency/history or compare the relevant Qwen tier.
Repeat the same task on a paid candidate, with the same inputs and acceptance criteria. Compare the actual result and cost.
Discuss reserved capacity or dedicated deployment. A Qwen recharge does not provide a latency SLA.
Cost = uncached input tokens / 1M × input price + cached input tokens / 1M × cached-input price + output tokens / 1M × output price. Split input into cached and uncached portions so it is not counted twice. Use billed output, including reasoning where applicable.
Prices below use the same catalog as the pricing page and refresh from the public price endpoint when available. No quality or speed ranking is implied.
Catalog snapshot: 2026-10-09. Live prices have not been verified yet.
| Model | Input | Cached input | Output |
|---|---|---|---|
| Qwen3.8-27B | $0 | $0 | $0 |
| Qwen3.8-2.4T-A95B | $1.95 | $0.245 | $5.70 |
| GLM-5.3-Flash | $0.099 | $0.025 | $0.35 |
| Kimi K2.7 Code | $0.69 | $0.15 | $3.29 |
| DeepSeek V4 Pro | $0.89 | $0.030 | $2.69 |
| GLM-5.3 | $0.99 | $0.245 | $3.45 |
| Kimi K3 | $2.39 | $0.24 | $11.99 |
| MiniMax M3 | $0.299 | $0.045 | $1.19 |
| DeepSeek V4.1 Flash | $0.29 | $0.0058 | $1.16 |