Routing

Every request passes through ProxySave's routing engine, which evaluates all available providers against your constraints:

1. Collect candidates. All configured providers (your BYOK keys + managed pool) are considered.
2. Apply constraints. Providers exceeding your cost ceiling or latency threshold are filtered out.
3. Rank by cost. Remaining providers are sorted by effective cost per GB, cheapest first.
4. Route. The request is sent to the cheapest qualifying provider.

The result: you always get the lowest price that meets your requirements, without manually comparing providers or switching between accounts.

Not all proxy traffic is the same. Scraping product pages on Amazon has different provider performance characteristics than monitoring airline prices. ProxySave learns these differences.

By tagging requests with a workload label, ProxySave tracks per-workload metrics for each provider:

• Success rate for that specific target
• Typical response time
• Block rate (how often the target rejects the provider)

Over time, routing decisions become more accurate for your specific use case. A provider that's cheap but frequently blocked on your target will be automatically deprioritized, even if it meets your stated constraints.

When a provider fails (network error, timeout, blocked response), ProxySave automatically retries through the next cheapest qualifying provider. This happens transparently — your application receives a single response.

The retry chain works like this:

1. Request sent to cheapest qualifying provider
2. If it fails, retry through next cheapest
3. Continue until a provider succeeds or all candidates are exhausted

This is why ProxySave achieves near-100% effective success rates — even when individual providers have spotty reliability, the automatic fallback chain absorbs the failures.

ProxySave periodically samples alternative providers to detect when pricing or performance changes. If a previously expensive provider drops their rates, ProxySave detects it and begins routing your traffic accordingly.

This exploration always stays within your constraints — ProxySave never routes through a provider that exceeds your cost or latency limits, even for sampling purposes.