Meta AI means two things now. One is the assistant of Meta for people, with an app of its own and a web version. The other is Meta Model API, the developer side at dev.meta.ai, which serves the Muse models to your code. A proxy goes in a different place for each, and the rules on countries apply to both. This page covers them from the Meta docs and policies, read on 28 September 2026.
| What you use | Where the proxy goes |
|---|---|
| The Meta AI app and web version | The proxy of the phone, browser or system. |
| Meta Model API from OpenAI clients | The SDK, with the /v1 base URL. |
| Claude Code and Anthropic clients | HTTPS_PROXY, with the host base URL. |
The app
The Meta AI app takes no proxy setting of its own. A phone applies the proxy of its Wi-Fi network. A browser follows its own settings or those of the system, and the app goes wherever the system sends it. The questions people ask about the app are mostly about countries. On 28 September 2026, Apple listed it in 40 of the 44 App Store storefronts we checked. No listing came back for Bangladesh, Russia, China or Ukraine. A listing does not prove that the assistant works in a country, and a proxy does not change where you are.
Meta Model API for developers
Meta Model API speaks the formats of other providers, so the familiar clients work with a new base URL. OpenAI clients take https://api.meta.ai/v1, and Anthropic clients take the host alone, https://api.meta.ai. For Claude Code, Meta writes that it is "the Model API base host. Claude Code appends /v1/messages." Codex takes Meta Model API as a model provider with the /v1 base.
export ANTHROPIC_BASE_URL="https://api.meta.ai"
export ANTHROPIC_AUTH_TOKEN="$MODEL_API_KEY"
export HTTPS_PROXY="http://USERNAME:PASSWORD@HOST:PORT" # the network proxy of Claude Code itself
Only the base URL changes, so each client keeps the proxy behaviour our labs of 27 September measured. The OpenAI Python SDK follows HTTPS_PROXY. The OpenAI Node SDK does so only when Node starts with NODE_USE_ENV_PROXY=1. Claude Code reads the lowercase variable first, as our Claude Code page shows, and our ChatGPT page has the SDK results.
Meta uses the word proxy once more, for keys. Its advice is to keep keys out of browser and mobile code: "Proxy requests through a server you control." That is a backend of your own, not an exit address.
The rules on countries
Meta says that "Meta Model API is available in most countries and territories where Meta AI is available and billing is supported." Its geographic use policy, updated on 18 September 2026, is the list that decides. "You may access the Services only in jurisdictions where Meta has enabled access. You may not use technical measures to circumvent, bypass, or otherwise evade geographic access controls."
The policy names 21 restricted territories, among them China with Hong Kong and Macau, Russia, Iran, Pakistan, Venezuela and "The Crimea, Donetsk, and Luhansk regions of Ukraine". It also covers travel: "If you are traveling to a region that is not currently supported, you will not be able to log in to your account." We give no steps around any of it.
The limits follow the team. Meta says: "Limits apply per team, not per API key." The terms also forbid anyone to "circumvent, violate, hack, disable, or evade rate limits, usage quotas" and other controls, so a different exit address changes nothing there either.
Where our lines fit
A proxy of your own fits Meta Model API in plain cases: a company network where every tool leaves through one egress, and a server whose traffic should leave from one fixed address. From our server in a data center, api.meta.ai answered with a plain 401 for the missing key. A dedicated ISP or IPv4 address stays the same, at $2.70/IP and $1.58/IP per month, and residential lines start at $0.44 per GB.
Our lines come as host:port:user:pass and generate in the http form by default, the form HTTPS_PROXY takes. On a Residential Premium plan, up to 150 addresses can connect without the password, so none has to sit in your shell. Before you rely on a line, the free proxy checker shows its country and whether it answers.
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 takes. Dedicated addresses are listed by the proxies API.
The full reference is at hproxy.com/docs.
What this page does not cover
We did not run the Meta AI app or any client against Meta Model API for this page. The help pages of Meta AI for consumers answered our server with an error, so we cannot say where the assistant works country by country; the store listing is the closest public measure. Llama, the open-weight models of Meta, is not served through Meta Model API; you download and run it yourself. We will check again by 28 December 2026.
Sources
- Meta Model API docs: SDKs, coding agents, pricing and rate limits and authentication, read on 28 September 2026.
- Meta developer help center: supported countries, travel access and Llama and Model API.
- Meta, the geographic use policy and terms of service of Meta Model API, both updated 18 September 2026.
- Apple, the App Store listing of Meta AI, read through its lookup API in 44 storefronts on 28 September 2026.
- HProxy: the edge check of 28 September 2026 from our server; our ChatGPT and Claude Code labs; our plan, dedicated proxy, free list, proxy checker and IP lookup documentation.
