NeverMetered
Get API key

Use NeverMetered with Continue

Open-source assistant for VS Code and JetBrains, configured in config.yaml.

OpenAI Chat
Model
qwen3.8-27b
128K context on the free plan65,536 max output tokens on the free planReplace YOUR_API_KEY with your key.
  1. 1

    Create an API key

    Create a key in API keys and name it after the tool, for example “Continue”. A dedicated key per tool lets you see its usage separately and give it its own parallel-stream cap. The key is shown once; the snippets below use YOUR_API_KEY where it goes.

  2. 2

    Install Continue

    Already have Continue? Skip this step. In VS Code press Ctrl+Shift+X (⌘ Shift X on macOS), search for Continue (published as Continue.continue) and click Install. In JetBrains IDEs find it under Settings → Plugins.

  3. 3

    Add the model to your config

    Open Continue's local config and add the model (merge the models entry if the file already has some). capabilities: tool_use lets Continue's agent mode call tools with it.

    ~/.continue/config.yaml
    name: NeverMetered assistant
version: 1.0.0
schema: v1
models:
  - name: NeverMetered qwen3.8-27b
    provider: openai
    model: qwen3.8-27b
    apiBase: https://api.nevermetered.com/v1
    apiKey: YOUR_API_KEY
    roles:
      - chat
      - edit
      - apply
    capabilities:
      - tool_use
    defaultCompletionOptions:
      contextLength: 131072
      maxTokens: 65536
  4. 4

    Verify it works

    Reload the Continue panel, pick the model and send a message. The request shows up in Requests within a few seconds, with its input, cached and output tokens.

Tips
  • Keep the config file out of version control, since it contains your key.

Troubleshooting

404 model_not_found
Use a model id exactly as GET /v1/models lists it, for example qwen3.8-27b. Plans can restrict which models a key may call.
400 context_length_exceeded
The conversation outgrew the 128K context window (input + output). Let the tool compact or start a fresh session, or get a larger window on your plan.
429 concurrency_limit_exceeded
All your parallel streams are busy and your queue allowance is full. Lower the tool's parallelism (subagents, batch size), or get more streams on your plan.
Answers stop mid-sentence
The response hit your plan's output cap of 65,536 tokens (finish reason length or max_tokens). Ask for shorter steps, or upgrade for a higher cap.
403 email_verification_required
Free requests need a verified email. Click the link in your verification email (you can resend it from the dashboard), or upgrade.
429 daily_quota_exceeded
You've used today's free requests; agents send one request per step, so they go quickly. The allowance resets at 00:00 UTC, and paid plans have no daily limit.
503 / 504 request_queue_timeout
The service stayed busy longer than the queue timeout and nothing was generated. Retry with backoff, and give the tool a generous request timeout.
503 service_unavailable
No GPU capacity is online at the moment. It's temporary and your setup is fine: retry in a little while, and check the status page.