> 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/static-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 %}

A static residential proxy refers to an IP address that originates from a real residential network and remains fixed over the long term. Each IP remains stable throughout the entire usage period, with no rotation and no interruption, making it particularly suitable for scenarios such as persistent connections, identity preservation, automated execution, and account operation.

The static residential proxies we provide focus on delivering a professional-grade proxy experience of "high-purity source, high-stability connection, and unlimited traffic." They support self-selected country and city nodes and are suitable for various highly sensitive application scenarios.

**Core Features**

**High-Purity Residential Source** All IPs originate from real residential networks, effectively reducing the risk of blocking and verification.

**Extreme Stability** Each IP remains stable without interruption, supporting long-term idle operation, continuous logins, persistent tasks, and long-duration data synchronization.

**Unlimited Traffic** No usage limits, supporting stable 24/7 operation and ensuring execution efficiency.

**Ultra-Low Risk Control Trigger Rate** Pure, highly anonymous IPs combined with stable egress paths effectively reduce platform detection and CAPTCHA interference.

**Precise Node Selection** Supports specifying countries and cities (e.g., United States, Japan, Germany, etc.) to facilitate region-targeted operations and regional deployment.

**Countries and Regions**

<table data-search="false"><thead><tr><th width="144">Continent</th><th width="262.2000732421875">Country/Region</th><th>Major Cities</th></tr></thead><tbody><tr><td rowspan="3"><strong>North America</strong></td><td>United States (US)</td><td>Los Angeles, New York, Seattle, Chicago, Dallas, etc.</td></tr><tr><td>Canada (CA)</td><td>Toronto</td></tr><tr><td>Mexico (MX)</td><td>Mexico City</td></tr><tr><td rowspan="5"><strong>Europe</strong></td><td>United Kingdom (GB)</td><td>London</td></tr><tr><td>France (FR)</td><td>Paris</td></tr><tr><td>Germany (DE)</td><td>Berlin, Frankfurt</td></tr><tr><td>Italy (IT)</td><td>Rome</td></tr><tr><td>Spain (ES)</td><td>Madrid</td></tr><tr><td rowspan="12"><strong>Asia</strong></td><td>Japan (JP)</td><td>Tokyo</td></tr><tr><td>South Korea (KR)</td><td>Seoul</td></tr><tr><td>Singapore (SG)</td><td>Singapore</td></tr><tr><td>Vietnam (VN)</td><td>Hanoi, Ho Chi Minh City</td></tr><tr><td>Thailand (TH)</td><td>Bangkok</td></tr><tr><td>Philippines (PH)</td><td>Manila</td></tr><tr><td>Indonesia (ID)</td><td>Jakarta</td></tr><tr><td>Malaysia (MY)</td><td>Kuala Lumpur</td></tr><tr><td>Saudi Arabia (SA)</td><td>Riyadh</td></tr><tr><td>United Arab Emirates (AE)</td><td>Dubai</td></tr><tr><td>India (IN)</td><td>Mumbai</td></tr><tr><td>Hong Kong (HK)</td><td>Hong Kong</td></tr><tr><td><strong>Oceania</strong></td><td>Australia (AU)</td><td>Melbourne</td></tr><tr><td><strong>South America</strong></td><td>Brazil (BR)</td><td>São Paulo, Rio de Janeiro</td></tr><tr><td><strong>Africa</strong></td><td>South Africa (ZA)</td><td>Johannesburg</td></tr></tbody></table>

> **Tip: To check support for more cities or countries, please contact customer service for the latest information.**

**Protocol Support**

Supports mainstream proxy protocols:

* HTTP
* SOCKS5


---

# 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/static-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.