Developer Quickstart

How the kairoxo Network Works

Every request you make traverses a three-tier topology: an authentication edge, a routing fabric, and a distributed exit fleet. The edge authenticates your credentials in under 8 ms, the routing fabric selects the optimal exit node based on your targeting parameters, and the exit fleet delivers the request from a legitimate residential, ISP, mobile, or datacenter IP.

The platform is built around three guarantees: a globally distributed pool of 100M+ unique IPs, a 99.99% SLA backed by automatic failover, and a sub-200 ms median TTFB to the most common collection targets. All endpoints terminate TLS 1.3 and support HTTP, HTTPS, and SOCKS5 on the same gateway.

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 (country allow-list, per-domain throttles, concurrency caps). Rotate the password at any time from Settings → Credentials; old tokens stop working within 30 seconds without dropping in-flight TCP sessions.

Rotating Residential Pool

Residential proxies route requests through a peer-to-peer pool of consenting devices on real ISP connections. Because the source IP belongs to a household subscriber, residential is the highest-trust tier for targets that scrutinize ASN, browser fingerprints, or behavioral patterns — search engines, e-commerce sites, sneaker drops, ad-verification platforms.

• check_circle 100M+ unique IPs across 195 countries
• check_circle City- and ASN-level targeting included
• check_circle Sticky sessions up to 30 minutes
• check_circle Unlimited concurrent connections
• check_circle Automatic rotation on every request (default)
• check_circle TLS 1.3 + HTTP/2 on the edge

import requests

proxies = {
  "http":  "http://USERNAME-country-us:PASSWORD@gateway.kairoxo.io:9000",
  "https": "http://USERNAME-country-us:PASSWORD@gateway.kairoxo.io:9000",
}
r = requests.get("https://api.ipify.org?format=json", proxies=proxies, timeout=15)
print(r.json())

Static ISP (Datacenter-Hosted Residential)

ISP proxies are residential IP addresses leased directly from Tier-1 carriers and hosted in our datacenter racks. You get the legitimacy of a residential ASN with the throughput and stability of a dedicated datacenter line — the right choice when a workload needs the same IP for hours and cannot tolerate rotation.

Unmetered High-Throughput Endpoint

The unlimited endpoint is a fixed-cost gateway optimised for predictable, large-volume workloads such as RPA, market intelligence crawls, and continuous ML training data collection. You pay a flat daily rate per port and consume as much bandwidth as the port can sustain — no per-GB metering, no overage charges.

import fetch from "node-fetch";
import { HttpsProxyAgent } from "https-proxy-agent";

const agent = new HttpsProxyAgent(
  "http://unlimitedKey:PASSWORD@unlimited.kairoxo.io:10000"
);

const r = await fetch("https://example.com", { agent });
console.log(r.status);

Choosing the Right Pool

Each pool exposes the same authentication surface but differs in concurrency, session persistence, and egress IP behavior. Match the pool to the trust profile of your target endpoint.

Granular Geo Modifiers

Append targeting segments to the username to constrain exit nodes. Segments are evaluated left-to-right and the most specific match wins. Unknown or empty targets fall back to the broader scope.

Management Endpoints

All management endpoints live under https://api.kairoxo.io, authenticated with a bearer token. Responses are JSON with cursor-based pagination on collections.

Response Codes & Retry Policy

Proxy errors are surfaced as standard HTTP status codes on the upstream response. Always implement exponential backoff with jitter; never retry tighter than 250 ms on a 429 or you will compound the rate limit. Persistent 5xx responses should trigger a fresh sticky session before the next retry.