> For the complete documentation index, see [llms.txt](https://help.thenorthcop.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.thenorthcop.com/botting-information/residential-proxies.md).

# Residential Proxies

## Residential Proxies

Residential proxies are **slower** than datacenter proxies but get banned on websites a lot less than datacenter proxies. Residential proxies are just like they sound, they use **home ips** to look like they are coming from **legitimate places** around the world.

Residential proxies are bought in **Gigabytes of data**. Think about it like a **phone plan**, you have a certain amount of data you can use and once you reach that data you **can't use your internet anymore**. **Residential proxies** are priced by the **GB** but you can make **unlimited** amounts of proxies.

**Proxy Data**. Proxy data is only used when you start **requesting website information**. So every time you make a task and start it / stop it, it will use a **small amount of data**. It is recommended to purchase about **2GB** of data monthly for your botting needs. This will cover a few releases. 

## **Where are residential proxies used most?** 

* Residential proxies are great on footsites to avoid antibot bans, as well as Yeezy Supply and adidas. <br>
* Residential proxies basically work everywhere and are good everywhere, the only time they lack is when you’re running for restocks because they will constantly eat up your data. That's where you may want to run datacenter proxies.

## Proxy Recommendations

* Chi Proxies
* Leaf Proxies
* Fatal Proxies
* Zenu Proxies
* Space Residential Proxies
* AYCD Residential Proxies


---

# 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://help.thenorthcop.com/botting-information/residential-proxies.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.