Connect Cline to every model through one endpoint
Cline is an open-source AI coding agent for VS Code that brings its own bill: you plug in an API provider and pay for what the agent consumes. Pointing Cline's OpenAI-compatible provider at Router One gives it access to GPT, Claude, Gemini, and DeepSeek family models behind one key — with a per-request cost trace, so you can see exactly what each coding session cost.
Configure Cline to use the Router One base URL
In Cline's settings, choose "OpenAI Compatible" as the API provider and fill in three fields — base URL, API key, and the model ID copied from the /models page:
# Cline → Settings → API Provider: OpenAI Compatible Base URL: https://api.router.one/v1 API Key: sk-your-router-one-key Model ID: <copy the exact ID from /models>
Which model ID should Cline send?
Copy the exact model ID from the /models page — IDs are case-sensitive, and the page lists each model's context window, capabilities, and current per-token rates. Create a dedicated API key per tool with its own maxSpend cap, so one runaway tool can't affect other workloads.
Verify the Cline call in your request trace
After your first request, open Dashboard → Logs to see its full trace: model, tokens, cost, latency, and status code. From here every Cline call has a ledger and a trail instead of being a black box.
FAQ
Where do these settings live in Cline?
Open the Cline panel in VS Code → settings (gear icon) → API Provider → select "OpenAI Compatible". The three fields are Base URL, API Key, and Model ID.
Which models can Cline use through the gateway?
Any chat-capable model in the catalog — GPT, Claude, Gemini, Grok, DeepSeek, GLM, MiniMax, and Doubao families. The /models page is the source of truth for model IDs and per-token rates.
Does this work from Mainland China?
Yes. The gateway is reachable from Mainland China without a VPN, and the configuration is identical to the global setup.
How do I debug a 401/403/429?
Open Dashboard → Logs first to see whether requests reached the gateway and with what status, then walk the error-codes reference to check env vars, key status, and limits.