Claude Access from Mainland China Across Apps and APIs
Compare Claude web accounts, desktop chat clients, Claude Code, and APIs using current region policy and recent Chinese community reports, with payment and KYC caveats.
A search for “using Claude from mainland China” can mean four different things: the claude.ai website, a desktop chat client, Claude Code, or the model API. Accounts, payment, and configuration differ. A successful connection report may describe a different product from the one you need.
As checked on November 11, 2026, Anthropic’s Help Center location list does not include mainland China. Its public Supported Regions Policy is marked effective November 12 and explicitly covers physical location, entity incorporation and headquarters, ownership or control, cloud platforms, and authorized resellers. This article describes the published scope; it does not predict enforcement after that date.
What the commonly discussed methods address
For this series, we read seven recent V2EX discussions and their replies. The useful evidence is the combination of reported successes and later failures.
| Community approach | Intended purpose | What the follow-up establishes |
|---|---|---|
| Overseas registration, bank cards, or US App Store subscriptions | Signup and payment | Old and newly paying accounts still reported KYC or bans; payment is not eligibility |
| Residential proxies, English prompts, timezone changes, or remote machines | Connectivity and detection concerns | Contradictory outcomes, without an independently reproducible long-term guarantee |
| Claude inside an editor such as Cursor | A different product and billing relationship | A suggestion, not verification of every plan, region, or model |
| APIs, company gateways, and desktop clients | Separate authentication and request paths | Upstream region and resale conditions still need review |
| A model explicitly available locally | Continuing work | The client can stay; output and tool behavior need retesting |
In one account-ban thread, the author reported losing access after upgrading, while replies included both advice to stay on Pro and reports of Pro restrictions. A return-to-China Claude Code question discusses overseas accounts, jump hosts, and editor integrations. These are individual reports, not a proven stable route.
For chat, keep the client portable
Chatbox and Cherry Studio can connect to multiple providers. In custom-API mode, you supply a provider key rather than handing over your Claude website password. The practical benefit is portability: if one route is unavailable, you can retain the interface and your material while changing provider.
That does not grant upstream eligibility or turn the client into an official Claude app. See the desktop client and provider guide for the actual configuration differences.
For Claude Code, check location and credentials
An account opened abroad or paid with an overseas card does not establish that continued use after returning is supported. The published upcoming policy refers to physical location and entity relationships, not simply email address or language.
Check applicable terms before debugging the CLI. A company gateway centralizes routing and credentials but still needs appropriate upstream authorization. Follow the return-to-China checklist, with installation details in the existing Claude Code guide.
For an integration, identify the service relationship
The direct API, cloud platforms, and compatible gateways have separate credentials, catalogs, support contacts, and data paths. Before buying, confirm the contracting provider, supported entity and location, key owner, data handling, and shutdown or refund terms.
The API integration article supplies a minimal request and acceptance sequence. Nbility’s documentation describes its interfaces; it is not eligibility confirmation from Anthropic. A Claude model name on a catalog does not prove authorized reseller status.
Before paying
Test public short text, inspect the model and request record, then add files and tools as needed. A client subscription, an Anthropic plan, and API credit are different purchases. Anthropic’s Pro help page explicitly excludes Console API usage.
If an account is already restricted, use the appeal and data preservation guide. The community evidence reviewed here does not support a promise of permanent access or guaranteed verification. Keep important code, task notes, and portable configuration under your own control.
