Cline API keys for OpenAI-compatible providers must come from the same platform as the Base URL. To use RutaAPI with Cline, choose an OpenAI-compatible provider option, set the Base URL to https://api.rutaapi.com/v1, paste a RutaAPI API key, and use a Model ID returned by /v1/models. The Cline API key, Base URL and Model ID must all belong to the same provider. Do not paste the website URL, dashboard URL or a full chat completions endpoint as the Base URL. Do not use an OpenAI key with the RutaAPI Base URL.
Need the full setup guide? Read the complete Cline OpenAI-compatible API setup guide.
Before you start
You need a RutaAPI account, a prepaid credit pack, and an API key. Make sure your account has credits before making requests — requests without sufficient credits will return a 401 or 403 error.
Cline API keys: where to put your OpenAI-compatible key When you configure Cline to use an OpenAI-compatible provider, Cline asks for three things: a Base URL, an API Key, and a Model ID. All three must belong to the same provider. The Cline API key is the API key from your selected provider — not a generic key. For RutaAPI, create the key in the RutaAPI dashboard and paste it where Cline asks for the OpenAI-compatible API key. Do not use an OpenAI key with the RutaAPI Base URL. Do not use a RutaAPI key with another provider's Base URL. Never paste your Cline API key into screenshots, public issues or public GitHub repositories.
What Cline asks for When you configure Cline to use a custom OpenAI-compatible provider, Cline typically asks for three things: a Base URL, an API Key, and a Model ID. All three must belong to the same provider. If you enter a Base URL from one platform and an API key from another, the connection will fail with a 401 error.
What OpenAI-compatible means in Cline OpenAI-compatible means an API that uses the same request and response format as OpenAI — the same JSON structure, field names and endpoint paths. When Cline says OpenAI-compatible, it means you can point Cline at any gateway that follows this format, as long as you provide the right Base URL, API key and model name.
What the Base URL is The Base URL is the root address of the API gateway. It tells Cline where to send requests. The correct RutaAPI Base URL is <strong>https://api.rutaapi.com/v1</strong> — it includes /v1 and points to the API root, not the dashboard or marketing site.
What the API Key is The API key is a secret token that identifies your account. It is generated by the provider and must be kept private. Never paste it into screenshots or shared scripts. If the key is exposed, rotate it immediately from the provider dashboard.
What the Model ID is The Model ID is the identifier of the AI model that handles your request. It must match one of the models returned by /v1/models for your account. Do not guess — identifiers differ between providers. Always copy from the /v1/models response.
Cline version caveat Cline UI labels and provider behaviour can change by version. Official Cline documentation describes OpenAI-compatible setup around Base URL, API Key and Model ID, but users should verify the current Cline UI in their installed version before relying on a setup.
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 — Create a RutaAPI account
Register at app.rutaapi.com. No credit card is required to sign up.
Step 2 — Add prepaid credits
Purchase a credit pack from the billing section. Credits are added immediately after payment. Requests without sufficient credits return 401 or 403.
Step 3 — Create an API key
Go to the Tokens section and create a new key. Copy it right away — it is shown only once at creation.
Security: Never paste your full API key into screenshots or shared scripts. If exposed, rotate it immediately from the dashboard.
Step 4 — Verify /v1/models
Before configuring Cline, confirm the key works by calling /v1/models:
A 200 response with a model list means the key is valid. A 401 response means the key is wrong or revoked.
curl https://api.rutaapi.com/v1/models \
-H "Authorization: Bearer YOUR_RUTAAPI_KEY"Step 5 — Copy a returned model id
Use one of the model id values from the /v1/models response as YOUR_ENABLED_MODEL_ID. Do not guess — identifiers differ between providers.
Run /v1/models and copy the exact id string. The Model ID in Cline must match one of the returned model identifiers.
Step 6 — Configure Cline
In Cline settings, choose an OpenAI-compatible provider option if your version supports it. Enter https://api.rutaapi.com/v1 as the Base URL, paste your RutaAPI API key where the OpenAI-compatible API key is expected, and use a model id returned by /v1/models as the Model ID.
Do not use https://rutaapi.com, https://app.rutaapi.com, or https://api.rutaapi.com/v1/chat/completions as the Base URL. Do not promise exact UI labels because Cline changes over time.
Step 7 — Send a small test request
Before running any coding tasks, send a simple request to confirm end-to-end connectivity:
A successful response confirms the key, Base URL, Model ID and credits are all working correctly.
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": "Hello from RutaAPI"}
]
}'Who this guide is for
This guide is for Cline users who want to connect Cline to an OpenAI-compatible API gateway provided by RutaAPI.
It helps if you are familiar with API keys, Base URLs and making HTTP requests from a terminal.
Who should not use this setup
- Users whose Cline version does not support external OpenAI-compatible provider configuration.
- Users who require official Cline, OpenAI or Anthropic-only features.
- Users whose tool does not support custom API endpoints.
Testing before you start coding
Before running any Cline coding tasks, send a simple request from the terminal to confirm your key, Base URL and Model ID all work together. This rules out configuration issues before you start a real session.
If the first request succeeds, the Cline configuration should also work. If it fails, fix the terminal request first — that gives you clearer error messages than the Cline UI.
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 more credits or contact support.
Common mistakes
- Pasting the website URL (https://rutaapi.com) as the Base URL instead of the API root.
- Pasting the dashboard URL (https://app.rutaapi.com) as the Base URL.
- Pasting https://api.rutaapi.com/v1/chat/completions as the Base URL — that is an endpoint, not the root.
- Using a key from one provider with a Base URL from another.
- Guessing the Model ID instead of copying from /v1/models.
Common errors
401 Unauthorized / invalid API key
The API key is missing, incorrect, or sent to the wrong Base URL. Verify the key and Base URL both come from RutaAPI. Run /v1/models to confirm the key is valid.
403 Forbidden
The key exists but lacks permission. Check credits and model access in your RutaAPI account.
404 Model not found
The Model ID is not in your account. Run GET /v1/models and copy a returned model id.
429 Too Many Requests
Rate or concurrency limit. Lower the number of concurrent requests and retry.
503 Service Unavailable
The provider route is temporarily unavailable. Try a short request or contact support if persistent.
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 the needed provider mode
- The selected model is unavailable upstream
- Your API key belongs to another provider
- You require official Cline, OpenAI or Anthropic-only features
- You need official Cline or OpenAI-only features instead of a gateway
Related setup guides
- API Key and Base URL explained
- Unified Base URL for AI coding tools
- Cursor custom API setup guide
- Codex CLI setup with RutaAPI
- Claude Code setup with RutaAPI
- Codex CLI invalid_api_key troubleshooting
- Claude Code timeout troubleshooting
- Available models
- Pricing and credit packs
FAQ
Where do I put API keys in Cline?
In Cline, paste your provider API key into the Cline API Key field in the OpenAI-compatible provider settings. The Cline API key must be the key from the same provider as the Base URL. For RutaAPI, create the key in the RutaAPI dashboard and paste it where Cline asks for the API key.
Can I use a RutaAPI key as a Cline API key?
Yes. If you are using the RutaAPI Base URL (https://api.rutaapi.com/v1), create a RutaAPI API key from the dashboard and paste it into the Cline API Key field. The Cline API key must match the Base URL.
Can I use an OpenAI key with the RutaAPI Base URL?
No. Do not use an OpenAI API key with the RutaAPI Base URL. Each provider's API key only works with its own Base URL. If you use an OpenAI key with the RutaAPI Base URL, Cline will return a 401 invalid_api_key error.
Can I use a RutaAPI key with another provider's Base URL?
No. A RutaAPI API key only works with the RutaAPI Base URL. If you enter a RutaAPI key with another provider's Base URL, the connection will fail with 401.
Why does Cline say my API key is invalid?
An invalid Cline API key error usually means the API key does not match the Base URL, or it was sent to the wrong endpoint. Verify that both the key and Base URL come from the same platform. Run /v1/models to confirm the key is valid. Do not use an OpenAI key with the RutaAPI Base URL.
Is the Cline API key the same as the model provider API key?
Yes. The Cline API key is the API key from your selected OpenAI-compatible provider. It must match the Base URL you enter. For RutaAPI, this means the Cline API key should be a RutaAPI key when the Base URL is set to https://api.rutaapi.com/v1.
What should I check before changing Cline API keys?
Before changing the Cline API key, verify the new key works by running /v1/models with it. Make sure the key and Base URL belong to the same provider. Add prepaid credits if needed. Do not paste keys into screenshots or public channels.
Should I share my Cline API key in screenshots?
No. Never share your full Cline API key in screenshots, forum posts, public GitHub issues or any shared channel. If exposed, rotate it immediately from the dashboard.
What does Cline Model ID mean?
The Cline Model ID is the exact identifier of the AI model that processes your requests. It must match one of the model ids returned by /v1/models for your account. Do not guess the Model ID — always copy from the /v1/models response.
How do I verify the model before using it in Cline?
Call GET /v1/models with your API key and check that the model appears in the response. Use one of the returned model ids as the Model ID in Cline. If the model is not in the /v1/models response, it is not active in your account — add credits or contact support.
What Base URL should I use for RutaAPI in Cline?
Use https://api.rutaapi.com/v1 — the /v1 path is the OpenAI-compatible API root. Always include /v1. Do not use https://rutaapi.com, https://app.rutaapi.com, or any path ending in /chat/completions.
Should the Cline Base URL include /v1?
Yes. The correct RutaAPI Base URL is https://api.rutaapi.com/v1. Without /v1, you are pointing to a non-API endpoint and will get 404 or 401 errors.
Can I use https://rutaapi.com as the Base URL?
No. https://rutaapi.com is the marketing site, not the API root. Using it as the Base URL will result in errors. Always use https://api.rutaapi.com/v1.
Can I use https://app.rutaapi.com as the Base URL?
No. https://app.rutaapi.com is for account management, not the API. Using it as the Base URL will result in errors. Always use https://api.rutaapi.com/v1.
Where do I get my RutaAPI API key?
Create one from the RutaAPI dashboard at https://app.rutaapi.com in the Tokens section. Keys are shown only once at creation — copy and store them securely.
How do I know which Model ID to use?
Run GET /v1/models with your API key and use one of the model id values from the response as the Model ID in Cline. Do not guess — identifiers differ between providers.
Can a wrong Base URL cause 401?
Yes. If the Base URL belongs to a different provider than the API key, the provider rejects the key with 401. The key and Base URL must come from the same platform.
What does 403 mean?
HTTP 403 means the key exists but lacks permission. Check that your account has enough prepaid credits and that the model is enabled for your account tier.
What does 404 model not found mean?
HTTP 404 means the Model ID is not recognised at that endpoint. Run /v1/models and use one of the returned model id values as the Model ID. Do not guess.
What does 429 mean?
HTTP 429 means you have hit a rate or concurrency limit. Lower the number of concurrent requests, pause parallel tasks and retry after a short pause.
What does 503 mean?
HTTP 503 means the provider route is temporarily unavailable. Try a short request, check model availability, and contact support if the issue persists.
Is RutaAPI an official Cline or OpenAI service?
No. RutaAPI is an OpenAI-compatible API gateway operated by BDR FIDUCIARY LLC. It is not an official service of Cline, OpenAI, Anthropic, Google or Microsoft.
Can RutaAPI guarantee Cline compatibility?
No. Cline provider behaviour can change by version. RutaAPI cannot guarantee compatibility with every Cline version. Verify the current Cline UI in your installed version before configuring a custom provider.
What should I send to support?
Include: request time (UTC), model name, error code, Base URL, any request ID from response headers, and approximate request size. Do not share your full API key. Describe the key prefix if needed.