proxy-config-skill

Configure residential proxies by adding a provider with a specific url_template, storing credentials, and validating the setup via a health test. You can then execute geo-targeted HTTP requests with country routing and session control.

Manage sticky sessions during scraping by using proxy request operations that support session type configuration. This maintains IP continuity across multiple requests while preserving the anonymity and failover benefits of residential proxies.

Set up routing rules by configuring domain-to-provider mappings during provider onboarding. This directs HTTP traffic to specific proxy vendors based on the target URL, ensuring requests use the correct provider-specific url_template.

Yes, you can test residential proxy provider connectivity by executing a test operation against httpbin. This validates the provider health, credentials, and url_template configuration before you attempt live geo-targeted HTTP requests.

Proxy failover and retries work by executing controlled proxy request operations that automatically handle connection failures. If a residential proxy provider fails, the system attempts retries to ensure scraping stability and continuous request execution.

Yes, the proxy configuration approach supports different URL-encoding formats via provider-specific url_template JSON strings. This allows you to correctly format credentials, country routing, and session parameters across various proxy vendors.