A Grok proxy means one of two things. Searches for a "Grok proxy URL" come from Janitor AI and other chat apps, where the proxy field wants the address of a model. The official answer is the xAI API with your own key, and our Grok on Janitor AI page covers that setup. A URL from someone else is a relay, and it receives your key and every message you send.
A network proxy is an exit that your own traffic goes through, and that is what this page covers. It rests on the xAI docs, the source docs of the SDKs, news reports of the 2026 blocks, and one check from our server.
Where the proxy goes
| Where you use Grok | Where the proxy goes |
|---|---|
| grok.com in a browser | Browser or system settings. |
| The Grok and X apps | The Wi-Fi settings of the phone. |
| The OpenAI SDK on the xAI API | HTTPS_PROXY, plus the Node switch in Node. |
| The xAI Python SDK | grpc_proxy, https_proxy or http_proxy, in lowercase. |
| Grok Build | HTTPS_PROXY, HTTP_PROXY and NO_PROXY. |
| The web_fetch tool of Grok Build | An egress proxy of its own. |
The xAI API speaks the OpenAI format, so the OpenAI SDKs work with the base URL set to https://api.x.ai/v1. Their proxy settings carry over, and our ChatGPT page tested them. The Python SDK follows HTTPS_PROXY. The Node SDK needs NODE_USE_ENV_PROXY=1 as well, on Node 24.0.0 or 22.21.0 and later.
The xAI Python SDK works differently, because it "is a gRPC-based Python library". gRPC reads its own list, grpc_proxy, then https_proxy, then http_proxy: "These variables are checked in order, and the first one that has a value is used." The gRPC docs give those names in lowercase, so set https_proxy rather than only HTTPS_PROXY. Hosts in no_grpc_proxy or no_proxy skip the proxy. We did not run the SDK, so treat this as the documented behavior.
Grok Build, the coding CLI of xAI, lists HTTPS_PROXY, HTTP_PROXY and NO_PROXY as its "Standard HTTP(S) proxy variables for outbound traffic." Its web_fetch tool is "Off by default for security", and it has an egress proxy of its own. Set GROK_WEB_FETCH_PROXY, or proxy_endpoint under [toolset.web_fetch] in the config. The fetches of the tool can then leave through one exit while the model traffic uses another. Our page on AI coding tools compares the other CLIs.
grok.com follows the browser, and Chrome uses the proxy of the system. Chrome and other Chromium browsers never send a SOCKS5 user name and password, so use an HTTP line there. On a phone, the proxy goes into the settings of one Wi-Fi network. An iPhone takes a user name and password, while Android takes a host and a port only. We did not install the apps, so we cannot say whether they honor the setting.
Where the API runs, and how it limits you
"https://api.x.ai is the global endpoint", and xAI "may route requests between regions for capacity or reliability, so the processing location is not guaranteed." For processing in the United States, xAI offers a US endpoint at https://us.api.x.ai/v1, where tokens cost 10 percent more. The endpoint decides where the model runs, not the exit of your proxy.
"Every xAI API team has per-model rate limits on two dimensions": requests per second and tokens per minute. The tier behind them rests on "cumulative spend on the xAI API since January 1, 2026". Past a limit, the API answers 429. A proxy changes the exit only, so it moves neither the region nor the limits.
What we measured
We asked Grok and xAI for a few pages from our server in a data center in the US, with no proxy and plain curl, on 28 September 2026. grok.com answered 200 with the Grok page and no challenge, also to the user agent of Python requests. One scraping guide says such a request gets a redirect to the login page or a 403, and ours did not. The API answered 401, "No credentials presented.", without a key.
The company site was another matter. x.ai, its terms page and the sign-in host accounts.x.ai all answered with a Cloudflare page that reads "Sorry, you have been blocked". From our server, a sign-in would have failed there, whatever the proxy settings. We give no steps for getting past that page.
The record, with dates
| date | what happened |
|---|---|
| By 11 January 2026 | Indonesia and Malaysia temporarily block Grok. |
| By 23 January 2026 | Malaysia lifts its ban. |
| 1 February 2026 | Indonesia lets Grok resume. |
| 8 July 2026 | Grok 4.5 launches without the European Union. |
Sources: TechCrunch, ABC News, Engadget, The Jakarta Post and Wikipedia.
Both blocks came after the authorities said Grok was being used to generate explicit and non-consensual images. Indonesia lifted its block after X Corp committed to improving compliance with the law there, as The Jakarta Post reported. For Grok 4.5, xAI targeted mid-July 2026 for the European Union. A national block is an order to local networks, and we give no steps around one. If you read about a block, check whether it is still in force.
Where our lines fit
Our lines come as host:port:user:pass and generate in the http form by default. Browsers, the OpenAI SDKs, gRPC and Grok Build all take that form. For the web_fetch tool of Grok Build, a line of its own keeps its fetches apart from your model traffic. On a Residential Premium plan, up to 150 addresses can connect without the password, which helps on Android. Residential lines start at $0.44 per GB, and a dedicated ISP line costs $2.70/IP per month.
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 that browsers, the SDKs and Grok Build take. A Residential Premium plan can allow up to 150 addresses without a password.
The full reference is at hproxy.com/docs.
What this page does not cover
x.ai answered our server with a block page, so we could not read its consumer terms or its acceptable use policy for this page. Read them yourself before you automate anything. We ran no Grok client: the SDK, Grok Build and the apps rest on their docs. We did not check whether any country blocks Grok today beyond the January 2026 events. We will check again by 28 December 2026.
Sources
- xAI docs: quickstart, regional endpoints, rate limits and the Grok Build settings reference.
- xAI, the Python SDK README; gRPC, environment variables.
- TechCrunch, Indonesia and Malaysia block Grok, 11 January 2026; ABC News, Grok blocked in Indonesia and Malaysia, 12 January 2026; Engadget, Malaysia lifts ban on Grok, 23 January 2026; The Jakarta Post, Indonesia lets Grok resume, 1 February 2026; Wikipedia, Grok (chatbot).
- Chromium, Proxy support in Chrome; Android Developers, the ProxyInfo reference; Apple, the Global HTTP Proxy settings.
- HProxy, our ChatGPT and Grok on Janitor AI pages, our requests to Grok and xAI of 28 September 2026, and our plan, free list, proxy checker and IP lookup documentation.
