Targeting

Targeting narrows the set of exits eligible for a request. Start with the broadest constraint that satisfies the use case, then add detail only when the result must be more specific.

Token grammar

Target	Token	Example
Country	`country-{iso2}`	`country-us`
Region	`region-{slug}`	`region-texas`
City	`city-{slug}`	`city-houston`
ASN	`asn-{number}`	`asn-7018`
ISP	`isp-{slug}`	`isp-provider-name`

Use lowercase values and hyphens for spaces. Country values use a two-letter ISO code. Available regions, cities, ASNs, and ISPs depend on the package and current provider catalog.

package-elite-country-us-region-texas-city-houston-asn-7018

Selection strategy

Retrieve the package or order used for the connection.
Read available location and network options for that package through the API.
Choose the minimum set of constraints required by the product promise.
Normalize human labels to the exact slug or identifier returned by the catalog.
Cache catalog results and refresh on a package change or cache miss.

Availability matrix

Requirement	Suggested targeting	Availability impact
Any exit	No location token or `country-any` when supported	Lowest
Country compliance	Country	Low
Localized content	Country + region or city	Medium
Network-specific validation	Country + ASN or ISP	Medium to high
Exact local network	Country + region + city + ASN/ISP	Highest

Combine targeting with a session

Place sid and ttl after targeting tokens:

package-elite-country-us-city-houston-sid-cart-42-ttl-1800

Changing the targeting while reusing the same session ID creates a different routing request. Keep both stable when continuity matters.

cURL

curl --proxy http://package-elite-country-us:[email protected]:8000 https://api.ipify.org?format=json

Keep credentials server-side.Never embed a proxy password in frontend code or a public repository.

For API-driven catalog discovery, see catalog and proxy generation.