Skip to content

Client parameters

Create a separate Nexus profile for each client. Use an exact model identifier returned by GET /v1/models.

Client Profile Base URL Key Guide
Codex CLI OpenAI Responses https://api.nexus-hub.ru/v1 NEXUS_API_KEY Codex
ChatGPT / Codex Desktop OpenAI Responses https://api.nexus-hub.ru/v1 NEXUS_API_KEY Codex Desktop
Claude Code Anthropic Messages https://api.nexus-hub.ru ANTHROPIC_AUTH_TOKEN Claude Code
Claude Desktop Anthropic Messages https://api.nexus-hub.ru API Key or ANTHROPIC_AUTH_TOKEN Claude Desktop
VS Code Custom Endpoint depends on the selected protocol input variable VS Code
Zed OpenAI-compatible or Anthropic-compatible /v1 for OpenAI, no /v1 for Anthropic keychain or environment variable Zed
T3 Code separate Codex or Claude Code profile depends on the profile API Key or environment variable T3 Code
CC Switch separate Codex or Claude Code entry depends on the entry protected profile field CC Switch
Direct API / cURL OpenAI, Anthropic, or Gemini depends on the protocol authorization header Direct API
Custom integration OpenAI, Anthropic, or Gemini depends on the protocol secret manager or environment variable Custom integration
Other client custom endpoint depends on the protocol protected client field Other client

Choosing a URL

  • OpenAI Responses and Chat Completions: https://api.nexus-hub.ru/v1;
  • Anthropic Messages: https://api.nexus-hub.ru;
  • Gemini-compatible: https://api.nexus-hub.ru/v1beta.

Enter the base URL rather than the operation's full route. For example, a Responses client appends /responses, while an Anthropic client appends /v1/messages.