Overview
Pick your coding agent and the right model.
AivoKey works with every popular coding agent. Find your tool below and follow its page — each one is a copy-paste setup.
Pick your tool
| Tool | Setup page | Base URL to use |
|---|---|---|
AivoCode CLI (aivo) | AivoCode CLI | https://api.aivokey.dev (configured automatically) |
| Claude Code | Claude Code | https://api.aivokey.dev (no /v1) |
| Codex CLI | Codex | https://api.aivokey.dev/v1 |
| OpenCode | OpenCode | https://api.aivokey.dev/v1 |
| Cline, Roo Code, Kilo Code | VS Code extensions | https://api.aivokey.dev/v1 |
| Continue, Aider, SDKs, others | Other tools & SDKs | https://api.aivokey.dev/v1 |
Rule of thumb: Anthropic-style tools (Claude Code, Anthropic SDK) get the base URL without /v1. Everything else gets it with /v1.
Choosing a model for coding
Coding agents read files, run commands and edit code through tool calls, so the model must support tools.
- On the Models page, pick a model with the tools badge. A model without it can chat, but cannot act in an agent.
- Bigger context windows let the agent hold more of your project at once.
- Models with the cache badge get cheaper on long sessions (see Prompt caching).
- If you have a plan, use a model your plan includes — otherwise the request is refused with
model_not_in_plan(see Model access).
One key per machine
Create a separate key for each computer or tool. If a key leaks, you revoke just that one in Console → API keys and everything else keeps working.
Web search
Claude Code's WebSearch and Codex's web search work with every model through AivoKey — see Web search & fetch.