Skip to main content
Claude Code reads two env vars to decide which Anthropic-compatible endpoint to use. Set them, and every Claude Code session in that shell routes through qlaud.

Setup

That’s it. claude --print "what's 2+2" now hits qlaud → AIG → Anthropic.

What works

  • claude interactive sessions
  • claude --print non-interactive
  • --model accepts any qlaud catalog slug — even non-Anthropic ones like gpt-5.4, gemini-3-pro-preview, qwen-coder-plus, kimi-k2.6 — Claude Code’s UI is generic
  • ✅ Tool use (Bash, Read, Edit, …) — full agentic loop
  • cache_control: ephemeral markers — preserved verbatim, ~75% input cost reduction kept
  • ✅ Image content blocks (screenshots) — preserved
  • ✅ Thinking blocks — preserved

Mint a key per developer

If your team is using Claude Code internally, mint one qlaud key per developer + cap their monthly spend:
End of month, pull per-developer spend:
The by_key field gives you spend per developer, broken out by model.

CLAUDE.md snippet for multi-modal

Drop this in ~/.claude/CLAUDE.md so every session knows about qlaud’s non-chat endpoints:
Once dropped, you can prompt Claude Code with things like “generate a picture of a corgi via qlaud and save to ./corgi.png” and it’ll write the curl + base64 decode itself.