

For API and Claude Code, personal IPv4 addresses are sufficient — they are fast, stable and used only by you. For working with an account in the browser, Prime (ISP/Residential) is better: addresses from real ISPs and business networks.
Yes. Claude Code uses the environment variables <code>HTTPS_PROXY</code> and <code>HTTP_PROXY</code>. HTTP/HTTPS is supported — SOCKS does not work in Claude Code. Just set the variables before running <code>claude</code>.
Yes. The Anthropic SDK accepts a custom HTTP client, so requests can be routed through SOCKS5 or HTTPS. See the <code>httpx</code> example above.
One account — one proxy. Using a single IP for multiple accounts may cause Anthropic's systems to link them together.
Only the traffic you choose goes through the proxy — browser, API or terminal. Other apps run directly. Public VPN addresses are used by many users at once, while a personal proxy is used only by you.
No, traffic is unlimited. Long agent sessions, large contexts and high API load do not hit data caps.
The US or European countries supported by Anthropic. It's important that the IP country matches the account region, timezone and browser language — this reduces the risk of additional checks.
Install the Proxy-solutions settings extension, create a profile (SOCKS5 or HTTPS), enter IP, port, login and password. Switch to the profile — all browser traffic will go through the proxy.
Under normal load, one personal proxy works for weeks without change. For high request volumes, use a pool of 5–10 IPs with rotation.
Yes, support is available 24/7 in live chat. The site has a setup guide section and video tutorials on our YouTube channel.
Claude is not available in every country, and Anthropic restricts access by region. Even where the service is available, the IP itself matters: the system evaluates its type, reputation and history. Shared and free addresses are used by many users at once — this can trigger additional checks.
This is especially true for developers. Claude Code and the Anthropic API often run from servers, VPS and corporate networks, where the outgoing IP depends on the infrastructure in use. A proxy lets you separate the application's outgoing IP from your main network and use a dedicated IP from the required country.
Important: a proxy solves the IP question, but does not replace the other conditions of using the service (region, payment method, Anthropic rules). Follow them.
Addresses of real internet providers and business networks. Suitable when you need an address from a real ISP or business network for account work.
For SOCKS: pip install "httpx[socks]"
import httpx
from anthropic import Anthropic
proxy_url = "socks5://username:password@ip_address:port"
client = Anthropic(
api_key="your_api_key",
http_client=httpx.Client(proxy=proxy_url),
)
For high-volume workloads, consider bulk IPv4 proxies to distribute requests across a pool.
Linux / macOS:
export HTTPS_PROXY="http://username:password@ip_address:port"
export HTTP_PROXY="http://username:password@ip_address:port"
claude
Windows (PowerShell):
$env:HTTPS_PROXY="http://username:password@ip_address:port"
$env:HTTP_PROXY="http://username:password@ip_address:port"
claude
Use HTTP/HTTPS proxy — SOCKS is not supported in Claude Code.
Personal IPv4 works for API and Claude Code, Prime for account work in the browser. Advantages: personal IPs, unlimited traffic, country selection, 24/7 support.
Related AI material: proxies for ChatGPT.
Legal aspects of proxy use: is it legal to use proxy servers and VPNs.
Claude Code and the API often run from servers and VPS. If you need a server for automation tasks — see VPS from Hoster Solutions in combination with proxies.