Credentials & Targeting Parameters
KAIROXO uses standard HTTP Basic authentication over the proxy URL. Targeting modifiers are encoded as hyphenated segments inside the username, which keeps the wire protocol compatible with any HTTP, HTTPS, or SOCKS5 client without custom headers.
Credentials are scoped to a sub-account, which lets you isolate billing per project, revoke a single integration without touching the rest of your stack, and apply distinct ACLs. Rotate the password at any time from Settings > Credentials; old tokens stop working within 30 seconds without dropping in-flight TCP sessions.
| Parameter | Type | Description |
|---|---|---|
| USERNAME | string | Sub-account identifier issued in the dashboard. Scope tokens by project to isolate billing and ACLs. |
| PASSWORD | string | Rotating credential. Regenerate from Settings > Credentials; old tokens are revoked within 30 seconds. |
| country | ISO-3166 | Two-letter exit country code, for example us, de, or jp. Combine with region or city for granular targeting. |
| sid | string | Sticky session identifier. Reuse the same sid to keep the same exit IP for up to 120 minutes. |
Issue one sub-account per environment (dev, staging, prod) and one per workload. This makes billing attribution easier and contains blast radius if a token leaks.
Do not share a single credential across browser automation and backend crawling. The two workloads have different rotation needs and you lose the audit trail.