Targeting & geo

Before a strategy picks a node, bytetourist filters the fleet down to nodes that satisfy your constraints. Set them via the username encoding or X-Proxy-* headers (see Authentication).

Region (hierarchical)

region matches a dot-delimited prefix. eu matches eu and eu.west; eu.west does not match eu. This lets you go as broad or as narrow as you like:

# anywhere in the EU
-U "YOUR_API_KEY-region-eu:"
# specifically EU-West
-U "YOUR_API_KEY-region-eu.west:"

Country

cc matches the node’s country code exactly:

-U "YOUR_API_KEY-cc-de:"   # Germany only

IP type

iptype selects the network class of the egress IP:

Value	Use it for
`datacenter`	Fast, cheap, fine for permissive targets.
`residential`	Real ISP IPs — for targets that block datacenter ranges.
`mobile`	Carrier-grade NAT mobile IPs — the hardest to block.

-U "YOUR_API_KEY-iptype-residential:"

Protocol

protocol requires a node that advertises a given protocol (e.g. http, socks5). Most traffic doesn’t need this.

Combining constraints

Constraints stack — the node must satisfy all of them:

-U "YOUR_API_KEY-region-eu.west-cc-de-iptype-residential:"

When nothing matches

By default (strict=false), if no node matches and a primary pick is unhealthy, bytetourist relaxes to the best available node so your request still goes out. Set strict-true to fail fast with an error instead — see Reliability & retries.