> For the complete documentation index, see [llms.txt](https://jollyproxy.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://jollyproxy.gitbook.io/docs/buying-proxy/residential-proxy.md).

# Residential Proxy

{% hint style="danger" icon="exclamation" %}
**Usage Notice**: All Jollyproxy proxy products must be used in an overseas network environment. Please ensure that you have configured the corresponding overseas network environment yourself.
{% endhint %}

This article will explain how to purchase a Residential Proxy on the **Jollyproxy** **platform**.

### **Step 1: Log In and Check Account Status**

Visit the [**Jollyproxy official website**](https://www.jollyproxy.com/) and log in to your account. The system will automatically take you to the console interface. On this page, you can view the **wallet balance** and the **package purchase** entry.

<figure><img src="https://1126830726-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FureEI2hB2llelhLWxJFY%2Fuploads%2F7pKRcNS64X94LgoolDOM%2Fimage.png?alt=media&amp;token=0997bfb8-94a2-4040-bdf1-b7f7da59f5e9" alt=""><figcaption></figcaption></figure>

### **Step 2: Select and Purchase a Proxy Package**

1. **Enter the purchase page**: Click **Residential Proxy** in the left sidebar.
2. **Select a package**: Configure and select the appropriate package according to your business needs.
3. **Complete payment**: Click **Buy Now** to complete the purchase.

The platform currently supports the following payment methods:

<table data-search="false"><thead><tr><th>Payment Method</th><th>Description</th></tr></thead><tbody><tr><td>Wallet Balance</td><td>Recommended, credited in real time</td></tr><tr><td>Alipay</td><td>Convenient QR code payment</td></tr><tr><td>WeChat Pay</td><td>Convenient QR code payment</td></tr><tr><td>UnionPay</td><td>Supports major bank cards</td></tr><tr><td>Credit Card</td><td>Supports Visa / Mastercard</td></tr><tr><td>Apple Pay</td><td>Apple Pay</td></tr><tr><td>Google Pay</td><td>Google Pay</td></tr><tr><td>Cryptocurrency</td><td>USDT / BTC, etc.</td></tr></tbody></table>

<figure><img src="https://1126830726-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FureEI2hB2llelhLWxJFY%2Fuploads%2FhSu0BrQhVMalRKZUivvU%2Fimage.png?alt=media&amp;token=cfe5d488-9f5b-4e8a-bb5c-d538f625852b" alt=""><figcaption></figcaption></figure>

<figure><img src="https://1126830726-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FureEI2hB2llelhLWxJFY%2Fuploads%2FvDhCASM0jy5NYdXqujvm%2Fimage.png?alt=media&amp;token=39d4c9b5-31e3-4a72-987e-2c4be53bfc20" alt=""><figcaption></figcaption></figure>

***

**Next step**: After the proxy is purchased successfully, you can read "Residential Proxy" for configuration.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://jollyproxy.gitbook.io/docs/buying-proxy/residential-proxy.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.