Continue.dev OpenAI-compatible API setup: Base URL, API key, and model

How to start with RutaAPI

curl https://api.rutaapi.com/v1/models \
  -H "Authorization: Bearer YOUR_RUTAAPI_KEY"

What Continue.dev needs

When you configure Continue.dev with an OpenAI-compatible API provider, you typically provide four things:

• Provider — Choose OpenAI-compatible or OpenAI API-compatible so Continue.dev uses OpenAI-compatible request formatting.
• Base URL — The root address of the API gateway. The correct value is https://api.rutaapi.com/v1.
• API Key — A secret token that identifies your RutaAPI account. Create one from the dashboard.
• Model — 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.

RutaAPI values for Continue.dev

Base URL: https://api.rutaapi.com/v1

API key: Create one after signing in to RutaAPI at https://app.rutaapi.com.

Model: Use a model ID visible in the RutaAPI app pricing/dashboard. Run GET /v1/models to see which models are enabled.

Example Continue.dev config

Here is a general Continue.dev config example. Replace the placeholder values with your actual RutaAPI credentials:

{
  "models": [
    {
      "title": "RutaAPI model",
      "provider": "openai",
      "model": "YOUR_ENABLED_MODEL_ID",
      "apiBase": "https://api.rutaapi.com/v1",
      "apiKey": "YOUR_RUTAAPI_KEY"
    }
  ]
}

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 in Continue.dev 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/dashboard.

Common Continue.dev setup mistakes

Cost and usage tracking

RutaAPI uses prepaid credits. Check the app pricing for model rates and the dashboard logs for usage and remaining balance.

Users should review usage logs and remaining balance after initial test calls.

View model pricing

Continue.dev setup checklist

• I selected an 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 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, Codex CLI, Claude Code and Continue.dev
• You want usage visibility before scaling

When RutaAPI may not be the right fit

• Your Continue.dev version does not support OpenAI-compatible provider configuration
• The selected model is unavailable upstream
• Your API key belongs to another provider
• You require official Continue.dev, OpenAI or Anthropic-only features