> ## Documentation Index
> Fetch the complete documentation index at: https://www.illusory.io/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> Premium residential proxies: real residential IPs across 195+ countries, billed by the gigabyte.

Illusory Residential Proxies route your traffic through **real residential IP addresses** sourced from a global pool spanning **195+ countries**. Unlike a dedicated mobile proxy (one device, one IP that you rent by time), residential proxies are a **shared pool**: you connect to a single endpoint, target the location you want, and pay only for the bandwidth you use.

<Note>
  Residential Proxies are currently in **private beta**. Reach out to get your credentials and an allotment of GB to test.
</Note>

## How it works

<CardGroup cols={2}>
  <Card title="One endpoint" icon="plug">
    Connect every request to a single host and port, with no per-device setup.
  </Card>

  <Card title="Target anywhere" icon="map-pin">
    Choose a country, state, city, or network right in your proxy username.
  </Card>

  <Card title="Rotating or sticky" icon="repeat">
    Get a fresh IP per request, or keep the same IP for a session.
  </Card>

  <Card title="Pay per GB" icon="gauge">
    Usage is metered by the gigabyte. No device rental, no expiry.
  </Card>
</CardGroup>

## Mobile vs. Residential

|           | Mobile (dedicated)        | Residential (pool)                       |
| --------- | ------------------------- | ---------------------------------------- |
| Exit IP   | One dedicated device      | Rotating pool, 195+ countries            |
| Billing   | Rented by time            | Metered by bandwidth (GB)                |
| Connect   | Per-device details        | One shared endpoint + your credentials   |
| Targeting | Fixed to the device       | Country / state / city / ASN per request |
| Best for  | A stable, single identity | Scale, geo-coverage, and rotation        |

## Protocols

Residential proxies support both **HTTP/HTTPS** and **SOCKS5** on the same port. The protocol is auto-detected, so any tool that speaks either will work (browsers, `curl`, scrapers, and most automation frameworks).

## Next steps

<CardGroup cols={2}>
  <Card title="Get Started" icon="rocket" href="/docs/residential/get-started">
    Connect and make your first request
  </Card>

  <Card title="Targeting" icon="crosshair" href="/docs/residential/targeting">
    Select a country, city, or network
  </Card>

  <Card title="Sessions" icon="repeat" href="/docs/residential/sessions">
    Rotating vs. sticky IPs
  </Card>

  <Card title="Code Examples" icon="code" href="/docs/residential/code-examples">
    curl, browsers, Python, and Node
  </Card>

  <Card title="Ethical Sourcing" icon="shield-check" href="/docs/residential/sourcing">
    How our residential network is sourced
  </Card>
</CardGroup>