> 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/get-started/product-introduction.md).

# Product Introduction

## 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 provides you with professional global residential proxy services, with extensive IP resource coverage. We centrally schedule and maintain all lines through the platform, ensuring smooth and stable network connections even in high-concurrency scenarios.

***

**Product Types**

JollyProxy offers diversified residential proxy solutions to meet the needs of different business scenarios:

* **Residential Proxy**: Highly anonymous and flexible, suitable for high-frequency, dynamically changing business scenarios.
* **Static Residential Proxy**: Long-lasting and stable, suitable for businesses that require maintaining a fixed identity over the long term.
* **Unlimited Residential Proxy**: Massive concurrency, meeting the needs of high-volume, high-speed scraping.

***

**IP Scale and Country Distribution**

* **Resource Scale**: Tens of millions of IPs in reserve
* **Geographic Coverage**: 200+ countries and regions
* **Precise Targeting**: Supports country-level and city-level targeting

**Core Regional Resources:**

<table><thead><tr><th width="265.4000244140625">Continent</th><th>Covered Countries and 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>Oceania</strong></td><td>Australia, New Zealand</td></tr><tr><td><strong>Africa</strong></td><td>South Africa, Nigeria, Egypt, Kenya, Morocco, etc.</td></tr></tbody></table>

> *The above are partial coverage examples, not a complete list. The actual supported scope shall be subject to the final offering of the platform.*

***

**SLA (Service Availability Commitment)**

JollyProxy solemnly commits to providing you with high-availability service assurance:

{% hint style="success" %}

* **Up to 99.8% connection availability**
* **24/7 automatic system scheduling and monitoring**
* **Enterprise-grade support: dedicated line resources and priority response**
  {% endhint %}

***

**Disclaimer**

All JollyProxy residential IP resources are obtained through legitimate and lawful channels. When using proxy services to access third-party platforms or services, users must comply with local laws and regulations as well as the terms of service of the target platforms.


---

# 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/get-started/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.
