Continue

Create your API key →

Mint an aireserve_api_… key in the portal — Continue’s chat, edit, and agent requests are then metered and billed through your organization.

Continue (VS Code, JetBrains, and the cn CLI) reads models from ~/.continue/config.yaml (config reference). Any OpenAI-compatible gateway is provider: openai plus an apiBase — Claude models included, since the gateway bridges them onto the same surface:

name: AI Reserve
version: 0.0.1
schema: v1

models:
  - name: AI Reserve GPT-5.4 Mini
    provider: openai
    model: gpt-5.4-mini
    apiBase: https://api.aireserve.com/v1
    apiKey: aireserve_api_…   # your key — keep this file private
    roles:
      - chat
      - edit
      - apply
  - name: AI Reserve Claude Sonnet 4.6
    provider: openai
    model: claude-sonnet-4-6
    apiBase: https://api.aireserve.com/v1
    apiKey: aireserve_api_…
    roles:
      - chat
      - edit
      - apply

Keep the /v1 suffix on apiBase. Continue appends /chat/completions to it — without /v1 the request 404s, and Continue’s own error message points here.

Verify

The fastest end-to-end check is the CLI in headless mode:

npm install -g @continuedev/cli
cn --config ~/.continue/config.yaml -p "Reply with exactly: gateway-ok"

The reply streams back through the gateway, and the request appears on your usage page. The IDE extensions read the same config.yaml — pick the AI Reserve model from Continue’s model dropdown and everything (chat, edit, apply) routes the same way.

⌘I

Getting started

Connect your tool

Models

Capabilities

Migrate

Data & privacy

Create your API key →

Verify

Create your API key →

​Verify

Verify