# API key configuration by tool

> One table: where each client expects the key and the base URL, with the /v1 suffix spelled out.

_Source: https://aiprimetech.io/docs/guides/api-key-configuration/ · Home > Docs > Integration guides_

A single reference so you do not have to open five guides to remember one suffix.

| Tool | Key goes in | Base URL |
|---|---|---|
| Claude Code | `ANTHROPIC_AUTH_TOKEN` | `https://aiprimetech.io` |
| Anthropic SDK (Python/TS) | `api_key=` or `ANTHROPIC_API_KEY` | `https://aiprimetech.io` |
| OpenAI SDK (Python/TS) | `api_key=` or `OPENAI_API_KEY` | `https://aiprimetech.io/v1` |
| Cursor | Settings → Models → OpenAI key | `https://aiprimetech.io/v1` |
| Cline | Extension settings, Anthropic provider | `https://aiprimetech.io` |
| Continue | `apiKey` in `config.json` | `https://aiprimetech.io` (anthropic) / `https://aiprimetech.io/v1` (openai) |
| Aider | `ANTHROPIC_API_KEY` / `OPENAI_API_KEY` | `ANTHROPIC_API_BASE` / `OPENAI_API_BASE` |
| Codex CLI | `OPENAI_API_KEY` | `https://aiprimetech.io/v1` |
| Zed | Assistant provider settings | `https://aiprimetech.io/v1` |
| LangChain / LiteLLM | `OPENAI_API_KEY` | `https://aiprimetech.io/v1` |
| curl (Messages) | `x-api-key` header | `https://aiprimetech.io/v1/messages` |
| curl (Chat Completions) | `Authorization: Bearer` | `https://aiprimetech.io/v1/chat/completions` |

> Anthropic-format clients take the bare origin. OpenAI-format clients take the origin plus `/v1`. That one line resolves most support questions we get.

- [Authentication](https://aiprimetech.io/docs/getting-started/authentication/) — Header reference
- [Base URLs](https://aiprimetech.io/docs/getting-started/base-urls/) — Why the suffix differs
- [Troubleshooting](https://aiprimetech.io/docs/guides/troubleshooting/) — Symptom-first index


---
_ClaudeAPIKey.dev is an independently operated, Anthropic-compatible API gateway. Not affiliated with Anthropic._