Use your ready-to-use Claude account

Read your delivery details, set up the included static proxy in Chrome, and check account access. Includes proxy chaining for mainland China.

Use this guide if you bought a ready-to-use Claude account from XiuStore. Collect the details, sign in, and check the plan before regular use. If something fails, keep the original error message and avoid repeatedly trying different sign-in methods.

Start with your delivery

Your order contains the account, sign-in instructions, plan, and subscription term. Use the SessionKey (SK) flow only when your order provides one. An SK is a Claude web sign-in credential: protect it like a password. It is not an API key and cannot call the Anthropic API.

Open the original order on the delivery day and confirm the account, plan, and term.
If a proxy is included, decide whether to use it. Set up the network before signing in.
Sign in on your own device, check the plan and remaining usage, then send an ordinary message.
Keep redacted screenshots of the plan, term, and successful reply.

If sign-in details are missing, the account cannot sign in, or the plan is wrong, contact support from the original order.

Read the delivered fields

Field	Where to use it
`sessionKey`	Claude web sign-in, following the instructions below
Email, password, recovery email, recovery password	Mailbox access and recovery details; these are separate from the proxy password
Proxy link starting with `socks5://`	A proxy client that supports SOCKS5 username and password authentication

An email entry may contain four fields separated by ----, in this order: email, password, recovery email, recovery password. An empty field means that detail was not supplied. Do not shift the remaining fields into its place. Follow your order when using the mailbox to receive sign-in codes.

Maintenance before delivery may leave a small amount of conversation or usage history. Still check the plan and remaining usage when you first sign in. Report unavailable access, the wrong plan, or unexpected usage through the order. Maintenance does not guarantee that an account will avoid restrictions.

Set up the included static proxy

This walkthrough uses Chrome on Windows or macOS. Chrome sends its web requests through a working upstream connection, then uses the delivered static IP to reach Claude.

The delivered static proxy cannot be reached directly from mainland China. It needs a working upstream proxy connection. If you already have stable access, using the included proxy is optional. Its term and region are stated in your order.

Step 1: Prepare the client and upstream connection

What you need	Where to get it
Chrome and Clash Verge Rev	Use a current Chrome version. Install the Windows or macOS version from the official Clash Verge Rev installation page
A Clash / Mihomo subscription URL for your upstream connection	Sign in to your network provider and copy its Clash or Mihomo subscription URL
The static proxy link	Copy the complete `socks5://` link from the original order

A network subscription URL imports the provider’s connections into the client and usually starts with https://. It is separate from your Claude subscription and the order’s socks5:// link.

If you do not have an upstream connection, start with network setup. This walkthrough requires a provider that supplies a Clash / Mihomo subscription. If your provider only offers a dedicated app, ask whether it provides this subscription format. An app download URL will not work.

Test the upstream connection first:

In Clash Verge Rev, open Profiles, paste the provider’s subscription URL into the input, and select Import.
Select the new profile card to activate it.
Open Proxies, select a working connection in the provider’s selection group, and enable System Proxy. Group names depend on the provider.
Open https://claude.ai/ in Chrome without signing in yet.

Continue when you can see the Claude sign-in page. If import fails, no connections appear, or the page will not open, resolve the upstream connection with your provider first. You have not configured the delivered static proxy yet.

Step 2: Fill in the complete template

Download the Claude static proxy template and save it as claude-chain-en.yaml. Open it in Notepad or another plain-text editor. In macOS TextEdit, choose Format → Make Plain Text first.

The template already defines the connection order. Replace only the five marked values. You do not need to merge an old configuration or write routing rules. This fictional link is only an example and cannot connect:

socks5://proxy_user:proxy_password@192.0.2.10:1080

Template field	What to enter	Value in the example
`url:`	The Clash / Mihomo subscription URL tested in step 1	Your own subscription URL
`server:`	The address after `@` and before the final colon	`192.0.2.10`
`port:`	The number after the final colon	`1080`
`username:`	The text after `socks5://` and before the first colon	`proxy_user`
`password:`	The text between the username’s colon and `@`	`proxy_password`

Replace the values while keeping the indentation, colons, and quotation marks. Enter only digits for the port. Use the proxy password, not your email password or SessionKey. If a value contains a double quote or backslash, ask support through the order how to enter it; do not remove characters from the credential.

Check that the saved filename ends in .yaml, not .yaml.txt. The completed file contains your private subscription URL and proxy password. Keep it on your own device and do not upload it to an online converter.

Step 3: Import the template and select the upstream connection

Drag the completed claude-chain-en.yaml file into Profiles in Clash Verge Rev.
Select the new profile card to activate it. Keep the original profile from step 1 so you can switch back.
In Proxies, open the group named Upstream connection and select the connection you tested in step 1.
Set the client to Rule mode and keep System Proxy enabled.

You should see the Upstream connection group and your provider’s connections. If the list is empty, check that url: contains the same subscription URL as step 1, then use the troubleshooting table below.

Keep this template in Rule mode. Its single rule sends every web request received by the client through Claude static proxy, which connects through your selected upstream connection. You do not need to choose GLOBAL or add Claude domains individually.

Step 4: Connect Chrome to the client

Pause other extensions that change Chrome’s proxy settings.
Save your work, fully quit Chrome, and reopen it to avoid reusing earlier connections.
Enter chrome://settings/system in the address bar and open your computer’s proxy settings.
Confirm that Clash Verge Rev has set the proxy to 127.0.0.1. The port must match the client’s HTTP / mixed port, commonly 7897 or 7890. System Proxy normally sets this automatically; do not enter the order’s remote IP or password here.

Chrome cannot directly authenticate the delivered SOCKS5 proxy. Clash Verge Rev handles that authentication. Do not paste the socks5:// link into Chrome’s address bar or a SessionKey extension.

Open XiuStore AI IP Check in this Chrome and start the check.
Compare the exit IP with your delivery instructions. It should be the static proxy’s exit; a matching country or a working web page alone is not enough. If no exit IP was specified, confirm it through the order. 127.0.0.1 is not your public exit IP.
Open https://claude.ai/, follow the sign-in instructions below, and send an ordinary message.
In Clash Verge Rev, open Connections, find the new claude.ai request, and confirm that its outbound path uses Claude static proxy.

The initial setup is complete when the exit IP matches, the connection uses the static proxy, and Claude replies normally. Keep this profile, Rule mode, and System Proxy enabled while using Claude.

Other web pages and applications that use the system proxy also use this static exit. To stop using it, switch back to the original profile in Profiles. To restore a direct connection, turn off System Proxy as well.

If a step fails

What you see	What to do
Step 1 cannot import the subscription or open Claude	Ask the network provider to check the subscription format, term, and available connections before troubleshooting the static proxy
Import reports a YAML syntax error	Check indentation, colons, and quotes, or download a fresh template and replace only the five values
You cannot find the YAML file	Check the download folder and whether the editor saved it with an extra `.txt` extension
The upstream group has no connections	Check `url:` and update the subscription in the client; switch back to the original profile to check whether the provider’s subscription can be downloaded
The connection keeps timing out	Check the selected upstream connection, then the static proxy address, port, and term; mainland China cannot connect directly to this node
Authentication fails	Check the proxy username and password for missing characters or extra spaces; do not use the email password
Claude opens but still shows the upstream exit IP	Activate the new template, select Rule mode, and enable System Proxy; pause other proxy extensions and restart Chrome
The original profile still works	Focus on the template, static proxy fields, and expiration date

For help, provide the device OS, client version, failing step, and original error through the order. Hide subscription URLs, proxy passwords, SessionKeys, and mailbox details.

Claude also loads sign-in, verification, image, attachment, and other services. A rule for claude.ai alone can miss them. This template sends all web requests received by the client through the static proxy, so you do not need to maintain a domain list.

To inspect a particular feature, close old connections in Connections, then refresh Claude, sign in again, or test an attachment in Chrome. Check the new Claude, Anthropic, and related resource requests. They should use Claude static proxy, without DIRECT or an upstream-only route.

The complete path is:

Chrome → local Clash Verge Rev → selected upstream connection → delivered static proxy → Claude

The template’s dialer-proxy already points to Upstream connection. Do not add a fallback to direct access.

If the IP check shows a different public address for WebRTC, follow exit IP and WebRTC troubleshooting. These steps check Chrome web requests. Claude mobile, desktop, and Claude Code may not follow the system proxy; verify each separately.

Phones and other clients

The template above is for Clash Verge Rev on a computer. Phones in mainland China also need an upstream connection followed by the static proxy, but setup menus vary. Provide your OS and client name through the order to confirm the appropriate setup. Running two proxy apps at once does not establish a proxy chain by itself.

For official client installation, follow Install Claude. For ongoing precautions, read account safety.

Copy the complete SK from the original order without typing or shortening it.
Use it in your own browser as instructed by the order.
Open claude.ai and check the account, plan, and subscription term.

An SK does not automatically require a browser extension. If the order specifically instructs you to use Claude Session Login:

Install the named extension from its Chrome Web Store page.
Open the extension and paste the complete SK into Enter new sessionKey.
Save the SessionKey, then use the extension’s link to open Claude.
Complete the first account check immediately.

This is a third-party extension, not an Anthropic product. Use it only when specified in the order. Avoid installation files from advertisements, file-sharing sites, or chats, and do not paste the SK into other sites or extensions.

When your order allows email verification

Choose email sign-in on claude.ai and enter the delivered account’s email address.
Open the corresponding mailbox as instructed and retrieve the latest verification code.
Enter it in Claude, then check the account, plan, and term.

If the code does not arrive or the mailbox will not open, stop repeated requests and do not change the email address or password yourself.

Mobile and desktop apps

The SK is for the web sign-in method specified by the order. Do not paste it into the Claude app, desktop client, or terminal. If email verification is allowed, complete the official sign-in flow in the app. Otherwise, confirm the sign-in method through the order first.

Use the account safely

Use one account for one person. Do not share access or run frequent simultaneous activity across devices.
Do not connect a personal subscription to a reverse proxy, local API, shared panel, or third-party service. Use an Anthropic API key for product development.
Only change passwords, email addresses, payment methods, or plans when the order allows it.
Keep passwords, verification codes, SKs, cookies, recovery details, and API keys out of support chats, group chats, and other websites.
Keep your usual network and devices reasonably consistent. A normal device or network change does not necessarily cause a ban, and a fixed IP or maintenance activity cannot guarantee account safety.
Follow Anthropic’s current Usage Policy. No method guarantees that an account will avoid restrictions.

Plans, models, and usage

Check the actual plan in Claude against the order’s Pro, Max 5×, or Max 20× description.
On the web, open Settings → Usage for current usage and reset times.
In Claude Code, use /status to inspect the current account and usage.
Claude and Claude Code may share Pro or Max usage. Long conversations, large files, and complex tasks usually consume more.
When you reach a limit, wait until the displayed reset time. Do not switch accounts to bypass limits.
Do not add a credit card, enable extra usage, or upgrade the plan yourself. Contact support through the order about renewal or more capacity.

Models and features change. Use the options currently shown in the account. Start with the default model for everyday writing and questions, and choose an available model suited to more complex reasoning or coding when needed.

Available tools also vary by plan, region, and provider changes. Conversations support writing and analysis; Projects organize ongoing work; file upload reads supported documents; Claude Code handles terminal-based coding tasks. Check the account for the availability of web search, Research, Artifacts, and other tools.

Use Claude Code

Complete the first web check, then run Claude Code and choose the Claude App account through its official authorization flow. Do not put SKs, passwords, or cookies into terminal commands or shell scripts.

Grant access only to the directories and commands the task requires.
Do not use --dangerously-skip-permissions by default.
If ANTHROPIC_API_KEY is present, Claude Code may use API billing. Check the active account and billing method first.
Web pages, issues, documents, and repositories can contain untrusted instructions. Check before deleting files, publishing, sending messages, or paying.

Common questions

Problem	What to do
SK sign-in returns to the login page	Confirm that the SK and extension match the order; stop and contact support if it still fails
No email code arrives	Check the specified mailbox and request only one fresh code
The plan looks wrong	Refresh once, then contact support through the order on the delivery day
Usage or conversation length limit	Check `Settings → Usage` or `/status`; wait for a reset or start a new conversation as appropriate
Busy service or system error	Check Anthropic Status and try again later
Sign-in works but messages fail	Keep the full error and distinguish usage limits, service outages, and account restrictions
The account is restricted	Save the original notice and email, stop repeated sign-ins, and follow the product and order’s refund terms
Can I change account details?	Only change the password, email address, payment method, or plan when allowed by the order
Can I use several devices?	Use your own usual devices without account sharing or frequent simultaneous activity
Should I back up conversations?	Save important work using the available export or copy functions
Can I share a conversation?	Use Claude’s available sharing controls and check for private information before creating a link
What happens at expiration?	Check the actual account state and contact support through the order for renewal

Change one variable at a time when troubleshooting. Do not change the SK, mailbox, browser, device, and network all at once.

Get better results

State the task, context, and output you need. You can adapt this short prompt:

Task: What I need you to do
Context: Information you need
Output: Table, Markdown, checklist, or another format
Requirements: Length, tone, what to include, and what to leave out

Check important results yourself. Break long tasks into steps and confirm the direction before continuing. Keep the context, files, and instructions for an ongoing project together in a Project.

Sign out or handle exposed credentials

If you left a shared device signed in, use Claude’s account settings to sign out and sign in again through the method allowed by the order.
If an SK is exposed, stop using or forwarding it and contact support through the order. Do not resend the complete SK in chat.
Use Claude Code’s official sign-out or authorization-revocation flow. Do not delete the entire ~/.claude directory.
Do not install unknown browser-fingerprint, timezone-spoofing, or environment-cleaning tools.

Support and warranty

Report missing access, the wrong plan, or an unusable SK through the original order on the delivery day.
If a covered subscription ends during its term, refunds follow the remaining-day calculation; a partial used day counts as one day.
Restricted Claude Max accounts go through an Anthropic appeal first. Refund eligibility and amount depend on what Anthropic actually refunds. Other products follow their own product and order terms.
Hide passwords, verification codes, SKs, cookies, and recovery details in evidence.

Read the full refund and after-sales policy. For access problems, use account troubleshooting. See recording and evidence for support materials, or contact support.

Reference links

Sources and review date

Delivery fields, the mainland-China proxy-chain requirement, and maintenance information were reviewed against XiuStore’s delivery process on 2026-09-17. Proxy behavior follows the Chromium, Mihomo, and Clash Verge Rev sources listed above. The Claude sign-in, usage, policy, and appeals references were last reviewed on 2026-08-26. This English translation preserves those review dates. Third-party sign-in and proxy tools are not Anthropic products and do not guarantee protection from account restrictions.