Choose routing as part of the request
RunHarvester provides direct, auto, http, browser, residential, and residential_browser route modes. Auto handles route selection; explicit modes enable you to define specific requirements. Availability and commercial limits depend on account and deployment details.
Residential routing concerns egress. Browser execution concerns how the page runs. A target may need either or both; selecting a residential route alone does not execute JavaScript.
Treat location as an input to validate
Refer to the current geographic routing contract for available options and inventory. Targets can also localize through language, cookies, account settings, or their own location detection. Review the returned content instead of assuming a requested region results in a specific currency or language.
For a regional test, hold the URL, language, and session assumptions steady while changing the routing preference. Record timestamps and returned routing metadata so differences can be investigated.
Account for failures and effective cost
A route does not guarantee access or bypass a target's rules. Keep credentials and target cookies private, use appropriate access permissions, and inspect public errors when acquisition fails.
Estimate cost from actual effective routes and billing metadata. Avoid static country counts, success-rate promises, or fixed prices that are not supported by current service data.