OpenAI API access for non-US teams (2026): the country list is the gate, not the entity

Most “OpenAI from abroad” posts mix three different products into one panic. ChatGPT the consumer app, the API Platform, and Azure-hosted OpenAI models do not share a single signup form, a single country list, or a single bill. This page is about the API Platform — the thing a distributed SaaS team actually wires into production — and only about facts on OpenAI’s own pages the day we fetched them.

The usual advice is also wrong in a specific way. People treat a Delaware C-corp, a US card, or a US VPS as the unlock. OpenAI’s published rule is about where the services are accessed or offered, not where the company is incorporated. If your location is not on the list, the entity paperwork does not write it in.

The actual gate: the supported-countries list

The page is blunt: accessing or offering access to the services outside the countries and territories listed may result in the account being blocked or suspended. That is the whole rule. There is no published exception for “we have a US parent” or “we only store keys in Virginia.”

On 2026-08-31 the list had 208 entries. For the corridors this site already writes about, the result is not “the API is a US product.” It is a much narrower map:

• On the list — India, Singapore, the Philippines, Indonesia, Vietnam, Nigeria, Kenya, South Africa, the UAE, Israel, Turkey, Australia, Canada, Japan, Taiwan, and the usual EU/UK set. Ukraine is listed with “certain exceptions.”
• Not on the list — mainland China, Hong Kong, Macau, Russia, Belarus, Iran, Cuba, North Korea, Syria and Venezuela. Those names were checked by absence against the fetched page, not guessed from news.

That split is the decision. A five-person product team with engineers in Bangalore, Manila and Berlin is on the list three times. A founder operating from Shenzhen with a Delaware LLC is not, and paying Firstbase or Atlas first does not change the sentence OpenAI published.

ChatGPT the consumer app has its own supported-countries article. We could not extract that page (cookie wall) so we will not pretend we read it. Do not copy this API list onto a ChatGPT-Plus question.

Three teams, three different answers

Same product, same model bill. The geography is what changes the answer.

Team A — Berlin parent, contractors in India and the Philippines. All three locations are on the 2026-08-31 API list. The operational work is billing and data handling, not “can we sign up.” If EU customers or a DPA require in-region processing, Europe is one of the three residency regions that publish regional processing = Yes (eu.api.openai.com). India and Singapore offer residency storage on in.api.openai.com and sg.api.openai.com but regional processing is published as No — storage in-region, inference not guaranteed in-region.

Team B — Singapore company, no US entity, US and EU customers. Singapore is on the list. You do not need Atlas to obtain an API key. You might still want a US entity later for Stripe, app stores or enterprise contracts; that is an incorporation question, not an OpenAI-access question. Mixing the two is how founders spend $500 and four weeks to solve the wrong gate.

Team C — operators in mainland China, Delaware C-corp already formed. China is not on the list. The C-corp is necessary for Mercury, useful for some US vendors, and irrelevant to the sentence about accessing the services from an unlisted country. Anthropic’s commercial API list, fetched the same day, also omits mainland China, so “just use Claude” is not a documented escape hatch for that location. Azure OpenAI is a Microsoft Azure commercial path — a different contract, a different identity, regional model SKUs — not a way to stand on OpenAI’s country list while sitting off it. We are not going to describe workarounds that violate the published rule.

What a US entity is actually for

Seed tables on this site point this URL at Stripe Atlas because Atlas shows up in “non-US team needs US commercial plumbing” searches. That is a real job. It is not the OpenAI country gate.

A US entity starts to matter when you need a US taxpayer identification number, a US bank account, or a vendor that invoices US companies. OpenAI’s published access rule does not name any of those. If the reason you are incorporating is “so we can call api.openai.com from an unsupported country,” stop and reread the list. If the reason is “we need a Delaware company for Stripe / AWS / a US customer’s vendor form,” go to Firstbase vs Stripe Atlas and cost the entity properly.

Stripe Atlas’s own pricing, captured on our tools pillar on 2026-08-03, is a $500 one-time fee including government fees and the first year of registered agent, plus stated partner credits. Those credits do not appear on OpenAI’s API pricing page. Do not budget Atlas as an OpenAI discount.

Data residency: ten regions, three that process in-region, 10% extra

OpenAI’s data-controls guide describes residency as a project configuration, not a self-serve toggle on every hobby account. Contact sales for eligibility. Once enabled, new projects pick a region; requests use a prefixed host.

Three footnotes from the same page, because they change the spreadsheet:

1. Residency endpoints charge a 10% uplift for models released on or after 5 March 2026 that are eligible for data residency.
2. Any region other than the United States requires approval for abuse-monitoring controls and a Modified Retention amendment.
3. The UAE row needs additional approval on top of that. System data (account, billing, usage metadata without customer content) may still leave the region. If processing is No, OpenAI may process and temporarily store customer content outside the region to deliver the service.

Worked cost, using list prices from the pricing page on 2026-08-31. Take gpt-5.4-mini at $0.75 input / $4.50 output per million tokens, and a month of 50M input + 5M output. Global: 50 × 0.75 + 5 × 4.50 = $60.00. Same volume on a residency endpoint for a post-5-March-2026 eligible model: $66.00. gpt-5 at $1.25 / $10.00 on the same volume is $112.50 global and $123.75 with the 10%. That is the residency premium as published — not a guess at your negotiated Enterprise rate.

Default data handling, also from the data-controls page: as of 1 March 2023 API data is not used to train models unless you opt in; abuse-monitoring logs default to up to 30 days. Zero Data Retention is a sales-gated control, not a checkbox on a $20 month.

If you are not on the list

Documented options, not folklore:

• Move the access location onto the list. Hire or incorporate where OpenAI actually offers the API. That is an EOR or entity decision with real payroll cost, not a DNS trick.
• Check Anthropic’s list, not a tweet. anthropic.com/supported-countries is public. Mainland China is absent there too. India, Singapore, the Philippines, Indonesia, Vietnam, Nigeria and Taiwan are present on both fetches.
• Azure OpenAI / Foundry. This is a Microsoft customer relationship. Availability follows Azure regions and your Azure enrollment, not OpenAI’s 208-name page. We did not capture a usable region matrix from Microsoft’s products-by-region table (the page did not yield one), so we will not invent which Azure region sells which model this week.

We are not going to recommend grey-market “API relays,” shared keys, or pretending a request originated in a listed country. OpenAI’s own sentence already says offering access from outside the list can get the account suspended. That is enough.

Billing: what we will not invent

API list prices are in USD on the pricing page. ChatGPT consumer subscriptions have a separate multi-currency article; that article is not API billing, and we will not paste its currency list here as if it were. OpenAI help articles on API cards either did not extract or were about ChatGPT Ads. So this page does not claim which cards, prepaid products or billing countries the API checkout accepts. If your problem is “the form rejected my card,” that is a payments problem — start at the fintech pillar and get a card issuers actually clear, then retry the official checkout. Do not treat a declined card as evidence you are off the country list, and do not treat a successful charge as evidence you are on it.

Frequently asked

Related

• AI & SaaS tools pillar — seat costs by stage; this page is the model-access footnote that page refused to invent.
• US incorporation — when a Delaware company is the right spend.
• Fintech pillar — cards and accounts that vendors actually charge.
• EOR pillar — putting a hire in a listed country costs payroll, not a VPN invoice.

Not legal, tax, or export-control advice. Supported-country count and omissions verified against developers.openai.com/api/docs/supported-countries on 2026-08-31. Residency table, processing flags, 10% uplift, training opt-in date and 30-day default logs from developers.openai.com/api/docs/guides/your-data and /api/docs/pricing the same day. Anthropic comparison from anthropic.com/supported-countries the same day. Help-centre URLs that returned a cookie wall are omitted rather than paraphrased. OpenAI and Anthropic change lists without notice — follow the linked pages. Some incorporation links are affiliate links; the OpenAI and Anthropic documentation links are not.