On this page
01
Why this works
Cloptima exposes an Anthropic-compatible endpoint and translates between protocols. So any tool that speaks the Anthropic Messages API — Claude Code, the Anthropic SDKs, editor agents — can drive non-Anthropic models through Cloptima without code changes, while you keep budgets, policy, and attribution.
02
Point Claude Code at Cloptima
Set the Anthropic base URL to Cloptima and use a Cloptima virtual key. Pick whatever model your policy approves — the upstream provider can be OpenAI, Gemini, or Bedrock.
export ANTHROPIC_BASE_URL="https://api.cloptima.ai"
export ANTHROPIC_API_KEY="clop_vk_dPXO67p…" # Cloptima virtual key (sent as x-api-key)
# Run Claude Code as usual. Choose an approved model — e.g. a Gemini or GPT model —
# and Cloptima routes, governs, and records the usage under your team/app.03
Attribution without extra plumbing
When a tool can't easily set custom headers, bind the team and app to the virtual key itself. Policy and attribution use the key's principal, so usage is owned and budgeted even when the client only sends a model and a key.
04
It stays governed
Model allowlists, budgets, token/rate limits, and no-retention prompt policy all still apply. Spend shows up in the same explorer alongside your other AI usage.