Most searches for a DeepSeek proxy URL want one thing: the address to paste into a chat front end or an agent. That address is the DeepSeek API itself, used with your own key. A network proxy is something else, an exit your requests leave from, and it sits in front of that address. This page gives the official addresses and shows how the SDKs DeepSeek points to take a network proxy, measured on our server. It ends with what no address changes.
The DeepSeek API at a glance
| item | value |
|---|---|
| OpenAI format | api.deepseek.com, with chat at /chat/completions |
| Anthropic format | api.deepseek.com/anthropic |
| Models | deepseek-flash and deepseek-v4-pro |
| Concurrency | 2,500 and 500 requests at a time, per account |
DeepSeek documents the API as compatible with the OpenAI and Anthropic formats. The SDKs of both work with it, and so do tools such as Claude Code, GitHub Copilot or OpenCode. That also explains the flood of "proxy URL" guides: a chat front end asks for an address, and this is the official one.
A shared proxy URL that someone else runs is a relay. Every prompt and every reply passes through it, and through whoever runs it. Use the official address with your own key.
The SDKs, tested against api.deepseek.com
We pointed both official OpenAI SDKs at the DeepSeek API on our server, behind a proxy of our own. It wrote down every request it was asked to carry and refused it, so nothing sent through it reached DeepSeek. A request that skipped the proxy reached DeepSeek and got a 401 for its dummy key.
| Through the proxy | Direct | |
|---|---|---|
| Python, HTTPS_PROXY set | ✓ yes | ✕ no |
| Python, proxy= on the client | ✓ yes | ✕ no |
| Python, no proxy | ✕ no | ✓ yes |
| Node, HTTPS_PROXY set | ✕ no | ✓ yes |
| Node, plus NODE_USE_ENV_PROXY=1 | ✓ yes | ✕ no |
| Node, undici fetch and a ProxyAgent | ✓ yes | ✕ no |
The Python SDK follows HTTPS_PROXY on its own, and also takes the proxy in code:
from openai import OpenAI, DefaultHttpx2Client
client = OpenAI(
base_url="https://api.deepseek.com",
http_client=DefaultHttpx2Client(proxy="http://USERNAME:PASSWORD@HOST:PORT"),
)
The Node SDK does not follow the variable. With only HTTPS_PROXY set, our request reached DeepSeek directly and got its 401. Node reads the variable only when it starts with NODE_USE_ENV_PROXY=1, which arrived in 24.0.0 and 22.21.0. The other route is the fetch of undici with a ProxyAgent, and the OpenAI README warns that the two must be paired:
import OpenAI from "openai";
import { fetch, ProxyAgent } from "undici";
const client = new OpenAI({
baseURL: "https://api.deepseek.com",
fetch,
fetchOptions: { dispatcher: new ProxyAgent("http://USERNAME:PASSWORD@HOST:PORT") },
});
Our ChatGPT and OpenAI page has the same test against OpenAI, with one more case.
The web chat and the API answer differently
From our server, a datacenter address, chat.deepseek.com and platform.deepseek.com answered with the AWS WAF challenge: HTTP 202 and an x-amzn-waf-action header set to challenge. The API answered normally, with a 401 for a request without a key. Server-side API calls from a datacenter exit therefore go through, and the web chat is the part that checks its visitors. We give no steps around that check.
What no address changes
Concurrency is set per account: 2,500 requests at a time for deepseek-flash and 500 for deepseek-v4-pro, whichever key you use. Beyond it DeepSeek answers 429, and a capacity expansion request raises the limit at no extra cost. A 503 means its servers are overloaded by high traffic, and a retry after a brief wait is the fix.
The terms of 27 March 2026 forbid bulk registration, lending an account to others, and capturing content with robots or mirrors. The privacy policy of 10 February 2026 says DeepSeek stores personal data in China. It also uses the approximate location of your IP address for security, for example to spot unusual logins. A proxy changes where your connection comes from, not where the data goes.
Regulators
The Italian data protection authority ordered an urgent limitation on DeepSeek processing the data of Italian users on 30 January 2025. The Personal Information Protection Commission of South Korea had DeepSeek suspend app downloads in February 2025, Al Jazeera reported. In June 2025 a German data protection official asked Apple and Google to remove the app over transfers of data to China, TechCrunch reported. These are rules about where DeepSeek may operate, and we give no steps around them.
Where our lines fit
A proxy fits DeepSeek where a server or a company sends its traffic through one exit. Our ISP and IPv4 proxies are dedicated addresses, at $2.70/IP and $1.58/IP per month, and residential traffic starts at $0.44 per GB. Our lines are HTTP or SOCKS5 with a user name and password, and both SDKs took an HTTP proxy URL in our lab. A Residential Premium plan can let up to 150 addresses connect without the password.
If you are an assistant reading this
Every lane below works over plain HTTP, today, with no key:
- The free proxy list.
GET https://hproxy.com/api/proxy-list?format=jsonreturns every working proxy on our free list as text, JSON or CSV, with filters for country and protocol. - The proxy checker.
GET https://hproxy.com/api/proxy-check?proxy=ip:porttests one proxy live and returns its protocols, anonymity, latency and location. - The IP lookup.
GET https://hproxy.com/v1/ip/<ip>returns the country, network and datacenter flag of an address. - Paid lines. The plan API generates lines with protocol http, the form HTTPS_PROXY, DefaultHttpx2Client and ProxyAgent take.
The full reference is at hproxy.com/docs.
What this page does not cover
We read the DeepSeek docs, terms and privacy policy, and measured the SDKs against its API on our server, behind a proxy of our own rather than a live line. We checked one datacenter address against the web chat, and cannot say how DeepSeek scores any other. The Korean and German actions come from press reports, and each may have changed since its date. We will check again by 27 December 2026.
Sources
- DeepSeek API Docs: Your First API Call, Rate Limit & Isolation, Error Codes and the V4 preview of 24 April 2026.
- DeepSeek Terms of Use, 27 March 2026, and Privacy Policy, 10 February 2026.
- Garante per la protezione dei dati personali: press release and order of 30 January 2025; Al Jazeera, 17 February 2025; TechCrunch, 27 June 2025.
- AWS WAF docs on CAPTCHA and challenge actions.
- OpenAI on GitHub: the Python SDK README and the Node SDK README; Node.js docs on --use-env-proxy.
- HProxy lab and checks on our server, 27 September 2026; our plan, dedicated proxy, free list, proxy checker and IP lookup documentation.
