Integration · Aider

Run Aider on Crazyrouter models

Aider's OpenAI-compatible mode works with Crazyrouter out of the box. Two environment variables and a model flag; use a cheap weak model for commit messages and summaries.

Get an API key

Manual configuration

Install Aider with its official installer (aider.chat/install.sh or install.ps1), then point it at Crazyrouter. The openai/ prefix is what tells LiteLLM to use your custom base URL.

Environment + launch

bash

export OPENAI_API_KEY=sk-your-crazyrouter-key
export OPENAI_API_BASE=https://api.crazyrouter.com/v1
aider --model openai/claude-opus-4-8

Aider goes through LiteLLM, so prefix the model with openai/ to force the OpenAI-compatible route.

Or ~/.aider.conf.yml

yaml

openai-api-key: sk-your-crazyrouter-key
openai-api-base: https://api.crazyrouter.com/v1
model: openai/claude-opus-4-8
weak-model: openai/deepseek-v4-flash

Base URL rule

https://api.crazyrouter.com/v1 — This tool is OpenAI-compatible and appends /chat/completions (or /responses) itself. Use the /v1 base URL exactly as shown.

Recommended models

Live Crazyrouter prices, refreshed hourly. Any model in the catalogue works; these are the ones we'd start with.

Claude Opus 4.8

claude-opus-4-8

$3.25 in · $16.25 out /1M tokens

GPT-5.5

gpt-5.5

$3.25 in · $19.50 out /1M tokens

DeepSeek V4 Flash

deepseek-v4-flash

$0.23 in · $0.67 out /1M tokens

FAQ

Why the openai/ prefix?

Aider routes through LiteLLM; the prefix selects the OpenAI-compatible provider so OPENAI_API_BASE is honoured for any model name.

Aider warns the model is unknown

That is LiteLLM's metadata warning for custom names; the request still works. Add a .aider.model.metadata.json if you want token limits recognised.

Which weak model?

deepseek-v4-flash — near-zero cost for the commit-message and summary calls Aider makes constantly.

Guides and comparisons

Podcast

AI Dev Tools: The Crazyrouter Podcast

Short episodes for developers on AI APIs, gateways, cost control and coding tools.

Latest episodes

EP196 · Oct 29, 2026 · 6:53
AI API Security Posture — Turn Controls Into Continuous Evidence
A practical guide to AI API security posture: inventory exposure, verify controls continuously, protect keys and data, constrain tools, and turn security assumptions into evidence that operators can act on.
EP195 · Oct 28, 2026 · 7:21
AI API Policy Drift — Detect When Production Rules Stop Matching Intent
A practical guide to policy drift in AI APIs: version routing and safety rules, detect stale enforcement, compare intended and observed behavior, and restore control before small gaps become incidents.