Coding agents
Coding agents are where inference spend adds up fastest — long sessions, large context, many turns. Every agent below reaches Inferray through a base URL and a key, with no change to how you use the tool.
Two things decide which setup a given agent needs:
| The agent speaks | Base URL | Credential |
|---|---|---|
| OpenAI Chat Completions | https://api.inferray.com/v1 | Authorization: Bearer |
| OpenAI Responses | https://api.inferray.com/v1 | Authorization: Bearer |
| Anthropic Messages | https://api.inferray.com | x-api-key or Authorization: Bearer |
Pick your agent
- Claude Code — two environment variables, Anthropic format
- Codex — a provider block in
config.toml, Responses format - opencode — a provider block in
opencode.json - Cline — VS Code, OpenAI Compatible provider
- Roo Code — VS Code, OpenAI Compatible provider
- Aider — two environment variables and a model prefix
- Continue — an
apiBaseinconfig.yaml
Model pickers
Inferray answers GET /v1/models with the catalogue, so agents that populate a dropdown from the API will find one. Agents that don't ask — opencode and Continue declare their models in config — take the id from the models page instead. Ids look like claude-opus-4-8 or gpt-5.5, and every one of them works on all three endpoints.
Keep the key out of your repo
Agent config files are easy to commit by accident. Prefer an environment variable and reference it from the config where the agent supports that, and add any file holding a literal key to .gitignore.