Context-Aware Routing

Context-Aware Routing

Context-Aware Routing automatically selects the best IP type for your target URL — residential, datacenter, or dedicated — without manual configuration.

IP Types

Type	Best For	Speed	Cost
Residential	E-commerce, social media, anti-bot sites	Medium	$$$
Datacenter	APIs, non-protected sites, bulk requests	Fast	$
Dedicated	Account management, long sessions	Medium	$$

How Routing Works

When you request a proxy, HydraSkill analyzes the target:

# HydraSkill automatically picks residential for Amazon
proxy = client.get_proxy(target="amazon.com")
print(proxy.type)  # "residential"

# And datacenter for a public API
proxy = client.get_proxy(target="api.github.com")
print(proxy.type)  # "datacenter"

The routing engine considers:

1. Target domain reputation — known anti-bot systems get residential IPs
2. Historical block rates — domains that frequently block get premium IPs
3. Request pattern — high-frequency requests get datacenter, session-based get residential
4. Geographic requirements — some regions have better residential coverage

Override Routing

You can always specify the IP type manually:

# Force residential even for an API
proxy = client.get_proxy(
    target="api.example.com",
    ip_type="residential"
)

# Force datacenter for speed
proxy = client.get_proxy(
    target="amazon.com",
    ip_type="datacenter"  # cheaper but higher block risk
)

Routing Rules (Enterprise)

Enterprise plans can define custom routing rules:

.hydraskill.yml

routing_rules:
  - match: "*.amazon.*"
    ip_type: residential
    country: auto  # match target locale
  - match: "api.*"
    ip_type: datacenter
  - match: "*.google.com"
    ip_type: residential
    rotate_every: 10  # new IP every 10 requests

Cost Optimization

Context-Aware Routing saves money by default — it only uses expensive residential IPs when needed. For targets that don’t have anti-bot protection, it routes through cheaper datacenter IPs automatically.

Typical savings: 30-50% vs always using residential.