> For the complete documentation index, see [llms.txt](https://docs.helodata.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.helodata.com/products/overview.md).

# Residential proxies

Residential proxies route your requests through real consumer devices on ISP networks worldwide. Target sites see them as ordinary household traffic, making them the most resilient choice against anti-bot defenses.

## At a glance

|                    |                                                    |
| ------------------ | -------------------------------------------------- |
| **Type code**      | `res`                                              |
| **Delivery**       | Gateway, username-encoded                          |
| **Endpoint**       | `gate.helodata.io:7777`                            |
| **Billing**        | Pay per GB                                         |
| **Pool size**      | 100M+ IPs                                          |
| **Geo targeting**  | Country, state, city, ASN                          |
| **Session length** | Rotating (per connection) or sticky (up to 30 min) |
| **Protocols**      | HTTP, HTTPS, SOCKS5                                |
| **Authentication** | User+password or IP whitelist                      |

## When to use residential

* Sites with strong anti-bot defenses (e-commerce, ticketing, social platforms)
* Geo-restricted content that requires a real consumer IP in a specific country
* Ad verification and SERP tracking that must blend with real user traffic
* LLM data pipelines that need fresh, unblocked web pages

If your target is unprotected, [Datacenter proxies](/products/overview-3.md) (coming soon) are cheaper. If you need the same IP for hours or days, [ISP proxies](/products/overview-2.md) are a better fit.

## Username grammar

```
helo_{username}-type-res-region-{region}[-state-{state}][-city-{city}][-asn-{asn}][-session-{session_id}-sesstime-{ttl}]
```

Full reference: [Username format](/getting-started/username-format.md).

## Five-second example

```bash
curl -x http://helo_s1a2b3c4d5e-type-res-region-us:PASSWORD@gate.helodata.io:7777 \
     https://ipv4.icanhazip.com
```

## On this page

* [Quick start](/products/overview/quick-start.md) — first request in five minutes
* [Authentication](/products/overview/authentication.md) — password vs IP whitelist
* [Endpoints & ports](/products/overview/endpoints-and-ports.md) — host, port, TLS
* [Locations](/products/overview/locations.md) — countries, states, cities
* [Protocols](/products/overview/protocols.md) — HTTP / HTTPS / SOCKS5
* [Sessions & rotation](/products/overview/sessions-and-rotation.md) — sticky vs rotating
* [ASN targeting](/products/overview/asn-targeting.md) — pin a specific ISP
* [Restricted targets](/products/overview/restricted-targets.md) — sites we don't route to
* [Error definitions](/products/overview/error-definitions.md) — what each status code means
* [Statistics](/products/overview/statistics.md) — dashboards and the traffic API


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.helodata.com/products/overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.