## TL;DR

Their adaptive mode (mode=auto) escalates to rendering and residential proxies only when the simple fetch fails - and you are billed only for the configuration that actually succeeds. Stop pre-enabling js_render and premium_proxy on every ZenRows request.

## Fix

1. Their adaptive mode (mode=auto) escalates to rendering and residential proxies only when the simple fetch fails - and you are billed only for the configuration that actually succeeds.
   Expected: You get the expected result; the problem is gone.

## When to use

- You are dealing with this situation.
- The symptom matches: ZenRows mode=auto bills only for what succeeds - stop pre-enabling js_render and premium_proxy everywhere.

## When NOT to use

- Unrelated issues with a different cause.
- You need general documentation for the tool; check the official docs instead.

## Compatibility

Reported per the linked source.

## Variant phrasings

### ZenRows mode=auto bills only for what succeeds - stop pre-enabling js_render and premium_proxy everywhere

## Why it happens

ZenRows' own agent skill (zenrows/cli SKILL.md): prefer the cheapest reliable primitive and start with Adaptive Stealth Mode (mode=auto) - ZenRows escalates to JS rendering and premium proxies only when needed, and you are billed only for the configuration that succeeds. Their rule: escalate only with evidence - if a fetch fails, read the trace (zenrows trace explain [run-id]) before adding --js-render or --premium-proxy. Manually pre-enabling js_render (5 credits) and premium_proxy (10 credits) on every request burns both on pages the adaptive mode would have fetched for 1 credit.

## Edge cases

- If your error message differs even slightly, this is probably a different issue; search the exact text.
- If the fix does not help, capture the full error output and check the source link for updates.