Fixie gives you a static IP address for your Claude Code agent so outbound HTTP and HTTPS requests can reach services that require IP whitelisting.

Use this setup when Claude Code needs to call a private API, webhook endpoint, SaaS admin API, internal tool, or any third-party service that only accepts traffic from approved IP addresses. Claude Code runs through Fixie, and the remote service sees your Fixie static IP addresses instead of the changing IP address of your laptop, development container, or remote host.

This page is for HTTP and HTTPS requests from Claude Code. For databases, SSH, SFTP, FTP, and other raw TCP connections, use Fixie Socks with a SOCKS-aware client or fixie-wrench.

1. Create a Fixie HTTP/S proxy

Create a Fixie HTTP/S proxy in the Fixie Dashboard, then copy its proxy URL. It will look like:

http://fixie:YOUR_TOKEN@YOUR_SUBDOMAIN.usefixie.com:80

Each Fixie proxy group has two static IP addresses. Add both IP addresses from the Fixie dashboard to the allowlist for the service your Claude Code agent needs to call.

2. Start Claude Code with Fixie proxy variables

Claude Code supports standard HTTP proxy environment variables. Start Claude Code with Fixie configured as the HTTP and HTTPS proxy:

export FIXIE_URL="http://fixie:YOUR_TOKEN@YOUR_SUBDOMAIN.usefixie.com:80"
export HTTPS_PROXY="$FIXIE_URL"
export HTTP_PROXY="$FIXIE_URL"
export NO_PROXY="localhost,127.0.0.1,::1"

claude

Claude Code does not support SOCKS proxies, so use the Fixie HTTP/S proxy URL for Claude Code itself. If your workflow needs raw TCP through a static IP, use a SOCKS-aware command or fixie-wrench inside a command that Claude Code runs.

3. Store the proxy in Claude Code settings

Claude Code can also read these values from ~/.claude/settings.json:

{
  "env": {
    "HTTPS_PROXY": "http://fixie:YOUR_TOKEN@YOUR_SUBDOMAIN.usefixie.com:80",
    "HTTP_PROXY": "http://fixie:YOUR_TOKEN@YOUR_SUBDOMAIN.usefixie.com:80",
    "NO_PROXY": "localhost,127.0.0.1,::1"
  }
}

Prefer a user-local settings file for this. Do not put Fixie credentials in shared project settings.

4. Verify the static IP address

Run a request from the same Claude Code environment that will call the whitelisted service:

curl --proxy "$FIXIE_URL" http://welcome.usefixie.com
curl https://api.ipify.org

The first command verifies explicit Fixie proxy use. The second command verifies that the current shell environment is honoring the proxy variables.

Troubleshooting Claude Code static IP requests

If the remote service still sees the wrong IP address:

• Confirm both Fixie static IP addresses are on the remote service's allowlist.
• Confirm Claude Code was started from the shell where HTTP_PROXY and HTTPS_PROXY are set, or that ~/.claude/settings.json contains the proxy values.
• Check NO_PROXY; any matching host bypasses Fixie.
• If Claude Code runs commands inside Docker, SSH, WSL, or another remote environment, set the proxy variables there too.
• For raw TCP use cases, switch to Fixie Socks or fixie-wrench.