To use Cline with an OpenAI-compatible provider, open Cline settings, choose API Provider: OpenAI Compatible, enter the provider Base URL, paste your API key, and use a model ID returned by /v1/models. Use /v1 when your provider requires it. Do not paste /v1/chat/completions as the Base URL. If Cline shows 401, 404, or model not found, recheck the /v1 endpoint, your API key, and the exact model ID from /v1/models.
Cline OpenAI-compatible provider quick answer To use Cline with an OpenAI-compatible provider, choose API Provider: OpenAI Compatible, enter the Base URL as https://api.rutaapi.com/v1, paste your API key, and use a model ID returned by /v1/models. Use /v1 when your provider requires it. Do not paste /v1/chat/completions as the Base URL. If Cline shows 401, 404, or model not found, recheck the /v1 endpoint, your API key, and the exact model ID from /v1/models.
Cline setup table
| Field | What to use in Cline |
|---|---|
| API Provider | OpenAI Compatible |
| Base URL | https://api.rutaapi.com/v1 |
| API Key | Your RutaAPI API key |
| Model ID | A model enabled in your RutaAPI app pricing page |
What Cline needs When you configure Cline to use an OpenAI-compatible API provider, Cline asks for four things: an API Provider, a Base URL, an API Key, and a Model ID. All four must belong to the same provider. If you enter a Base URL from one platform and an API key from another, Cline will return a 401 error.
RutaAPI values for Cline Base URL: https://api.rutaapi.com/v1 — always include /v1. API key: Create one after signing in to RutaAPI. Model ID: Use a model ID visible in the RutaAPI app pricing page.
Cline version caveat Cline UI labels and provider behaviour can change by version. Depending on your Cline version, labels may vary slightly. Users should verify the current Cline UI in their installed version before configuring a custom provider.
RutaAPI disclaimer RutaAPI is an OpenAI-compatible API gateway. It is not an official Cline, OpenAI, Anthropic, Google or Microsoft service. Model availability and rates depend on your account configuration and upstream providers.
How to start with RutaAPI
Step 1 — Open Cline settings
Open Cline settings or preferences in your editor. Look for a provider or API configuration section.
Step 2 — Choose OpenAI Compatible as the provider
Select OpenAI Compatible from the available provider options. This tells Cline to use OpenAI-compatible request formatting.
Step 3 — Paste the RutaAPI Base URL
Enter https://api.rutaapi.com/v1 as the Base URL. Use /v1 when your provider requires it. Do not paste /v1/chat/completions as the Base URL. Do not use https://rutaapi.com or https://app.rutaapi.com.
Step 4 — Paste your RutaAPI API key
Paste your RutaAPI API key into the API Key field. Create or copy the key from the RutaAPI dashboard at https://app.rutaapi.com. Keys are shown only once at creation — copy and store them securely.
Security: Never paste your full API key into screenshots or shared scripts. If exposed, rotate it immediately from the dashboard.
Step 5 — Enter or select a model ID
Enter a model ID that is enabled in your RutaAPI account. Check the RutaAPI app pricing page for enabled model IDs. Do not guess — always copy the exact ID from the dashboard or from /v1/models.
Step 6 — Verify or send a small test request
Before running any coding tasks, confirm end-to-end connectivity from the terminal:
A 200 response with a model list means your API key and Base URL are working. A 401 response means the key is wrong or revoked.
curl https://api.rutaapi.com/v1/models \
-H "Authorization: Bearer YOUR_RUTAAPI_KEY"What Cline needs
When you configure Cline to use an OpenAI-compatible API provider, Cline asks for four things:
- API Provider — Choose OpenAI Compatible so Cline uses OpenAI-compatible request formatting.
- Base URL — The root address of the API gateway. Use the provider Base URL or
/v1endpoint when your provider requires it. The correct RutaAPI value ishttps://api.rutaapi.com/v1. - API Key — A secret token that identifies your RutaAPI account. Create one from the dashboard.
- Model ID — The identifier of the model that handles your requests. Must be enabled in your RutaAPI account.
All four must belong to the same provider. Do not mix keys or Base URLs across platforms.
Use /v1 when your provider requires it. Do not paste /v1/chat/completions as the Base URL.
RutaAPI values for Cline
Base URL: https://api.rutaapi.com/v1
API key: Create one after signing in to RutaAPI at https://app.rutaapi.com.
Model ID: Use a model ID visible in the RutaAPI app pricing page. Run GET /v1/models to see which models are enabled.
Test your RutaAPI key before using it in Cline
Before configuring Cline, verify that your API key and Base URL work together by calling /v1/models from the terminal:
curl https://api.rutaapi.com/v1/models \
-H "Authorization: Bearer YOUR_RUTAAPI_KEY"If the response returns a model list, your API key and Base URL are working. Use one of the returned model IDs as the Model ID in Cline.
Example OpenAI-compatible request
Once your key is verified, you can also send a chat completions request to confirm everything works end-to-end:
curl https://api.rutaapi.com/v1/chat/completions \
-H "Authorization: Bearer YOUR_RUTAAPI_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "YOUR_ENABLED_MODEL_ID",
"messages": [
{"role": "user", "content": "Say hello from RutaAPI"}
]
}'Replace YOUR_ENABLED_MODEL_ID with one of the model IDs from the /v1/models response. Do not hardcode a model name you have not verified.
How to pick a Model ID
Model IDs are returned by the GET /v1/models endpoint. Copy one of the model id values from the response and use it as the Model ID in Cline settings.
Model availability is per-account. If a model ID is not in your /v1/models response, it is not active in your account — add credits or check the app pricing page.
Common Cline setup mistakes
| Problem | Likely cause | Fix |
|---|---|---|
| Cline says invalid API key | Wrong key, missing Bearer, expired/disabled key | Create a new key in RutaAPI and test /v1/models |
| Model not found | Model ID is not enabled or typed incorrectly | Check app pricing page for enabled model IDs |
| 404 or endpoint not found | Wrong Base URL, missing /v1 | Use https://api.rutaapi.com/v1 |
| 429 rate limit | Too many requests or limited route | Slow down requests or choose another enabled route/model |
| 503 / upstream unavailable | Upstream route, gateway, or provider temporarily unavailable | Retry, switch model route, or check status/support |
Cost and usage tracking
RutaAPI uses prepaid credits. Model pricing and enabled routes are shown in the app pricing page. Users should check usage logs and remaining balance after test calls.
Cline setup checklist
- I selected OpenAI Compatible provider
- I used https://api.rutaapi.com/v1 as the Base URL
- I pasted a RutaAPI API key
- I selected an enabled model ID
- /v1/models returns a model list
- I checked pricing and usage in the dashboard
When RutaAPI may be a good fit
- You need an OpenAI-compatible Base URL for Cline
- You want dashboard-generated API keys
- You want prepaid credits
- You want to verify available models with /v1/models
- You need docs for Cursor, Cline, Codex CLI and Claude Code
- You want usage visibility before scaling
When RutaAPI may not be the right fit
- Your Cline version does not support OpenAI-compatible provider configuration
- The selected model is unavailable upstream
- Your API key belongs to another provider
- You require official Cline, OpenAI or Anthropic-only features
FAQ
How do I set up an OpenAI-compatible provider in Cline?
Open Cline settings, choose API Provider: OpenAI Compatible, enter the provider Base URL, paste your API key, and use a model ID returned by /v1/models. Use /v1 when your provider requires it. Do not paste /v1/chat/completions as the Base URL.
What Base URL should I use in Cline?
Use the provider Base URL or /v1 endpoint when your provider requires it. For RutaAPI, use https://api.rutaapi.com/v1 as the Base URL in Cline.
Should the Base URL include /v1 or /v1/chat/completions?
Use /v1 when your provider requires it, but do not paste /v1/chat/completions as the Base URL because that is a specific endpoint, not the API root.
Where do I enter the API key in Cline?
Paste your API key into the API Key field in Cline after selecting API Provider: OpenAI Compatible.
What model ID should I use?
Use a model ID returned by /v1/models and enabled in your RutaAPI account. Copy the exact id value instead of guessing.
Why does Cline show 401, 404, or model not found?
401 usually means the API key is missing, wrong, or sent to the wrong Base URL. 404 usually means the Base URL is wrong or missing /v1. Model not found usually means the model ID is unavailable, misspelled, or not returned by /v1/models.
Which API provider should I choose in Cline?
Choose OpenAI Compatible.
How do I test the key before using Cline?
Call GET /v1/models with your RutaAPI API key. A 200 response with a model list means the key is valid.
Is RutaAPI an official Cline provider?
No. RutaAPI is an OpenAI-compatible API gateway that can be configured through compatible provider settings. It is not an official Cline, OpenAI, Anthropic, Google or Microsoft service.
What does 403 mean in Cline?
HTTP 403 means the key exists but lacks permission. Check that your account has enough prepaid credits and that the model is enabled.
What does 429 mean in Cline?
HTTP 429 means you have hit a rate or concurrency limit. Lower the number of concurrent requests and retry.
What does 503 mean in Cline?
HTTP 503 means the provider route is temporarily unavailable. Retry, switch model route, or check status/support.