Home / Docs / API key configuration by tool

API key configuration by tool

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

View as Markdown Ask ChatGPT Ask in Claude

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

ToolKey goes inBase URL
Claude CodeANTHROPIC_AUTH_TOKENhttps://aiprimetech.io
Anthropic SDK (Python/TS)api_key= or ANTHROPIC_API_KEYhttps://aiprimetech.io
OpenAI SDK (Python/TS)api_key= or OPENAI_API_KEYhttps://aiprimetech.io/v1
CursorSettings → Models → OpenAI keyhttps://aiprimetech.io/v1
ClineExtension settings, Anthropic providerhttps://aiprimetech.io
ContinueapiKey in config.jsonhttps://aiprimetech.io (anthropic) / https://aiprimetech.io/v1 (openai)
AiderANTHROPIC_API_KEY / OPENAI_API_KEYANTHROPIC_API_BASE / OPENAI_API_BASE
Codex CLIOPENAI_API_KEYhttps://aiprimetech.io/v1
ZedAssistant provider settingshttps://aiprimetech.io/v1
LangChain / LiteLLMOPENAI_API_KEYhttps://aiprimetech.io/v1
curl (Messages)x-api-key headerhttps://aiprimetech.io/v1/messages
curl (Chat Completions)Authorization: Bearerhttps://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.
AuthenticationHeader referenceBase URLsWhy the suffix differsTroubleshootingSymptom-first index
PreviousMCP servers for Claude CodeNextCost control