docs/en/guides/claude-code-integration.md

Claude Code Integration Guide

---

Overview

AxonHub can act as a drop-in replacement for Anthropic endpoints, letting Claude Code connect through your own infrastructure. This guide explains how to configure Claude Code and how to combine it with AxonHub model profiles for flexible routing.

Key Points

• AxonHub performs AI protocol/format transformation. You can configure multiple upstream channels (providers) and expose a single Anthropic-compatible interface for Claude Code.
• You can aggregate Claude Code requests from the same session into one trace (see "Configure Claude Code").

Prerequisites

• AxonHub instance reachable from your development machine.
• Valid AxonHub API key with project access.
• Access to Claude Code (Anthropic) application.
• Optional: one or more model profiles configured in the AxonHub console.

Configure Claude Code

1. Open your shell environment and export the AxonHub credentials:

   export ANTHROPIC_AUTH_TOKEN="<your-axonhub-api-key>"
   export ANTHROPIC_BASE_URL="http://localhost:8090/anthropic"
   # Or using the root path:
   # export ANTHROPIC_BASE_URL="http://localhost:8090"
   

2. Launch Claude Code. It will read the environment variables and route all Anthropic requests through AxonHub.
3. (Optional) Confirm the integration by triggering a chat completion and checking AxonHub traces.

Trace aggregation (important)

To aggregate requests from the same Claude Code session into a single trace, enable the following in config.yml:

server:
  trace:
    claude_code_trace_enabled: true

Note: Enabling this also ensures that requests from the same trace are prioritized to be sent to the same upstream channel, significantly improving provider-side cache hit rates (e.g., Anthropic Prompt Caching).

Tips

• Keep your API key secret; store it in a shell profile or secret manager.
• If your AxonHub endpoint uses HTTPS with a self-signed certificate, configure trust settings in your OS.

Working with Model Profiles

AxonHub model profiles remap incoming model names to provider-specific equivalents:

• Create a profile in the AxonHub console and add mapping rules (exact name or regex).
• Assign the profile to your API key.
• Switch active profiles to alter Claude Code/Codex behavior without changing tool settings.

Model Profiles

Example

• Request claude-sonnet-4-5 → mapped to deepseek-reasoner for getting more accurate responses.
• Request claude-haiku-4-5 → mapped to deepseek-chat for reducing costs.

Troubleshooting

• Claude Code cannot connect: verify ANTHROPIC_BASE_URL points to the /anthropic path and that your firewall allows outbound calls.
• Unexpected model responses: review active profile mappings in the AxonHub console; disable or adjust rules if necessary.

---

Using Claude Code as a Provider Channel

AxonHub can also use your Claude Code subscription as a backend provider, allowing non-Claude Code tools to leverage Claude Code's capabilities. This is useful when you want to route requests from other applications (OpenAI-compatible clients, custom tools, etc.) through Claude Code.

Prerequisites

• Claude Code CLI installed (https://claude.com/claude-code)
• Valid Anthropic account with Claude Code subscription
• AxonHub instance with channel management access

Getting an Authentication Token

To configure Claude Code as a provider channel, you need a long-lived authentication token:

1. Run the token setup command:

   claude setup-token
   

2. You will be prompted to authenticate with your Anthropic account through your browser

3. Upon successful authentication, a long-lived token starting with sk-ant will be printed to your terminal:

   Your authentication token: sk-ant-api03-xyz...
   

4. Copy this token - you'll use it in the AxonHub channel configuration

Configuring the Channel

1. Navigate to the Channels section in the AxonHub management interface

2. Create a new channel with the following configuration:

   • Type: claude-code

   • Name: A descriptive name (e.g., "Claude Code Provider")

   • Base URL: Defaults to https://api.anthropic.com/v1. You can point this to a reverse proxy or compatible gateway; AxonHub will send requests to {baseURL}/messages (or {baseURL}/v1/messages depending on whether your base URL ends with /v1).

   • API Key: The token from claude setup-token (starts with sk-ant)

   • Supported Models: Add the Claude models you want to expose:

     • claude-haiku-4-5
     • claude-sonnet-4-5
     • claude-opus-4-5

     Note: These are the unversioned 'latest' variants. You can also use specific versioned model names (e.g., claude-sonnet-4-5-20250514) if you prefer to pin to a specific version.

3. Test the connection using the Test button

4. Enable the channel once the test succeeds

Use Cases

• Multi-Tool Access: Allow multiple applications to share your Claude Code subscription through AxonHub
• Cost Management: Use Claude Code alongside other providers with load balancing and failover
• Extended Context: Route requests requiring large context windows through Claude Code
• Model Flexibility: Combine Claude Code with other providers using model profiles for intelligent routing

Troubleshooting

• Channel test fails: Verify the configured base URL is reachable and the endpoint is compatible with Anthropic Messages API
• Authentication errors: Verify the token from claude setup-token is correct and hasn't expired
• Network issues: If using a remote gateway/proxy, check firewall rules and network connectivity
• Model not available: Confirm the requested model is listed in the channel's supported_models

---

Provider Quota Tracking

AxonHub automatically tracks quota usage for Claude Code provider channels, displaying the current status with battery icons in the interface.

How It Works

• Automatic Polling: AxonHub periodically polls your Claude Code account to check quota status
• Storage: Quota data is stored in the database and updated based on the configured check interval
• Visual Indicators: Battery icons show your remaining quota at a glance.

Quota Buckets

Claude Code uses two quota windows:

• 5-hour window: Usage limits over a 5-minute rolling period
• 7-day window: Usage limits over a 7-day rolling period

The system shows both bucket percentages and indicates which bucket is currently limiting your access.

Configuration

Adjust the quota check interval in config.yml:

provider_quota:
  check_interval: "20m"          # Check every 20 minutes (default)

Or via environment variable:

export AXONHUB_PROVIDER_QUOTA_CHECK_INTERVAL="30m"

Supported intervals: 1m, 2m, 3m, 4m, 5m, 6m, 10m, 12m, 15m, 20m, 30m, 1h, 2h, etc.

Recommendations:

• Development: Use shorter intervals (e.g., 5m) for quick feedback
• Production: Use 20m or longer to reduce API calls

Refreshing Quota Data

You can manually trigger a quota refresh by clicking the refresh icon in the quota status popover.

Viewing Quota Status

1. Look for the battery icon next to the settings gear in the header
2. Click the battery icon to view detailed quota information including:
   • 5-hour and 7-day window usage percentages
   • Which quota bucket is currently limiting access
   • Time until the quota window resets

---

Related Documentation

• Tracing Guide
• OpenAI API
• Codex Integration Guide
• Channel Management Guide
• README sections on Usage Guide