Proxies.ai

Using the Proxy

Configure your HTTP client to route through Hyperproxy.

Any HTTP/S client that supports proxy configuration works with Hyperproxy. This page shows the general pattern; see the sub-sections for language-specific examples.

Proxy URL Format

Your proxy URL is shown in the dashboard. It takes the form:

bash
Sign in with active access to insert your proxy host. This command remains a template.
https://<proxy-host>:443

The examples use <proxy-host> for the complete hostname. Copy the exact proxy URL from your dashboard; do not construct or guess the host.

The proxy requires authentication. Use the username and password you generated on the Credentials tab. Most HTTP libraries accept proxy credentials either in the URL or as a separate option.

Proxy Credential in the URL

bash
Sign in with active access to insert your proxy host. This command remains a template.
https://username:password@<proxy-host>:443

URL-embedded credentials are convenient for quick tests but avoid them in production since they may appear in logs or shell history. Use your client's dedicated proxy auth option instead (e.g. -U user:pass in curl, or proxiesdict with auth in Python requests).

Secret Placeholders

In auto-auth mode, send the placeholder syntax instead of the real credential:

bash
Authorization: Bearer {$MY_SECRET_NAME}

The proxy resolves MY_SECRET_NAME from its encrypted store and replaces the entire header value before forwarding. You can use placeholders in any header, not just Authorization.

Multiple placeholders in a single header value are supported:

bash
X-Custom: prefix-{$SECRET_A}:{$SECRET_B}

TLS and Proxy CA Trust

For inspected HTTPS in Auto-Auth or Firewall mode, configure your client to trust the proxy CA certificate. Auto-Auth needs TLS inspection to replace encrypted headers; Firewall uses it for HTTPS request-level rules.

Trust only the public CA certificate in intended client environments. This is server-certificate trust, not a client certificate for mutual TLS. An opaque CONNECT tunnel cannot support HTTPS header rewriting or request-level inspection. Plain HTTP requests do not require TLS inspection.

bash
Sign in with active access to insert your proxy host. This command remains a template.
# Download CA cert for your proxy
curl https://proxies.ai/api/proxies/proxy-id/ca-cert > cifp-ca.pem

# Tell curl to trust it
curl --cacert cifp-ca.pem -x "https://<proxy-host>:443" ...

# Or add to system trust store (macOS)
sudo security add-trusted-cert -d -r trustRoot -k /Library/Keychains/System.keychain cifp-ca.pem