Environment variables first
A base URL and key should be changeable without editing a tool, plugin, or checked-in config file.
CODING AGENT API INTEGRATIONS
Keep the provider switch in configuration.
Most coding tools need a base URL, an API key, and a model identifier. Put those values behind environment variables so a team can test a different route without changing application code.
Built around a stable OpenAI-compatible request shape.
REQUEST LEDGERillustrative
route /v1$0.42
in prompt context18.4k
out model output2.1k
↺ cached context6.8k
latency windowyour data · your keys
Provider-neutral client
Use the client your tool already supports, then point its OpenAI-compatible settings at the Codimixa API.
One change at a time
Change the route or model ID independently so a failed test tells you what moved.
GENERIC SETUP
The three values most tools need
The names differ by client, but the boundary is usually the same. Keep the values local to the process that starts the coding tool.
CODIMIXA_BASE_URL
https://api.codimixa.com/v1CODIMIXA_API_KEY
set in your shellCODIMIXA_MODEL
YOUR_MODEL_IDTool-specific setup needs its own verification
Claude Code, Codex, IDE extensions, and home-built agents do not all read the same variables or support the same response features. Use the client documentation for its exact configuration, then use the Codimixa quickstart to validate the request against the gateway.
Claude Code
Confirm the gateway or compatibility setting supported by your Claude Code release, then test a read-only repository task first.
Read Anthropic's gateway docs ↗OpenAI-compatible clients
Set the base URL to https://api.codimixa.com/v1, use a console-issued key, and select an account-visible model ID.
SETUP IN ORDER
Make the smallest change that proves the connection
A provider-neutral integration is easier to debug when the values are introduced one at a time.
| Step | Action | Evidence |
|---|---|---|
| 1 | Set the base URL | The client prints the intended endpoint without a key |
| 2 | Load a secret at runtime | The key is absent from source, logs, and browser bundles |
| 3 | Select an account-visible model | The first request uses a confirmed model ID |
| 4 | Run a read-only task | The client receives and displays a response |
| 5 | Add tools and retries | Each loop has a timeout and stop condition |
Keep setup outside checked-in code
Use the environment variable names your client supports. The following names are a neutral convention for a shell, CI job, or local wrapper; they are placeholders until you connect them to your tool.
bash
export CODIMIXA_BASE_URL="https://api.codimixa.com/v1"
export CODIMIXA_API_KEY="set-this-in-your-secret-store"
export CODIMIXA_MODEL="YOUR_MODEL_ID"TROUBLESHOOTING
When an integration fails, isolate the boundary
A 401 usually belongs to the key path, a 400 usually belongs to the request shape, and a 404 may mean the client is using the wrong base path. A 429 or 5xx response needs bounded retry behavior rather than a second client configuration change.
Confirm the same request with the quickstart before debugging a tool-specific adapter. That separates a gateway problem from a client setting problem.