# Mobile proxies

Mobile proxies route your requests through real 3G/4G/5G devices on carrier networks. Target sites see them as ordinary phones on cellular data — the highest-trust signal on the public internet.

## At a glance

|                    |                                                                             |
| ------------------ | --------------------------------------------------------------------------- |
| **Type code**      | `mob`                                                                       |
| **Delivery**       | Gateway, username-encoded                                                   |
| **Endpoint**       | `gate.helodata.io:7777`                                                     |
| **Billing**        | Pay per GB                                                                  |
| **Pool size**      | 10M+ mobile IPs                                                             |
| **Geo targeting**  | Country, ASN (carrier) — most countries do not expose state/city for mobile |
| **Session length** | Rotating (per connection) or sticky (up to 60 min)                          |
| **Protocols**      | HTTP, HTTPS, SOCKS5                                                         |
| **Authentication** | User+password or IP whitelist                                               |
| **KYC required**   | Yes                                                                         |

## When to use mobile

* Sites that score mobile-vs-desktop or carrier IP as a strong trust signal
* Social platforms (DM flows, account integrity checks)
* Apps and APIs that gate features behind carrier networks
* Anti-bot bypass when residential is still being detected

Mobile is the **slowest** and **most expensive** of the helodata products. Use it where residential has already failed — not as a default.

## Username grammar

```
helo_{username}-type-mob-region-{region}[-asn-{asn}][-session-{session_id}-sesstime-{ttl}]
```

`state` and `city` are accepted but, for most countries, the resulting pool is too small to be useful. Carrier targeting via `asn` is the primary geo refinement on mobile.

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

## Five-second example

```bash
curl -x http://helo_s1a2b3c4d5e-type-mob-region-jp-asn-2516:PASSWORD@gate.helodata.io:7777 \
     https://ipv4.icanhazip.com
```

(That username pins KDDI in Japan.)

## On this page

* [Quick start](/products/overview-1/quick-start.md) — first request in five minutes
* [Authentication](/products/overview-1/authentication.md) — password vs IP whitelist
* [Endpoints & ports](/products/overview-1/endpoints-and-ports.md) — host, port, TLS
* [Locations & carriers](/products/overview-1/locations.md) — country coverage and major carriers
* [Protocols](/products/overview-1/protocols.md) — HTTP / HTTPS / SOCKS5
* [Sessions & rotation](/products/overview-1/sessions-and-rotation.md) — sticky up to 60 minutes
* [ASN targeting](/products/overview-1/asn-targeting.md) — the most important mobile filter
* [Error definitions](/products/overview-1/error-definitions.md) — what each status code means
* [Statistics](/products/overview-1/statistics.md) — dashboards and traffic API


---

# Agent Instructions: 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:

```
GET https://docs.helodata.com/products/overview-1.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.