> 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/residential-proxy/product-introduction.md).

# Product Introduction

{% 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 %}

JollyProxy Residential Proxy provides IP resources based on real residential network egresses. The egress IP automatically changes according to the configuration on each connection or request, ensuring that the access identity keeps changing. It is suitable for connection tasks that require short connections, IP rotation, or multiple egress network identities.

**Resource Coverage**

| Resource Metric                 | Details                                                           |
| ------------------------------- | ----------------------------------------------------------------- |
| **IP Pool Size**                | Tens of millions                                                  |
| **Country and Region Coverage** | 200+                                                              |
| **Regional Distribution**       | Widely distributed globally, covering mainstream internet markets |

**Residential IP Resource Coverage (including but not limited to):**

<table><thead><tr><th width="282.199951171875">Continent</th><th>Example Covered Countries/Regions</th></tr></thead><tbody><tr><td><strong>Asia</strong></td><td>Singapore, Japan, South Korea, India, Indonesia, Malaysia, Thailand, Vietnam, etc.</td></tr><tr><td><strong>Europe</strong></td><td>United Kingdom, Germany, France, Netherlands, Spain, Italy, Switzerland, etc.</td></tr><tr><td><strong>North America</strong></td><td>United States, Canada, Mexico</td></tr><tr><td><strong>South America</strong></td><td>Brazil, Argentina, Chile, Colombia, Peru, etc.</td></tr><tr><td><strong>Africa</strong></td><td>South Africa, Nigeria, Egypt, Kenya, Morocco, etc.</td></tr><tr><td><strong>Oceania</strong></td><td>Australia, New Zealand</td></tr></tbody></table>

**Protocol Support**

Supports mainstream proxy protocols:

* **HTTP**
* **SOCKS5**

**Authentication Methods**

Residential Proxy supports **username-password sub-account authentication** for proxy connections:

* Sub-accounts are used for proxy connection identity verification and **are not used to log in to the main platform**
* Supports sharing proxy permissions among multiple people or devices while maintaining connection authentication isolation

**Service Assurance**

> **99.8% service availability**
>
> **The platform automatically schedules and monitors IP connection status to ensure stable business operations.**


---

# 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/residential-proxy/product-introduction.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.