- Prioritizes successful extraction above all else
- Starts with the cheapest viable configuration for each request
- Automatically escalates to more powerful features only when necessary
- Bills only for the configuration that succeeds - failed attempts incur no charges
- Adapts automatically as website behavior changes over time
- Reduces maintenance overhead by eliminating the need to monitor and update scraping configurations
How Adaptive Stealth Mode Works
Adaptive Stealth Mode executes each request using a progressive strategy:- Target Analysis: Evaluates the target URL using known patterns and runtime signals to predict the best starting configuration.
- Lowest-Cost Attempt: Executes the request with the least expensive configuration likely to succeed based on the analysis.
- Automatic Escalation: Retries with stronger features if the initial attempt fails, progressively adding capabilities as needed.
- Success-Only Billing: You are billed only for the configuration that completes successfully. Failed attempts incur no charges.
Basic Usage
API Usage
Addmode=auto to your request:
When to Use Adaptive Stealth Mode
Recommended when:- Scraping multiple websites with different behaviors
- Website requirements are unknown or change frequently
- Reliability matters more than manual optimization
- You’re running production workloads at scale
- You want to minimize maintenance overhead from website changes
- Single, stable domains where you know the optimal setup
- Scenarios requiring predictable, consistent feature usage
- Cost-sensitive applications with well-understood requirements
Managed Parameters
Adaptive Stealth Mode automatically manages these API parameters:| Parameter | Purpose | When Applied |
|---|---|---|
js_render | JavaScript rendering for dynamic content | Sites using React, Vue, Angular, or AJAX loading |
premium_proxy | Residential IP addresses | Sites blocking datacenter IPs or requiring geo-location |
Adaptive Stealth Mode vs Manual Configuration
| Aspect | Adaptive Stealth Mode (mode=auto) | Manual Parameters |
|---|---|---|
| Setup time | Single parameter | Requires tuning |
| Success optimization | Automatic | User-managed |
| Cost optimization | Automatic, per request | Fixed by chosen config |
| Adaptation to site changes | Automatic | Requires updates |
| Failed attempts billed | No | No |
| Best for | Production, multi-domain workloads | Stable, well-known targets |
Troubleshooting
Common Issues
Adaptive Stealth Mode not working as expected- Verify the
mode=autoparameter is correctly set - Check that other conflicting parameters aren’t overriding Adaptive Stealth Mode
- Review the response headers for cost and feature information
- Monitor the
X-Request-Costheader to understand feature usage - Consider manual configuration if cost patterns are predictable
- Use the Builder UI to preview costs before running requests
- Adaptive Stealth Mode adapts to website changes, which may affect feature selection
- Use
session_idto maintain consistency across related requests - Switch to manual configuration for completely predictable behavior
Pricing
Adaptive Stealth Mode uses transparent, usage-based pricing with these cost multipliers:| Configuration | Cost Multiplier | When Used |
|---|---|---|
| Basic request | 1x | Simple static websites |
| JavaScript rendering | 5x | Dynamic content requiring browser processing |
| Premium Proxies | 10x | Sites blocking datacenter IPs |
| Combined features | 25x | Highly protected sites requiring both JS and proxies |
You are billed only once, for the configuration that succeeds. If Adaptive Stealth Mode requires multiple internal attempts before success, ZenRows bills only for the successful configuration.
Frequently Asked Questions (FAQ)
Will Adaptive Stealth Mode increase my costs?
Will Adaptive Stealth Mode increase my costs?
No. Adaptive Stealth Mode minimizes costs by avoiding unnecessary features and charging only for successful requests. It often reduces costs compared to manually over-configuring parameters.
How much visibility do I have into Adaptive Stealth Mode decisions?
How much visibility do I have into Adaptive Stealth Mode decisions?
You retain full visibility through response headers (including request cost) and the Analytics dashboard, without needing to manage configuration decisions manually.
What happens if a website changes its anti-bot measures?
What happens if a website changes its anti-bot measures?
Adaptive Stealth Mode adapts automatically without requiring parameter updates on your end. The system learns from new blocking patterns and adjusts accordingly.
Can I use Adaptive Stealth Mode with other parameters?
Can I use Adaptive Stealth Mode with other parameters?
Yes, but with limitations. When you use
mode=auto, only the managed parameters (js_render, and premium_proxy) are disabled to prevent conflicts. You can still use other API parameters like css_extractor, session_id, or custom request settings alongside Adaptive Stealth Mode.