Use MagmaRouter in Continue

Continue's config.yaml takes an OpenAI-style provider with a custom apiBase. The VS Code and JetBrains extensions cannot read your shell environment, so the key goes in Continue's own .env.
- Base URL
- https://api.magmarouter.com/v1
- API key
- Get one, starts sk-mr-
- Example model
- glm-5.3-xploded
A models block in config.yaml
In ~/.continue/config.yaml:
YAML
name: MagmaRouter version: 0.0.1 schema: v1 models: - name: GLM 5.3 Flash Xploded (MagmaRouter) provider: openai model: glm-5.3-xploded apiBase: https://api.magmarouter.com/v1 apiKey: ${{ secrets.MAGMAROUTER_API_KEY }} capabilities: - tool_use roles: - chat - edit - apply
Put MAGMAROUTER_API_KEY=sk-mr-... in ~/.continue/.env. The capabilities: [tool_use] line matters: Continue drops Agent mode for a model id it does not recognise unless you declare tool use, so set it only for a tool-capable model.
Pick a model
Each page has the Continue setup with that model's id and limits filled in, and what a session costs.
GLM 5.3 Xploded in Continue1M context, $2.00 in / $5.00 out per 1M
GLM 5.3 Flash Xploded in Continue1M context, $0.30 in / $1.00 out per 1M
DeepSeek V4.1 Flash 1017 Xploded in Continue1M context, $1.25 in / $2.50 out per 1M
DeepSeek Flash Lite Xploded in Continue512K context, $0.36 in / $1.44 out per 1M
MiMo V2.6 Flash Xploded in Continue1M context, $1.00 in / $2.00 out per 1M
Qwen3.8 27B Xploded in Continue1M context, $1.50 in / $5.00 out per 1M
Qwen3.8 27B Ultrafast Xploded in Continue524K context, $1.75 in / $5.50 out per 1M