# Octo Browser

Octo Browser is similar in capability to Dolphin and AdsPower — per-profile proxies, fingerprint sync, bulk import.

## Per-profile setup

1. **New profile** → **Proxy → Add new**.
2. Pick **HTTP** or **SOCKS5** as type.
3. Fill in:

### Residential / Mobile (gateway)

| Field    | Value                                                            |
| -------- | ---------------------------------------------------------------- |
| Host     | `gate.helodata.io`                                               |
| Port     | `7777`                                                           |
| Login    | `helo_s1a2b3c4d5e-type-res-region-us-session-prof01-sesstime-30` |
| Password | sub-user password                                                |

### ISP

| Field    | Value              |
| -------- | ------------------ |
| Host     | `198.51.100.42`    |
| Port     | `8000`             |
| Login    | `helo_s1a2b3c4d5e` |
| Password | sub-user password  |

4. **Verify** — Octo probes the proxy and shows IP, country, ASN.
5. Octo offers **Use proxy timezone and locale**; enable it.

\[screenshot: Octo Browser proxy form]

## Bulk import

**Proxies → Import file**. Accepts:

* `ip:port:user:pass` (one per line)
* CSV with header `host,port,login,password`

For ISP IPs, the helodata-default plain text export is a drop-in.

## API

Octo exposes a local HTTP API for scripted profile management. The `proxy` object format mirrors the dashboard:

```json
{
  "name": "isp-us-042",
  "proxy": {
    "type": "http",
    "host": "198.51.100.42",
    "port": 8000,
    "login": "helo_s1a2b3c4d5e",
    "password": "PASSWORD"
  }
}
```

## Verify

Hit `https://browserleaks.com/ip` and `https://browserleaks.com/webrtc` in the launched browser.

## Common pitfalls

* **Octo "smart connection" mode** retries on a different IP if a request fails — for sticky sessions, disable smart retry per profile.
* **Saved proxies without check** — Octo doesn't auto-revalidate on profile launch. After a password rotation, re-check the proxy explicitly.


---

# 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/integrations/antidetect-browsers/octo.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.