---
name: cliproxy-traffic-proxy
description: Cliproxy traffic proxy integration for CLI workflows. Build and debug authenticated proxy commands for both HTTP (`curl -x`) and SOCKS5 (`curl --socks5`) using dynamic account parameters (`region`, `st`, `sid`, `t`). Use when users need to switch exit country/state, control sticky vs rotating IP behavior, validate proxy formatting, or troubleshoot Cliproxy connection/authentication issues.
---

# Cliproxy Traffic Proxy

## Overview
Generate ready-to-run Cliproxy commands for HTTP and SOCKS5 clients, with correct account parameter formatting and session behavior.
Prefer explicit, copy-paste commands and keep explanations short and operational.

## Core Inputs To Collect

- Relay host and port (example: `sg.arxlabs.io:3010`)
- Base username (for account identity)
- Password (for authentication only)
- `region` (ISO 3166-1 alpha-2 code, uppercase)
- Optional `st` (state/province)
- Optional `sid` (session ID)
- Optional `t` (IP duration in minutes, used in sticky mode)
- Proxy mode: `http` or `socks5`
- Target URL for verification (example: `mayips.com`)

If the user does not provide a relay host, prefer the provider relay nearest to the exit region. Current documented relays are `us.cliproxy.io` and `sg.cliproxy.io`, but always prioritize the endpoint provided by the user/account panel.

## Account Grammar

Build account strings using hyphen-separated key-value tokens.

All parameters:

`<username>-region-<CC>-st-<STATE>-sid-<SESSION_ID>-t-<MINUTES>`

Required:

- `<username>`
- `region-<CC>`

Optional:

- `st-<STATE>`
- `sid-<SESSION_ID>`
- `t-<MINUTES>`

### Sticky Mode Format

Use sticky mode when the user wants a stable IP for a session window:

`<username>-region-<CC>-st-<STATE>-sid-<SESSION_ID>-t-<MINUTES>`

Behavior:

- Changing `sid` creates a new session and usually a new exit IP.
- Keeping the same `sid` keeps session affinity.
- `t` controls sticky duration; after expiry, IP can rotate automatically.

### Rotating Mode Format

Use rotating mode when the user wants frequent IP changes:

`<username>-region-<CC>-st-<STATE>`

Behavior:

- Without `sid` stickiness, requests generally rotate across available IPs.

## Command Templates

### HTTP Proxy (`curl -x`)

```bash
curl -x <host>:<port> \
  -U "<account>:<password>" \
  <target_url>
```

### SOCKS5 Proxy (`curl --socks5`)

```bash
curl --socks5 <host>:<port> \
  -U "<account>:<password>" \
  <target_url>
```

## Canonical Examples

### HTTP, Japan, Sticky Session

```bash
curl -x sg.arxlabs.io:3010 \
  -U "p6nq1109601-region-JP-sid-uU2ZHxYn-t-5:w8dadvyn" \
  mayips.com
```

### SOCKS5, Japan, Sticky Session

```bash
curl --socks5 sg.arxlabs.io:3010 \
  -U "p6nq1109601-region-JP-sid-uU2ZHxYn-t-5:w8dadvyn" \
  mayips.com
```

### SOCKS5, Vietnam, Sticky Session

```bash
curl --socks5 sg.arxlabs.io:3010 \
  -U "p6nq1109601-region-VN-sid-vHqJQfpt-t-5:w8dadvyn" \
  mayips.com
```

## Generation Workflow

1. Confirm proxy mode (`http` or `socks5`).
2. Normalize `region` to uppercase two-letter code.
3. Build account string in the requested mode:
   - Sticky: include `sid` and optionally `t`.
   - Rotating: omit `sid` and `t`.
4. Render one copy-paste command.
5. If requested, render multiple variants (different `region`, `sid`, or mode).
6. Provide one verification target (`mayips.com` or user-provided endpoint).

## Validation Checklist

- Use `-x` only for HTTP proxy mode.
- Use `--socks5` for SOCKS5 mode.
- Keep username tokens separated by `-` exactly.
- Ensure password is after `:` inside `-U "<account>:<password>"`.
- Ensure `region` uses ISO two-letter country code (see `references/iso-country-examples.md`).
- Keep credentials unmodified; do not URL-encode unless user asks.

## Troubleshooting

- Authentication failure: verify password and full account string (including token order).
- Wrong exit country: verify `region-<CC>` code and relay proximity.
- IP not rotating: rotate `sid` or switch to rotating format.
- High latency/timeouts: switch relay (`us` vs `sg`) closer to target region.

## Output Style

- Return final command(s) first.
- Keep explanations concise and tied to `region`, `sid`, and mode behavior.
- When user provides real credentials, avoid echoing them repeatedly; show once unless asked.