AI Tools
Route your AI coding tools through Axemere Gateway to get governance, attribution, and audit logging over every request, without changing how you write code.
All tools that support a custom base URL work the same way: point the tool's base URL env var at your gateway endpoint. The gateway applies your org's policies, records the request, and forwards it to the AI provider.
Supported Tools
| Tool | Status |
|---|---|
| Claude CLI | Full guide |
| VS Code (Claude Code) | Full guide |
| Continue.dev | Full guide |
| JetBrains AI | Full guide |
| Cline | Full guide |
| Xcode (Claude Code) | Full guide |
| Any OpenAI-compatible SDK | Full guide |
| Zed | Coming soon |
| Neovim | Coming soon |
Not Supported
These tools route AI traffic through their own proprietary backends. There is no base URL setting that can redirect requests through a gateway; governance and attribution are not possible without changes from the vendor.
| Tool | Reason |
|---|---|
| Cursor | Routes through Anysphere's backend |
| Windsurf | Routes through Codeium's backend |
| GitHub Copilot | Routes through Microsoft's backend |
If you use one of these tools and want governance over your AI usage, ask the vendor to support a configurable base URL, the same capability that makes every tool in the supported list above work with Axemere.
How It Works
Set the tool's base URL env var to your gateway endpoint. That's the only change required:
ANTHROPIC_BASE_URL=https://us.gw.axemere.ai/proxy/anthropic/k/mvgc_k_your-keyThe gateway authenticates the request using the gateway key embedded in the path, applies your org's policy bundle, writes an execution record, and forwards the request to the AI provider using the credential configured in your console.
Prerequisites for All Tools
- A running Axemere gateway: either Managed or Self-Hosted
- A gateway key from Console → Gateway Keys