To use RutaAPI with Continue.dev, configure an OpenAI-compatible provider pattern if your version supports it, set apiBase or baseUrl to https://api.rutaapi.com/v1, use a RutaAPI API key, and choose a model returned by /v1/models. The provider, API key, Base URL and model 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. Exact config field names such as apiBase or baseUrl may vary by Continue.dev version.
Need the full setup guide? Read the complete Continue.dev 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.
Continue.dev OpenAI-compatible API: apiBase, baseUrl and API key Continue.dev can use an OpenAI provider pattern for OpenAI-compatible APIs when supported by the user's version and config. Depending on config format or version, fields may be named apiBase or baseUrl. The API key must match the apiBase/baseUrl. For RutaAPI OpenAI-compatible usage, use https://api.rutaapi.com/v1 as the Base URL, use YOUR_RUTAAPI_KEY as the API key, and use a model returned by /v1/models. Exact config field names can vary across Continue.dev versions and config formats.
What Continue.dev asks for When you configure Continue.dev to use a custom OpenAI-compatible provider, Continue.dev typically asks for a model name, an API key, and a Base URL or provider endpoint. 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 Continue.dev OpenAI-compatible means an API that uses the same request and response format as OpenAI — the same JSON structure, field names and endpoint paths. Continue.dev docs state that for many OpenAI-compatible APIs, users can use the openai provider and change baseUrl to point to their server. This lets Continue.dev connect to any gateway that follows the OpenAI 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 Continue.dev 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 name is The model name 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.
Continue.dev version caveat Continue.dev configuration format, provider names and supported fields can change by version. Official Continue.dev docs show provider configuration around model, provider and API key, and also state that OpenAI-compatible APIs can often use the openai provider with a changed baseUrl. Users should verify the current Continue.dev config reference for their installed version before relying on a setup.
RutaAPI disclaimer RutaAPI is an OpenAI-compatible API gateway. It is not an official Continue.dev, 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 Continue.dev, 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 name
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 name in Continue.dev must match one of the returned model identifiers.
Step 6 — Configure Continue.dev
In Continue.dev config, use an OpenAI-compatible provider pattern if your installed version supports it. For many OpenAI-compatible APIs, Continue.dev docs state that users can use the openai provider and change baseUrl to point to their server.
Exact field names such as apiBase or baseUrl can vary across Continue.dev versions and config formats. Check the current Continue.dev config reference for your version. Do not promise exact config keys because Continue.dev changes over time.
models:
- name: RutaAPI model
provider: openai
model: YOUR_ENABLED_MODEL_ID
apiKey: YOUR_RUTAAPI_KEY
apiBase: https://api.rutaapi.com/v1Step 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 name 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 Continue.dev users who want to connect Continue.dev to an OpenAI-compatible API gateway provided by RutaAPI.
It helps if you are familiar with YAML config files, API keys and making HTTP requests from a terminal.
Who should not use this setup
- Users whose Continue.dev version or config format does not support external OpenAI-compatible provider configuration.
- Users who require official Continue.dev or OpenAI-only features.
- Users whose tool does not support custom API endpoints.
Testing before you start coding
Before running any Continue.dev coding tasks, send a simple request from the terminal to confirm your key, Base URL and model name all work together. This rules out configuration issues before you start a real session.
If the first request succeeds, the Continue.dev configuration should also work. If it fails, fix the terminal request first — that gives you clearer error messages than the Continue.dev UI.
How to pick a model name
Model names are returned by the GET /v1/models endpoint. Copy one of the model id values from the response and use it as the model name in your Continue.dev config.
Model availability is per-account. If a model name 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 name instead of copying from /v1/models.
- Using a config format or field name that your Continue.dev version does not support.
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 name 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 Continue.dev
- 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, Continue.dev, Codex CLI and Claude Code
- You want usage visibility before scaling
When RutaAPI may not be the right fit
- Your Continue.dev version or config format does not support the needed provider mode
- The selected model is unavailable upstream
- Your API key belongs to another provider
- You require official Continue.dev or OpenAI-only features
Related setup guides
- API Key and Base URL explained
- Unified Base URL for AI coding tools
- Cursor custom API setup guide
- Cline OpenAI-compatible API setup
- 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
Can Continue.dev use an OpenAI-compatible API?
Yes. Continue.dev can use an OpenAI-compatible API when the config is set up correctly. For OpenAI-compatible providers, Continue.dev typically uses an openai provider pattern with apiBase or baseUrl pointing to the provider's API root. Exact config field names can vary by version.
Should I use apiBase or baseUrl in Continue.dev?
That depends on your Continue.dev version and config format. Some versions use apiBase, others use baseUrl. Check the current Continue.dev config reference for your installed version. Do not assume both names work interchangeably — use the field name that matches your version.
What Base URL should I use for RutaAPI in Continue.dev?
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.
Can missing /v1 cause Continue.dev errors?
Yes. Without /v1, you are pointing to a non-API endpoint. This causes 401 or 404 errors. The correct RutaAPI Base URL for Continue.dev is https://api.rutaapi.com/v1 — it must include /v1.
Why does Continue.dev not show my model?
The model may not be in your account, not active, or not assigned correctly in your Continue.dev config. Verify the model name matches an id from /v1/models. Check that the model is assigned to the correct role or feature in your config. Reload or restart Continue.dev after config changes.
Can wrong apiBase/baseUrl cause 401?
Yes. If the apiBase/baseUrl belongs to a different provider than the API key, the provider rejects the key with 401. The apiBase/baseUrl and API key must come from the same platform.
Can wrong apiBase/baseUrl cause 404 model not found?
Yes. If the apiBase/baseUrl is wrong or missing /v1, the endpoint may not exist and return 404. Always verify the Base URL ends with /v1 and matches the provider.
Should I copy the model from /v1/models?
Yes. Always copy the model name from the /v1/models response. Do not guess the model identifier — it must match exactly. If the model is not in the response, it is not active in your account.
Do I need to reload or restart Continue.dev after config changes?
Possibly. After editing the config file, reload or restart Continue.dev to apply changes. If the model still does not appear, verify the config file is saved and the correct file is being read.
Is RutaAPI an official Continue.dev or OpenAI service?
No. RutaAPI is an OpenAI-compatible API gateway operated by BDR FIDUCIARY LLC. It is not an official service of Continue.dev, OpenAI, Anthropic, Google or Microsoft.
Can RutaAPI guarantee Continue.dev compatibility?
No. Continue.dev configuration format and provider behaviour can change by version. RutaAPI cannot guarantee compatibility with every Continue.dev version or config format. Verify the current Continue.dev config reference for your installed version.
Should the Continue.dev 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 name to use?
Run GET /v1/models with your API key and use one of the model id values from the response as the model name in your Continue.dev config. Do not guess — identifiers differ between providers.
Why does Continue.dev show invalid API key?
An invalid_api_key or 401 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.
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 name is not recognised at that endpoint. Run /v1/models and use one of the returned model id values as the model name. 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.
Should I paste my API key into screenshots?
No. Never share your full API key in screenshots, forum posts or any public or shared channel. If exposed, rotate it immediately from the dashboard.
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.